[01:21] <perrito666> thanks for the review waigani very good questions
[01:22] <waigani> perrito666: np :)
[01:25] <menn0> waigani: here's the fix for the frequent panics in the machine-dep-engine under Go 1.5: https://github.com/juju/juju/pull/4090
[01:25] <menn0> waigani: review please
[01:25] <waigani> menn0: looking
[01:29] <waigani> menn0: ship it. I didn't know about sync.Once - handy
[01:31] <menn0> waigani: I knew about it but had never used it
[01:34] <waigani> menn0: It does feel like a slight kluge. Shouldn't the flow be such that close can only be called once?
[01:34] <menn0> waigani: well it's perfectly ok for Kill to be called lots of times
[01:34] <waigani> that's true
[01:34] <menn0> waigani: and this case you want the channel to be close on Kill
[01:35] <waigani> okay, fair enough :)
[02:11] <mup> Bug #1533431 opened: Bootstrap fails inexplicably with LXD local provider  <docteam> <juju-core:New> <https://launchpad.net/bugs/1533431>
[03:09] <cherylj> mwhudson: is someone actively working on getting go 1.5 into trusty?
[04:08] <mup> Bug #1533469 opened: github.com/juju/juju/api/reboot Build failed <ci> <ppc64el> <regression> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core controller-rename:Triaged> <https://launchpad.net/bugs/1533469>
[04:20] <mup> Bug #1533469 changed: github.com/juju/juju/api/reboot Build failed <ci> <ppc64el> <regression> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core controller-rename:Triaged> <https://launchpad.net/bugs/1533469>
[04:23] <mup> Bug #1379930 changed: relation config values set to the empty string are lost <charm> <relations> <juju-core:Expired> <https://launchpad.net/bugs/1379930>
[04:23] <mup> Bug #1514570 changed: 'JUJU_DEV_FEATURE_FLAGS=address-allocation' blocks after first 3 ips are allocated <juju-core:Expired> <https://launchpad.net/bugs/1514570>
[04:23] <mup> Bug #1533469 opened: github.com/juju/juju/api/reboot Build failed <ci> <ppc64el> <regression> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core controller-rename:Triaged> <https://launchpad.net/bugs/1533469>
[04:26] <mup> Bug #1379930 opened: relation config values set to the empty string are lost <charm> <relations> <juju-core:Expired> <https://launchpad.net/bugs/1379930>
[04:26] <mup> Bug #1514570 opened: 'JUJU_DEV_FEATURE_FLAGS=address-allocation' blocks after first 3 ips are allocated <juju-core:Expired> <https://launchpad.net/bugs/1514570>
[04:29] <mup> Bug #1379930 changed: relation config values set to the empty string are lost <charm> <relations> <juju-core:Expired> <https://launchpad.net/bugs/1379930>
[04:29] <mup> Bug #1514570 changed: 'JUJU_DEV_FEATURE_FLAGS=address-allocation' blocks after first 3 ips are allocated <juju-core:Expired> <https://launchpad.net/bugs/1514570>
[05:11] <mup> Bug #1532130 changed: Config item 'version' vanishes with 1.26 <regression> <juju-core:Invalid> <https://launchpad.net/bugs/1532130>
[05:15] <mup> Bug #1532130 opened: Config item 'version' vanishes with 1.26 <regression> <juju-core:Invalid> <https://launchpad.net/bugs/1532130>
[05:18] <mup> Bug #1532130 changed: Config item 'version' vanishes with 1.26 <regression> <juju-core:Invalid> <https://launchpad.net/bugs/1532130>
[05:21] <mup> Bug #1532130 opened: Config item 'version' vanishes with 1.26 <regression> <juju-core:Invalid> <https://launchpad.net/bugs/1532130>
[05:24] <mup> Bug #1532130 changed: Config item 'version' vanishes with 1.26 <regression> <juju-core:Invalid> <https://launchpad.net/bugs/1532130>
[07:30] <mup> Bug #1532130 opened: Config item 'version' vanishes with 1.26 <regression> <juju-core:New> <https://launchpad.net/bugs/1532130>
[08:41] <mattyw> anastasiamac, morning, still around?
[08:42] <anastasiamac> mattyw: m on and off - kids r home, dinner...
[08:42] <mattyw> anastasiamac, no problem
[09:04] <dimitern> frobware, dooferlad, morning :) can I bother you with a review on http://reviews.vapour.ws/r/3482/ please?
[09:31] <frobware> dimitern, welcome back & done.
[09:31] <dimitern> frobware, thanks!
[09:32] <frobware> dimitern, I plan to make everything a bridge on the maas-spaces branch when we re-render /e/n/i. Any thoughts or concerns?
[09:34] <dimitern> frobware, like we discussed last week? i.e. is_active always True?
[09:35] <frobware> dimitern, yes. I think, initially, I would like to take the simplest approach and if we find that bridging the world is too much we take another look.
[09:41] <frobware> dimitern, do you want to drop this (http://reviews.vapour.ws/r/3472/) as my 1.25-redux branch landed?
[09:43] <dimitern> frobware, sounds good
[09:43] <dimitern> frobware, will do
[10:01] <dimitern> voidspace, jam, frobware, standup?
[10:01] <alexisb> dimitern, I am keeping jam busy
[10:02] <dimitern> alexisb, sure, np just checking
[10:03] <voidspace> dimitern: omw
[10:27] <jam> dimitern: voidspace: have any time to chat briefly about what's going on here?
[10:29] <dimitern> jam, sure - when will be a good time for you?
[10:29] <jam> I'm writing up a summary email of the discussions from the morning, I have lunch pretty soon
[10:30] <jam> I seem to have a gap in about 4hrs, does that work for both of you?
[10:31] <dimitern> jam, works for me
[10:39] <voidspace> jam: should be fine
[10:43] <jam> bridge
[14:46] <mup> Bug #1533694 opened: inconsistent juju-gui and juju status <juju-core:New> <https://launchpad.net/bugs/1533694>
[14:52] <mup> Bug #1533694 changed: inconsistent juju-gui and juju status <juju-core:New> <https://launchpad.net/bugs/1533694>
[14:55] <mup> Bug #1533694 opened: inconsistent juju-gui and juju status <juju-core:New> <https://launchpad.net/bugs/1533694>
[15:01] <cherylj> yikes.  what happened with that controller-rename test, sinzui ?
[15:01] <cherylj> http://reports.vapour.ws/releases/3503
[15:01] <sinzui> cherylj: the previous job left xenial-slave dirty. I am not having must success cleaning either
[15:01] <cherylj> :(
[15:02] <sinzui> cherylj: I am going to remove the failed 1.25 revision from testing to make controller-rename complete testing, thenlet 1.25 be rediscovered.
[15:02] <cherylj> sinzui: sounds good
[15:03] <voidspace> dimitern: ping
[15:03] <voidspace> dimitern: unping
[15:05] <TheMue> voidspace: *lol* didn't know this "command"
[15:05] <voidspace> TheMue: heh :-)
[15:05] <voidspace> I use it all the time...
[15:05] <TheMue> cool
[15:17] <voidspace> well, writing tests has just found two more bugs in my code
[15:18] <perrito666> voidspace: writing tests always does that
[15:19] <perrito666> its very bad for the pride :p
[15:20] <voidspace> :-)
[15:22] <TheMue> voidspace: just writing tests for my latest feature too
[15:23] <voidspace> TheMue: heh, cool
[15:33] <jam> natefinch: katco: I'm trying to use the LXD provider, but it is failing to set up ssh keys on the started container
[15:33] <jam> I can see authorized-keys that make sense in the instanceconfig
[15:33] <katco> jam: ericsnow as well ^^^
[15:33] <katco> jam: that's a new one i think
[15:33] <jam> but /home/ubuntu/.ssh/ is empty
[15:34] <katco> that's very strange...
[15:34] <jam> I can see in cloud-init-output.log it is complaining that there was nothing in /home/ubuntu/.ssh as well
[15:34] <jam> (i think)
[15:35] <perrito666> jam: try adding that to your keyring
[15:35] <perrito666> I recall some of the providers not working for that
[15:35] <perrito666> sinzui: it was the key ring right? during the sprint with HP
[15:36] <katco> jam: talking this over with the team, but on the surface this doesn't sound like something the lxd provider would be responsible for. what build of juju are you using?
[15:37] <katco> jam: also, standard questions: what ubuntu+lxd are you running?
[15:37] <sinzui> jam: perrito666 : yes, add the $HOME/.ssh/<keys> to your key ring.
[15:37] <jam> katco: trusty with the stable ppa
[15:38]  * perrito666 is working at a bar and just asked a coffee in english
[15:38]  * perrito666 hides under the table
[15:38] <jam> perrito666: if I attach to the instance, /home/ubuntu/.ssh is empty
[15:38] <jam> that doesn't sound like a keyring thing
[15:39] <jam> And if I add a debug print before the instance is spawned, I see the ssh public key in the instance config
[15:39] <perrito666> :|
[15:39] <jam> katco: I'm using nate's branch
[15:39] <katco> jam: ah... i'm surprised it's even getting that far? the trusty version doesn't have lxd built in because it's not >= go1.3
[15:39] <jam> katco: stable ppa
[15:39] <jam> ppa:ubuntu-lxc/lxd-stable IIRC
[15:39] <jam> katco: I'm using the resources branch
[15:39] <katco> ohhh for lxd
[15:40] <katco> ok ok gotcha
[15:40] <jam> I can "lxc attach" to the instance to debug it
[15:40] <jam> but I get the same result reliably right now
[15:40] <jam> (lxc exec ... bash)
[15:41] <katco> jam: ok, that makes a lot more sense. natefinch is telling me the pastebin i sent you was local provider, not lxd. we're investigating lxd now
[15:41] <katco> jam: we're probably just sitting on an unstable commit of master
[15:41] <jam> ci-info: no authorized ssh key fingerprints found for user ubuntu
[15:42] <natefinch> we know we're kind of out of date wrt to master... I'd just use local, if it's all the same.
[15:44] <blackboxsw> g
[15:45] <jam> natefinch: with local provider I can replicate the demo script
[15:46] <katco> jam: we're working on getting lxd to work (as well as resource-get)
[15:50] <dooferlad> dimitern, frobware, voidspace: I can work around the issue of not having a default gateway set in MAAS by setting a guests default gateway to its hosts IP address. Since we have forwarding enabled on all our hosts this works.
[15:51] <dooferlad> It is a bit rubbish, but it doesn't involve parsing any more files - the data is in state.
[15:52] <frobware> dooferlad, does that mean the "real" gateway is not in state?
[15:53] <dooferlad> frobware: yes
[15:53] <dimitern> dooferlad, we only have fwding on with the A-C feature flag
[15:53] <dooferlad> dimitern: I have set no flags
[15:53] <dooferlad> frobware: the host is getting its address by DHCP
[15:54] <dooferlad> and the guest from the MAAS API
[15:54] <dooferlad> it feels really messed up
[15:54] <jam> katco: so talking with the guys here about lxd, you *shouldn't* use the linuxcontainers.org images, because those don't have cloudinit installed
[15:54] <jam> you just need the lxd-images import
[15:54] <jam> as that is from cloud-images.ubuntu.com simplestreams info
[15:54] <dimitern> dooferlad, that's exactly what we do for A-C - host acts like a gateway, but that has its drawbacks
[15:55] <perrito666> jam: the instructions do say to use the cloud images, doesn't it? (i only used lxd provider once)
[15:55] <dimitern> like the need for fwding on, as well as packets coming from a container will have different TTL and source as they arrive at the destination
[15:55] <jam> perrito666: the first thing it says is to "lxc add linuxcontainers.org" but then not use it
[15:56] <jam> katco: fwiw, it fails with master as well
[15:56] <jam> same "(publickey)" issue
[15:56] <katco> jam: bootstrapping lxd?
[15:56] <perrito666> jam: ah, I just ignored that one
[15:56] <jam> katco: yeah
[15:56] <jam> I'm using ubuntu-trusty and not ubuntu-wily, don't know ifthat matters
[15:56] <jam> IIRC they use a diffreent cloud-init version
[15:57] <natefinch> jam: you need ubuntu wily for the bootstrap server at least
[15:57] <natefinch> jam: iirc
[15:57] <katco> jam: that should work, i'm using ubuntu-trusty
[15:57] <jam> anyway, I can reproduce this if you want a test case
[15:57] <jam> but I'm off to other things now
[15:57] <dooferlad> dimitern: I don't know why we have the host using DHCP but not for the container. Is that how the MAAS devices API works?
[15:57] <katco> jam: absolutely, ty for the input
[15:57] <natefinch> I'm pretty sure this is just a result of using the wrong images
[15:58] <katco> jam: you're doing --upload-tools?
[15:58] <jam> katco: it fails right away if you don't
[15:58] <jam> (it fails with "I don't know what lxd provider is" cause it uses some other version)
[15:58] <katco> jam: i dunno, i think natefinch is correct. there's something unique with what you're doing. sounds like the image
[15:59] <katco> jam: i've got a bootstrapped env. right now on ubuntu-trusty
[15:59] <katco> jam: but we'll figure it out, open a bug if you don't mind
[15:59] <jam> katco: I just did "lxd-images import ubuntu --alias ubuntu"
[16:01] <frobware> dooferlad, you have mail
[16:01] <jam> its release-2015218
[16:01] <katco> jam: fingerprint?
[16:02] <katco> jam: actually what's lxc image list
[16:02] <jam> getting it, just a sec
[16:02] <dooferlad> frobware: a victory for sanity!
[16:02] <katco> jam: np. understand if you have to run too
[16:02] <jam> ffs. just ran into a bug with lxd-images. I had deleted the image to double check the download, and now lxd-images import is giving me a "NoneType is not iterable" after doing the download
[16:03] <katco> jam: =|
[16:07] <jam> katco: 0afd3f6ac was in my terminal backtrace
[16:08] <natefinch> that's different than mine... are they supposed to be the same fingerprint for different people and/or different times?  I'm not sure I'd trust they don't get updated with security patches etc
[16:08] <katco> jam: i think that's the one i'm on: 0afd3f6ac0d7
[16:12] <jam> katco: https://bugs.launchpad.net/juju-core/+bug/1533742
[16:12] <mup> Bug #1533742: lxd provider fails to setup ssh keys during bootstrap <lxd> <juju-core:Triaged> <https://launchpad.net/bugs/1533742>
[16:12] <jam> natefinch: katco: 20151218 is dec-18 when they last updated it
[16:12] <jam> (according to the URL from lxd-images import)
[16:16] <katco> jam: i'm trying to repro from master as well (but my host is wily)
[16:17] <jam> katco: thanks.
[16:17] <jam> I would think the issue would be the image version vs the host, which I'm guessing you're thinking as well
[16:18] <katco> jam: what version of go are you compiling master with?
[16:18] <jam> katco: 1.6
[16:18] <jam> 1.5
[16:18] <jam> the one that you get after adding the lxd ppa
[16:18] <jam> 1.5.1
[16:19] <katco> jam: should be sufficient
[16:19] <jam> anyway, now need to get ready for dinner. but I do have your demo working. I think I'm scheduled for Fri morning
[16:20] <jam> so if you can add resource-get to show the resources working, that'd be great
[16:20] <katco> jam: k, we're also pushing for resource-get
[16:20] <perrito666> bbl, changing locations
[16:20] <katco> jam: thx john
[16:22] <mup> Bug #1533742 opened: lxd provider fails to setup ssh keys during bootstrap <lxd> <juju-core:Triaged> <https://launchpad.net/bugs/1533742>
[16:25] <mup> Bug #1533742 changed: lxd provider fails to setup ssh keys during bootstrap <lxd> <juju-core:Triaged> <https://launchpad.net/bugs/1533742>
[16:28] <mup> Bug #1533742 opened: lxd provider fails to setup ssh keys during bootstrap <lxd> <juju-core:Triaged> <https://launchpad.net/bugs/1533742>
[16:37] <mup> Bug #1533750 opened: 2.0-alpha1 stabilization <blocker> <juju-core:Triaged> <https://launchpad.net/bugs/1533750>
[16:37] <mup> Bug #1533751 opened: Increment minimum juju version for 2.0 upgrade to 1.25.3 <blocker> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1533751>
[16:40] <mup> Bug #1533750 changed: 2.0-alpha1 stabilization <blocker> <juju-core:Triaged> <https://launchpad.net/bugs/1533750>
[16:40] <mup> Bug #1533751 changed: Increment minimum juju version for 2.0 upgrade to 1.25.3 <blocker> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1533751>
[16:46] <mup> Bug #1533750 opened: 2.0-alpha1 stabilization <blocker> <juju-core:Triaged> <https://launchpad.net/bugs/1533750>
[16:46] <mup> Bug #1533751 opened: Increment minimum juju version for 2.0 upgrade to 1.25.3 <blocker> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1533751>
[17:02] <fwereade> huh, I think that was an earthquake
[17:02] <natefinch> neat
[17:02]  * natefinch says from a place that pretty much never has earthquakes.
[17:03] <fwereade> yeah, it's a bit disconcerting, I never remember feeling one in the uk
[17:18] <cherylj> katco: ping?
[17:18] <katco> cherylj: hey
[17:18] <cherylj> katco: got a minute?
[17:18] <katco> cherylj: yeah sure
[17:19] <cherylj> katco: https://plus.google.com/hangouts/_/canonical.com/cheryl-katco?authuser=0
[17:28] <katco> natefinch: don't forget to drag the card for the bug you're working on to in progress
[17:28] <katco> ericsnow: ping?
[17:28] <ericsnow> katco: hey
[17:28] <ericsnow> katco: sorry, I'm ready to go
[17:28] <katco> ericsnow: "no more than half an hour" - ericsnow 2.5h ago
[17:28] <katco> ;)
[17:29] <katco> ericsnow: at this point, let's wait until after lunch.
[17:29] <cherylj> Can I get a review?  http://reviews.vapour.ws/r/3519/
[17:29] <cherylj> Small review
[17:29] <ericsnow> katco: k
[17:30] <katco> cherylj: lgtm
[17:30] <cherylj> thanks, katco
[18:38] <perrito666> jam: ping
[18:41] <natefinch> good licl., ot
[18:41] <natefinch> it's 10:41pm where he is
[18:41] <natefinch> good luck, that is...
[18:41] <natefinch> unless he's in cape town, in which case it's 8:41
[18:42] <natefinch> still not good odds :)
[18:44] <perrito666> I assumed he was in capetown
[18:50] <natefinch> katco: sorry, was at lunch and then trying to figure out which of the networking bugs is least terrible to work on
[19:01] <mup> Bug #1533790 opened: GCE provider is very restrictive when using a config-file (json) <juju-core:New> <https://launchpad.net/bugs/1533790>
[19:01] <mup> Bug #1533792 opened: Panic: TestProvisioningMachinesWithSpacesSuccess <ci> <panic> <ppc64el> <regression> <test-failure> <juju-core:Incomplete> <juju-core controller-rename:Triaged> <https://launchpad.net/bugs/1533792>
[19:27] <perrito666> is anyone aware of the current status of syslog vs mongodb?
[19:59] <katco> ericsnow: ok i'm ready to pair if you are
[19:59] <ericsnow> katco: gimme half an hour <wink>
[19:59] <ericsnow> katco: BRT :)
[19:59] <katco> rofl
[19:59] <thumper> morning folks
[20:00]  * thumper grunts
[20:00] <thumper> almost 2500 emails
[20:00] <katco> heyo thumper
[20:31] <perrito666> thumper: returning from holidays?
[20:46] <thumper> perrito666: aye
[20:46] <thumper> first day back after three weeks
[20:46] <natefinch> thumper: must be rough
[20:46] <perrito666> uff, heavy
[20:46] <thumper> lots of email
[20:46] <perrito666> it would be nice to have a "valid until" feature on emails
[20:46] <perrito666> :p
[20:46] <perrito666> "sorry this email went sour"
[20:47] <thumper> :)
[20:47] <cherylj> jog__: are you around?
[20:48] <jog__> cherylj, yes
[20:48] <cherylj> jog__: are the MAASes currently occupied?
[20:49] <jog> cherylj, yes, there are 3 CI jobs running. What do you need?
[20:49] <cherylj> jog: if I could look at a running env while it's doing the deployer test, I might be able to get more data on the rabbitmq-server failures
[20:50] <cherylj> jog: or if I could do a simple depoy
[20:50] <cherylj> deploy even
[20:52] <jog> cherylj, If you want to bootstrap and just deploy a single rabbitmq-server charm, the MAAS should have capacity for that... deploying the entire OS bundle when other things are running is when we run into resource issues... I can deploy a rabbitmq-server for you.
[20:52] <cherylj> jog: it would need to be in a container
[20:53] <jog> ok
[20:53] <cherylj> so just deploy --to lxc:0
[20:53] <cherylj> I'm wondering if we've run into bug 1329930
[20:53] <mup> Bug #1329930: rabbitmq-server fails to deploy into lxc container on maas provider <rabbitmq-server (Juju Charms Collection):Fix Released> <https://launchpad.net/bugs/1329930>
[20:53] <cherylj> I see someone else has run into it recently
[21:02] <natefinch> cherylj: git blame says I should talk to you about https://bugs.launchpad.net/juju-core/+bug/1515289
[21:02] <mup> Bug #1515289: bootstrap node does not use the proxy to fetch tools from streams.c.c <bug-squad> <juju-core:Triaged> <https://launchpad.net/bugs/1515289>
[21:02] <cherylj> natefinch: I didn't do it!
[21:03] <natefinch> cherylj: totally possible :)
[21:03] <natefinch> cherylj: https://github.com/juju/juju/blob/master/cloudconfig/userdatacfg_unix.go#L260
[21:04] <natefinch> cherylj: so, I think the title of that bug is wrong
[21:04] <natefinch> cherylj: he can bootstrap just fine, which means he gets the tools from streams ok.  It looks like the problem is actually that new nodes can't get the tools from the state server
[21:05] <natefinch> cherylj: sorry, I may be confused, however
[21:06] <cherylj> natefinch: he includes something else later that shows the get command the bootstrap node is trying to use to get the tools from streams
[21:07] <cherylj> I then inspected the bootstrap node, and found this in all-machines.log: <...>
[21:08] <natefinch> cherylj: ok, I think I understand what I'm seeing... I thought the --noproxy on the curl command from the other node was the problem, but that's probably just failing because the state server can't get the tools either
[21:09] <cherylj> natefinch: yeah, I believe that's the case
[21:09] <natefinch> cherylj: ok, nevermind then. Thanks for helping me understand the bug report :)
[21:15] <jog> cherylj, it's bootstrapping
[21:25] <natefinch> ericsnow: gah, you broke GenerateFingerprint(nil) :/
[21:32] <mup> Bug #1533849 opened: github.com/juju/juju/version [build failed] on windows <ci> <regression> <test-failure> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged by cherylj> <https://launchpad.net/bugs/1533849>
[21:35] <mup> Bug #1533849 changed: github.com/juju/juju/version [build failed] on windows <ci> <regression> <test-failure> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged by cherylj> <https://launchpad.net/bugs/1533849>
[21:41] <mup> Bug #1533849 opened: github.com/juju/juju/version [build failed] on windows <ci> <regression> <test-failure> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged by cherylj> <https://launchpad.net/bugs/1533849>
[21:42] <cherylj> stop it, mup
[21:42] <cherylj> review, pretty please: http://reviews.vapour.ws/r/3520/
[21:43] <natefinch> cherylj: shipit
[21:43] <natefinch> cherylj: are you not using goimports?
[21:44] <mup> Bug #1533849 changed: github.com/juju/juju/version [build failed] on windows <ci> <regression> <test-failure> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged by cherylj> <https://launchpad.net/bugs/1533849>
[21:44] <natefinch> cherylj: or hmm, is it because it's an _windows file, so it gets missed
[21:45] <natefinch> cherylj: was going to ask how you even landed code that wouldn't compile, but of course our landing bot isn't compiling on windows (yet)
[21:45] <perrito666> goimports rocks
[21:45] <natefinch> perrito666: yeah, I wasn't convinced until I used it, now I love it.
[21:46] <perrito666> I have it hooked on save
[21:47] <natefinch> yep, me too.  The only problem I have is when I manually add an import (for example, one that needs to be named) and then accidentally hit save before I have used it.
[21:47] <mup> Bug #1533849 opened: github.com/juju/juju/version [build failed] on windows <ci> <regression> <test-failure> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged by cherylj> <https://launchpad.net/bugs/1533849>
[21:47] <perrito666> yup, happens sometimes
[21:48] <perrito666> but i usually write the code the other way
[21:49] <natefinch> perrito666: I have autocomplete, to help remind me what the names of things are, but it won't work if the import doesn't exist yet, so it's kind of a chicken and egg thing.
[21:50] <perrito666> aaand of course, defaulting mongo log breaks tests
[21:52] <natefinch> lol
[21:52] <natefinch> because of course it does
[21:59] <natefinch> perrito666: what, logging to mongo and having tests that inspect log output don't somehow turn two bad ideas into a good idea? :)
[22:00] <perrito666> yeah, logging one into one unreliable destination beats just logging all into one destination
[22:01] <natefinch> whelp, dinner time.  Back later.  Good luck storming the castle!
[22:08] <cherylj> jog: any luck getting rabbitmq-server to deploy?
[22:09] <jog> cherylj, not yet, I had to cleanup left behind nodes on the MAAS, it's redeploying now
[22:10] <cherylj> jog: can I ssh into it from finfolk and watch the deploy?
[22:11] <jog> cherylj, yes... export JUJU_HOME then run juju status -e min-lxc
[22:11] <cherylj> jog: thanks!
[22:16] <jog> cherylj, kill-controller ran despite --keep-env
[22:17] <cherylj> blargh
[22:26] <katco> cherylj: do you need me in the release standup?
[22:28] <cherylj> katco: no, I don't think so.  Thanks!
[22:28] <katco> cherylj: cool ty, pairing atm
[22:46] <thumper> perrito666: still here?
[22:47] <thumper> perrito666: state environ.go, LatestAvailableTools, never written to, added back in Sep, is it going to be used?
[22:47] <thumper> hmm... found something
[22:47] <thumper> nm
[23:13] <cherylj> hey thumper, I figured out the cause of some of the test failures.  I have the change merging for master now.  Would you be able to rebase controller-rename once it merges?
[23:17] <perrito666> axw: anastasiamac going
[23:17] <perrito666> thumper: here,
[23:19] <jog> the controller-rename juju binary complains if destroy-environment is used with: ERROR "parallel-maas18" is a system; use 'juju system destroy' to destroy it
[23:19] <perrito666> thumper: sorry I was trying to sport away the effects of working on a desk
[23:19] <jog> it also complains with: ERROR unrecognized command: juju system
[23:20] <perrito666> thumper: that was added and later changed by menn0 iirc
[23:20] <jog> I was able to destroy with 'destroy-controller' are we just in transition here or is a bug needed?
[23:41] <mup> Bug #1533896 opened: Metadata worker repeatedly errors on new azure <juju-core:In Progress by anastasia-macmood> <https://launchpad.net/bugs/1533896>
[23:44] <mup> Bug #1533896 changed: Metadata worker repeatedly errors on new azure <juju-core:In Progress by anastasia-macmood> <https://launchpad.net/bugs/1533896>
[23:47] <mup> Bug #1533896 opened: Metadata worker repeatedly errors on new azure <juju-core:In Progress by anastasia-macmood> <https://launchpad.net/bugs/1533896>