[02:33] <blahdeblah> Anyone able to advise on the proposed release date for juju 2.2?
[02:48] <cmars> blahdeblah, toward the end of may
[02:49] <cmars> blahdeblah, toward the end of may
[02:58] <blahdeblah> cmars: thanks
[05:00] <mup> Bug #1688177 opened: juju show-action-status needs more details <canonical-bootstack> <juju-core:New> <https://launchpad.net/bugs/1688177>
[05:54] <axw> wpk: did you delete your comment about keeping HardwareId? I can't see it in the web UI, but I got an email
[05:57] <axw> wpk: anyway, there's no point in filling in HardwareId if it's a WWN path. HardwareId should only be populated if it's (e.g.) ata-KINGSTON_SV300S37A240G_50026B724501D2D2. if it's wwn-... it'll never match anything
[06:25] <wpk> axw: I've re-added it as a part of review.
[06:28] <wpk> axw: why it'll never match anything?
[08:48] <axw> wpk: because the worker that publishes block device info will never put /dev/disk/by-id/www-... in the BlockDevice.HardwareId field
[09:00] <wpk> axw: ok, just wanted to make sure, thanks
[09:27] <rogpeppe> axw: do you know what "ExternalControl" means when migrating, by any chance?
[09:28] <axw> rogpeppe: nope, sorry
[09:28] <rogpeppe> axw: ok, ta
[13:34] <ashipika> hey guys.. who is the core ocr today?
[13:46] <tasdomas> jam, ping?
[13:48] <tasdomas> cmars, ping?
[14:09] <cmars> tasdomas, pong
[14:10] <cmars> tasdomas, how's it going?
[14:10] <tasdomas> cmars, hey
[14:10] <tasdomas> ashipika, ^
[14:10] <cmars> tasdomas, i think i've resolved ashipika's issue :D
[14:10] <cmars> but really we have a slight CI UX issue
[14:10] <ashipika> indeed we have
[14:10] <tasdomas> cmars, ah, good
[14:10] <ashipika> slight* :)
[14:10] <tasdomas> ;-]]
[14:11] <cmars> although, and maybe this is bad, i usually just $$merge$$ if it passes all the tests locally
[14:11] <cmars> i do run them
[14:11] <cmars> promise :)
[14:11] <tasdomas> a guillotine is just a barber's chair with poor ux ;-]
[14:11] <cmars> LOL
[14:11] <cmars> that's awesome tasdomas
[14:17] <ashipika> tasdomas: i'd panic("arrrggh") in that chair :)
[17:03] <wpk> while setting up on on AWS with --constraints spaces=... I'm getting machines stuck in:
[17:03] <wpk> 6        pending                 pending              xenial                 Setting up groups
[17:03] <wpk> Anyone seen something like that?
[17:17] <rick_h> wpk: how many security groups do you have and did you hit a cap on them?
[17:17] <rick_h> wpk: might try "juju show-machine 6" and see if anything's there and then have to hit the logs
[17:22] <wpk> rick_h:
[17:22] <wpk>     machine-status:
[17:22] <wpk>       current: allocating
[17:22] <wpk>       message: Setting up groups
[17:23] <wpk> it only hangs if I use contraints spaces,without this option I can add-machine just fine
[17:24] <rick_h> wpk: yea, so coming from https://github.com/juju/juju/blob/abf46a71316cd64e67db4f5878f9638de82e2e79/provider/ec2/environ.go#L499 I'd think you hit something with security groups there in AWS.
[17:24] <rick_h> wpk: have to poke at the AWS console and see what's up? Or maybe it's asking for osmething that AWS is erroring with that is not getting caught
[17:27] <wpk> aha2017-05-04 17:02:15 WARNING juju.provisioner provisioner_task.go:739 failed to start instance (cannot set up groups: fetching security group "juju-edf... (in VPC "vpc-01...."): Tags could not be retrieved. (Unavailable)), retrying in 10s (3 more attempts)
[17:28] <rick_h> wpk: hmm, so did it create the group and not able to find it over the api? Or is something else causing the connectivity issue between the aws api/controller?
[17:29] <wpk> I can see this group in console
[18:10] <wpk> rick_h nothing to do with security groups, all to do with spaces - if a space is not available for a certain AZ/VPC combination the result is as above
[18:10] <rick_h> wpk: well that's less than helpful heh
[23:47] <axw> babbageclunk: standup?
[23:50] <babbageclunk> axw: D'oh sorry - omw