[00:07] <mup> Bug #1577988 opened: Revert destroy service when machine is off <juju-core:New> <https://launchpad.net/bugs/1577988>
[01:04] <wallyworld> redir: ericsnow: meeting?
[02:28] <menn0> axw: ping
[02:28] <axw> menn0: pong, in a meeting atm
[02:28] <menn0> axw: np... let me know when you're done please
[02:51] <axw> menn0: sorry, back now
[02:51] <thumper> either, we suck horribly
[02:51] <thumper> or the last CI test run had issues
[02:52]  * thumper gives each one about 50%
[02:52] <menn0> axw: np... I think I've mostly figured it out but i'll confirm with you anyway
[02:52] <menn0> axw: you did the debughooks work right?
[02:53] <axw> menn0: yes, long ago
[02:53] <menn0> axw: I'm in the final throes of integrating the SSH host key stuff and noticed the debughooks tests don't do what they appear to
[02:53] <menn0> axw: https://github.com/juju/juju/blob/master/cmd/juju/commands/debughooks_test.go
[02:53] <menn0> axw: in debugHooksTests the proxy and result fields aren't used :)
[02:54] <menn0> axw: I guess I just wanted be sure that I wasn't missing something before fixing
[02:55] <axw> menn0: :/  they used to be
[02:55] <axw> menn0: don't think you're missing anything
[02:56] <menn0> axw: must have been later edits that broke the tests
[02:56] <menn0> axw: I need to rework them anyway. i'm trying to get them to pass again.
[02:57] <menn0> (with my changes)
[03:13] <mup> Bug #1508923 changed: Support for Azure Resource Groups <azure-provider> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1508923>
[03:43] <mup> Bug #1291201 changed: Azure provider does not use storage service's affinity group <azure-provider> <juju-core:Won't Fix> <https://launchpad.net/bugs/1291201>
[04:29] <axw> wallyworld: I was expecting at least an "argh!" response from someone to using sync.Cond :)
[04:29] <wallyworld> axw: i can live with it :-)
[04:30] <wallyworld> seems to do what's needed nicely
[04:31] <axw> wallyworld: yeah, it's appropriate IMO. people reach for channels because they're easy, but they're not always sufficient
[04:31] <wallyworld> +1
[04:31] <wallyworld> when you have a hammer, everything looks like a nail
[04:31] <axw> wallyworld: were you looking at the restore-backup bug? ISTR you were looking at something in the area
[04:31] <wallyworld> yeah
[04:48] <axw> wallyworld: thanks for review, please see reply on BuildToolsTarball PR
[04:48] <wallyworld> ok
[04:50] <wallyworld> axw: yeah, i was wondering if there were more tests. it seems ok i think
[08:54] <voidspace> mgz: ping
[08:56] <voidspace> mgz: unping - emailed instead
[09:01] <babbageclunk> voidspace, dimitern: standup? Am I in the wrong one? You guys missed the fire alarm test!
[09:01] <voidspace> omw
[09:01] <dimitern> oops sorry omw
[09:02] <voidspace> babbageclunk: eager beaver
[09:02] <voidspace> babbageclunk: keen bean
[09:45] <babbageclunk> voidspace, dimitern: porting tests to MAAS2 http://reviews.vapour.ws/r/4766/
[09:46] <voidspace> babbageclunk: looking
[09:49] <voidspace> babbageclunk: LGTM
[09:49] <babbageclunk> voidspace: thanks#!
[09:49] <babbageclunk> -#
[09:51] <dimitern> babbageclunk: still reviewing btw
[09:51] <babbageclunk> dimitern: d'oh, sorry
[09:51] <dimitern> babbageclunk: np :) I should've said I did
[09:51] <babbageclunk> dimitern: luckily there are blockers anyway
[09:54] <dimitern> babbageclunk: reviewed
[09:59] <babbageclunk> dimitern: thanks, fixed. How do I spell jfdi for this again?
[10:00] <dimitern> babbageclunk: $$__JFDI__$$
[10:00] <babbageclunk> dimitern: Thanks
[10:01] <dimitern> babbageclunk: thanks for chasing all those CI issues so quickly :)
[10:02] <babbageclunk> dimitern: :)
[10:29] <babbageclunk> hmm - godef stopped working for stdlib packages after upgrading to xenial. Any hints for how to make it work again?
[10:33] <dimitern> babbageclunk: what error are you getting?
[10:34] <babbageclunk> dimitern: Just eg "godef: no declaration found for sort.Strings"
[10:37] <babbageclunk> dimitern: still works fine for local types and cross-package ones.
[10:37] <dimitern> babbageclunk: ah, you might have GOROOT set (or unset - can't remember what was supposed to work)
[10:39] <dimitern> babbageclunk: I use GOROOT=/usr/lib/go-1.6 and that works with golang-1.6 from xenial/main
[10:39] <babbageclunk> dimitern: thanks, I'll try that. Wonder why it stopped.
[10:41] <babbageclunk> dimitern: yay, thanks! Worked great.
[10:41] <dimitern> babbageclunk: \o/ :)
[10:43] <babbageclunk> dimitern: man, felt like I had a phantom limb for a bit.
[10:45] <dimitern> babbageclunk: re godef not working? :)
[10:47] <babbageclunk> dimitern: yeah, just got so used to hitting a key to pull up the type of a thing that when it stopped I felt like I had an itch in a place that I didn't have a place anymore.
[10:48] <dimitern> babbageclunk: I know what you mean - I use and depend on godef all the time; I only wish it worked better for stuff in export_test.go :/
[10:51] <dimitern> babbageclunk: I have M-. bound to godef-jump and C-M-. to godef-jump-other-window
[10:52] <babbageclunk> dimitern: Man, I love godef-jump-other-window
[10:54] <dimitern> babbageclunk: another very useful package to add is go-eldoc btw - it shows type info in the minibuffer
[10:55] <babbageclunk> dimitern: ooh, just as you move around? I've been hitting C-c C-d for that, but something that was always there would be nicer.
[10:56] <dimitern> babbageclunk: yeah, e.g. with point at 'errors.IsNotFound' it shows 'errors.IsNotFound: func(err error) bool'
[10:56] <dimitern> (assuming errors is already imported)
[10:57] <dimitern> babbageclunk: most of the tricks in http://dominik.honnef.co/posts/2013/03/writing_go_in_emacs/ and its follow-up are good to know
[10:59] <babbageclunk> dimitern: nice, thanks - I've got go-mode set up, but not all of these.
[11:55]  * dimitern steps out for ~1h
[12:47]  * dimitern is back
[12:53] <mgz> dimitern: `juju help add-subnet` mentions `juju create-subnet` - which doesn't exist?
[12:55] <dimitern> mgz: oh, yeah - it's under a feature flag "post-net-cli-mvp", but the help doc should mention it
[12:55] <dimitern> s/should/shouldn't/
[12:57] <mgz> okay, that's a new flag to me
[12:57] <mgz> should it work on aws/maas at present? (create-)
[13:01] <dimitern> mgz: no, it doesn't work.. well, the flag it changes a few things if enabled, like registering extra networking commands, but the commands themselves are not fully implemented (end-to-end)
[13:05] <alexisb> jam, fwereade ping
[13:28] <alexisb> jam and fwereade officially owe me a beer at the sprint
[13:32] <alexisb> voidspace, babbageclunk, dimitern, mgz, again really well done on the maas 2.0 stuff!
[13:33] <dimitern> alexisb: indeed! it's exciting to see all coming together so quickly!
[13:45] <babbageclunk> Gah, does anyone know why strace -c -f is giving me negative times?
[13:48] <mup> Bug #1576509 changed: Race in macaroon-bakery <blocker> <ci> <race-condition> <regression> <test-failure> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1576509>
[13:48] <mup> Bug #1576527 changed: listSuite.TestListJSON got null (showSuite too) <blocker> <ci> <go1.6> <regression> <test-failure> <unit-tests> <windows> <juju-core:Fix Released by ericsnowcurrently> <https://launchpad.net/bugs/1576527>
[13:48] <mup> Bug #1576911 changed: github.com/juju/juju/environs/bootstrap timeout (sigquit) <blocker> <centos> <ci> <go1.6> <regression> <test-failure> <unit-tests> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1576911>
[13:57]  * babbageclunk is out code clubbing.
[14:00] <mup> Bug #1576509 opened: Race in macaroon-bakery <blocker> <ci> <race-condition> <regression> <test-failure> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1576509>
[14:00] <mup> Bug #1576527 opened: listSuite.TestListJSON got null (showSuite too) <blocker> <ci> <go1.6> <regression> <test-failure> <unit-tests> <windows> <juju-core:Fix Released by ericsnowcurrently> <https://launchpad.net/bugs/1576527>
[14:00] <mup> Bug #1576911 opened: github.com/juju/juju/environs/bootstrap timeout (sigquit) <blocker> <centos> <ci> <go1.6> <regression> <test-failure> <unit-tests> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1576911>
[14:12] <mup> Bug #1576509 changed: Race in macaroon-bakery <blocker> <ci> <race-condition> <regression> <test-failure> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1576509>
[14:12] <mup> Bug #1576527 changed: listSuite.TestListJSON got null (showSuite too) <blocker> <ci> <go1.6> <regression> <test-failure> <unit-tests> <windows> <juju-core:Fix Released by ericsnowcurrently> <https://launchpad.net/bugs/1576527>
[14:12] <mup> Bug #1576911 changed: github.com/juju/juju/environs/bootstrap timeout (sigquit) <blocker> <centos> <ci> <go1.6> <regression> <test-failure> <unit-tests> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1576911>
[14:19] <voidspace> alexisb: thanks
[14:24] <mup> Bug #1578237 opened: lxd Raw response debug logging too verbose <jujuqa> <logging> <lxd> <juju-core:Triaged> <https://launchpad.net/bugs/1578237>
[14:47] <natefinch> bogdanteleaga: got a minute?
[14:49] <natefinch> or gsamfira?
[14:50] <bogdanteleaga> natefinch, what's up
[14:51] <natefinch> bogdanteleaga: I changed jujud's TLS configuration to only support TLS 1.2 last week... however, this is proving a problem for windows machines trying to download tools.  Seems like the .Net WebClient doesn't always default to having TLS 1.2 enabled.
[14:52] <natefinch> bogdanteleaga: I think it's something we can enable in the cloudconfig script we send up, but wanted to get your input on it... this code specifically: https://github.com/juju/juju/blob/master/cloudconfig/userdatacfg_win.go#L197
[14:52] <bogdanteleaga> yup, noticed it yesterday, got a fix, but still testing it across windows versions
[14:52] <natefinch> bogdanteleaga: oh, awesome. Thanks!
[14:54] <mup> Bug #1537153 changed: juju deploy --config option ignored when deploying a bundle <2.0-count> <juju-release-support> <juju-core:Invalid> <https://launchpad.net/bugs/1537153>
[14:54] <mup> Bug #1565872 changed: Juju needs to support LXD profiles as a constraint <adoption> <juju-release-support> <lxd> <juju-core:Triaged> <https://launchpad.net/bugs/1565872>
[14:54] <mup> Bug #1578254 opened: Race in apiserver/common and apiserver/proxyupdater <blocker> <ci> <race-condition> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1578254>
[15:02] <katco> natefinch: standup time
[15:23] <perrito666> does anyone have the critical bugs link?
[15:24] <natefinch> perrito666: blockers: https://bugs.launchpad.net/juju-core/+bugs?field.tag=blocker+
[15:24] <perrito666> tx
[15:24] <perrito666> almost everything is in progress sweeeeet
[15:24] <mup> Bug #1554819 changed: juju help create-model is misleading <juju-release-support> <juju-core:Triaged> <https://launchpad.net/bugs/1554819>
[15:33] <mup> Bug #1554819 opened: juju help create-model is misleading <juju-release-support> <juju-core:Triaged> <https://launchpad.net/bugs/1554819>
[15:37] <perrito666> does anyone oppose at me taking https://bugs.launchpad.net/juju-core/+bug/1578254 ?
[15:37] <mup> Bug #1578254: Race in apiserver/common and apiserver/proxyupdater <blocker> <ci> <race-condition> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1578254>
[15:42] <mup> Bug #1554819 changed: juju help create-model is misleading <juju-release-support> <juju-core:Triaged> <https://launchpad.net/bugs/1554819>
[15:43] <mup> Bug #1561212 changed: register logic can lead to user lockout <2.0-count> <docteam> <juju-release-support> <juju-core:Fix Released> <https://launchpad.net/bugs/1561212>
[15:43] <mup> Bug #1576313 changed: windows: uniter tests fail because logs get dumped to stderr <blocker> <ci> <regression> <test-failure> <windows> <juju-ci-tools:Triaged> <juju-core:Won't Fix by hduran-8> <https://launchpad.net/bugs/1576313>
[15:45] <natefinch> perrito666: go for it.  I was going to look at it, but hadn't gotten there yet
[15:45] <perrito666> sorry
[15:45]  * perrito666 notices that all our criticals are in progres :D go team
[15:45] <natefinch> perrito666: it's all the same to me
[15:46] <natefinch> \o/
[15:50] <natefinch> sinzui: did you get in touch with the MAAS guys about the centos7 image?
[15:50] <sinzui> natefinch: oh, sorry, they never replied. I will poke again
[15:51] <natefinch> sinzui: do you mind if I split https://bugs.launchpad.net/juju-core/+bug/1576873 into two bugs?  One for centos and one for windows?  They're likely to be fixed in different ways by different people
[15:51] <mup> Bug #1576873: Juju2 cannot deploy centos or windows workloads on maas 1.9 <blocker> <centos> <ci> <maas-provider> <regression> <windows> <juju-core:In Progress by natefinch> <https://launchpad.net/bugs/1576873>
[16:00] <mgz> natefinch: that sounds sensible
[16:00] <natefinch> mgz: there's no built-in like duplicate this bug or split this bug into two or anything, is there?
[16:02] <natefinch> mgz: nevermind, copy and paste is quick enough
[16:02] <mgz> natefinch: yeah, that should do
[16:04] <natefinch> there - https://bugs.launchpad.net/juju-core/+bug/1578286
[16:04] <mup> Bug #1578286: Juju2 cannot deploy windows workloads on maas 1.9  <blocker> <ci> <maas-provider> <regression> <windows> <juju-core:In Progress by natefinch> <https://launchpad.net/bugs/1578286>
[16:04] <natefinch> also edited the original to remove the windows-specific stuff
[16:04] <mgz> thanks nate
[16:07] <mup> Bug #1578286 opened: Juju2 cannot deploy windows workloads on maas 1.9  <blocker> <ci> <maas-provider> <regression> <windows> <juju-core:In Progress by natefinch> <https://launchpad.net/bugs/1578286>
[16:36] <redir> ericsnow: I'm here, give me a few minutes and I am ready
[16:37] <ericsnow> redir: k
[16:47] <rcj> Who can answer rackspace provider questions?
[16:49] <redir> ericsnow: in Moonstone
[16:50] <rcj> ericsnow, the rackspace development account loaned to juju from cpc has a litter of monitoring entities for old juju machines from prior deployments.  These might be old but I'd like you to check and ensure that the provider does clean these up correctly if it's not doing that already.
[16:50] <rcj> ericsnow, I'm seeing them @ https://intelligence.rackspace.com/cloud/entities
[16:52] <ericsnow> rcj: OTP, but you might want to check with mgz, abentley_, or sinzui
[16:53] <rcj> ^ mgz, abentley_, sinzui: Can someone from Juju track this down?  I'd like to hand this off.
[16:54] <mgz> rcj: what exactly is a monitoring entity?
[16:54] <rcj> good question
[16:54] <sinzui> rcj: my question too
[16:54] <rcj> something in the UI at that spot in the webapi.  we see a bunch on the test account we loaned out for use in provider development.
[16:55] <sinzui> rcj: I delete servers every few days, but not Odd_Bloke's server
[16:56] <Odd_Bloke> sinzui: < me, earlier> I've never used RAX.  < rcj> You have a server in there.  < me> ... oh ...
[16:56] <rcj> sinzui, not Odd_Bloke's servers.  this is just some entity, probably created at vm creation, that is hanging around presumably left by the juju rax provider given the entity "juju-<hash>-machine-#" names.  Wanted to make sure someone was aware and would look at the provider to ensure a clean user experience.
[16:56] <mgz> rcj: so, we're not deliberately creating those, I guess we might get them as a side effect of creating machines?
[16:57] <rcj> mgz, ack
[16:57] <sinzui> Odd_Bloke: oh, it is gone now, but there was one for 2 weeks
[16:57] <mgz> in which case it's unclear why the matching destroy doesn't clear them
[16:57] <Odd_Bloke> sinzui: Yeah, I know; I am not a smart man.
[16:57] <Odd_Bloke> :p
[17:00] <mgz> rcj: I have no idea what to do about this
[17:01] <mgz> it's not even clear from the docs how you configure the behaviour
[17:01] <sinzui> mgz: rcj: cannot find this in the UI to get a list
[17:02] <sinzui> mgz: I think we need a bug for juju and one for ourselves. We need a cleanup script for rackspace now
[17:03] <sinzui> ah, rackspace inteligence
[17:08] <rcj> https://intelligence.rackspace.com/cloud/entities
[17:13] <mup> Bug #1541445 changed: empty uuid in cache.yaml after destroy-controller <2.0-count> <juju-release-support> <juju-core:Invalid> <https://launchpad.net/bugs/1541445>
[17:42] <redir> ericsnow: same thing different branch http://reviews.vapour.ws/r/4767/
[17:42] <niedbalski> sinzui, mgz I'd might need a fix on the upstart service (1.25); What's the target branch for doing a merge proposal?
[17:43] <sinzui> 1.25
[17:43] <sinzui> ^ niedbalski
[17:43] <mup> Bug #1578327 opened: juju 1.25.5: Juju Login with invalid user tag should return CodeUnauthorized <landscape> <juju-core:New> <https://launchpad.net/bugs/1578327>
[17:43] <sinzui> niedbalski: https://github.com/juju/juju/tree/1.25
[17:44] <niedbalski> sinzui, yep, but afaik this is part of packaging and it seems that the debian sources are not on the same tree, right?
[17:44] <sinzui> niedbalski: That is the branch we will make 1.25.6 from.
[17:46] <sinzui> niedbalski: 1.25 does have different packaging rules, but to be clear NO juju has upstart or systemd rules in packaging.
[17:47] <sinzui> niedbalski: jujud generates its system files on installation. So jujud supports both systemd and upstart. It chooses which files to generate based on the host OS. this is also true for windows and centos
[17:48] <redir> ericsnow: tx
[17:49] <niedbalski> sinzui, cool. It seems that the service definition template lives in github.com/juju/juju/service/upstart/upstart.go, thanks!.
[17:49] <sinzui> fab
[17:50] <sinzui> balloons: r=me
[17:53] <balloons> sinzui, ack. I'll remove the tweaks to the jobs to call my code and enable the flow
[17:54] <sinzui> :)
[18:28] <mup> Bug #1578337 opened: no command to remove controllers <juju-core:New> <https://launchpad.net/bugs/1578337>
[18:31] <mup> Bug #1578337 changed: no command to remove controllers <juju-core:New> <https://launchpad.net/bugs/1578337>
[18:36] <frobware> I was running `juju upgrade-juju --upload-tools' and ran into "ERROR POST https://192.168.19.150:17070/model/63ffd949-a9c4-4319-8b70-c33d505cc7ef/tools?binaryVersion=2.0-beta7.2-xenial-amd64&series=trusty,quantal,saucy,yakkety,wily,precise,vivid,xenial,raring,utopic Forbidden Port" - is this a known issue?
[18:43] <mup> Bug #1578337 opened: no command to remove controllers <juju-core:New> <https://launchpad.net/bugs/1578337>
[19:11] <katco> the true test of a tiling wm... my mouse cursor disappears =|
[19:29] <redir> katco: i3?
[19:29] <katco> yep
[19:29] <katco> redir: yep
[19:29] <redir> katco: mine doesn't
[19:29] <katco> redir: doesn't what?
[19:29] <redir> disappear
[19:30] <katco> redir: oh, no, i wouldn't expect it to. i've been using i3 for a few years, i've just triggered some kind of bug
[19:30] <redir> oic
[19:31] <katco> redir: and i expect it's not a bug in i3
[19:31] <natefinch> my cursor disappears about once a month, but I use unity
[19:31] <katco> natefinch: redir: it seems to happen when i mouse over the ubuntu terminal
[19:31] <katco> natefinch: redir: not all the time, but when the bug happens that seems to be what i was doing
[19:31] <redir> running the 1.x tests wipes out all open terminals or spams them with systemd messages
[19:31] <natefinch> katco: easy fix, don't do that ;)
[19:31] <katco> o.0
[19:32] <katco> natefinch: you're absolute right. i should be using the emacs terminal ;p
[19:32] <redir> katco: ahhh, I have terminator set as sensible-terminal
[19:32] <natefinch> redir: yeah, the systemd thing with the 1.x tests is super annoying
[19:33] <mgz> did you guys open a bug for that?
[19:35] <natefinch> mgz: you mean for the mouse thing?
[19:35] <mgz> I mean for running the tests doing weird things
[19:36] <natefinch> mgz: I think there was one open for it.... don't remember exactly
[19:48]  * redir thought it was a feature
[19:49] <redir> ericsnow: another same thing different branch review http://reviews.vapour.ws/r/4768/ -- no major rush as the target is blocked.
[19:50] <redir> brb reboot
[20:35] <mup> Bug #1578373 opened: unblock panic: invalid memory address or nil pointer dereference <jujuqa> <panic> <unblock> <juju-core:Triaged> <https://launchpad.net/bugs/1578373>
[20:50] <natefinch> moved a true unit test to a test suite that doesn't do setup or teardown, shortened test length by 2/3rds :/
[20:50] <perrito666> anyone could check this very brief yet critical patch? http://reviews.vapour.ws/r/4769/
[20:51] <katco> natefinch: \o/ keep doing stuff like that. we'll widdle away at this problem yet!
[20:51] <katco> whittle?
[20:51] <katco> i don't know how to spell that.
[20:51] <perrito666> still sounds foreign to me :p
[20:53] <mup> Bug #1578376 opened: Cannot add MAAS credentials through juju add-credential <juju-release-support> <maas-provider> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1578376>
[20:53] <mup> Bug #1578383 opened: incorrect extension on resource upload <juju-core:New> <https://launchpad.net/bugs/1578383>
[20:53] <natefinch> katco: it's just one of many reasons why I don't like testsuites... it's too easy to fall into the trap of just adding another test to the existing suite, even if it doesn't need any of the setup or teardown.
[20:54] <katco> natefinch: yes. it would be much better to share functionality by making shared code functions, not methods.
[20:56] <natefinch> katco: yep
[20:58] <mgz> katco: I'm pretty sure 'widdle' is as in, to pee on
[20:58] <katco> mgz: o.o
[20:59] <katco> mgz: what do you brits know about the english language anyhow
[20:59] <mgz> so unless our test suite is on fire, I'm not sure we widdling away on it will help...
[20:59] <katco> mgz: ...well
[20:59] <mgz> :P
[20:59] <katco> mgz: it is a tire fire, so.
[20:59] <natefinch> lol
[21:00] <natefinch> widdling on a tire fire probably doesn't help ;)
[21:00] <natefinch> especially one of this size
[21:01]  * natefinch pauses widdling for dinner
[21:13] <babbageclunk> So this is what you folks talk about when we go to sleep.
[21:13] <babbageclunk> :)
[21:36] <redir> perrito666: why can't one use %#v with tomb?
[21:40] <perrito666> we think that might trigger, through reflection, reading on attributes being written in other routines
[21:45] <redir> Thanks perrito666
[21:52] <thumper> ugh
[21:53] <thumper> bit by my first golang 1.6 issue (I'm still on 1.5)
[21:53] <mup> Bug #1576695 changed: Deployer 2 on trusty cannot talk to Juju2 because :tlsv1 alert protocol version <ci> <deployer> <maas-provider> <python2.7> <regression> <juju-core:Invalid> <juju-deployer:New> <https://launchpad.net/bugs/1576695>
[21:53] <mup> Bug #1576873 changed: Juju2 cannot deploy centos workloads on maas 1.9 <blocker> <centos> <ci> <maas-provider> <regression> <cloud-images:New> <juju-core:Won't Fix by natefinch> <https://launchpad.net/bugs/1576873>
[21:53] <mup> Bug #1577798 changed: azure 400 bad request creating networks <azure-provider> <blocker> <bootstrap> <ci> <juju-core:Invalid> <https://launchpad.net/bugs/1577798>
[21:56] <babbageclunk> hey menn0, thumper - any idea why strace starts giving me nonsense numbers when I pass -f (trace children)?
[21:56] <thumper> babbageclunk: no idea sorry
[21:57] <babbageclunk> Seems like maybe it's something like it's subtracting too much from the times to compensate for tracing overhead. cProfile can do that sometimes in Python land.
[21:58] <menn0> babbageclunk: doesn't ring any bells for me either
[22:01] <babbageclunk> :(
[22:02] <alexisb> thumper, wallyworld ping
[22:02] <babbageclunk> Ahh well, also passing overhead of 0 doesn't help.
[22:16] <perrito666> wow, I completely forgot about the graduated reviewer thing
[22:17] <perrito666> hey, could someone review http://reviews.vapour.ws/r/4769/diff ?
[22:40] <wallyworld> thumper: can you join https://plus.google.com/hangouts/_/canonical.com/moonstone
[22:42] <perrito666> oh great, we are in one of those "no reviewers" timezone holes :p
[22:46] <axw> wallyworld: when you're free, can I please get your eyeballs on http://reviews.vapour.ws/r/4765/
[22:46] <wallyworld> sure
[23:00] <thumper> wallyworld: still want me/
[23:00] <thumper> ?
[23:00] <thumper> was making coffee
[23:01] <wallyworld> thumper: all good, there was a question over payload persistence. eric will look to move it across tomorrow
[23:01] <thumper> ok, cool
[23:34] <axw> wallyworld: http://reviews.vapour.ws/r/4770/ another one please
[23:34] <wallyworld> sure
[23:35] <wallyworld> axw: ooops, i missed that in review
[23:36] <axw> wallyworld: all good, it's subtle
[23:46] <perrito666> wallyworld: I might need to ignore your comment, some checks might trigger a race even though is harmless
[23:47] <wallyworld> perrito666: not sure how. we already access the NotifyId or whatever it is from the result params, we just need to check the Error attribute too