[00:00] <menn0> thumper: yep naked send
[00:00]  * menn0 checks master
[00:01] <menn0> thumper: fixed in master but not 1.24
[00:01]  * menn0 backports
[00:42] <thumper> cmars: are you going to merge your branch?
[00:42] <cmars> thumper, i'd like to
[00:42] <cmars> thumper, master's blocked
[00:43] <thumper> I've committed a fix
[00:43] <thumper> cmars: please JFDI it
[00:43] <cmars> thumper, with pleasure
[00:51] <thumper> menn0: thanks for the backport
[00:52] <menn0> thumper: np. hopefully my PR will make it through once this is in
[01:09] <katco> cherylj: still there?
[01:12] <thumper> wallyworld: I'm having a lateish lunch with Rachel
[01:12] <thumper> wallyworld: will probably be late for our 1:1
[01:12] <wallyworld> sure, np
[01:29] <natefinch> evening all
[01:39] <natefinch> man I really hate linux utilities' default of "don't tell the user wtf is going on"
[01:46] <thumper> wallyworld: back
[01:46] <thumper> wallyworld: good now?
[01:47] <wallyworld> sure
[02:00] <wallyworld> axw: just finishing up, be there in a sec
[02:00] <axw> wallyworld: thanks for reminding me ;)
[02:12] <thumper> cmars: http://reports.vapour.ws/releases/2890/job/run-unit-tests-win2012-amd64/attempt/908
[02:12] <thumper> cmars: another intermittent metics collection failure
[02:13]  * thumper sighs
[02:13] <thumper> cmars: I'm wondering if all the extra tests in uniter also pushed the ppc timeout over 10 minutes
[02:20]  * thumper is looking at http://reports.vapour.ws/releases and feeling sad
[02:31] <thumper> menn0_: got a minute to talk through another intermittent failure?
[02:31] <menn0_> thumper: yep
[02:31] <thumper> menn0_: standup hangout
[02:32] <thumper> menn0_: click "join" :)
[02:33] <menn0_> thumper: it's not that. I have to re-auth and it wants a new password
[02:33] <thumper> ah
[02:50] <natefinch> anyone seen a gccgo error where it thinks you've multiply defined things that are not multiply defined?
[02:53] <natefinch> thumper: ^ ?   I seem to remember a bug we've hit with gccgo in the past where like embedding things the wrong way will make gccgo mad.  Do you happen to remember what caused that?
[02:56] <natefinch> nvm, pretty sure it's this: https://github.com/golang/go/issues/7627    which is fixed in go 1.3 .... which does not help us
[03:04] <thumper> decisions, decisions
[03:05] <thumper> wanting a new laptop bag
[03:05] <thumper> trying to decide between black or red
[03:05] <natefinch> if not-black is an option you like, go with not-black.  There's too much black in everything tech
[03:07]  * natefinch looks at his black keyboard, black monitor stands, black headset, black camera strap, black camera, black CD player... all just on his desk
[03:54]  * thumper chose black
[03:55] <thumper> it was pointed out how grubby red would look when a little dirty
[05:40] <thumper> ok, I'm done
[05:40] <thumper> drink time
[05:40] <thumper> laters folks
[07:05] <mup> Bug #1475509 opened: upgrade-charm --force behavior causes races <juju-core:New> <https://launchpad.net/bugs/1475509>
[09:04] <TheMue> dooferlad: hangout, and do you know where dimitern is?
[09:04] <dooferlad> TheMue: No, I don't. I think we should wait for him.
[09:04] <dimitern> here I am
[09:04] <dooferlad> ah
[09:04] <dimitern> sorry guys :)
[09:04] <TheMue> hehe
[09:04] <dooferlad> no worries. Joining
[10:06] <dimitern> tgif :) why do meteors always land in craters :D http://9gag.com/gag/aPGB9YV?ref=fbp
[10:08] <dimitern> ^^ if I heat my SSD drive until it becomes a gaseous state hard drive would that enable cloud computing? <<- good idea for a juju plugin
[10:17] <mup> Bug #1475565 opened: juju expose should allow ip/port restrictions <juju-core:New> <https://launchpad.net/bugs/1475565>
[10:29] <mup> Bug #1475565 changed: juju expose should allow ip/port restrictions <juju-core:New> <https://launchpad.net/bugs/1475565>
[10:35] <mup> Bug #1475565 opened: juju expose should allow ip/port restrictions <juju-core:New> <https://launchpad.net/bugs/1475565>
[11:36] <fwereade> perrito666, ping
[11:48] <dimitern> dooferlad, check out bug 1474946 btw and thumper's fix http://reviews.vapour.ws/r/2190/diff/#
[11:48] <mup> Bug #1474946: kvmBrokerSuite worker/provisioner: tests are poorly isolated <blocker> <ci> <regression> <test-failure> <juju-core:Fix Committed by thumper> <https://launchpad.net/bugs/1474946>
[11:49] <dimitern> dooferlad, I believe the kvm broker shouldn't need to call EnsureRootFS.. as it only applies to lxc broker tests with lxc-clone: true (when we have the template)
[11:54] <fwereade> perrito666, what's the source of the differences in SetStatus on unit vs service in state?
[12:00] <fwereade> perrito666, and for that matter unitagent?
[12:17] <perrito666> fwereade: sorry was @gym
[12:17] <fwereade> perrito666, no worries, I expect asynchronicity :)
[12:18] <perrito666> fwereade: I feel your comment a bit context lacking
[12:19] <fwereade> perrito666, so, we have 4 SetStatus methods in state
[12:19] <fwereade> perrito666, they're all basically setting the same document, and they're all different
[12:19] <fwereade> perrito666, do you know what the source of the differences is, and/or if there are any plans to fix this?
[12:22] <fwereade> perrito666, some gate on entity life, some don't; some error out when the entity disappears, some don't; some use buildTxn functions, some don't; some follow the very few documented guidelines for state methods, some don't...
[12:31] <perrito666> fwereade: there are different rules for each entity, they satisfy state.StatusSetter, they could be a bit smaller and cleaned of redundant code tho
[12:31] <fwereade> perrito666, what are the differences that aren't encoded in the newFooStatusDoc funcs?
[12:34] <perrito666> fwereade: little to nothing, there is some extra resilience around service status and machine status has no history
[12:35] <perrito666> oh and unit agent has a slightly different op
[12:36] <mup> Bug #1475635 opened: Subordinate can break juju run for principal service <juju-core:New> <https://launchpad.net/bugs/1475635>
[12:37] <perrito666> omg you've got to be kidding me one of my monitors will do a humming noise unless brightness is set in 56-60 or >95 levels
[12:37] <perrito666> it has been driving me crazy since last night
[12:38] <wwitzel3> katco: ping?
[12:41] <fwereade> perrito666, do you know the reasons behind the various differences?
[12:41] <fwereade> perrito666, eg, when implementing history, why *didn't* we do machine status?
[12:41] <perrito666> partly
[12:42] <fwereade> perrito666, why does service status need extra resilience, but not the others?
[12:42] <fwereade> perrito666, why doesn't the unit agent check its entity? etc
[13:09] <mup> Bug #1475641 opened: Bug in hooks can make jujud unresponsive <juju-core:New> <https://launchpad.net/bugs/1475641>
[13:27] <mup> Bug #1475386 opened: unit not dying after failed hook + destroy-service <destroy-service> <juju-core:Triaged> <https://launchpad.net/bugs/1475386>
[13:37] <perrito666> is anywone working on https://bugs.launchpad.net/juju-core/+bug/1474946 ?
[13:37] <mup> Bug #1474946: kvmBrokerSuite worker/provisioner: tests are poorly isolated <blocker> <ci> <regression> <test-failure> <juju-core:Fix Committed by thumper> <https://launchpad.net/bugs/1474946>
[13:37] <perrito666> says thumper there but I think he is no longer here
[13:51] <fwereade> perrito666, I've figured out why RB2148 is making me uncomfortable
[13:52] <fwereade> perrito666, lots of the changes are to the tests, changing the way they reach into the internals of state to "test" it
[13:53] <fwereade> perrito666, which means that none of them are testing the important things -- what happens in real life when people call particular state methods -- they're *all* testing how the methods work when someone makes a specific change to the db
[13:54] <fwereade> perrito666, so those tests become less accurate, and potentially have to be rewritten, every time someone changes the status code
[13:56] <fwereade> perrito666, if you test to the exported interface you can change the implementation and have some confidence that it works how it used to
[13:58] <dooferlad> TheMue, dimitern: http://reviews.vapour.ws/r/2197/ please!
[13:58] <TheMue> dooferlad: *click*
[13:58] <katco> wwitzel3: here now
[14:07] <dimitern> dooferlad, looking
[14:08] <TheMue> dooferlad: reviewed
[14:12] <fwereade> dooferlad, one significant comment
[14:13] <fwereade> TheMue, I am a bit disappointed you didn't spot that...
[14:13] <TheMue> fwereade: pardon?
[14:14] <fwereade> TheMue, non-bulk api call
[14:14] <TheMue> fwereade: iiirks, yes
[14:15] <fwereade> TheMue, ehh, it's friday afternoon, these things happen
[14:16] <TheMue> fwereade: but should not
[14:18] <perrito666> fwereade: too bad you realized after I pulled it :p
[14:18] <perrito666> I change it
[14:20] <fwereade> is anyone feeling up to speed on the ugly details of destroy-environment in JES?
[14:22] <sinzui> dimitern: katco : can you ask someone to triage this issue? I cannot say if the issue is the local machine or a juju bug, and if it is a juju bug, is it something that needs fixing in 1.25 https://bugs.launchpad.net/juju-core/+bug/1474885
[14:22] <mup> Bug #1474885: juju deploy fails with ERROR EOF <local-provider> <precise> <juju-core:New> <https://launchpad.net/bugs/1474885>
[14:24] <katco> cherylj: perrito666: dimitern: moonstone is in meetings for the next 4 hours. can one of you TAL?
[14:27] <dimitern> sinzui, katco, will do
[14:27] <katco> dimitern: ty
[14:27] <dimitern> dooferlad, I have not finished yet, but do have a few comments already, please wait for my review first
[14:33] <katco> ericsnow: meeting time
[14:33] <ericsnow> katco: omw
[14:37] <katco> akhavr: o/
[14:40] <dimitern> dooferlad, reviewed
[14:41] <dooferlad> dimitern: thanks
[14:41] <dooferlad> fwereade: thanks as well
[14:43] <dooferlad> dimitern: guess I should have tried harder for a pair programming session earlier!
[14:43] <dimitern> dooferlad, :) no worries
[14:43] <dimitern> we can still do it, but it's getting a bit late for me ;/
[14:44] <dooferlad> dimitern: can you do 30 minutes? Clearly there was some stuff I just hadn't encountered before and combining that with a little too much copy and paste has set me off in the wrong direction.
[14:46] <dooferlad> dimitern: though I guess it is mostly that I should have gone back and looked at the spec again and need to know about the significance of bulk API calls.
[14:46] <dimitern> dooferlad, sure, let's use the standup g+
[14:48] <dimitern> dooferlad, juju-sapphire
[15:00] <mup> Bug #1475565 changed: juju expose should allow ip/port restrictions <expose> <improvement> <juju-core:Triaged> <https://launchpad.net/bugs/1475565>
[15:06] <natefinch> davecheney: about that  bug I emailed you about.  It was marked as fixed in 1.3, but we're running 1.2.1 officially.  I'm not sure how that interacts with the gccgo version, but it seems like maybe we're not yet running a version that has that fix?
[15:26] <natefinch> sinzui: davecheney says that enabling trusty updates should fix that ppc issue... is that something that we're allowed to do on the stilson machines?
[15:26] <sinzui> natefinch: they are supposed to be on...ubuntu doesn't not support machines that do not accept updates
[15:27] <sinzui> natefinch: I think they must have been turned off when diagnosing other issues.
[15:27] <natefinch> sinzui: my local machine has gcgo 4.9.1-16ubuntu6, but stilson-07 has 4.9.1-13ubuntu1
[15:28] <sinzui> :/
[15:28] <natefinch> sinzui: oh, forgot I'm not on trusty anymore
[15:28] <natefinch> sinzui: just utopic, though
[15:30] <sinzui> natefinch: trusty-updates are already enabled on stilson-09
[15:31] <katco> natefinch: wwitzel3: planning time
[15:32] <wwitzel3> katco: brt
[15:32] <natefinch> me too
[15:32] <natefinch> sinzui: weird, that one has gccgo 4.9.1-1ubuntu3
[15:33] <natefinch> at least we're consistently inconsistent
[15:37] <sinzui> natefinch: yes, stilson 6-8 permanently dirty. That is why we want the tests to pass in lxc so we can run them in a clean disposable env
[15:46] <natefinch> sinzui: can I mark the bug failure as "invalid because it's running on a dirty machine"?  https://bugs.launchpad.net/juju-core/+bug/1471657
[15:46] <mup> Bug #1471657: linker error in procsPersistenceSuite unit test on ppc64 <ci> <ppc64el> <test-failure> <unit-tests> <juju-core:Triaged> <juju-core feature-proc-mgmt:Triaged> <https://launchpad.net/bugs/1471657>
[15:46] <sinzui> natefinch: 09 is not dirty
[15:47] <natefinch> sinzui: oh, sorry, misread, thanks for the clarification
[16:40] <rogpeppe> natefinch: you might want to take a look at this - it's a little cache package that i've just moved out of charmstore internal into juju/utils: https://github.com/juju/utils/pull/144
[16:44] <natefinch> rogpeppe: nice.  Needs a package level comment, though.
[16:44] <rogpeppe> natefinch: good point
[16:45] <mup> Bug #1474382 changed: MeterStateSuite teardown failure on windows <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by bteleaga> <https://launchpad.net/bugs/1474382>
[16:45] <mup> Bug #1474946 changed: kvmBrokerSuite worker/provisioner: tests are poorly isolated <blocker> <ci> <regression> <test-failure> <juju-core:Fix Released by thumper> <https://launchpad.net/bugs/1474946>
[16:45] <mup> Bug #1475724 opened: UniterSuite.TestUniterRelations <blocker> <ci> <ppc64el> <regression> <unit-tests> <windows> <juju-core:Triaged> <juju-core jes-cli:Triaged> <https://launchpad.net/bugs/1475724>
[16:51] <davecheney> wallyworld: ping
[16:51] <davecheney> oh, sorry, it's saturday
[16:51] <alexisb> davecheney, it is also very early for him
[16:54] <perrito666> alexisb: early as in friday night :p
[16:54] <perrito666> its around 3AM for ian
[16:55] <katco> davecheney: you people from the western hemisphere wouldn't understand.
[16:55] <alexisb> AM == morning
[16:56] <perrito666> alexisb:  I place the line between late and early around 5AM
[16:56] <natefinch> 4am == night time, I agree with that :)
[16:56] <perrito666> which is the time when, if I wake up Ill go with a coffee instead of more sleep
[16:57] <mup> Bug #1475724 changed: UniterSuite.TestUniterRelations <blocker> <ci> <ppc64el> <regression> <unit-tests> <windows> <juju-core:Triaged> <juju-core jes-cli:Triaged> <https://launchpad.net/bugs/1475724>
[16:57] <mup> Bug #1474382 opened: MeterStateSuite teardown failure on windows <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by bteleaga> <https://launchpad.net/bugs/1474382>
[16:57] <mup> Bug #1474946 opened: kvmBrokerSuite worker/provisioner: tests are poorly isolated <blocker> <ci> <regression> <test-failure> <juju-core:Fix Released by thumper> <https://launchpad.net/bugs/1474946>
[16:59] <jcastro> Does anyone have a quick tldr on Juju/LXD support? I'd like to answer this question: http://askubuntu.com/questions/643658/lxd-and-juju-management
[17:04] <mup> Bug #1474382 changed: MeterStateSuite teardown failure on windows <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by bteleaga> <https://launchpad.net/bugs/1474382>
[17:04] <mup> Bug #1474946 changed: kvmBrokerSuite worker/provisioner: tests are poorly isolated <blocker> <ci> <regression> <test-failure> <juju-core:Fix Released by thumper> <https://launchpad.net/bugs/1474946>
[17:04] <mup> Bug #1475724 opened: UniterSuite.TestUniterRelations <blocker> <ci> <ppc64el> <regression> <unit-tests> <windows> <juju-core:Triaged> <juju-core jes-cli:Triaged> <https://launchpad.net/bugs/1475724>
[17:12] <davecheney> natefinch: that bug you emailed me about earlier
[17:12] <davecheney> i'm pretty sure that is fixed
[17:12] <davecheney> and has been fixed for a long time
[17:12] <davecheney> _but_ there is a catch
[17:12] <davecheney> it's not available for 14.04 out of the box
[17:12] <davecheney> even in 14.04.2
[17:12] <davecheney> you _have_ to enable trusty-updates to get it
[17:14] <natefinch> davecheney: sinzui says trusty updates is enabled on the ppc machines
[17:14] <natefinch> sinzui: silson-09 says that gccgo is installed and set to "manual"... does that mean it's not getting updates?
[17:14] <davecheney> the magic package is libgo5
[17:15]  * davecheney struggles to contain his rage
[17:15] <davecheney> WE OWN THE DISTRIBUTION
[17:15] <davecheney> WHY CAN WE NOT ACTUALLY SHIP UPDATES FOR SHIT WE MAINTAIN
[17:15] <natefinch> s/silson/stilson/
[17:15] <davecheney> phase 1. fix bug
[17:15] <davecheney> phase 2. ???
[17:15] <davecheney> phase 3. nobody actually gets the bug fix
[17:15] <davecheney> ffs
[17:15] <natefinch> afk for 15-ish or so, sorry.  Kids need naps
[17:16] <sinzui> davecheney: the machine always had updates on, but the issue might be that trusty didn't officiall support ppc4el. Its packages come from ports.ubuntu.com
[17:16] <davecheney> natefinch: just emailed you the background
[17:17] <davecheney> actually no
[17:17] <davecheney> that was the wrong email thread
[17:19] <davecheney> natefinch: i cannot find it now
[17:19] <davecheney> but the summary was
[17:19] <davecheney> "no versions of our LTS release ship with a working gccgo, you must be using the updated versions from trusty-updates"
[17:22] <rogpeppe> davecheney: i'd appreciate a glance at https://github.com/juju/utils/pull/144 if you have a few moments.
[17:22]  * davecheney looks
[17:22] <davecheney> rogpeppe: safe flight back to blighty ?
[17:22] <rogpeppe> davecheney: yup, no probs at all
[17:22] <rogpeppe> davecheney: you still in US ?
[17:27]  * rogpeppe leaves
[17:55] <katco> wwitzel3: i'm ready to party.
[18:12] <wwitzel3> katco: ok, I'm running a bit behind, lots of plates spinning
[18:12] <katco> wwitzel3: np, lemme know when you're ready
[19:14] <alexisb> perrito666, ping
[19:14] <perrito666> alexisb: pong
[19:14] <alexisb> are you still working this bug w/ menno:
[19:14] <alexisb> https://bugs.launchpad.net/juju-core/+bug/1474606
[19:14] <mup> Bug #1474606: $set updates may clear out the env-uuid field <juju-core:Triaged by menno.smits> <juju-core 1.24:Triaged by menno.smits> <https://launchpad.net/bugs/1474606>
[19:15] <perrito666> alexisb: I added a fix for the original issue, but as I understand menn0 was working on some additional code to do a more general fix
[19:15] <alexisb> perrito666, ok
[19:16] <alexisb> sinzui, we are still blocked on 1474606
[19:16] <sinzui> alexisb: understood
[20:52] <mup> Bug #1475779 opened: EnsureJujudPassword fails if the registry keys are not present <juju-core:New for bteleaga> <https://launchpad.net/bugs/1475779>
[21:45] <katco> jw4: hey didn't you do a relation state diagram at some point?
[21:53] <jw4> katco: yeah - a first pass
[21:53] <jw4> it should be in the docs folder
[21:54] <katco> jw4: do you remember where that is? i couldn't find it
[21:54] <katco> jw4: oh, hm. nothing jumped out at me there
[21:54] <jw4> katco: I think it's doc/uniter-model.txt
[21:55] <jw4> katco: pretty thin
[21:55] <katco> jw4: no worries, ty
[21:55] <jw4> :e
[21:55] <jw4> um... that was supposed to be :)
[21:55] <katco> jw4: haha thought you were in vim for sec
[21:56] <jw4> exactly
[22:35] <mbruzek> rick_h_: ping
[22:37] <mbruzek> I have a bundle question rick_h_