mupBug #1346597 opened: cannot get replset config: not authorized for query on local.system.replset <cloud-installer> <landscape> <oil> <juju-core:Incomplete> <juju-core 1.24:Won't Fix> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1346597>00:04
mupBug #1575895 opened: juju loses apt-http/s-proxy information if a model is deleted and a new one created <add-model> <juju-release-support> <landscape> <rc1> <usability> <juju-core:Incomplete> <https://launchpad.net/bugs/1575895>00:04
rediraxw mostly just a question, when I `juju add-model --region us-east-1 foo` from a controller boostrapped in `us-west-1`, does anything actually happen in `us-east-1`? or is that all stored on the controller and nothing happens in us-east-1 until I `juju deploy something`?00:20
rediraxw: I was under the impression from my convo with wallyworld that I should see something come up when I add a model to another region, but it makes sense that it wouldn't, too.00:21
menn0axw: rubber stamp pls http://reviews.vapour.ws/r/5467/00:34
thumpermenn0, axw, wallyworld: thoughts ?  http://reviews.vapour.ws/r/5468/00:36
wallyworldoutput looks nice00:37
menn0thumper: +1 the output and args are nice00:38
menn0thumper: ship it00:44
axwredir: atm, nothing happens. we may change it soon so that the model's security group gets created when you add the model00:48
rediraxw tx01:01
redirgtg. Until tomorrow, #juju-dev01:16
wallyworldcmars: yo01:26
wallyworldcmars: you and roger really need to talk more, or you need to read his email :-D01:27
natefinchaxw or anyone else.... trying to run juju on windows, but it seems to die mysteriously right away? http://pastebin.ubuntu.com/23066001/02:03
axwnatefinch: probably https://bugs.launchpad.net/juju-core/+bug/161283602:03
mupBug #1612836: Cannot bring up hosted  model machines in azure <azure-provider> <ci> <deploy> <regression> <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1612836>02:03
axwnatefinch: one mo, I have a small patch you can apply to test02:04
axwnatefinch: http://paste.ubuntu.com/23066004/02:04
natefinchaxw: will give it a go02:06
natefinchaxw: thanks02:06
axwnatefinch: if you have a moment to review, the fix is in a PR now: http://reviews.vapour.ws/r/5469/02:33
natefinchaxw: sure02:33
natefinchaxw: doh - axw/juju-tools/main.go:45: cannot use buildToolsCommand literal (type *buildToolsCommand) as type modelcmd.ModelCommand02:39
natefinchaxw: bah,. it's because gnuflag moved02:39
axwnatefinch: ah, I'll update it in a moment02:39
axwnatefinch: pushed02:41
natefinchaxw: cool02:43
natefinchI really love that go install has no middle man between git push and me getting and installing the code.02:43
natefinchlike, no npm repository to update or anything.  Just get the code from git and build it.02:44
natefinchI wish kill controller had a --jfdi that would just kill the machines via the provider... waiting for azure to nicely close everything down is so slow...02:46
mupBug #1614329 opened: Cannot deploy charm to new lxd container on machine: permissions error <lxd> <juju-core:New> <https://launchpad.net/bugs/1614329>02:46
mupBug #1614330 opened: agree command uses 'less' for a pager, fails on windows <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1614330>02:46
axwnatefinch: I often just "azure group delete -q <resource group> --nowait", then "juju unregister -y <controller>"02:54
natefinchaxw: nice02:58
axwnatefinch: groups are quite neat - only one thing to delete, and your model or controller is cleaned out02:59
axwthe time they take to delete is just a bit painful03:00
anastasiamacpretty awesome suffix git put on commit 0806e96e6e79b530161cbb40f54bd8b338e0bad103:04
thumperaxw: where will I find the code that stores storage-pool settings?03:06
thumperthink I've found it03:10
axwthumper: sorry went afk, sorted?03:12
axwwallyworld: if we start making API calls in list-controllers, then one bad controller is going to hang the whole command. can we isolate the access to show-controller at least?03:15
wallyworldthat becomes rather inconvenient for a user to see at a glance what they have access to03:16
wallyworldbut you are right about a bad controller03:16
wallyworldmaybe it has to be show controller03:17
thumperaxw: will there ever be storage pools for pools that aren't defined on volumes or filesystems?03:37
axwthumper: non capisco. do you mean "will there ever be storage pools that aren't referred to by volumes or filesystems"?03:38
thumperwill there be pool settings for pools not currently refered to03:39
axwthumper: if so, yes. e.g. when you bootstrap ec2, you get a storage pool out of the box called "ebs-ssd"03:39
thumperhow do I know all the pool names?03:39
axwthumper: storage/poolmanager.PoolManager.List03:39
axwname is part of the config returned03:40
thumperactually, I could just iterate through all settings looking for "pool#" prefix03:40
thumperI have all the settings read03:41
axwor that03:41
thumperperhaps that :)03:41
mupBug #1614345 opened: add-subnet subcommand references absent create-subnet command <usability> <juju-core:New> <https://launchpad.net/bugs/1614345>03:46
wallyworldaxw: i did it for show controllers, but also added a tabular option to show controllers to make the output nice if needed04:16
axwwallyworld: sounds good04:17
wallyworldi'll now move on to list-models and list-users04:17
veeberswallyworld: re: --build-agent, can it use just a binary in path (i.e. for jujud) or does it need to build from source?04:23
wallyworldveebers: it uses a binary in the path if build-agent is not specified04:24
wallyworldbuild-agent means build04:24
veeberswallyworld: hmm ok. Is it still possible to pass something in to upgrade-juju to get the build number bumped (as I was trying with --upload-tools). Does that require --build-agent?04:26
wallyworldno need, the build number is bumped regardless04:26
veeberswallyworld: ok cool, thanks :-)04:28
wallyworldif you find an issue, let me know04:28
veeberswill do :-)04:28
thumpermenn0: http://reviews.vapour.ws/r/5472/04:39
menn0thumper: about to do a kid pickup. will review after.04:39
mupBug #1614364 opened: manual provider lxc units are behind NAT, fail by default <manual-provider> <uosci> <juju-core:New> <https://launchpad.net/bugs/1614364>04:49
axwwallyworld: I have reviewed http://reviews.vapour.ws/r/5471/, would appreciate if you would also take a look later, after anastasiamac has responded to comments04:51
wallyworldaxw: np, just popping out to get kid from camp, bbiab04:52
axwwallyworld: there's lots of changes, but there's a bunch of discrete changes in separate commits on github04:52
axwthanks, later04:52
mupBug #1604474 changed: Juju 2.0-beta12  userdata execution fails on Windows <azure-provider> <ci> <juju2.0> <oil> <oil-2.0> <regression> <vpil> <windows> <juju-core:Fix Released by natefinch> <https://launchpad.net/bugs/1604474>05:19
thumperaxw: hmm... part of the reason of using the database implementation to get at the storage pools is that is exactly what the migration import and export code does, it does low level database stuff, which is why the entire setting collection is read at once05:20
thumperall the migration code has deep knowledge of implementation details05:20
thumperthat is how it works05:20
thumperI'm happy enough changing the core description definition05:21
axwthumper: I guess that's fine, changing core description would be enough then05:21
thumperto make it slightly less hacky05:21
axwthumper: though I thought importing didn't involve inserting docs?05:21
axwthumper: but using AddMachine, etc.05:21
thumperhaha, no05:21
thumpernot at all05:21
thumpermuch hacky doc op foo05:22
axwthumper: yeah that wouldn't work, not sure what I was thinking :)  very well then05:22
thumpermost of the AddMachine etc high level function try to apply checks we don't want05:22
* axw nods05:22
mupBug #1604474 opened: Juju 2.0-beta12  userdata execution fails on Windows <azure-provider> <ci> <juju2.0> <oil> <oil-2.0> <regression> <vpil> <windows> <juju-core:Fix Released by natefinch> <https://launchpad.net/bugs/1604474>05:22
thumperI'll tweak the description :)05:23
thumperhmm.. why has review board stopped updating with some changes?05:23
thumperphew... romulas command branch finally landed05:24
thumperweird, because it found http://reviews.vapour.ws/r/5474/05:25
mupBug #1604474 changed: Juju 2.0-beta12  userdata execution fails on Windows <azure-provider> <ci> <juju2.0> <oil> <oil-2.0> <regression> <vpil> <windows> <juju-core:Fix Released by natefinch> <https://launchpad.net/bugs/1604474>05:28
menn0thumper: ship it on the loggo one05:37
thumpermenn0: I'm just updating the storage pools05:37
thumperwhich loggo one?05:37
menn0thumper: the small one which changes the default writer05:37
thumperthe cmd one?05:37
thumperI see it :)05:38
thumperI hope it lands due to deps05:38
thumperif not, I'll poke veebers :)05:38
thumpermenn0: https://github.com/juju/juju/pull/602505:39
menn0thumper: RB now working?05:40
thumpermenn0: didn't pick up that one05:40
thumperno idea why05:40
menn0thumper: LGTM, with one query05:43
* menn0 wants this stuff to land so he can see what it looks like05:44
thumpermenn0: it is different due to loggo.Level vs. string key05:44
thumperdebug-log sends but string representations of the level05:44
menn0thumper: ah right. makes sense.05:44
menn0thumper: all good.05:44
veebersthumper: Hey I'm about to EOD, did you want me to take a look at something?05:45
thumpergimmie two ticks05:45
thumperveebers: nope, all good05:46
veebersthumper: sweet :-)05:46
menn0thumper: VALIDATION phase done... pushing now05:56
thumperI have two branches06:08
thumperand was getting confused06:08
thumperand debug-log-color06:08
thumperwas editing wrong one06:08
blahdeblahHi folks; anyone know if there has ever been any attempt to deploy juju environments in a fully disconnected environment?  i.e. no streams available, no charm store, no external repos06:10
thumpernot something I do personally06:13
thumperblahdeblah: some of the folk with orange boxes do I think06:13
blahdeblahthumper: OK, interesting; any suggestion who to talk to?06:13
thumpertry scott06:14
* thumper looks for nick06:14
thumperScott Croft06:14
thumperI think he has06:14
blahdeblahthanks thumper06:21
=== akhavr1 is now known as akhavr
=== frankban|afk is now known as frankban
voidspacefrobware: ping09:07
frobwarevoidspace: hi09:07
voidspacefrobware: hey, hi09:07
voidspacefrobware: I'm looking at a 1.25 port of the fix  for bug 160271609:08
mupBug #1602716: MAAS provider bridge script doesn't handle alias interfaces IP <2.0> <maas-provider> <network> <sts> <juju-core:Fix Released by freyes> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1602716>09:08
voidspacefrobware: even with the new code in place, 1.25 doesn't bridge the alias09:08
voidspacefrobware: is this because 1.25 does a lot less bridging than 2.0?09:08
frobwarevoidspace: yes09:08
frobwarevoidspace: we only brindge the default route09:09
voidspacefrobware: so I'll leave the code in place, but mark the specific bug as wontfix for 1.25 (again)09:09
frobwarevoidspace: is there harm it being there? in general I think the bridge script should be identical between 1.25 and 2.009:09
voidspacefrobware: I've put the code in there - but there was a card to handle it linked to the LP bug09:10
voidspacefrobware: so I'm landing the code but it doesn't actually fix the bug... I was just checking this was expected.09:10
voidspacefrobware: which you've confirmed. So thanks.09:11
frobwarevoidspace: this is not expected. why doesn't it fix the bug?09:11
voidspacefrobware: on 1.25 it doesn't fix the bug because we don't bridge the alias (which was the bug)09:11
voidspacefrobware: surely?09:11
frobwarevoidspace: hmm. can you create an alias for the default route (MAAS UI) and validate that we bridge the alias09:12
frobwarevoidspace: you'll need an alias for this to make sense09:13
voidspacevoidspace: I have an alias for eth0, eth0 is bridged but eth0:1 isn't - as expected09:14
voidspacefrobware: I have an alias for eth0, eth0 is bridged but eth0:1 isn't - as expected09:14
voidspacefrobware: if I now disable eth0 should that make the alias the default route, or should I do something else?09:14
frobwarevoidspace: can you PB your original ENI09:16
voidspacefrobware: http://pastebin.ubuntu.com/23066815/09:17
voidspacefrobware: that's before and after09:18
voidspacefrobware: the gateway is specified on the bond, should I create an alias for that?09:19
frobwarevoidspace: looking at the PB09:20
voidspacere-bootstrapping with an alias to the bond as well and grabbing coffee09:21
frobwarevoidspace: the script seems broken09:23
frobwarevoidspace: I take that back. apologies.09:25
frobwarevoidspace: you can do this without rebooting - just run the script on the original eni, observing the output depending on what you pass to --interface-to-bridge09:26
voidspacefrobware: so what should I test for 1.25?09:29
frobwarevoidspace: still looking and understanding...09:29
voidspacefrobware: ok09:29
frobwarevoidspace: do you have an ENI where bond0 has an alias?09:29
voidspacefrobware: this is the branch https://github.com/juju/juju/pull/601309:29
voidspacefrobware: I just did that - bond0 is still active though09:30
voidspacefrobware: juju-br0 is created but the bond alias is left in place, no additional bridge is created09:30
voidspacefrobware: if we only bridge the interface with the gateway (which I assume is the default route) then that is still expected I think09:31
frobwarevoidspace: if you're running the script by hand, you can ignore the gateway bit. the arguments --interface-to-bridge and --bridge-name control what gets bridged09:32
frobwarevoidspace: on 2.0 we don't use those arguments so everything (appropriate) gets bridged09:32
voidspacefrobware: so it won't fix the specific bug for 1.25 (unless the alias is the default route) but it's nice to have the code the same in both 1.25 / 2.0 for maintenance09:34
frobwarevoidspace: yes, for the latter. but you can have an alias so we should check what it would do09:35
frobwarevoidspace: just a little confused about what its doing for the 2.0 case atm09:35
voidspacefrobware: ok09:35
voidspacefrobware: dimitern and I have both tested this branch with deploys and it seems to work fine09:36
voidspacefrobware: http://reviews.vapour.ws/r/5460/09:36
frobwarevoidspace: deploys that involve an alias on 1.25?09:36
voidspacefrobware: you can see what dimitern used in his comment on the review09:36
frobwarevoidspace: and an alias on the interface that is the default route?09:37
voidspaceI'm just looking now09:37
voidspaceah no, not an alias09:37
dimiternfrobware: no aliases09:37
frobwarevoidspace: isn't that a different PR?09:37
dimiternis it broken with them?09:37
frobwarevoidspace: that PR is about the MTU09:38
voidspacefrobware: yeah, but I rolled the code into that09:38
voidspacefrobware: so no, that's the right PR09:38
voidspacefrobware: I did one PR with all the new code09:38
frobwarevoidspace: why not separate PRs?09:38
frobwarevoidspace: that makes no sense to me. if we ever had to revert the MTU for example we just added/created more work09:39
voidspacefrobware: because the patches didn't apply cleanly - so it would have been a lot more work to do as separate patches09:39
frobwarevoidspace: why not separate patches?09:39
voidspacefrobware: we created "possibly more work" - doing them separately now would be "definitely more work"09:39
frobwarevoidspace: disagree. we should do discrete things.09:39
voidspacefrobware: because the patches don't apply cleanly as separate patches09:39
frobwarevoidspace: but we can fix the patches per PR09:40
voidspacefrobware: I understand your disagreement. This patch is really "bring 1.25 up to using the same code for bridging as 2.0" which is a discrete thing.09:41
frobwarevoidspace: fwiw, I think this is the wrong approach. patches should be discrete so that they can be reverted if necessary. seems like we have conflated things.09:41
voidspacefrobware: I understand and I don't think it is worth the extra effort. If this patch introduces regressions it can be reverted.09:42
frobwarevoidspace: so i think the script is broken for the single use case, where single use means we explicitly pass the interface name to be bridged10:05
* frobware was trying to look at yakkety... and wonders how much more of this fun and games is to come in netplan10:05
frobwarevoidspace, dimitern: https://bugs.launchpad.net/juju-core/+bug/161447110:18
mupBug #1614471: MAAS bridge script doesn't bridge aliases correctly where --interface-to-bridge is specified <juju-core:New> <https://launchpad.net/bugs/1614471>10:18
voidspacefrobware: ok10:19
voidspacefrobware: what do you think the right fix is for 1.25, or will that need some thinking about?10:19
frobwarevoidspace: just going to try it10:20
frobwarevoidspace: not a fix, just to understand the current behaviour10:20
voidspacefrobware: I can look at breaking the patch into pieces and talk to Rick about it. I have a critical bug I'm assigned to in the meantime (although that should be easy).10:20
voidspacefrobware: sure10:20
frobwarevoidspace: take a look at the critical patch - was going to try the alias stuff10:21
voidspacefrobware: I can't create an alias that is the default route on my maas setup, but it can be done by directly calling the script10:21
frobwarevoidspace: even if that means I'm just doing some additional QA10:21
voidspacefrobware: ok10:21
frobwarevoidspace: I'm wondering if the alias stuff would have worked if we had landed 395cd8d812c004e8c9a8783c47fcfc22ded9de2e some time earlier.10:22
frobwarevoidspace: or more conveniently https://github.com/juju/juju/pull/579210:23
frankbanaxw: could you please take a look at http://reviews.vapour.ws/r/5475/ ?10:23
babbageclunkMy ssd died. :(10:29
mupBug #1614471 opened: MAAS bridge script doesn't bridge aliases correctly where --interface-to-bridge is specified <juju-core:New> <https://launchpad.net/bugs/1614471>10:32
babbageclunkdimitern, voidspace, frobware: my ssd died. Setting up on a loaner machine now (my ansible script has mostly worked!).10:48
* dimitern is back; catching up11:02
dimiternbabbageclunk: oh bugger :/ any notable losses?11:08
voidspacebabbageclunk: :-( but glad you're getting set back up11:09
dimiternfrobware: re bug 161447111:09
mupBug #1614471: MAAS bridge script doesn't bridge aliases correctly where --interface-to-bridge is specified <juju-core:New> <https://launchpad.net/bugs/1614471>11:09
dimiternfrobware: I'm not sure we should create juju-br0:1 in that case11:09
frobwaredimitern: because?11:10
dimiternfrobware: how will that be useful?11:10
dimiternfrobware: juju-br0 will work with its primary IP coming from eth0, which will be on the default route as well11:11
frobwaredimitern: so... this is what I'm trying to understand. why was it broken and would the presence of an auto stanza have fixed the initial bug report11:11
dimiternfrobware: eth0:1 will also work, if you need for some reason not to go through juju-br011:11
dimiternor perhaps it won't actually..11:12
* dimitern gives it a quick test11:12
babbageclunkdimitern: Lost a couple of days work. :( Really wish I'd pushed yesterday afternoon.11:24
dimiternbabbageclunk: oh man :( sorry!11:25
dimiternyeah, pushing at EOD is a good rule of thumb11:25
dimiternfrobware: so if we're bridging aliases as well, what happens if the alias is on a different subnet?11:26
dimiternfrobware: that would imply a separate bridge, not just moving the alias address over to the bridge11:26
fwereadeso, I am without power where I'm staying, and am rather stuck with cafes if I want internet11:30
fwereadeI'll be catching up on mail and reviews and stuff while I'm here, but if anyone wants my advice/company/whatever, they should talk to me while I'm here11:33
dimiternfwereade: are you in the uk?11:44
fwereadedimitern, yeah12:02
dimiternfwereade: so brexit reached the power companies? :)12:02
fwereadedimitern, haha12:03
fwereadedimitern, not yet, that I'm aware of ;p12:03
dimiternfwereade: ;) too early12:03
fwereadedimitern, trouble in the building, people are working on it12:03
dimiternfwereade: is your bandwidth wide enough for a HO, if you have some time as well?12:04
fwereadedimitern, HO probably not great, there's background noise12:04
dimiternfwereade: I'd like to chat about the ipam story and how it fits in core12:04
dimiternfwereade: right, ok - irc then :)12:05
voidspacefrobware: I think you're right - with auto the interface would have come up and the fact that it wasn't bridged would only have mattered for containers12:26
voidspacefrobware: so for 1.25 just ensuring the auto is there is enough12:26
voidspacefrobware: *unless* it's an ipv6 specific thing12:27
voidspacefrobware: can you effectively have two default routes, one for ipv6 and one for ipv4?12:27
voidspacefrobware: the alias in the original bug report was ipv612:27
dimiternfrobware, voidspace: I've tested with eth0 bridged to juju-br0 and eth0:1 not, deployed 3 lxc containers - works fine12:38
voidspacefrobware: ah no, in the original bug report the alias does have auto in the generated /e/n/i12:42
voidspacedimitern: cool12:42
frobwarevoidspace: yeah, I don't know how ipv6 creeped into that12:43
frobwarevoidspace: I think you raise a good point about containers - should aliases be bridged for containers?12:48
frobwaredimitern: ^^12:48
frobwarevoidspace, dimitern: can we HO re: aliases?12:49
voidspacefrobware: ok with me12:49
voidspacefrobware: in 1.25 we only alias the default route, we don't provide multi-nic support - which probably means no ipv6  support if that's on a separate interface/alias12:50
dimiternfrobware: sure12:50
voidspacefrobware: which is probably fine as we're doing it in 2.012:50
voidspacefrobware: HO channel?12:50
frobwarevoidspace: standup12:50
babbageclunkmgz: ping?12:58
voidspacemgz: ping12:58
babbageclunkvoidspace: dibs12:58
voidspacemgz: do you still want a review from me? you were going to create some PRs12:58
niedbalskifwereade, ping12:59
voidspacebabbageclunk: haha, good luck with that...13:00
fwereadeniedbalski, pong13:00
fwereadeniedbalski, what can I do for you?13:00
babbageclunkvoidspace: I'm pretty sure etiquette dictates that he talk to me first.13:00
mgzbabbageclunk: yo13:01
mgzvoidspace: alyo13:01
niedbalskifwereade, hey William :) , Could you check this https://pastebin.canonical.com/163030/? this is preventing to start the units. I think is related to LP: #153410313:02
mupBug #1534103: "unknown operation kind run-action" (1.26alpha3) <2.0-count> <actions> <sts> <juju-core:Triaged by rharding> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1534103>13:02
babbageclunkmgz: Hey, the mgo fix is in upstream, so we no longer need to apply the nasty patch in our build.13:02
niedbalskifwereade, here is the current action list on the database (I've a full mongo dump) http://pastebin.ubuntu.com/23067364/13:02
babbageclunkmgz: If I land a change to remove the .diff file, juju/juju/patches is probably going to disappear (since there's nothing else in it).13:02
fwereadeniedbalski, that just looks like... utterly broken uniter code13:03
babbageclunkmgz: Is that going to break your script that applies the patch?13:03
fwereadeniedbalski, looking further13:03
babbageclunkmgz: Or, I could leave a readme file in patches to keep the dir alive in the repo. Would your script cope with that?13:04
mgzbabbageclunk: a readme sounds good to me13:05
mgzbabbageclunk: it does not at present but that should change I think13:07
mgzvoidspace: I shall link you my prs, onesec13:08
voidspacemgz: cool, thanks13:08
babbageclunkmgz: I guess the alternative is a null patch, but if you're happy to change the script that's probably less obtuse.13:08
voidspacebabbageclunk: pthbthpthbthpt13:08
mgzbabbageclunk: so, options, delete the dir, add note to general hacking docs somewhere13:08
mgzbabbageclunk: or add dummy file for git in patches dir, make sure that lands after I update the script13:08
babbageclunkvoidspace: don't care, he responded to me first. I'll allow multiplexing.13:08
voidspacebabbageclunk: I refer the honourable gentleman to my previous comment (pthbthpthbthpt)13:09
mgzvoidspace: https://code.launchpad.net/~gz/juju-ci-tools/jujupy_ssh_keys13:09
mgzvoidspace: https://code.launchpad.net/~gz/juju-ci-tools/assess_ssh_keys13:09
voidspacemgz: looking13:09
mgzvoidspace: I'll bug a qa guy as well, so don't worry too much about juju-ci-tools specifics, but feedback on approach/code welcome13:10
fwereadeniedbalski, and, yeah, that bug looks like completely broken uniter code as well13:10
babbageclunkmgz: I'm ok with the latter option - having the note in the dir is probably more useful than in the docs somewhere.13:10
mgzbabbageclunk: so, we think patcher should only apply things named *.patch in the dir given?13:11
mgzor some other rule would be more suitable?13:11
fwereadeniedbalski, I don't have any immediate insight, except that it's 99.99% certainly a uniter problem and mongo isn't relevant13:12
voidspacemgz: ok, one of those branches has conflicts (the assess one)13:12
babbageclunkmgz: The existing one is called *.diff, so should probably use that.13:12
mgzvoidspace: yeah, I did the merge for it's prereq but having propogated that merge yet13:12
babbageclunkmgz: but otherwise yes.13:12
babbageclunkmgz: Although now you say it *.patch is better.13:13
niedbalskifwereade, OK, I tried restarting the agent, then it enters in the agent.go:17 [AGENT-STATUS] failed: resolver loop error, state.13:13
niedbalskifwereade, can you think on any way to manually workaround this?13:13
mgzlets allow both, I will just not be able to glob13:14
voidspacemgz: first one is fine, nice and straightforward13:15
voidspacemgz: I hate __metaclass__ = type13:15
voidspacemgz: :-(13:15
voidspacemgz: but I'm sure we've had this discussion before13:15
voidspaceand future imports generally13:16
voidspacemagic stuff at the start of a file that changes the semantics of code later in the file13:16
mgzvoidspace: I am also not a fan, but am following style13:17
voidspacemgz: yeah13:17
fwereadeniedbalski, not without hand-hacking the uniter state file and I am very uncertain about what consequences would follow from that13:17
voidspacemgz: hardcoding the key in the script?13:17
voidspacemgz: VALID_KEY13:18
voidspacemgz: ah, is that a test13:18
voidspacefair enough then13:18
fwereadeniedbalski, my immediate judgement is more "omg that bug is clearly critical, how has it been hanging around for 8 months" :(13:18
mgzvoidspace: yeah, could use ssh-keygen to make one up on the fly, but just using a known valid thing is fine I think?13:19
niedbalskifwereade, agree :)13:19
voidspacemgz: if it's just for a test fine13:19
voidspacemgz: that all looks fine to me13:20
mgzvoidspace: thanks!13:20
voidspacesome interesting patterns in the testing there13:21
voidspacelooks good13:21
niedbalskianastasiamac, fwereade Could be possible to flag LP: #1534103 as critical for the next beta release?13:24
mupBug #1534103: "unknown operation kind run-action" (1.26alpha3) <2.0-count> <actions> <sts> <juju-core:Triaged by rharding> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1534103>13:24
anastasiamacniedbalski: fwereade: sure :D William, shall I assign it to u?Happy to tackle it?13:26
fwereadeanastasiamac, niedbalski: just did so13:27
fwereadeanastasiamac, mmmmmmmight be better targeted to axw/wallyworld, I am having real trouble with the charm-deletion bits13:27
fwereadeanastasiamac, and they're likely more immediately familiar with that code13:28
anastasiamacfwereade: k.. we'll assign at release call, unless rick_h_ has a better plan13:28
fwereadeanastasiamac, cheers13:28
anastasiamacfwereade: niedbalski: \o/13:29
* rick_h_ 's ears tingle 13:29
niedbalskifwereade, anastasiamac thank you!13:29
anastasiamacniedbalski: nps -it's not fixed yet :D13:30
rick_h_niedbalski: do we have somehting to replicate with?13:30
niedbalskirick_h_, unfortunately I am not able to replicate that bug locally; It's happening on a beta7 installation on which we have access/logs/dumps.13:32
rick_h_niedbalski: right, so the question for us will be how to replicate/verify it's fixed13:33
mgzbabbageclunk: please review https://code.launchpad.net/~gz/juju-release-tools/non_patch_ext/+merge/30326313:33
rick_h_it looks like it's happened with a few differnt actions on different workloads, benchmarking, casey's stuff, and openstack in the bug13:34
fwereaderick_h_, niedbalski: it looks like it should be reproable by unit test13:34
niedbalskirick_h_, yep, we need to work on getting consistent reproducer, so far, no luck for me.13:34
rick_h_fwereade: can you brain dump any helpful info for someone to chase down into the bug please?13:34
babbageclunkmgz: LGTM! Spelling error - should be PATCH_EXTENSIONS13:35
fwereaderick_h_, it'll be about 1 vague sentence but I will try to compose a helpful one13:35
mupBug #1614471 changed: MAAS bridge script doesn't bridge aliases correctly where --interface-to-bridge is specified <juju-core:Invalid> <https://launchpad.net/bugs/1614471>13:35
mgzbabbageclunk: ehe, whoops13:36
mgzdid I tyop that twice, or copy or, or can I just not spell? I am not sure.13:37
natefinchthat feeling when you typo the word typo13:41
dimiternfrobware: so with the eni produced by the script, it boots ok and here's the routes and addresses: http://paste.ubuntu.com/23067462/13:55
frobwaredimitern: and presumably an ipv6 route13:56
frobwaredimitern: curious that it doesn't fail on 'post-up ifup eth0:1'13:56
dimiternfrobware: yeah - both ipv6 addrs ended up on br-eth1 though13:59
rick_h_dimitern: fwereade voidspace macgreagoir ping for standup14:00
dimiternomw T-10s14:00
voidspacerick_h_: omw14:04
mupBug #1614559 opened: Juju rejects lxd 2.1 <blocker> <bootstrap> <ci> <jujuqa> <lxd> <regression> <juju-core:Triaged by rharding> <https://launchpad.net/bugs/1614559>14:36
natefinchrick_h_:  you want me to fix that security bug?14:38
rick_h_natefinch: yes please14:45
rick_h_natefinch: hopefully more a packport than anything14:45
natefinchrick_h_: it's tricky, because the code is in the juju/utils repo, so updating 1.25 with a new version of that may break other things.  BUt maybe I'll get lucky and it won't be a big deal14:47
natefinchfwereade: I really wish juju controllers listed the juju version14:56
mupBug #1614571 opened: Data race: TestLogOutput <ci> <jujuqa> <race-condition> <unit-tests> <juju-core:Triaged by rharding> <https://launchpad.net/bugs/1614571>15:03
katcorick_h_: ta for the response; updated 1614329. lmk what you think15:13
katcobug 1614329 that is15:13
mupBug #1614329: Cannot deploy charm to new lxd container on machine: permissions error <lxd> <juju-core:New> <https://launchpad.net/bugs/1614329>15:13
rick_h_katco: looking ty15:14
katcorick_h_: another update with a simpler/alt repro. sorry if i'm nto being clear15:17
redirmorning juju-dev15:54
katcoredir: morning15:55
* rick_h_ lunches16:01
mupBug #1614599 opened: i/o timeout downloading resource <ci> <intermittent-failure> <jujuqa> <resources> <juju-core:Incomplete> <https://launchpad.net/bugs/1614599>16:25
bleepbloopI have a bundle I exported from the juju gui in the current beta version and it fails to import and complains about `cannot unmarshal !!str `xenial` into charm.legacyBundleData`, is this a known issue?16:32
perrito666Pseudo morning16:33
rick_h_bleepbloop: not triggering any bells at the moment. can you file a bug over at the gui tracker https://github.com/juju/juju-gui please?16:36
bleepbloopSure will do16:36
redirpseudo morning, perrito66616:42
rediror maybe sudo morning16:42
bleepbloopredir is not in the sudoers file.  This incident will be reported.16:43
redirthat's awesome16:44
redirrick_h_: can we mark bug 1608533 as invalid or incomplete or something?16:46
mupBug #1614622 opened: Cannot list-resources <ci> <intermittent-failure> <jujuqa> <list-resources> <resources> <juju-core:Incomplete> <https://launchpad.net/bugs/1614622>16:46
mupBug #1608533: Race in github.com/juju/juju/apiserver/tools_test <ci> <race-condition> <regression> <unit-tests> <juju-core:In Progress by reedobrien> <https://launchpad.net/bugs/1608533>16:46
rick_h_redir: looking16:47
rediralso are you working on bug 1614571?16:47
mupBug #1614571: Data race: TestLogOutput <ci> <jujuqa> <race-condition> <unit-tests> <juju-core:In Progress by rharding> <https://launchpad.net/bugs/1614571>16:47
rick_h_redir: rgr, looks like it's not occurred since June so definitely ok putting it to bed unless it shows up again16:47
redirrick_h_: ^^^16:48
rick_h_redir: I am the target to assign bugs so I can gets folks assigned to work on16:48
rick_h_redir: so no, I'm not working on it but need to find someone to work on it.16:48
=== frankban is now known as frankban|afk
redirOK I'm happy to start trying to repro that in the bg while working... and switch to fixing when it triggers and I am otherwise waiting for a build  or bootstrap16:49
redirrick_h_: ^16:53
rick_h_redir: rgr ty much. Feel free to take it16:53
mupBug #1613487 changed: Fails to build tools when no matching tools found. <bootstrap> <ci> <regression> <juju-core:Fix Released by wallyworld> <https://launchpad.net/bugs/1613487>17:10
natefinchmgz. perrito666:  isee you both have committed stuff to juju/utils 1.25 branch lately.  What's the policy? Do we cherry-pick from master?17:11
mgznatefinch: I landed the same code on both branches17:11
mgzbasically in parallel17:12
mgzbut whatever work17:12
natefinchmgz: ok17:12
natefinchsinzui, mgz: 1.25 still builds with go 1.2, right?17:14
mgznatefinch: it needs to, yes17:17
mgzit will build with 1.6 but shouldn't require it17:17
natefinchmgz: right17:18
natefinchmgz: ok17:18
sinzuinatefinch: mgz: no, we switched the same say we switched master17:22
mupBug #1614633 opened: A unit with a failed storage-detaching hook cannot be destroyed <juju-core:New> <https://launchpad.net/bugs/1614633>17:22
sinzuimgz: natefinch there is a bug in Juju's Makefile that installs the wrong jgolang17:22
mgzsinzui: all the backported versions are also going to be 1.6?17:23
sinzuimgz: natefinch: Ci is testing with Go 1.6 install and the agents and clients are built with go 1.617:23
mgzI guess they can be, though I'm not crazy about changing compiler in sru minor updates17:24
sinzuimgz: golang-1.6 is in trusty universe. Of course the people preparing the ubuntu packages need to update controll an rules to match the ~juju packages17:25
natefinchwait... so we are building 1.25 with go 1.6?17:25
mgznatefinch: we are in CI17:25
mgzand curtis is saying we should be for the distro as well (but we aren't atm)17:26
sinzuinatefinch: I keep saying that on IRC and emails since April 10 2-1617:26
sinzuioh look, I pointed out the Makefile deps were wrong on April 1- too17:27
mupBug #1614633 changed: A unit with a failed storage-detaching hook cannot be destroyed <juju-core:New> <https://launchpad.net/bugs/1614633>17:28
natefinchI would fix the makefile except I think it's an abomination against nature17:28
natefinchwell good, I'll stop worrying about why I can't build the go tool for go 1.2 then17:29
* natefinch goes back to go 1.717:32
perrito666natefinch: lately?17:37
natefinchperrito666: top two PRs. More lately than anyone else :)17:38
perrito666natefinch: wow, those must be at least 3 months old17:38
mupBug #1614633 opened: A unit with a failed storage-detaching hook cannot be destroyed <juju-core:New> <https://launchpad.net/bugs/1614633>17:40
mupBug #1614635 opened: Bundle or app deploy fails behind a proxy <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1614635>17:40
rick_h_cmars: filed 8min ago: https://bugs.launchpad.net/juju-core/+bug/161463517:42
mupBug #1614635: Bundle or app deploy fails behind a proxy <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1614635>17:42
cmarsrick_h_, thanks, i'll keep an eye on it17:43
natefinchfor anyone with a little time to kill and who has ever played D&D: http://whothefuckismydndcharacter.com/18:08
* perrito666 uses his +10 in social life to repell that link18:09
natefinchkatco: ^^18:09
natefinchomg, it's so good18:10
natefinchquick backport review anyone? http://reviews.vapour.ws/r/5479/18:20
natefinchliterally copy and paste from master, all new code, so... anyone want to rubber stamp me?18:20
mgznatefinch: lgtm18:21
natefinchmgz: thanks18:22
redirwhat version of go are we using with juju on AWS currently?19:26
natefinchanother backport using the previously mentioned utils backport.  This one was manually created because for some reason cherry-pick was getting mad.... but it's just a mechanical change: http://reviews.vapour.ws/r/5480/19:26
natefinchredir: 1.6 for everything19:26
redirnatefinch: ?19:27
natefinchredir: 1.6.0 IIRC19:28
natefinchredir: why?19:28
redirnatefinch: but if I bootstrap from my machine it runs the agent built with my version, yes?19:28
natefinchredir: if you have a self-built client, it'll use the self-built server, yes.19:29
redirnatefinch: trouble reproducing races recently, and the only difference I can think of is the version of go that CI is building juju with19:29
natefinchraces might be load-dependent. I've definitely had ones that only happen if I'm deploying a large bundle etc.19:31
bleepbloopCould someone help me with respect to completely nuking the configuration of juju and restarting from scratch? I had juju 2 installed and I uninstalled it but it seems there are still some artifacts hanging around and I want to start completely fresh19:35
rick_h_bleepbloop: sudo updatedb && locate juju ?19:36
natefinchfor juju2, everything is stored in ~/.local/share/juju19:36
natefinchif you're switching to juju 1.x, you don't need to worry about it, they can run side by side19:37
natefinch(they use different storage paths, different environment variables, everything)19:37
redirnatefinch: yeah also have process loading the CPU to help drive contention to trigger the race -- hopefully19:38
* natefinch goes to see who is on call reviewer, sees that it is himself.19:39
bleepbloopThanks Nate and Rick, the leftover files that were messing things up were located in ~/.local/share/juju19:40
* redir lunches19:41
mupBug #1614689 opened: azure-arm provider is very slow <azure-provider> <ci> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1614689>20:26
voidspacerick_h_: did you get an ok on that 1.25 JFDI for network backports?20:38
rick_h_voidspace: sorry, I never looked for it tbh20:39
voidspacerick_h_: ok, no problem20:39
voidspacerick_h_: I'm hanging around to see if thumper appears so I thought I'd ask20:39
rick_h_voidspace: yea, I can ask folks now20:41
natefinchanyone for a rubber stamp on a backport?  http://reviews.vapour.ws/r/5480/20:46
rick_h_redir: can you peek at ^ please?20:47
redirrick_h_: ack20:47
rick_h_redir: <3 ty20:47
=== natefinch is now known as natefinch-afk
=== beisner is now known as beisner-biab
redirnatefinch-afk: LGTM21:06
redirrick_h_: I followed the link in that race bug. It led me to http://goo.gl/R8J8zJ21:08
redirwhich is linked to a fixed race, rick_h_. So sinzui is creating a new bug for it and updating.21:09
redirand which I've repro'd and will fix before the one assigned I guess.21:10
rick_h_redir: I didn't follow that but ... ok?21:23
mupBug #1614724 opened: Juju isn't protected from new versions of LXD <juju-core:New> <juju-release-tools:New> <https://launchpad.net/bugs/1614724>21:26
thumperhmm... forgot to open this...21:26
rick_h_thumper: voidspace was going to look for you21:28
rick_h_thumper: not sure if he found you before this or not then21:28
thumperah... nope21:28
=== beisner-biab is now known as beisner
thumperepic review up for grabs:  86 files changed, 775 insertions(+), 719 deletions(-)21:30
thumperperhaps I'll save it for menno21:30
thumperhe loves those21:30
perrito666Thumper i owe you one of these21:32
thumperjust found one failing test...21:33
thumpertwo failing tests...21:33
* thumper gets to fixing21:33
voidspacethumper: hey, hi21:35
thumpervoidspace: hey21:35
voidspacethumper: so we have another bug related to comparing structs in asserts21:35
voidspacethumper: however this one is actually comparing a slice of slices of structs, so building it into a collection of asserts is annoying (double loop to build)21:36
voidspacethumper: fwereade suggested just comparing txn-revno instead21:36
voidspacethumper: I wondered if you had any insight before I went ahead and did that21:36
voidspacehah, ok21:36
thumpersounds reasonable21:36
voidspacethanks, thought I'd ask21:37
voidspaceyeah, if I have to I can build the asserts with the double loop - but I'd rather not21:37
mupBug #1614732 opened: Race in github.com/juju/juju/api/state.go <ci> <intermittent-failure> <race-condition> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1614732>21:41
thumpersinzui: in the bug ^^^ title says race in state, but text says catacomb21:52
sinzuithumper: I typo/paste error. I will fix21:53
* rick_h_ runs away for the day21:59
* thumper sighs22:03
thumperconflicts with master22:03
* thumper pulls, merges, and resolves22:03
mupBug #1614749 opened: juju ssh fails on azure <azure-provider> <juju-core:Triaged by axwalk> <https://launchpad.net/bugs/1614749>22:08
thumperI guarantee that this branch will be less painful to review than it was to write22:08
thumperperrito666, menn0: http://reviews.vapour.ws/r/5481/22:12
menn0thumper: 1 min22:13
thumperno worries22:13
* thumper goes back to reviewing menno's branch22:13
menn0thumper: must .... stay .... awake... :)22:19
perrito666thumper: QA steps22:25
thumperheh... test everything?22:26
perrito666man, you fail the checklist at step 322:26
* thumper builds and tests22:26
thumperwallyworld: why would 'juju list-models' hang?22:28
thumpersurely it shouldn't22:29
thumperoh... I have a cunning idea...22:29
thumperfor later22:29
thumperperrito666: can you check `juju models`?22:32
thumperwallyworld: fyi http://pastebin.ubuntu.com/23068729/22:33
menn0thumper: while I'm still working through it, QA steps for that PR? (especially that the smart formatter still works with the feature flag)22:36
thumperlots of the jujuc tests show smart working with the feature falg22:37
menn0thumper: ok22:37
thumperbut I can manually check22:37
thumperI should have done that before deploying elastic search22:37
thumperwell they all failed due to bad squid proxy22:38
thumperso I'll create controller22:38
thumperwallyworld: I think it may have been a more up to date client and older controller22:39
thumperwill check22:39
menn0thumper: done22:43
perrito666thumper: what should I check about juju models?22:43
thumperperrito666: nm22:44
thumpermenn0: I'm just doing some manual QA22:45
thumperand yes, for application get if you ask for JSON and give a single name, then you don't get json22:45
thumperthis is the existing behaviour22:45
thumperhowever dumb22:45
menn0thumper: worth fixing before 2.0 final?22:51
thumperapt.cache.FetchFailedException: W:Failed to fetch http://packages.elastic.co/elasticsearch/2.x/debian/dists/stable/main/binary-amd64/Packages  403  Forbidden22:54
thumperfrom the install hook22:54
thumperin lxd22:54
mupBug #993557 changed: Charm store should delete charms that have been removed. <store> <pyjuju:Won't Fix> <juju-core:Invalid> <https://launchpad.net/bugs/993557>22:56
mupBug #1178497 changed: Provide an API for listing all charms that are present in the store <charmbrowser> <store> <juju-core:Fix Released> <https://launchpad.net/bugs/1178497>22:56
wallyworldthumper: sorry, was out buying dog food23:03
thumperthat's fine23:03
wallyworldi also got a 403 when using squid deb proxy23:03
thumperI've restarted my lxd with no proxy23:07
mupBug #1602572 changed: Handler function is not being called even after changed one of the config values of the config.yaml <juju-core:Invalid by johnsca> <https://launchpad.net/bugs/1602572>23:32
perrito666oh man wallyworld now you have me humming ready for the 80s23:43
redirI was getting a lot of 403s with squid deb proxy until I allowed world.23:46
thumperwallyworld: w00t, looks like the big command branch will land, all tests look like they passed23:50
wallyworldthat is most excellent23:52
katcothumper: i'm afraid to ask, but: does this affect the deploy command?23:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!