[02:01] <veebers> babbageclunk: the help summary for show-model states "Shows information about the current or specified model." yet there is no way to specify a model (i.e. no -m) is the summary wrong or is it wrong that it doesn't take -m
[02:01] <veebers> ?
[02:12] <babbageclunk> veebers: It takes model as a positional argument.
[02:12] <veebers> babbageclunk: d'oh, reading fail for me. Thanks :-)
[02:12] <babbageclunk> veebers: :)
[11:29] <hoenir> can someone take a look at this ? https://github.com/juju/juju/pull/6556
[13:32] <mup> Bug #1640079 changed: LXDs doesn't start after a reboot <lxd-provider> <openstack> <uosci> <juju:Triaged> <juju (Ubuntu):Triaged> <https://launchpad.net/bugs/1640079>
[15:03] <mgz> no one for standup?
[15:07] <macgreagoir> mgz: I can rejoin. I was there alone :-)
[15:07] <natefinch> we just did a super short one
[15:07] <mgz> macgreagoir: nate and I just did a lightning standup
[15:07] <mgz> feel free to fill us in here
[15:10] <macgreagoir> ipv6 blah blah blah
[15:12] <macgreagoir> Just trying to see if the enable-ha issue I'm hitting is ipv6 relatd or something else.
[15:18] <natefinch> macgreagoir: I wouldn't be surprised.
[15:20] <natefinch> macgreagoir: what version of mongo?
[15:20] <macgreagoir> 3.2
[15:20] <macgreagoir> .9
[15:21] <natefinch> hmmm... ok, if it had been 2.6 I'd almost assuredly think it was ipv6, but 3.2 is supposed to work
[15:21] <natefinch> but definitely could be a juju specific bug
[15:24] <macgreagoir> ipv6 seems good in 3.2. Seems to be an id clash somewhere in the momngo docs.
[17:22] <hoenir> could someone take a look on this PR https://github.com/juju/juju/pull/6556 ? and also could someone tell me that the CI logs are ok on the last commit ?
[17:22] <hoenir> what are your thoughts on this?
[17:56] <hoenir> someone?
[18:02] <mgz> hoenir: sorry, have been deep in several things today
[18:02] <mgz> hoenir: the checks passed, is there something in particular you want to see in the logs?
[18:23] <hoenir> mgz, I'm referring on that "bad certificates" warnings..
[18:25] <mgz> there are some "remote error: bad certificate" lines on stdout for the trusty unit tests
[18:25] <mgz> not actually causing any tests to fail
[18:25] <hoenir> so it's safe to merge
[18:26] <mgz> I don't know, what's the background?
[18:28] <hoenir> The background is that, on a previous PR axw suggested, in order to make these changes possible I should move the juju/cert (all the generic-common pieces) into a utils/cert pkg , the utils/cert part is already merged.
[18:29] <hoenir> this patch is already merged so.. I wanted to finish the job by merging the other patch in (juju-core).
[18:29] <hoenir> https://github.com/juju/utils/pull/250
[18:33] <hoenir> so mgz it's safe to $$merge$$ this bad boy?
[18:33] <mgz> as it's a us holiday and end of sprint, I think the people who were looking at your code just weren't around today
[18:34] <mgz> hoenir: the check says yes, and perrito666 approved
[18:35] <mgz> might be nice to send a message to the dev list about the cert error spam, so people are aware, and can follow up to fix?