[00:05] <rick_h_> menn0: ping, re: #1597601 this is in the process of a deploy, why can't we just catch that clear message and retry for a bit?
[00:05] <mup> Bug #1597601: ERROR cannot deploy bundle: cannot deploy application: i/o timeout <2.0> <bundles> <deploy> <oil> <oil-2.0> <repeatability> <retry> <juju-core:Triaged by menno.smits> <https://launchpad.net/bugs/1597601>
[00:05] <rick_h_> menn0: it's not clear why the user can retry when it's in our control from a bundle deployment (blocking operation atm) and know the issue? but they can?
[00:12] <perrito666> thumper: k reviewing
[01:02] <perrito666> thumper: I have a few comments
[01:02] <thumper> perrito666: ok
[01:02] <perrito666> dont hate me
[01:03] <perrito666> blame the checklist
[01:03] <perrito666> k ppl, dinner, bbl
[01:07] <menn0> rick_h_: it goes deeper than that
[01:07] <menn0> rick_h_: this error can happen at any time... not just during deploy
[01:07] <menn0> rick_h_: when mongodb does a leader election, it drops all it's connections and all our workers die
[01:08] <menn0> rick_h_: if an api request comes in just as the mongodb conns go down the i/o timeout happens
[01:08] <menn0> rick_h_: the apiserver gets taken down so we can't retry internally
[01:08] <menn0> rick_h_: changing that requires some pretty fundamental changes to the way our workers are arranged and how state.State works
[01:09] <menn0> I don't think we can get that done before 2.0
[01:10] <menn0> rick_h_: oh I see what you're saying... I guess I wasn't clear enough
[01:10] <menn0> rick_h_: the "please retry" error would come from the apiserver and be handled by the client. the end user wouldn't have to do anything.
[01:11] <menn0> updating the ticket
[01:38] <axw> menn0: in case you were planning to change any other workers to depend on environ-tracker, I'm updating storage-provisioner to do that now
[01:38] <axw> menn0: (related to my ongoing work)
[01:39] <menn0> axw: ok cool. I wasn't planning on doing that one but makes sense to do it while we're thinking about it
[01:41] <menn0> axw: that will mean that the minimal provider we inject in this other test will probably need to implement a little more, but I guess that won't be too ahrd
[01:41] <menn0> hard
[01:42] <axw> menn0: as long as it has a "Config()" method, it'll be fine for the storage provisioner
[01:42] <menn0> axw: that's fine then, as long as the config it has to return isn't too onerous
[01:42] <axw> menn0: AFAICR, it won't need anything at all
[01:42] <axw> I mean, just a base config
[01:43] <axw> I'll make sure of that before I land
[01:43] <menn0> axw: sounds great then.
[01:43] <menn0> axw: I'm working on the provisioner changes right now
[01:44]  * menn0 wants this done
[01:44] <axw> :)
[01:57] <perrito666> Wallyworld tx for the review
[02:09] <bdx> rick_h_: yea, I still can't seem to get the instance to deploy ....
[02:10] <bdx> rick_h_: or any instance for that matter
[02:12] <bdx> rick_h_: yea, the bootstrap instance deployed to the vpc I specified
[02:24] <natefinch> Hey, just realized I hit my 3 year anniversary
[02:25] <natefinch> (at canonical)
[02:27] <anastasiamac> natefinch: congrats? :)
[02:27] <perrito666> natefinch: sweet, congrats
[02:27] <perrito666> by all going to sleep
[02:28] <anastasiamac> perrito666: nite nite
[02:28] <natefinch> see ya
[02:28] <menn0> thumper: permission to JFDI this? (test only change) https://github.com/juju/juju/pull/5908
[02:28] <menn0> perrito666: good night
[02:39]  * thumper looks at menn0's patch
[02:39] <thumper> menn0: ack
[02:40] <menn0> thumper: thanks
[02:48] <thumper> menn0: http://reviews.vapour.ws/r/5349/
[02:48] <thumper> menn0: and http://reviews.vapour.ws/r/5350/
[02:48] <thumper> menn0: when those two have landed I have a juju branch
[02:48] <thumper> that needs these changes to make it work with the new loggo
[02:49] <thumper> 27 files changed in juju
[02:49] <menn0> thumper: ok, will look soon. just pushing my next thing.
[02:50] <thumper> menn0: np
[02:51] <thumper> ok... starting a stab at filesystem migration now
[02:51] <thumper> when I lose the will on that I may attack an intermittent failure
[02:55] <menn0> haha
[02:59] <menn0> axw: here's the provisioner change: http://reviews.vapour.ws/r/5351/
[03:00] <axw> menn0: thanks, will look shortly. if you have time, I've got the storage provisioner one up here: http://reviews.vapour.ws/r/5348/
[03:00] <menn0> axw: will do
[03:05] <natefinch> thumper: how much do you know about github.com/juju/schema?
[03:07] <natefinch> (or anyone else for that matter).  Mostly wonder if anyone will kick and scream if I unmangle the API very slightly.
[03:09] <natefinch> schema and environschema suffer from "I wish this was python" syndrome
[03:14] <menn0> thumper: reviews done
[03:14] <thumper> menn0: ta
[03:14] <thumper> natefinch: a reasonable amount
[03:14] <thumper> natefinch: why?
[03:15] <menn0> axw: just an FYI but I'm pretty sure QA steps are supposed to be detailed step by step instructions
[03:15] <menn0> axw: alexis has pulled me up on that recently
[03:16] <menn0> axw: don't worry about it for this one
[03:16] <axw> menn0: okey dokey, thanks
[03:16] <natefinch> thumper: so, the Coerce method on the checker returned by FieldMap uses a lot of reflection to avoid just casting the interface to map[string]interface..... the end result really just being that it effectively works with any key that is a string or has a String() method
[03:17] <natefinch> thumper: AFAIK, core code always passes in map[string]interface{} .... would it be kosher to strip out the reflection and just cast to map[string]interface{} inside fieldMap's coerce?
[03:17] <thumper> I don't know of other users
[03:18] <thumper> but it shouldn't hurt juju
[03:18] <thumper> but my question is why?
[03:18] <thumper> what are you doing to schema that got you looking there?
[03:18] <natefinch> thumper: it would make the code a lot simpler
[03:18] <thumper> I'm just thinking priorities
[03:18] <thumper> that's all
[03:19] <natefinch> thumper: I'm adding the concept of dependencies between attributes in a field map.  So, like, A should only be set if B is set to value XXX.
[03:19] <thumper> ah...
[03:19] <natefinch> thumper: this is to support add-cloud using the environschema to generate the add-cloud interactive prompts
[03:19] <thumper> is this mostly in environschema?
[03:20] <thumper> or the schema package itself?
[03:20] <thumper> but to go back to the original...
[03:20] <natefinch> thumper: the two are pretty intertwined... but the dependency stuff needs to be in schema
[03:20] <thumper> I'm pretty sure that juju doesn't passing "Stringer"s into the schema checking
[03:21] <thumper> pretty sure, as you said, that it all goes through map[string]interface{}
[03:21] <natefinch> thumper: it's not really important.  I don't want to break anyone... just struck me as making the code obtuse for no reason.
[03:23] <menn0> axw: review done
[03:24] <axw> menn0: thanks, yours too if you didn't see. I didn't get the name references sadly, so can't follow ;p
[03:24] <axw> something about Cats I think?
[03:24] <menn0> axw: thanks for your review. your suggestion is spot on. I'll add a TODO.
[03:24] <natefinch> brb
[03:25] <menn0> axw: I have NFI either. Just noted the high brow sounding names :)
[03:25] <axw> hehe
[03:25] <menn0> axw: looks like cats :)
[04:07] <thumper> menn0: last one
[04:07] <thumper> http://reviews.vapour.ws/r/5353/
[04:08]  * menn0 looks
[04:26] <mup> Bug #1325968 changed: juju 1.18.3 - MAAS Node - cannot execute binary file: Exec format error  <arm64> <bootstrap> <jujud> <maas-provider> <juju-core:Expired> <https://launchpad.net/bugs/1325968>
[05:45] <menn0> axw: here's the final PR for the TestHostedModelWorkers problem: http://reviews.vapour.ws/r/5354/
[05:46] <axw> menn0: cool, looking
[05:52] <axw> menn0: LGTM, thanks
[06:34] <anastasiamac> rick_h_: dimitern: before going, James put a fix for bug 1602054. PR is linked to the bug. Would be awesome to get into next release \o/ it was highlighted in sts call last week
[06:34] <mup> Bug #1602054: juju deployed lxd containers are missing a default gateway when configured with multiple interfaces <2.0> <network> <regression> <juju-core:In Progress by dooferlad> <https://launchpad.net/bugs/1602054>
[07:01] <dimitern> anastasiamac: ok, I'll have a look
[07:24] <mup> Bug #1608818 opened: Default storage pools are not registered for hosted models <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1608818>
[07:24] <mup> Bug #1608821 opened: "juju storage-pools --provider=..." does not work correctly <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1608821>
[07:36] <mup> Bug #1608818 changed: Default storage pools are not registered for hosted models <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1608818>
[07:36] <mup> Bug #1608821 changed: "juju storage-pools --provider=..." does not work correctly <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1608821>
[07:39] <mup> Bug #1608818 opened: Default storage pools are not registered for hosted models <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1608818>
[07:39] <mup> Bug #1608821 opened: "juju storage-pools --provider=..." does not work correctly <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1608821>
[08:03] <anastasiamac> dimitern: tyvm \o/
[08:16] <dimitern> reviewboard seems to be having issues - or it's just for me?
[08:16] <dimitern> can anybody open http://reviews.vapour.ws/r/5333/ for example?
[08:20] <dimitern> ah, it's back now
[08:21] <dimitern> :/ gone again
[08:44] <dimitern> macgreagoir: hey, are you around?
[08:57] <dimitern> should've checked the cal
[09:12] <rogpeppe> axw: just FYI, following up from yesterday, i reported https://bugs.launchpad.net/juju-core/+bug/1608494
[09:12] <mup> Bug #1608494: state: not all public methods are tested <juju-core:New> <https://launchpad.net/bugs/1608494>
[09:12] <axw> rogpeppe: ok, thanks
[09:13] <rogpeppe> axw: there are others which seem to have test coverage only coincidentally (no dedicated tests), e.g. State.Cloud (tested only because NewModel calls it)
[09:13] <rogpeppe> axw: i'm just fixing UpdateCloudCredentials now and writing a test for it
[09:14] <axw> rogpeppe: great, thank you
[09:15] <rogpeppe> axw: currently trying to work out how to create a named cloud
[09:15] <axw> rogpeppe: to bootstrap with?
[09:16] <rogpeppe> axw: so that i can have a valid cloud name to pass to UpdateCloudCredentials
[09:16] <rogpeppe> axw: for the test
[09:16] <axw> rogpeppe: for now you cannot add clouds, you can only refer to the cloud you bootstrapped with. in all the state tests (I think all?) that's "dummy"
[09:17] <rogpeppe> axw: ah, ok, cool
[10:00] <rogpeppe> axw: hmm, so the dummy provider has no attributes in its cloud credentials, and there seems to straightforward way to make more clouds
[10:00] <rogpeppe> axw: so i think it's not going to be easy to test the UpdateCloudCredentials logic
[10:01] <rogpeppe> s/to straightforward/no straightforward/
[10:01] <rogpeppe> axw: i guess i could write a new dummy provider and redo something like ConnSuite from scratch, but that seems... quite a bit of work
[10:02] <axw> rogpeppe: I don't think you need to write a new provider, just initialize state with a different cloud definition
[10:02] <rogpeppe> axw: ok, but ConnSuite has already initialized the state
[10:02] <axw> rogpeppe: yeah, you would have to not use ConnSuite
[10:03] <axw> rogpeppe: or... maybe change ConnSuite so that you can parameterise the cloud def
[10:03] <rogpeppe> axw: yeah, not sure which way's best
[10:03] <axw> rogpeppe: i.e. override before SetUpSuite
[10:03] <axw> or SetUpTest or whatever
[10:03] <axw> that's probably the least amount of work
[10:04] <rogpeppe> axw: i guess i'd need a separate test suite for every cloud variation then
[10:05] <rogpeppe> axw: or... i guess i could call SetUpTest inside each test directly
[10:05] <axw> rogpeppe: ew, but yeah :)
[10:06] <rogpeppe> axw: or provide some more modular functionality inside state/testing, i suppose
[10:07] <rogpeppe> axw: or provide the capability to add more clouds
[10:07] <axw> rogpeppe: it's probably fine to do that TBH, it's not going to harm anything
[10:08] <axw> rogpeppe: and it's going to happen sooner or later
[10:08] <axw> so if it's easy...
[10:08] <rogpeppe> axw: :)
[10:08] <rogpeppe> axw: this is all unbudgeted-for stuff
[10:11] <axw> rogpeppe: gtg, thanks for fixing it up - I'm still neck high in config stuff
[10:11] <rogpeppe> axw: np
[10:11] <rogpeppe> axw: have fun!
[10:17] <dimitern> reviews on http://reviews.vapour.ws/r/5356/ will be much appreciated!
[10:50] <babbageclunk> dimitern: I'll trade you! ;) Take a look at these ones? http://reviews.vapour.ws/r/5312/ http://reviews.vapour.ws/r/5317/
[10:50] <dimitern> babbageclunk: sure ;) looking
[10:54] <rogpeppe> anyone familiar with the new cloud stuff? named clouds and that sort of thing?
[10:54] <rogpeppe> axw: i'm presuming you're done for the day...
[11:09] <balloons> anastasiamac, are you going to schedule something this week to talk about the bootstrap acceptance criteria?
[11:13] <babbageclunk> dimitern: Reviewed, a couple of minor things.
[11:14] <dimitern> babbageclunk: cheers! still looking at yours I'm afraid
[11:17] <anastasiamac> oh balloons: I'd love to :D r u available? any pref days/times?
[11:19] <balloons> anastasiamac, it is easy for me to meet about this time. Does tomorrow work?
[11:19] <anastasiamac> balloons: i'll add it to calendar! tyvm :)
[11:20] <anastasiamac> balloons: bootsrap? there is add cloud.. not botstrap done :)
[11:22] <balloons> anastasiamac, is your github PR all up to date?
[11:23] <balloons> ahh right.. add-cloud: https://github.com/anastasiamac/juju/blob/acceptance-add-cloud/acceptance/cloud/add_cloud.feature
[11:27] <rick_h_> morning
[11:42] <dimitern> babbageclunk: thanks for fixing the vsphere issue btw - LGTM
[11:44] <anastasiamac> balloons: yes
[11:45] <anastasiamac> balloons: at least for now an as far as I got with everyone sprinting... it needs more discussions but i believe it's at the next logical step and can be useful for u to kick things off on ur side :P
[12:09] <mup> Bug #1571593 changed: lxd bootstrap fails with unhelpful 'invalid config: no addresses match' <juju-release-support> <lxd-provider> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1571593>
[12:17] <axw> rogpeppe: yes EOD. going away again :)
[12:17] <rogpeppe> axw: np :)
[12:18] <rogpeppe> axw: just wondering if clouds should be immutable
[12:39] <mup> Bug #1443942 changed: SNAT for externally routed traffic should be only for EC2 and for subnets in the VPC <bug-squad> <ec2-provider> <network> <tech-debt> <juju-core:Won't Fix> <https://launchpad.net/bugs/1443942>
[12:39] <mup> Bug #1540832 changed: Hard wired bridge prevents the use of the fan overlay network <network> <juju-core:Triaged> <https://launchpad.net/bugs/1540832>
[12:39] <mup> Bug #1608723 changed: "juju test" command needs updating for juju 2.0 <juju-core:Invalid> <https://launchpad.net/bugs/1608723>
[12:39] <mup> Bug #1535891 opened: Feature request: Custom/user definable cloud-init user-data <juju-core:Triaged> <https://launchpad.net/bugs/1535891>
[13:03] <dimitern> babbageclunk: updated http://reviews.vapour.ws/r/5356/ can you have a second look please?
[13:03] <babbageclunk> dimitern: yup, looking now
[13:04] <dimitern> babbageclunk: ta!
[13:06] <dimitern> babbageclunk: and if you can also have a look at https://github.com/juju/juju/pull/5871 at some point will be awesome! :)
[13:15] <mup> Bug #1608723 opened: "juju test" command needs updating for juju 2.0 <juju-core:New> <https://launchpad.net/bugs/1608723>
[13:15] <mup> Bug #1608938 opened: clientSuite.SetUpTest mongo could not create index <ci> <intermittent-failure> <mongodb> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1608938>
[13:15] <mup> Bug #1608942 opened: UpgradeCharmSuccessSuite.SetUpTest cannot set admin password <ci> <intermittent-failure> <mongodb> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1608942>
[13:19] <babbageclunk> dimitern: looking at 5871 now - why no RB for it?
[13:19] <dimitern> babbageclunk: dunno - perhaps due to formatting of the description the RB bot didn't pick it up ..
[13:30] <mup> Bug #1608947 opened: MSpan_Sweep: bad span state after sweep in github.com/juju/juju/api/provisioner <ci> <go1.6> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1608947>
[13:39] <mup> Bug #1608947 changed: MSpan_Sweep: bad span state after sweep in github.com/juju/juju/api/provisioner <ci> <go1.6> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1608947>
[13:45] <mup> Bug #1608947 opened: MSpan_Sweep: bad span state after sweep in github.com/juju/juju/api/provisioner <ci> <go1.6> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1608947>
[13:46] <mup> Bug #1608952 opened: Deployer: KeyError: 'uuid' connecting to environment <ci> <deployer> <regression> <juju-core:Triaged> <juju-deployer:New> <https://launchpad.net/bugs/1608952>
[13:46] <mup> Bug #1608956 opened: local charms can be deleted while still referenced <juju-core:Triaged> <https://launchpad.net/bugs/1608956>
[13:49] <mup> Bug #1608952 changed: Deployer: KeyError: 'uuid' connecting to environment <ci> <deployer> <regression> <juju-core:Triaged> <juju-deployer:New> <https://launchpad.net/bugs/1608952>
[13:49] <mup> Bug #1608956 changed: local charms can be deleted while still referenced <juju-core:Triaged> <https://launchpad.net/bugs/1608956>
[13:49] <perrito666> morning, I am OCR so ill be reviewing stuff :)
[13:55] <mup> Bug #1608952 opened: Deployer: KeyError: 'uuid' connecting to environment <ci> <deployer> <regression> <juju-core:Triaged> <juju-deployer:New> <https://launchpad.net/bugs/1608952>
[13:55] <mup> Bug #1608956 opened: local charms can be deleted while still referenced <juju-core:Triaged> <https://launchpad.net/bugs/1608956>
[14:05] <dimitern> babbageclunk: review poke ? :)
[14:06] <babbageclunk> dimitern: Still reading - sorry, was interrupted by call with alexisb.
[14:06] <babbageclunk> nearly done
[14:06] <dimitern> babbageclunk: no worries
[14:11] <babbageclunk> dimitern: done!
[14:11] <dimitern> babbageclunk: tyvm!
[14:13] <mup> Bug #1608959 opened: deleted local charms not removed from caches <juju-core:Triaged> <https://launchpad.net/bugs/1608959>
[14:13] <rick_h_> fwereade: are you up for cleaning the charm/cache problems 'the right way'?
[14:14] <rick_h_> fwereade: if you are cool with it would love to tackle those together with a central plan that removes the array of issues we're nipping at from different directions
[14:14] <fwereade> rick_h_, I... really rather sort of am, yeah
[14:14] <rick_h_> fwereade: cool, let's break down the steps then for the kanban board and make sure to collect the array of bugs that we're targeting to make sure they fall away when the work is complete.
[14:15] <fwereade> rick_h_, ack, will try to pull it all together
[14:15] <rick_h_> fwereade: <3 ty much
[14:18] <katco> fwereade: hey, i'm not sure what to do based on your email (i.e. which "fix" is "the fix" :)). are we ok to go ahead with the fix we discussed yesterday?
[14:25] <fwereade> katco, heh, I was sort of raising a big heap of related issues for general consideration
[14:26] <fwereade> katco, yesterday we were saying "delete the charm data, keep the doc, see what happens"?
[14:26] <katco> fwereade: yeah, it looks like our charm caching is in a bad way atm
[14:26] <katco> fwereade: yeah, that's what i have proposed
[14:27] <fwereade> katco, ah, hadn't spotted that -- I'll take a look
[14:27] <katco> fwereade: http://reviews.vapour.ws/r/5344/
[14:27] <katco> fwereade: it already has a ship it, i just wanted to see where we're at with ian's input, and if you were raising additional points
[14:28] <fwereade> katco, but, yeah, the worst consequence I can think of is the occasional failed download as a result of the related issues that are too big to drag in
[14:28] <katco> fwereade: yep
[14:28] <fwereade> katco, and that's mitigated by the evil caching anyway
[14:28] <fwereade> katco, so, yeah, I think it's the best step forward
[14:28] <katco> fwereade: ok, cool. i'll go ahead and land
[14:28] <katco> fwereade: ta
[14:29] <fwereade> katco, fix the docstring on deleteCharmarchive if you haven't triggered yet
[14:29] <katco> fwereade: np i can do that
[14:29] <fwereade> katco, ta
[14:31] <katco> rick_h_: looks like master is blocked. what do i do?
[14:31] <rick_h_> katco: mark your card as blocked and put it in landing please
[14:31] <rick_h_> katco: and let's see what's up and what needs to happen to unblock master
[14:32] <katco> rick_h_: apparently it's blocked on the other bug i am to be working on
[14:32] <rick_h_> katco: k, then leave the current card in landing/blocked and grab the other one please
[14:32] <katco> rick_h_: so i am my own grandma and i am blocking myself
[14:33] <rick_h_> katco: :)
[14:33] <rick_h_> katco: more like someone didn't stack the bugs in order of actual todo priority
[14:33]  * rick_h_ hides real quick 
[14:33] <katco> rick_h_: oh... jujubot has accepted my merge request... odd
[14:34] <katco> juju.fail is lying to me i suppose. i wish ci just had a dashboard
[14:37] <dimitern> katco: you can checkout the python script check-blockers from juju-ci-tools and run it trivially btw ;)
[14:38] <katco> dimitern: thanks, i might just start doing that. i dunno why ci can't provide that info on our dashboard though
[14:39] <dimitern> that's a good question... not a priority I guess
[14:46] <rick_h_> dimitern: katco we'll take that into advisement as we work on the new workflows/processes
[14:46] <dimitern> rick_h_: +1
[14:47] <katco> rick_h_: good luck. i raised that 2 years ago haha
[14:53] <perrito666> k I am about to tackle the queue as it is, anyone needs an urgent review before that?
[14:57] <natefinch> oh distro packages, you're so wacky.  installing the golang package installs gcc and make and some perl crap... geez
[14:58] <andrey-mp> Hi, I've asked a question about glance-charm in the OpenStack dev mailing list - http://lists.openstack.org/pipermail/openstack-dev/2016-August/100660.html  is it a suitable place for the question or there is a better place present?
[15:00] <perrito666> natefinch: odd, why would it install gcc?
[15:01] <dimitern> natefinch: simply golang or golang-go ? the latter shouldn't depend on gcc
[15:01] <perrito666> andrey-mp: hi there, I think #juju is a more suitable place but you are free to ask and if someone knows the answer will gladly tell it to you
[15:01] <natefinch> dimitern: golang... I certainly don't know the difference between thw two
[15:02] <andrey-mp> perrito666: thanks, will ask in #juju
[15:02] <natefinch> perrito666: http://pastebin.ubuntu.com/21900049/
[15:02] <dimitern> natefinch: one is a metapackage, the other specifically using the gc toolchain
[15:02] <dimitern> (IIRC)
[15:02] <perrito666> natefinch: it most likely depends on build-essentials
[15:02] <perrito666> ah, yes it does
[15:03] <perrito666> natefinch: build essential is the bag of stuff that is required to build pretty much everything (in terms of tools)
[15:03] <perrito666> dimitern: you notice rb failing earlier?
[15:04] <perrito666> dimitern: I am getting a 500
[15:05] <natefinch> perrito666: evidently not actually essential ¯\_(ツ)_/¯
[15:06] <perrito666> natefinch: the name made sense when it was crafted
[15:07] <perrito666> natefinch: ideally in any debian based distro you install build-essential and apt-get build-dep from whatever package you want and you can compile it by hand
[15:09] <perrito666> mgz: sinzui abentley could any of you take a peek at the rb server? I am getting a consistent 500, I will put all my chips in lack of space
[15:09] <natefinch> lol, but golang *doesn't* depend on bzr.  Nice.
[15:10] <sinzui> perrito666: what is rb?
[15:10] <natefinch> reviewboard
[15:10] <katco> perrito666: working for me
[15:11] <sinzui> natefinch: you marked bug 1604474 as fixed but ci still cannot deploy windows charms. I can when we rest with juju from the first week of July
[15:11] <mup> Bug #1604474: Juju 2.0-beta12  userdata execution fails on Windows <azure-provider> <ci> <juju2.0> <oil> <oil-2.0> <regression> <windows> <juju-core:Fix Committed by natefinch> <https://launchpad.net/bugs/1604474>
[15:12] <natefinch> sinzui: uh, weird.  Ok, I'll have to look at it again.
[15:22] <perrito666> katco: strange, It seems to be a random failure
[15:22] <perrito666> katco: would you try to enter this for me? http://reviews.vapour.ws/r/5355/
[15:23] <katco> perrito666: weird, that gives me a 500
[15:24] <perrito666> It is a django, so that must be logging errors somwehere
[15:48] <rick_h_> natefinch: heads up https://bugs.launchpad.net/juju-core/+bug/1604474
[15:48] <mup> Bug #1604474: Juju 2.0-beta12  userdata execution fails on Windows <azure-provider> <ci> <juju2.0> <oil> <oil-2.0> <regression> <windows> <juju-core:In Progress by natefinch> <https://launchpad.net/bugs/1604474>
[15:49] <rick_h_> natefinch: moved the card back to the high prio lane for after the current work/pr to see if we can understand why they're still seeing it
[15:53]  * rick_h_ goes out for lunchables today
[16:25] <mup> Bug #1609041 opened: Race in github.com/juju/juju/cmd/modelcmd <ci> <race-condition> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1609041>
[17:07] <perrito666> bbl lunch
[17:13] <natefinch> gah, gotta call an electrician... the outlet for our electric range is only feeding it 120, not 240, so I can't cook anything :/
[17:23] <mgz> natefinch: rediscover fire
[17:28] <perrito666> Natefinch most likely you have a breaker for one phase that you only use for that
[17:36] <rogpeppe> here's a fix to UpdateCloudCredentials. a review would be much appreciated, thanks! https://github.com/juju/juju/pull/5917
[17:37] <natefinch> perrito666: there's a double breaker just for the stove, but toggling it doesn't help.  Google says it's likely either a bad breaker or bad outlet.
[17:39] <perrito666> Do you have a multimeter?
[17:40] <perrito666> If so measure the input to the breaker
[17:41] <perrito666> And make sure that you measure between two  phases otherwise you will get 120
[17:43] <natefinch> I do have a multimeter, but I don't think I can get at the input to the breaker without taking the breaker box apart
[17:43] <natefinch> and whether it's the outlet or the breaker - I'm not doing that myself.  I could in theory do the outlet, but I doubt my wife would let me.
[17:45] <perrito666> Geek up
[19:15]  * rick_h_ goes to do kid duty, back later. 
[20:25] <alexisb> so natefinch, everytime I have to bootstrap without the interactive stuff I get annoyed :)
[20:25] <alexisb> liking the interactive bootstrap
[21:01] <katco> any python enthusiasts want to help me debug installing ci tools?
[21:04] <rick_h_> katco: what's up?
[21:05]  * rick_h_ dusts off python stuff
[21:06] <katco> rick_h_: getting an error after doing make install-deps. retrying after tweaking something... looks like it's potentially gotten past the error point
[21:07] <rick_h_> katco: k, let me know how it goes
[21:08] <katco> rick_h_: yep, different error this time; timeout. looks like it's doing something with s3...
[21:10]  * katco is now debugging a python script to install dependencies for a CI system so she can debug an actual Go bug in Juju
[21:11]  * katco feels fantastic about this
[21:14] <katco> i just tried re-running the test and it looks like it's doing something, so i'll just hope i don't need whatever this script is trying to download
[21:17] <rick_h_> katco: heh ok, welcome to the polyglot future :-)
[21:18] <katco> rick_h_: been there for awhile :)
[21:23] <perrito666> I either need to stop nodding on standups or buy a webcam
[21:34] <menn0> katco: ping
[21:34] <katco> menn0: pong
[21:34] <menn0> katco: how's bug 1603221 going?
[21:34] <mup> Bug #1603221: Charms utilizing storage fail on LXD <blocker> <jujuqa> <lxd-provider> <storage> <juju-core:In Progress by cox-katherine-e> <https://launchpad.net/bugs/1603221>
[21:34] <menn0> katco: is there a need for handoff before you finish up?
[21:35] <katco> menn0: i just started to try and reproduce today; nothing to really hand off atm
[21:35] <menn0> katco: ok cool.
[21:35] <menn0> katco: is it really worthy of blocker status?
[21:36] <katco> menn0: that i don't know. maybe not since it's limited to 1 feature on 1 substrate
[21:36] <menn0> katco: cool. I'll bring it up in the standup.
[21:37] <katco> menn0: cool. i'm not sure who deems things blockers these days
[21:37] <menn0> katco: in this case it was alexisb
[21:37] <menn0> :)
[21:38] <katco> menn0: ah. well maybe she can give some more info as to why
[21:38] <menn0> katco: that's what I'm thinking
[21:40] <alexisb> menn0, we are on lock down
[21:40] <alexisb> it gets decided in the release call
[21:41] <alexisb> we are working towards a bless for this weeks release
[21:42] <menn0> alexisb: ok cool
[23:06] <veebers> I'm seeing this error repeated in my mongodb deploy log (for a ci test) Not sure what may cause it: ERROR juju.worker.dependency engine.go:539 "leadership-tracker" manifold worker returned unexpected error: leadership failure: lease manager stopped
[23:33] <veebers> sigh, might need another coffee. Just tried --veebers instead of --version :-\
[23:34] <axw> lol
[23:34] <anastasiamac> new option \o/
[23:34] <veebers> hah, I would hate to think what it did
[23:36] <anastasiamac> functional test coverage? :)
[23:36] <veebers> heh :-)
[23:44] <menn0> veebers: that's not good. which version of Juju?
[23:45] <menn0> veebers: and do you have full logs?
[23:47] <veebers> menn0: I realised before it was a slightly older version (2.0-beta13-xenial-amd64)
[23:48] <veebers> menn0: I can put that log up somewhere if it's useful. I'm just about to try a run with beta14 if that'll be of more interest
[23:51] <menn0> veebers: it would be good to confirm if the problem still exists in a later version
[23:51] <menn0> veebers: I think fwereade_ has been doing some work to fix things in this area
[23:52] <veebers> menn0: ack. I'll put these current logs aside so they don't get destroyed and do a couple of runs with a newer juju binary
[23:53] <menn0> veebers: great, thanks
[23:53] <veebers> nw