[04:35] <mup> Bug #1537880 changed: Juju missed a MAAS node transitioning to "deployed", shows it as pending <kanban-cross-team> <landscape> <juju-core:Expired> <https://launchpad.net/bugs/1537880>
[04:35] <mup> Bug #1560262 changed: relation visibility rules different between service/service and service/subordinate relations <canonical-is> <juju-core:Invalid> <PostgreSQL Charm:Triaged> <postgresql (Juju Charms Collection):Triaged> <https://launchpad.net/bugs/1560262>
[14:20] <natefinch> katco`: you around?
[14:21] <katco`> natefinch: hey, yeah
[14:21] <natefinch> katco: how are you feeling?
[14:21] <katco> natefinch: mostly fine. still throbs at times
[14:21] <katco> natefinch: thx for asking
[14:22] <natefinch> katco: good
[14:22] <natefinch> katco: is there a spec on this long lived macaroon thingy?
[14:22] <katco> natefinch: nope, just that email chain
[14:23] <katco> natefinch: afaik
[14:24] <katco> natefinch: didn't rick_h_ say to run with the 24h session idea?
[14:26] <natefinch> katco: yeah, as just wondering if there was anything more than the bug to go on.
[14:26] <katco> natefinch: no, not yet. this is all the conversation that's happened on this topic so far
[14:26] <natefinch> katco: ok
[14:27] <natefinch> katco: I'm going to go with a 48 hour expiration... 24h will almost certainly fail, given that we only poll every 24 hours... if we happen to poll a few milliseconds late.. boom
[14:28] <katco> natefinch: yeah i agree with that. i also strongly feel we need an escape hatch for when things go wrong
[14:29] <natefinch> katco: yeah... there's a whole host of extra work for that, unfortunately... notifying the user that there's something wrong, giving them a way to fix it, etc.
[14:33] <katco> natefinch: yeah... rick_h_ is right, let's just take care of the easy case and then we can start speccing out the rest of the work
[14:35] <katco> natefinch: can you pull that bug card over to in progress and give it an eta?
[14:36] <natefinch> katco: yep
[14:36] <katco> natefinch: thx... and happy monday
[14:36] <natefinch> katco: happy monday
[14:36] <natefinch> katco: btw, loved your twitter comment about the surgery being better than the Steve Jobs movie :)
[14:38] <katco> natefinch: lol... i am rarely hard on movies. i find enjoyment in bad movies, but i can't stand boring movies. and that movie was 2+ hours of exposition -- boring exposition -- behind the scenes of presentations
[14:38] <katco> natefinch: it was just so dry.
[14:38] <natefinch> katco: heh, yeah, I hear ya
[14:39] <katco> natefinch: have you seen it?
[14:39] <natefinch> katco: nope.
[14:39] <katco> natefinch: i really don't think you're missing anything. it's not even worth watching to discuss with others
[14:40] <natefinch> katco: lol, good to know.  yeah, I'd been kind of curious, but now, not so much.  Was this the ashton kutcher one, or the other one?
[14:40] <katco> natefinch: the other one
[14:40] <natefinch> katco: (and that's about all I know about the differences between the two ;)
[14:41] <katco> natefinch: you know when someone gives a presentation, and they bring up a slide-deck with nothing but black and white bullet points? and then they proceed to just read the presentation? that's what it felt like.
[14:41] <natefinch> katco: OMG that's the worst
[14:42] <katco> natefinch: btw, meant completion date for that card, not start date
[14:42] <natefinch> katco: aww.. the former is a lot easier to come up with ;)
[14:42] <katco> natefinch: lol
[14:42] <natefinch> katco: er latter
[14:45] <natefinch> katco: I think I should be able to have it done tomorrow, but I put Wednesday as a kind of buffer, since it's still so up in the air.
[14:45] <katco> natefinch: let's shoot for tomorrow with the understanding of the current scope and we can adjust as needed
[14:46] <natefinch> katco: sure
[14:56] <katco> natefinch: fyi i think it's just you and me today. eric's off, ian's gone. not sure we need to do a standup
[14:56] <natefinch> katco: yeah, I was thinking that
[14:56] <katco> natefinch: my jaw thanks you. i'm mostly sifting through email anyway
[14:57] <natefinch> katco: heh.  Hope it's all the way better soon.
[14:58] <katco> natefinch: yeah kind of curious how long the soreness is supposed to last. it has slowly gotten better, but still throbs (randomly?) at times
[14:59] <natefinch> katco: I don't remember how long it was for mine... but it's a fairly severe surgery, so a week doesn't seem unreasonable.  I do remember I had a random little chip of tooth worm its way out like a month later.
[15:01] <katco> natefinch: lol i think i may have already had that happen... wasn't sure
[15:43] <cherylj> Can I get a couple reviews?  https://github.com/juju/utils/pull/201
[15:43] <cherylj> https://github.com/juju/juju/pull/4899
[15:49] <katco> cherylj: i think mgz already gave you a ship it on the 1st one
[15:49] <katco> cherylj: tal at the 2nd
[15:50] <cherylj> hmm, I never got an email from RB on that.  Thanks, katco
[15:50] <katco> cherylj: rb gnomes imo
[16:31] <natefinch> man, I extracted 4 arguments into an argument struct, and found so far, 5 functions that all use the same list of args (derived from the same data, even)... and all of them are going to need to be updated to add the long lived macaroon I'm adding.
[17:02] <icey> possible to get an update on https://bugs.launchpad.net/juju-core/+bug/1559099 ? last comment was by anastasiamac a week ago
[17:02] <mup> Bug #1559099: JUJU_AVAILABILITY_ZONE not set in MAAS <maas-provider> <juju-core:Incomplete> <juju-core 1.25:In Progress by anastasia-macmood> <https://launchpad.net/bugs/1559099>
[17:03] <cherylj> icey: I'
[17:03] <cherylj> icey: I'm meeting with anastasia to talk about it today
[17:03] <cherylj> icey: I want to see if we can get it for 1.25.5
[17:04] <icey> thanks cherylj!
[17:43] <mup> Bug #1562052 changed: juju bootstrap doesn't create secgroups when there are environment naming conflicts <juju-core:Fix Released> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1562052>
[19:18] <thumper> morning folks
[19:18] <thumper> how is the crazy?
[19:19] <natefinch> thumper: pretty crazy
[19:27]  * natefinch starts a full test run and goes to flip the laundry
[19:38] <mup> Bug #1563015 opened: Cleanup from multi-nic branch <juju-core:Triaged> <https://launchpad.net/bugs/1563015>
[19:40] <natefinch> and as expected t(laundry) < t(go test github.com/juju/juju/...)
[19:43] <natefinch> anyone else having the cmd/jujud/reboot	tests always time out?
[19:44] <mup> Bug #1563015 changed: Cleanup from multi-nic branch <juju-core:Triaged> <https://launchpad.net/bugs/1563015>
[19:49] <durschatz1> Does anyone know how to get in touch with the neutron-dhcp-agent charm development team?
[19:53] <mup> Bug #1563015 opened: Cleanup from multi-nic branch <juju-core:Triaged> <https://launchpad.net/bugs/1563015>
[20:09] <gQuigs> if you deploy juju-gui or the openstack-dashboard charms on 14.04, they come up vulnerable with both SSLv3 and RC4 enabled
[20:09] <gQuigs> should it be the charms job to disable them?
[20:18] <natefinch> gQuigs: you should send an email to the juju list, you'll get more eyes on the question there
[20:19] <gQuigs> natefinch: k, will do
[20:19] <natefinch> gQuigs: definitely a good idea to bring that up, though
[21:56] <mup> Bug #1563067 opened: deploying from charmstore fails on lxd provider in a restricted network <juju-core:New> <https://launchpad.net/bugs/1563067>
[22:03] <alexisb> kwmonroe, was this working in beta2: https://bugs.launchpad.net/juju-core/+bug/1563067
[22:03] <mup> Bug #1563067: deploying from charmstore fails on lxd provider in a restricted network <juju-core:New> <https://launchpad.net/bugs/1563067>
[22:03] <alexisb> ??
[22:03] <kwmonroe> alexisb: i've only tried beta3
[22:03] <alexisb> kwmonroe, ok