[00:09] <mwhudson> davecheney: \o/
[00:10] <davecheney> mwhudson: got local provider *almost* working yesterday
[00:10] <mwhudson> davecheney: on ppc64el?
[00:13] <davecheney> mwhudson: ya
[01:04] <hazmat> what version of juju started using jenv file
[01:05] <hazmat> sinzui, abentley there's a separate bug on manual provider trunk, that needs --uploads-tools
[01:06] <hazmat> hmm.. although it looks like it found 1.17.0 there
[01:07] <hazmat> sinzui, the traceback on that bug is the same as i reported previously in https://bugs.launchpad.net/juju-core/+bug/1280678
[01:07] <_mup_> Bug #1280678: manual provider fails to get tools (1.17.2) <manual-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1280678>
[01:08] <hazmat> the first pastebin has the cli output with --debug
[01:16] <wallyworld__> waigani: did you want to do the stand up now?
[01:18] <waigani> wallyworld__: yep 1min
[01:54] <wallyworld__> axw: it appears the reason local upgrade fails from 1.16 is because the /usr/lib/juju/tools directory is owned by root and so can't be read when running juju upgrade. do you know how we deal with 1.16->1.17 upgrades in other places where 1.16 stuff was written as root?
[01:55] <axw> umm. why does it matter? the agents run as root?
[01:56] <wallyworld__> i'm not sure, i can check
[01:56] <wallyworld__> ha, 1.16 deploy fails error: symlink /var/lib/lxc/ian-local-machine-1/config /etc/lxc/auto/ian-local-machine-1.conf
[01:58] <wallyworld__> yes, the local jujud for machine 0 does run as root. the required file is there, i'll look further to see why it can't be read
[01:58] <wallyworld__> but gotta get a unit deployed first
[01:59] <axw> hurm, that looks like something that might've changed to support trusty?
[01:59] <axw> the auto thing
[02:02] <wallyworld__> yeah, i had to manually make the auto directory
[02:02] <wallyworld__> i thought we fixed that
[02:03] <wallyworld__> sigh
[02:03] <wallyworld__> local on trusty is buggered
[02:03] <wallyworld__> "lxc-start": command get_cgroup failed
[02:11] <axw> :\
[03:59] <axw> ah, that's better. phone point was dodgy. bet the bloody ants have gotten into the wires... last time they made a home in our phone
[04:03] <wallyworld__> axw: better bugs in your phone wires than your code
[04:04] <axw> heh
[04:05] <axw> it was pretty horrific. I picked up the phone, and they were swarming around under the screen
[04:05] <wallyworld__> \o/
[04:06] <wallyworld__> axw: i've given up getting the local provider working in trusty for now - i'll ask tim about it next week and/or raise it in the group meeting. but the root cause issue was that i was using the wrong data dir and so have a fix up for that
[04:06] <axw> okey dokey
[04:06]  * axw looks
[04:09] <axw> wallyworld__: reviewed
[04:09] <wallyworld__> thanks :-)
[04:10] <axw> just writing a test for mine now... sorry, I was being lazy
[04:11] <wallyworld__> np :-)
[04:12] <wallyworld__> given the nature of the issue, i think a test is crucial
[09:28] <dimitern> rogpeppe, https://codereview.appspot.com/66540044 - a relatively easy review?
[09:29] <rogpeppe> dimitern: only 1200 lines, trivial :-)
[09:29] <rogpeppe> dimitern: actually i'm on another review currently, will look after that
[09:30] <hazmat> is thumper on vacation?
[09:30] <dimitern> hazmat, yep, this week
[09:30] <dimitern> rogpeppe, cheers :) it's not that bad really
[09:34] <rogpeppe> wallyworld__: hiya
[09:35] <rogpeppe> wallyworld__: i was just looking at https://codereview.appspot.com/66540044
[09:36] <rogpeppe> oops, wrong URL!
[09:36] <rogpeppe> https://codereview.appspot.com/65740048, of course
[10:01] <jam> fwereade: just to let you know, I'm trying to get into the hangout, but the google talk plugin crashed, and Trusty wants to do a dist-upgrade that is about a hundred megs, so I should be there *soonish* but I can't guarantee when
[10:01] <jam> rogpeppe: wallyworld__ ^^
[10:02] <fwereade> jam, no worries :)
[10:02] <wallyworld__> lol
[10:02] <rogpeppe> jam: ok
[10:06] <mgz> I'm having fun with 2fa/hangouts atm so may take some struggling to get into the meeting
[10:14] <mgz> okay, backup otps generated, lets try
[12:04] <rogpeppe> wallyworld__: here's the kind of thing i'm thinking about for the upgrade-waiter worker: http://paste.ubuntu.com/6965038/
[12:05] <wallyworld__> thanks, will look
[12:05] <rogpeppe> wallyworld__: the SimpleWorker implementation is in one of nate's in-progress branches
[12:05] <wallyworld__> ok
[12:08] <rogpeppe> natefinch: can you make that branch available, so wallyworld__ can use it? (it doesn't seem to be in https://launchpad.net/~natefinch/juju-core/030-MA-HA any more)
[12:20] <natefinch> rogpeppe: launchpad's URL schema has to be the most inscrutable thing I've ever worked with.  I don't know what it's doing most of the time.  The code should still be there, I certainly didn't do anything to it.  This link works for the website at least: https://code.launchpad.net/~natefinch/juju-core/030-MA-HA
[12:21] <rogpeppe> natefinch: oh yeah, *code*.launchpad.net
[12:21] <rogpeppe> natefinch: thanks
[12:25] <dimitern> rogpeppe, review poke?
[12:25] <rogpeppe> dimitern: thanks, i needed it :-)
[12:39] <sparkiegeek> hi guys. I'm having trouble bootstrapping a precise environment using MAAS provider on 1.17.2
[12:39] <sparkiegeek> http://paste.ubuntu.com/6965180/
[12:40] <sparkiegeek> if I manually run that wget command on the maas provider (same network/firewall etc. as bootstrap node) I get a certificate error
[12:40] <sparkiegeek> http://paste.ubuntu.com/6965187/
[12:54] <rogpeppe> this machine has become unusable
[12:54] <rogpeppe> am rebooting to see if it helps
[12:55] <natefinch> rogpeppe: time to upgrade
[12:55] <rogpeppe> natefinch: to what?
[12:55] <natefinch> rogpeppe: new laptop
[12:56] <rogpeppe> natefinch: ha ha. it was fine before
[12:56] <rogpeppe> natefinch: i'm not doing anything different
[12:56] <natefinch> rogpeppe:  just take the excuse ;)
[12:57] <rogpeppe> natefinch: i'm waiting until september...
[12:57] <natefinch> rogpeppe: what's in sept?
[12:57] <rogpeppe> three years at canonical = new laptop
[12:57] <natefinch> rogpeppe: ahh nice
[13:02] <wrtp> natefinch: so, it looks like my laptop has died
[13:03] <rogpeppe> natefinch: when i tried to reboot it, i got a kernel panic (something about a thermal_notify call)
[13:04] <rogpeppe> natefinch: and now it just says "Fan Error" when i try to switch it on
[13:04] <rogpeppe> this is unfortunate
[13:04] <rogpeppe> i'm going to let it cool down for a bit and cross my fingers
[13:04] <natefinch> rogpeppe: ouch
[13:05] <rogpeppe> it is very hot underneath
[13:06] <natefinch> rogpeppe: that sounds really bad
[13:07] <natefinch> rogpeppe: maybe it is time for a new laptop?  I think you get a payout at 3 years regardless of whether you actually purchase a laptop...
[13:08] <rogpeppe> natefinch: i've only had this for two years. i can't believe that's the expected lifetime of a laptop
[13:09] <rogpeppe> natefinch: i don't know whether to blame trusty for thrashing it, or the laptop for not coping
[13:09] <rogpeppe> anyway, hopefully in a few minutes it will have cooled down and everything will be back to normal
[13:09] <natefinch> rogpeppe: 2 years shouldn't kill any reasonable laptop
[13:10] <rogpeppe> natefinch: indeed - and it was a decent one
[13:11] <rogpeppe> anyway, i guess i can continue with dimitern's review, from this apple laptop that's been rock solid for 4.5 years :-)
[13:14] <hazmat> rogpeppe, what kind of laptop?
[13:14] <rogpeppe> hazmat: lenovo x21
[13:14] <rogpeppe> hazmat: sorry, x220
[13:15] <rogpeppe> dammit, it's cooled down a reasonable amount, and i still get "Fan Error"
[13:15] <hazmat> rogpeppe, odd.. i've got the same model.. its held up pretty well for me.. i had one logic board replace (under warranty), i've tricked it out with an extra msata and 16gb of ram. .. what's the issue?
[13:16] <hazmat> rogpeppe, hmm.. i had some thermal issues when i had the logic board replaced.. are you still under warranty?
[13:16] <rogpeppe> hazmat: no, not for some time noe
[13:16] <rogpeppe> now
[13:16] <rogpeppe> hazmat: (it's 2.5 years old)
[13:17] <hazmat> rogpeppe, bummer.. not sure you have many options.. the docking station helped me not sure why.. it only do the random shutdown on thermal when unplugged i'd recommend picking up a 2|3 year warranty your next go around.. laptop's get abused
[13:18] <rogpeppe> hazmat: everything was running very jerkily, and the fan was coming on. i decided to reboot. i saw a kernel panic when i did so. did a hard power off. now i can't even get into the bios menu.
[13:19] <rogpeppe> hazmat: seems like it might be bricked :-\
[13:19] <hazmat> rogpeppe, hmmm.. you can still get service from lenovo its just pay as you go on labor parts.. might be cheaper to investigate a new laptop and yank the hd for an external enclosure to save data
[13:19] <hazmat> rogpeppe, the xps 15 / m3800 looks pretty nice albeit a bit pricey.
[13:19] <rogpeppe> hazmat: i really wanted to wait until my 3 years :-)
[13:20] <hazmat> yeah.. understood and the x220 is the last lenovo with a real (non-chicklet) keyboard
[13:20] <rogpeppe> hazmat: i do have a docking station. maybe i'll try that.
[13:20]  * rogpeppe googles for chicklet keyboards
[13:20] <hazmat> rogpeppe, if works at all with the docking station, its almost 100% a logic/motherboard replace..
[13:20] <hazmat> rogpeppe, its what standard keyboards on new laptops look like..
[13:21] <natefinch> hazmat, rogpeppe: the XPS 15 is pretty slick, btw
[13:22] <hazmat> rogpeppe, you can order just about any part from lenovo if your up for diy, although on  motherboard replace i'd go for a service  tech.
[13:45] <rogpeppe> hazmat: docking station (finally found it!) doesn't seem to make a difference, sadly
[13:47] <rogpeppe> i suppose it might actually be that the fan has gone
[14:00] <dimitern> natefinch, mgz, anyone? simple review https://codereview.appspot.com/66550044 to fix bug 1282553
[14:00] <_mup_> Bug #1282553: maas provider can't bootstrap on precise with 1.17.2 <landscape> <juju-core:In Progress by dimitern> <https://launchpad.net/bugs/1282553>
[14:01] <bac> hi jamespage, i was asked to check in with you regarding getting juju-quickstart into main rather than universe.  what's the status?
[14:07] <rogpeppe> dimitern: i was reviewing that when my machine died
[14:08] <rogpeppe> dimitern: i'm not sure about the agent config approach
[14:08] <rogpeppe> dimitern: but i need to think about it some more
[14:11] <rogpeppe> ha, actually my laptop *is* still under warranty
[14:11] <mgz> dimitern: reviewed
[14:14] <mgz> dimitern: I'm pretty sure curl has always been in the base cloud image, did you find you needed to install it?
[14:15] <dimitern> rogpeppe, it's the least intrusive approach imo
[14:15] <dimitern> thanks for the review mgz
[14:16] <dimitern> sinzui, do you know about the cross-team meting? when does it start?
[14:16] <dimitern> mgz, looking in #juju on canonical it seemed safer to add it
[14:16] <sinzui> dimitern, in 15 mintutes
[14:17] <dimitern> sinzui, ok, so because fwereade is not feeling well, i'd like to go in his place as he asked, can I have a g+ link in privmsg?
[14:21] <mattyw> rogpeppe, got time for another quick question?
[14:22] <sinzui> dimitern, https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.bbjh6akgumv8n4suee7li8mrfc?authuser=1
[14:22] <dimitern> sinzui, thanks
[14:33] <sparkiegeek> dimitern: if you were basing the need to install curl on my aptitude why trick then I think that's a mistake. http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.manifest shows it's in the base image. I'm +1 on mgz's comment that you don't need to install it
[14:35] <dimitern> sparkiegeek, ok, i can remove addpackage then
[14:40] <mramm> hey, any juju core members available to join the cross team meeting?
[14:40] <mramm> https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.bbjh6akgumv8n4suee7li8mrfc
[14:40] <dimitern> mramm, i'm there :P
[14:40] <mramm> ok
[14:40] <mramm> cool
[14:52] <rogpeppe> mattyw: sure
[14:53] <rogpeppe> mattyw: sorry, didn't see your question - i'm on a different machine 'cos my laptop has died :-(
[14:54] <mattyw> rogpeppe, no problem - I've just submitted my second part of the juju id stuff for review - there's definately more stuff to do - but I wanted to get it started - rather than finish everything and then have to redo parts...
[14:54] <mattyw> one of the things I haven't done yet is the cacheAPIInfo stuff - taking out the user stuff and doing it only on bootstrap
[14:55] <rogpeppe> mattyw: ok
[14:56] <mattyw> rogpeppe, there's an example in the current code of how I think the function should look - but I don't think I can call it directly from the bootstrap command without jumping through some hoops (I don't have an apiInfo in the bootstrap command)
[14:57] <mattyw> rogpeppe, also it breaks a few tests by not doing it - so I guess the cacheuser function will need to be called somewhere where the tests can invoke it as well
[14:57] <rogpeppe> mattyw: i'm just downloading the code so i can have a look
[14:58] <mattyw> rogpeppe, ok thanks - there's no particular hurry - but thanks :)
[14:59] <dimitern> rogpeppe, another review poke? :)
[14:59] <rogpeppe> dimitern: sorry, i've been busy trying to get my machine repair scheduled
[15:00] <mattyw> rogpeppe, you're the 3rd person I know who's had to send a laptop for repair this week
[15:00] <rogpeppe> mattyw: i wonder if it's anything to do with trusty thrashing things
[15:01] <rogpeppe> mattyw: i know that the fan never *needed* to come on before today
[15:01] <mattyw> fans always need to come on - it's their purpose in life
[15:12] <rogpeppe> 6 working days until i get it back, darn it
[15:14]  * rogpeppe wonders what he should do now. i guess i could get an enclosure for the SSD and try to access the disk drive from my macbook, and develop on that
[15:31] <dimitern> rogpeppe, try sticking it in the fridge :)
[15:38] <mgz> dimitern: got a mo to help me out?
[15:39] <dimitern> mgz, sure
[15:39] <mgz> I want to test a new (old) api command I've added in state/apiserver/client/status.go
[15:40] <mgz> this isn't used in real code, but I want to exercise the function in a unit test
[15:40] <mgz> where should I add that?
[15:40] <mgz> the existing testing in that package is confusing me
[15:40] <dimitern> is it one of these things where a CodeNotImplemented is involved?
[15:40] <mgz> well, that too
[15:41] <mgz> but this particular test isn't for that behaviour, though I should *also* have a test for that
[15:41] <mgz> I just want to call the apiserver function from a sensible test to make sure it does things, on the off chance the old 1.16 code was being relied on
[15:44] <dimitern> if you want to test the branch where a 1.16 fallback code should be run, what I usually do is go in api/client and change the name of the called method (in st.Call(...)) to something else, like adding "1" at the end, so the server will return not implemented
[15:44] <dimitern> it's otherwise hard (if not impossible currently) to write a unit test for that
[15:45] <mgz> moo, so, second test probably not possible
[15:45] <dimitern> am I making sense?
[15:45] <mgz> I'm sure the first is though
[15:46] <mgz> it's just like I've added a new api call that's not used anywhere and want to write a test for the server side
[15:46] <mgz> dimitern: I'll put up an mp so far, may be clearer
[15:46] <dimitern> mgz, looking at the code will help me understand better
[15:52] <rogpeppe> mgz: you can use Call directly if you need to
[15:53] <dimitern> rogpeppe, that's a bit over the edge I think
[16:04] <mgz> dimitern: https://codereview.appspot.com/66590043/
[16:06] <dimitern> mgz, looking
[16:14] <dimitern> mgz, reviewed
[16:14] <mgz> merci
[16:19] <mgz> dimitern: responded to comments will have another look at finding a sane test to emulate
[16:19] <dimitern> mgz, cheers
[16:30] <natefinch> dimitern, mgz: review please?  It's pretty small: https://codereview.appspot.com/66230043/
[16:30] <dimitern> natefinch, looking
[16:40] <wrtp> dimitern: i actually think that's ok - it's a public API. we're allowed to use it if others are.
[16:41]  * rogpeppe has just sent his laptop off for repair
[16:41] <natefinch> rogpeppe: boo.  That sucks.  good luck getting it back quickly
[16:42] <dimitern> natefinch, reviewed
[16:42] <dimitern> rogpeppe, what's that?
[16:45] <rogpeppe> natefinch: yeah, it's a bummer. i've just got a 2.5" enclosure to see if i can talk to the hard drive from my macbook
[16:46] <rogpeppe> natefinch: it may require me running an ubuntu VM, i guess
[16:46] <rogpeppe> can't remember what fs type i was using
[16:50] <hazmat> rogpeppe, ext4 if you have deafults
[16:50] <rogpeppe> hazmat: probably
[16:51]  * rogpeppe goes to look for an ext4 fs for macos
[16:51] <hazmat> rogpeppe, i wouldn't  bother..  you'll need a linux machine.. a vm might do depending on enclosure type (usb3) and if you can pass it through to the vm.
[16:52] <hazmat> rogpeppe, actually it does look like there are some commercial products for ext4 access from osx
[16:53] <rogpeppe> hazmat: that's actually what i'm doing right now - just upgrading my VMWare installation
[16:53] <rogpeppe> hazmat: perhaps i can boot the vmware directly off my laptop hard drive
[16:54] <hazmat> rogpeppe, if you encrypted your home drive.... things get trickier..
[16:54] <rogpeppe> hazmat: it's a usb2 enclosure, unencrypted
[16:54] <rogpeppe> i'm not paranoid  :-)
[16:54] <hazmat> i'm not either, but i encrypt ;-)
[16:54] <mgz> dimitern: pushed up an attempt at some tests, are they sane enough?
[16:55] <rogpeppe> hazmat: ok, let's just say i'm hopelessly naive :-)
[16:55] <dimitern> mgz, will look in a moment
[16:57] <rogpeppe> dimitern: i'm afraid i'm not going to finish your review today
[16:57] <rogpeppe> dimitern: i've got to stop a little early today, unfortunately
[16:58] <rogpeppe> dimitern: i was referring to your "member:rogpeppe, that's a bit over the edge I think" comment about my "just use Call directly" remark
[16:59] <dimitern> rogpeppe, no worries
[16:59] <dimitern> rogpeppe, i'll have to stop soon as well
[16:59]  * dimitern needs to pack for a 5 am flight this morning
[16:59] <rogpeppe> "You have Mac OS X 10.6.8. The application requires Mac OS X 10.7 or later."
[16:59] <rogpeppe> bugger
[17:00] <dimitern> mgz, I'm looking at your CL, could you look at mine? https://codereview.appspot.com/66340045
[17:00] <mgz> dimitern: sure thing :)
[17:01] <dimitern> cheers :)
[17:04] <mgz> dimitern: just looking at Andrew's change that introduced it to see if we're going to be borking anything in reverse, change itself looks fine
[17:04] <mgz> ah, eg:
[17:04] <dimitern> mgz, I also looked and couldn't find a sane reason for the change - ssh does not support -- neither does --
[17:04] <mgz> [17:05] <dimitern> s/does --/does scp/
[17:05] <mgz> -       args := []string{"--", fmt.Sprintf("sudo /bin/bash -c '%s'", innercmd)}
[17:05] <mgz> +       args := []string{fmt.Sprintf("sudo /bin/bash -c '%s'", innercmd)}
[17:05] <mgz> does that then want reverting?
[17:05] <mgz> (looking at `bzr diff -c2116`)
[17:05] <dimitern> mgz, I'll try running debug-hooks with the test
[17:07] <mgz> thinking about that bit, it's *probably* fine if we got our shell quoting correct
[17:07] <mgz> one string, should be quoted and interpreted as a command regardless
[17:08] <mgz> [17:08] <mgz> -               sshArgs + "dummyenv-0.dns\n",
[17:08] <mgz> +               sshArgs + "ubuntu@dummyenv-0.dns\n",
[17:08] <mgz> er.. not that hunk
[17:08] <mgz> but some later bits, changed to add --
[17:09] <arosales1> mgz: fwereade_ you guys available for a sync on the joyent provider
[17:09] <mgz> [17:10] <mgz> again, that change should be fine if we get our quoting right
[17:10] <dimitern> arosales1, fwereade_ is not i'm afraid - a bit ill and resting
[17:10] <mgz> arosales1: alas, I need to go get a bus in a sec
[17:10] <arosales1> fwereade_: ?
[17:10] <mgz> arosales1: you may need to rope in dimitern, it's his day of getting roped in :)
[17:10] <arosales1> ah dimitern :-)
[17:11] <mgz> have been doing a fair bit with daniele this week, he should be able to report most of it
[17:11] <dimitern> arosales1, :) hmm
[17:11] <dimitern> arosales1, I have no knowledge on joyent or its progress though
[17:12] <mgz> dimitern: utils/ssh/ssh.go has an interesting bit
[17:12] <mgz> -       args = append(args, host, "--", command)
[17:12] <mgz> +       args = append(args, host)
[17:12] <mgz> +       if len(command) > 0 {
[17:12] <mgz> +               args = append(args, "--")
[17:12] <mgz> +               args = append(args, command...)
[17:12] <mgz> +       }
[18:09] <hazmat> anyone know which version of juju started using jenv files?
[18:10]  * hazmat thinks it was 1.16
[18:13] <natefinch> hazmat: that sounds right, but I don't know for sure
[19:00] <hazmat> is there any way in the api to tell which machines are 'dirty'?
[19:00] <hazmat> afaicr.. no
[19:07] <hazmat> filed a bug
[19:07] <natefinch> hazmat: in the API?  Possibly not
[19:08] <natefinch> hazmat: I know we have that information, but not sure if it's exposed.  It should be.
[19:08] <hazmat> natefinch, doesn't appear to be any api for machines outside of create/destroy and sidecar via status
[19:08] <hazmat> well and inject/provisioning  scriptfor manual
[19:08] <natefinch> hazmat: I'd love a juju status <machine> that gives more details about the machine
[19:09] <hazmat> natefinch, yeah.. i think that's the intended direction for extended info
[20:46] <hazmat> chris38, btw that go get -u -v launchpad.net/juju-core/.... needs a go install launchpad.net/juju-core/... as well to get the latest binaries.
[22:07] <sinzui> natefinch, do you think you will merge this by your morning tomorrow? https://code.launchpad.net/~natefinch/juju-core/034-juju-mongo/+merge/207320