[09:24] <mup> Bug #1596462 opened: Deployment failed because state DB is locked <ci> <deploy> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1596462>
[09:27] <mup> Bug #1596462 changed: Deployment failed because state DB is locked <ci> <deploy> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1596462>
[09:42] <mup> Bug #1596045 changed: Juju says windows mongo: invalid version <blocker> <ci> <mongodb> <regression> <windows> <juju-core:Fix Released by 2-xtian> <https://launchpad.net/bugs/1596045>
[09:42] <mup> Bug #1596462 opened: Deployment failed because state DB is locked <ci> <deploy> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1596462>
[10:01] <mup> Bug #1596476 opened: juju charm resources does not map application name to charmstore url <juju-core:New> <https://launchpad.net/bugs/1596476>
[10:46] <mup> Bug #1596493 opened: github.comjuju/juju/apiserver package: first record does not look like a TLS handshake <blocker> <ci> <regression> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1596493>
[10:55] <mup> Bug #1596493 changed: github.comjuju/juju/apiserver package: first record does not look like a TLS handshake <blocker> <ci> <regression> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1596493>
[10:58] <mup> Bug #1596493 opened: github.comjuju/juju/apiserver package: first record does not look like a TLS handshake <blocker> <ci> <regression> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1596493>
[11:10] <mup> Bug #1596496 opened: Bootstrap should fail early if '-d controller' is specified <bitesize> <bootstrap> <juju-core:Triaged> <https://launchpad.net/bugs/1596496>
[13:18] <lazyPower> ey core, thanks for getting beta10 out the door Friday. *fires up the user-testing engine*
[13:19] <perrito666> lazyPower: our pleasure :p
[13:26] <dimitern> lazyPower: what's that engine btw?
[13:27] <lazyPower> dimitern my fingers and possibly duplicate bug reports ;)
[13:27]  * dimitern is interested in all sorts of testing automation we can share and reuse
[13:27] <dimitern> ah :)
[13:27] <dimitern> lazyPower: ok then, hope it goes fine :)
[13:34] <lazyPower> dimitern so far so good :) Yinzers do good work.
[13:34] <mup> Bug #1576985 changed: aggregateSuite.TestBatching wrong size <ci> <intermittent-failure> <unit-tests> <windows> <juju-core:Invalid> <https://launchpad.net/bugs/1576985>
[13:35] <dimitern> lazyPower: Yinzers ?
[13:35] <lazyPower> Thats Pittsburghese for "You all"
[13:43] <dimitern> :)
[13:43] <mup> Bug #1576985 opened: aggregateSuite.TestBatching wrong size <ci> <intermittent-failure> <unit-tests> <windows> <juju-core:Invalid> <https://launchpad.net/bugs/1576985>
[13:52] <mup> Bug #1559400 changed: TestManageModelRunsRegisteredWorkers is flaky <intermittent-failure> <juju-core:Invalid> <https://launchpad.net/bugs/1559400>
[13:52] <mup> Bug #1576985 changed: aggregateSuite.TestBatching wrong size <ci> <intermittent-failure> <unit-tests> <windows> <juju-core:Invalid> <https://launchpad.net/bugs/1576985>
[13:52] <mup> Bug #1580802 changed: NoContextWithLock fails on windows because of another process <ci> <intermittent-failure> <regression> <unit-tests> <windows> <juju-core:Invalid> <https://launchpad.net/bugs/1580802>
[13:55] <mup> Bug #1559400 opened: TestManageModelRunsRegisteredWorkers is flaky <intermittent-failure> <juju-core:Invalid> <https://launchpad.net/bugs/1559400>
[13:56] <mup> Bug #1580802 opened: NoContextWithLock fails on windows because of another process <ci> <intermittent-failure> <regression> <unit-tests> <windows> <juju-core:Invalid> <https://launchpad.net/bugs/1580802>
[14:05] <mup> Bug #1559400 changed: TestManageModelRunsRegisteredWorkers is flaky <intermittent-failure> <juju-core:Invalid> <https://launchpad.net/bugs/1559400>
[14:05] <mup> Bug #1580802 changed: NoContextWithLock fails on windows because of another process <ci> <intermittent-failure> <regression> <unit-tests> <windows> <juju-core:Invalid> <https://launchpad.net/bugs/1580802>
[14:43] <perrito666> axw: ping
[14:43] <wallyworld> ericsnow: katco: hey, did you guys have time for a staus update hangout?
[14:43] <ericsnow> wallyworld: sure
[14:44] <wallyworld> ericsnow: katco: https://hangouts.google.com/hangouts/_/canonical.com/tanzanite-stand
[14:53] <mup> Bug #1596559 opened: BootstrapSuite.TestRunTests <intermittent-failure> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1596559>
[15:03] <ericsnow> katco: ping me when you're around
[16:05] <mup> Bug #1596593 opened: juju show-model does not accept model as kwarg <juju-core:New> <https://launchpad.net/bugs/1596593>
[16:22] <wallyworld> ericsnow: i looked at the WIP forwarding worker. see if the comments make sense - i'm confused about what is expected as controller config; it seems it's been implemented as model config? also the worker loop seems a little unusually in not using a channel as the result of Next()?
[16:22] <ericsnow> wallyworld: thanks, I'll take a look
[16:28] <thumper> urulama-sprint: http://reviews.vapour.ws/r/5171/
[16:28] <thumper> some juju reviewer plz: http://reviews.vapour.ws/r/5171/diff/#
[16:29] <urulama-sprint> frankban|afk: ^ PTAL
[16:35] <mup> Bug # opened: 1596597, 1596603, 1596605, 1596607, 1596608, 1596609
[16:48] <perrito666> thumper: reviewed, shpit with a couple of gotchas
[16:48] <perrito666> I must admit I did not go through the whoooole menn0 checklist but I covered many points
[16:54] <mup> Bug #1596612 opened: show-controller output updates <2.0> <usability> <juju-core:New> <https://launchpad.net/bugs/1596612>
[16:54] <mup> Bug #1596615 opened: show-model output updates <2.0> <usability> <juju-core:New> <https://launchpad.net/bugs/1596615>
[16:54] <mup> Bug #1596616 opened: commands do not use two spaces between columns/headings <2.0> <usability> <juju-core:New> <https://launchpad.net/bugs/1596616>
[16:57] <katco> ericsnow: hey, i'm here. sorry, dentist appt.
[16:57] <ericsnow> katco: np
[16:57] <ericsnow> katco: just getting up to speed with wallyworld about status
[16:58] <ericsnow> katco: we need to get together at some point about how to integrate audit logs with log forwarding
[16:58] <ericsnow> * some point today
[16:58] <katco> ericsnow: i'm free now if you'd like
[16:59] <ericsnow> katco: sure, moonstone?
[16:59] <katco> ericsnow: brt
[17:18] <mup> Bug #1596619 opened: remove aliases from juju commands <2.0> <usability> <juju-core:New> <https://launchpad.net/bugs/1596619>
[17:27] <mup> Bug #1596626 opened: juju gui not showing multiple models <juju-core:New> <https://launchpad.net/bugs/1596626>
[17:36] <mup> Bug #1596626 changed: juju gui not showing multiple models <juju-core:New> <https://launchpad.net/bugs/1596626>
[17:42] <mup> Bug #1596626 opened: juju gui not showing multiple models <juju-core:Invalid> <https://launchpad.net/bugs/1596626>
[17:54] <mup> Bug #1596626 changed: juju gui not showing multiple models <juju-core:New> <https://launchpad.net/bugs/1596626>
[18:31] <perrito666> if we actally see cloud init apt-get failing suggesting update, why on earth would we not try that?
[18:49] <bogdanteleaga> do we have some sort of wiki entry for the multiple mongo gotchas that got posted lately to the ML?
[18:52] <katco> ericsnow: given all my changes, i think i need another proper review of: http://reviews.vapour.ws/r/5089/
[18:53] <ericsnow> katco: k
[18:53] <katco> ericsnow: ta
[18:53] <katco> bogdanteleaga: not that i know of
[18:54] <katco> ericsnow: i think i need to defer william's comments about RequestNotifier having internal knowledge of state, and tests for that type, but everything else is fair game
[18:54] <ericsnow> katco: k
[19:54] <mup> Bug #1596687 opened: command list output not consistent <2.0> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1596687>
[20:03] <katco> ericsnow: i'm ready to land http://reviews.vapour.ws/r/5089/. any thoughts?
[20:03] <mup> Bug #1596687 changed: command list output not consistent <2.0> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1596687>
[20:03] <ericsnow> katco: one minute
[20:06] <katco> ericsnow: np... took me 4 tries to land the previous one =|
[20:12] <mup> Bug #1596687 opened: command list output not consistent <2.0> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1596687>
[20:12] <mup> Bug #1596688 opened: normalizing the shares and user commands <2.0> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1596688>
[20:17] <ericsnow> katco: basically, ship-it
[20:18] <mup> Bug #1596688 changed: normalizing the shares and user commands <2.0> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1596688>
[20:19] <katco> ericsnow: ta
[20:24] <mup> Bug #1596688 opened: normalizing the shares and user commands <2.0> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1596688>
[21:07] <stokachu> ericsnow: are you familiar with the deploy api?
[21:07] <ericsnow> stokachu: a little
[21:08] <stokachu> im trying to get the latest beta10 to deploy via the api
[21:08] <stokachu> https://paste.ubuntu.com/17991715/
[21:08] <stokachu> we pass that to the apiserver but the response is always unable to find charm
[21:09] <stokachu> was there an additional requirement added in beta10?
[21:09] <stokachu> only thing we changed was to match the reworked  api parameter keys
[21:25] <katco> stokachu: ok, sorry, i'm back and looking at this
[21:25] <stokachu> thanks
[21:26] <stokachu> ive been digging through the go code but nothing yet
[21:26] <stokachu> katco: i did force a 'channel': 'stable' in the parameters
[21:26] <stokachu> still failed though with same message
[21:26] <katco> stokachu: hm
[21:27] <katco> stokachu: do you happen to have the debug logs from the controller?
[21:28] <stokachu> yea
[21:29] <stokachu> what would you need?
[21:32] <katco> stokachu: machine 0's log with debugging turned on and the deploy failure
[21:32] <katco> stokachu: controller might give us a hint at what exactly is failing
[21:32] <stokachu> whats the command to enable the debugging
[21:33] <katco> stokachu: i always forget, sec. it's juju set-config log-level=DEBUG or something
[21:34] <stokachu> juju set-config log-level=DEBUG
[21:34] <stokachu> error: no application name specified
[21:35] <stokachu> juju set-model-config logging-config='<root>=DEBUG;unit=DEBUG'
[21:40] <katco> stokachu: that looks right. easy, huh? where'd you find it?
[21:40] <stokachu> juju help set-model-config
[21:42] <stokachu> katco: http://paste.ubuntu.com/17994956/
[21:42] <stokachu> the bottom there has the latest deploy attempt
[21:42] <katco> stokachu: ta
[21:43] <stokachu> though it says params redacted
[21:43] <stokachu> how do i get it to display it all
[21:44] <katco> stokachu: probably can't; we hardcode that. let me 2xcheck though
[21:45] <katco> stokachu: set level to trace
[21:45] <katco> stokachu: and that should log the body as well
[21:46] <stokachu> nice
[21:47] <stokachu> katco: http://paste.ubuntu.com/17995148/
[21:47] <stokachu> thats everything
[21:48] <stokachu> line 5204 shows the deploy
[21:49] <stokachu> we don't pass a series as that usually is handled from the charmurl
[21:50] <stokachu> ericsnow: feel free to take a peek too
[21:53] <katco> stokachu: just on a whim, can you try passing the series?
[21:53] <stokachu> sure
[21:55] <stokachu> katco: same error
[21:55] <stokachu> https://paste.ubuntu.com/17995455/
[21:55] <stokachu> 9203
[21:55] <katco> stokachu: k, worth a try
[21:59] <katco> stokachu: i think this is where the error is coming from: https://github.com/juju/juju/blob/master/state/charm.go#L696
[21:59] <katco> stokachu: which would imply that it's not successfully being stored in mongo
[22:00] <stokachu> weird
[22:00] <stokachu> does the juju client code do something prior to calling the api?
[22:01] <stokachu> as far as mongo is concerned
[22:01] <katco> stokachu: yeah it does a few things, some related to resources
[22:01] <katco> stokachu: that's all this: https://github.com/juju/juju/blob/master/cmd/juju/application/deploy.go#L301
[22:02] <stokachu> so did that change from beta9 to beta10?
[22:04] <katco> stokachu: nope
[22:06] <stokachu> :(
[22:06] <katco> stokachu: https://github.com/juju/juju/commit/136d03f5987c89946b6987832c520c8879ea225f#diff-bad794df7c6f66424c0b9cc0961da6cc
[22:06] <katco> stokachu: looks... plausible
[22:07] <stokachu> so we have to upload first
[22:07] <stokachu> wtf
[22:09] <katco> stokachu: it... looks like that may be the case. it looks like that was a 1.16 guarantee... wow
[22:09] <stokachu> so i've no idea where to go from here
[22:09] <stokachu> do i need to start uploading every charm?
[22:09] <stokachu> this PR looks like it has the $jfdi$ tag
[22:10] <stokachu> lol with no review
[22:11] <katco> stokachu: http://reviews.vapour.ws/r/5092/
[22:11] <katco> stokachu: unfortunately we are having to JFDI everything to meet deadlines, even though master is blocked
[22:11] <stokachu> haha it just says shipit
[22:12] <katco> stokachu: if there were no issues found, that's how the tool indicates it's safe to land
[22:12] <katco> rick_h_: ping, you still up?
[22:12] <stokachu> so im guessing deploying via the API with juju gui or another client is out of the scope of testing?
[22:13] <katco> stokachu: upper management told us to move fast and break things as this is a beta
[22:13] <katco> stokachu: alexisb usually bends over backwards to avoid doing this, but we lost that particular battle
[22:15] <katco> stokachu: i don't know what the official stance on other clients is now. my guess is that yes, you have to upload charms/resources first... that seems weird to me
[22:15] <katco> stokachu: seems like something the controller should be taking care of
[22:15] <stokachu> yea
[22:16] <stokachu> which it has been since forever
[22:16] <katco> yeah
[22:19] <katco> stokachu: can you send an email out to juju-dev asking for clarification about what's intended with a link to that PR?
[22:19] <stokachu> katco: sure
[22:19] <katco> stokachu: ta. sorry for the trouble. sometimes we don't have control over the experience :(
[22:20] <stokachu> well the PR could've had more explanation at the very least
[22:20] <stokachu> i understand its beta and we dont care about breaking things
[22:55] <katco> ericsnow: wow, a lot of tests break if you add a new attribute to apiserver's ServerConfig struct :|
[22:56] <ericsnow> :(
[22:56] <katco> ericsnow: i suspect it'll take me a bit just to hunt all these down (sigh). FULL STACK TESTING FTW!
[22:56] <ericsnow> katco: I feel your pain
[22:57] <katco> ericsnow: do you? let's test it out. first, i need you to move to my city, then live in my house, etc. just to make sure we're exercising all aspects of me feeling pain
[22:58] <ericsnow> katco: heh