/srv/irclogs.ubuntu.com/2016/04/27/#juju-dev.txt

menn0thumper: SSHClient facade. Review pls. http://reviews.vapour.ws/r/4713/00:53
mwhudsonmenn0: i have a couple of simple PRs https://github.com/juju/juju/pull/5252 https://github.com/juju/juju/pull/524101:14
mwhudsonmenn0: reviewboard doesn't seem to have picked them up01:14
* redir is eod. See you tomorrow juju-dev01:21
mupBug #1575448 opened: trusty juju 1.25.5 HA availability issues <canonical-bootstack> <juju-core:New> <https://launchpad.net/bugs/1575448>01:46
menn0mwhudson: looking02:00
mwhudsonmenn0: looks like tim merged them02:00
menn0mwhudson: ok cool. I was having lunch.02:00
mwhudsonor well02:01
mwhudsonmenn0: https://github.com/juju/juju/pull/5252 hasn't merged, can you tell why?02:01
mwhudsonoh still processing02:01
menn0mwhudson: yep, still merging02:01
cheryljhey perrito666 - your window tests PR fixed this bug, right?  bug 157178302:02
mupBug #1571783: Windows unit tests cannot setup under go 1.6 <ci> <go1.6> <jujuqa> <regression> <test-failure> <unit-tests> <windows> <juju-core:In Progress by hduran-8> <https://launchpad.net/bugs/1571783>02:02
* perrito666 checks02:03
perrito666yes02:03
cheryljcool, thanks02:03
=== redir_ is now known as 16WAADNFF
=== 16WAADNFF is now known as redir
a123having trouble building juju(cb347bb7). Following the README.md results in: cannot find package "github.com/Azure/azure-sdk-for-go/Godeps/_workspace/src/github.com/Azure/go-autorest/autorest/mocks"02:06
davecheneya123: did you run godeps first ?02:06
davecheneycd $GOPATH/github.com/juju/juju && godeps -u dependencies.tsv02:07
a123no I did not. The README.md only says to run 'make install-dependencies'02:08
davecheneythat should do the same thing02:08
davecheneydid that process work ?02:08
davecheneyit might be easier to run the command I suggested02:08
davecheneyand raise a bug if our install docs are out of date02:08
a123hmm. godeps: command not found.    I'm using: go version go1.6.1 linux/amd6402:09
a123I'm new to go, if that's not obvious.02:09
davecheneyplease raise a bug that make install-dependencies does not install godeps, which is a dependency :)02:10
davecheneyfor the momement02:11
davecheneygo get launchpad.net/godep02:11
davecheneygo get launchpad.net/godeps02:11
davecheneyyou will need to install bzr, sorry02:11
a123ha. yep.02:12
davecheneythat may have been while make isntall-deps failed02:12
perrito666odd, I thought make install installed bzr02:13
a123hmm. odd. bzr already installed. here's the output of get get launchpad.net/godeps02:13
a123# cd .; bzr branch https://launchpad.net/godep /home/ubuntu/proj/gojuju/src/launchpad.net/godep bzr: ERROR: Not a branch: "https://launchpad.net/godep/". package launchpad.net/godep: exit status 302:13
perrito666a123: its godeps02:13
perrito666go get launchpad.net/godeps02:13
a123yep.02:13
perrito666with an s at the end02:13
perrito666you are missing it02:13
davecheneyyes, sorry, i typed it incorrectly the first time02:14
a123working....02:14
davecheneythere is a related tool with a very similar name02:14
a123godeps -u dependencies.tsv looks like it did its thing.02:16
a123now running go install -v github.com/juju/juju/... and that looks like it's doing its thing. Thanks for the help.02:19
davecheneyno worries02:20
a123BTW, anyone get juju bootstrap to work from behind a proxy? At home, no issues at all. Different story behind a proxy.02:21
davecheneyjuju _should_ pickup the various http_proxy variables if they are defined in your shell02:21
blahdeblaha123: 1.25, or 2.x?02:22
blahdeblah1.25 works for me02:22
a123yes. It does look like it does that at first.... Yes, 1.25 worked for me too, now trying 2.002:22
a123don't know if this is related to our proxy or not, but doing lxc remote list produced a table where images url looked like:02:24
a123 https://images.linuxcontainers.org02:24
a123I could not download any images from there. but when I redefined that url to include the port(8443) the image download was successful.02:25
davecheneyif you've change something (i'm not sure what you've changed) then you'll need to be explicit02:28
davecheneyit sounds like the thing your downloading from expects 443 as the default02:28
a123right. I ran: lxc remote set-url images https://images.linuxcontainers.org:844302:29
a123this redefined the remote images url. I then ran: lxc image copy images:ubuntu/xenial/amd64 local: --alias ubuntu-xenial02:29
a123w/out changing the URL, the lxc image copy command would not work behind our proxy02:30
davecheneyumm, juju 2.0 doesn't support lxc02:30
davecheneyonly lxd02:30
davecheneyi hope this statement is helpful, not frustating02:30
a123laughing... I thought lxd2.0 was built on top of lxc. Your point is taken though.02:31
davecheneywell it is02:32
davecheneyso your point is technically correct, which is the best kind of correctness02:32
a123before changing the image url and running: juju bootstrap --config default-series=xenial lxd-test lxd --debug produced:02:34
a123sorry guys. I'm seeing different debug output now than earlier. lots of connection refused to the 10.0.3.0/24 network. Does the no_proxy setting take CIDR?02:42
a123that network is attached to lxdbr002:44
a123What I should ask is, does juju understand CIDR if used in the no_proxy env var?  ie. export no_proxy=10.0.3.0/2402:47
mgza123: no, no_proxy doesn't take a cidr02:48
a123thanks.02:49
davecheneyi _think_ no_proxy is just a sort of match string02:49
davecheneyexport no_proxy=10.02:49
davecheney^ not tested02:49
mgzjust a comma seperated list of "domain extensions"02:50
mgzso, it's suffixes, not prefixes02:50
mgzvalid: no_proxy=.com02:51
mgzno_proxy=.25502:51
a123I've found this to be application dependent in the past.02:51
a123ah. nice.02:52
mgznot valid: no_proxy=10. no_proxy=10.* etc etc02:52
mgzwe plug this stuff into wget in some places so are limited by what wget supports02:52
a123oh. It wasn't clear to me if wildcards would work.02:52
a123ok. wget is the driver. I think I know why my debug is different now. I used the --keep-broken flag when running the bootstrap in hopes of finding answers. How do you destroy the model?02:54
davecheneyjuju kill-controller $controller02:54
davecheneyfrom memory02:54
davecheneykill is the more finite form of destroy02:55
davecheneywhich tends to not actually destroy things 'cos it's a wimp02:55
a123so much I don't know. Is the controller a different concept than a model? It looks like a controller never got created when using the --keep-broken flag.02:58
a123so. juju list-controllers returns an empty table. When I then run: juju list-models I get: error: controller local.lxd-test not found. What exactly does --keep-broken do?03:02
a123thanks for the help everyone. I'm not confident my environment is in a good state. I'm going to tear down the VM, bring up a fresh one and try again tomorrow.03:08
thumpermenn0: a few questions on your review03:21
* thumper goes to make coffee03:21
menn0thumper: ok, looking03:21
menn0thumper: good point... these APIs copy the existing APIs used by juju ssh/scp exactly but it's probably worth making sure they at least work for IPv6 too03:24
menn0thumper: hangout to discuss?03:28
thumpermenn0: sure, gimmie 5?03:31
menn0yep03:31
* thumper wants to enjoy his coffee first03:32
mupBug #1575463 opened: buildSuite.TestGetVersion* CryptAcquireContext: Provider DLL failed to initialize <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1575463>03:55
davecheneymenn0: are you looking at this bug https://bugs.launchpad.net/juju-core/+bug/145858504:09
mupBug #1458585: SSHGoCryptoCommandSuite.TestCommand fails <ci> <go1.6> <intermittent-failure> <regression> <test-failure> <wily> <xenial> <juju-core:Incomplete> <juju-core 1.23:Won't Fix> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1458585>04:09
davecheneyor a duplicate of it ?04:09
menn0davecheney: no and no04:09
menn0davecheney: I'm working on making juju ssh/scp use the actual SSH host keys of the machine being connected to04:11
menn0davecheney: close to being done04:11
davecheneyok, related, but not the same issue04:14
davecheneythanks04:14
thumperwallyworld: when do we add things into the cloud metadata storage?04:21
thumperwallyworld: is it "normal" behaviour for clouds04:21
thumperor more used for custom openstack stuff?04:21
wallyworldthumper: you mean keystone?04:21
wallyworldor the metadata url04:21
wallyworldwill still allow the use keystone for simplestreams04:22
wallyworldbut i don't think we've used the metadtaa url for ages04:22
wallyworldwe now bootstrap differently04:22
wallyworldit used to be a way to pass bootstrap instance info across04:23
mupBug #1575469 opened: liveSuite.TestBootstrapMultiple invalid character \"\\\\\" in host name <ci> <go1.6> <regression> <test-failure> <unit-tests> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1575469>04:25
mupBug #1575472 opened: Data Race github.com/juju/juju/environs/tools/build.g <ci> <race-condition> <regression> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1575472>04:25
thumperwallyworld: I mean the state cloudmetadataC collection04:32
wallyworldthumper: we cache the simplestreams metadata there at bootstrap and whenever we poll cloud-images04:34
thumperk04:42
davecheneymenn0: https://github.com/juju/juju/pull/528904:59
davecheneyi heard u were on call review04:59
menn0davecheney: looking06:09
menn0davecheney: looks fine. what's changed in x/crypto that fixes the isssue?06:11
davecheneymenn0: who knows it's been a year since we updated that dependency06:19
davecheneyand there have been heaps of bug fixes to the crypto repo06:19
davecheneyi'm deliberately phrasing it like this because I don't want to backport anything06:19
menn0davecheney: ah right... so you didn't find a specific upstream change that fixed the issue06:19
davecheneyi didn't even look06:19
davecheneyupgrading to tip fixed the problem06:19
menn0davecheney: well you have a ship it06:19
davecheneyDo we need to maintain comptabilty with Go 1.2 ?06:45
davecheneythe build bot just failed to land a branch 'cos it tried to build with Go 1.206:45
dimiternaxw: are you around by any chance?07:42
dimiternor wallyworld ?07:43
wallyworldhey, otp07:43
axwdimitern: yo, I am07:43
dimiternaxw, wallyworld: hey, just a quick question, if you happen know07:43
dimiternin provider/ec2 can we now only filter instances by model tags rather than secgroups ?07:44
dimiternaxw: I know you did something around that lately07:44
axwdimitern: not yet, tried to land today but master is blocked07:44
dimiternI'm working on bug 1321442 and it will be a lot easier not to have to make group filters work with explicit VPC ID07:45
mupBug #1321442: Juju does not support EC2 with no default VPC <ec2-provider> <network> <juju-core:In Progress by dimitern> <https://launchpad.net/bugs/1321442>07:45
dimiternaxw: I see, ok - I'll look into your changes07:46
axwdimitern: hmm you know, I just remembered a reason why we may not want to do away with the group filtering.07:46
axwdimitern: tags aren't added immediately after creating an instance...07:46
dimiternaxw: ah, bummer07:46
axwsorry07:46
axwdimitern: I mean, they're not added until after they're created07:47
axwdimitern: so there's a window where they could leak07:47
dimiternaxw: np, it makes sense in an AWS world I guess07:47
dimiternaxw: ok, cheers, I'll do group filtering then as well07:48
axwdimitern: and I'll revert that bit in my PR :)07:48
axwcheers07:48
dimiternyou gotta love how inconsistent AWS API is at times :[07:51
dimiternlol `deleteSecurityGroupInsistently`07:53
fwereadejam, tech board?08:03
voidspacedimitern: ping08:32
dimiternvoidspace: pong08:32
voidspacedimitern: I've addressed two of your comments from your review of the devices branch08:33
voidspacedimitern: you suggest just adding a test for the multi nic case as it's basically done08:33
voidspacedimitern: however, adding a test means some test infrastructure work as the multi-nic path calls additional provider methods08:33
voidspacedimitern: not difficult but not nothing08:34
dimiternvoidspace: it looked like that, but yeah - can be a follow up08:34
voidspacedimitern: in addition there is the known bug with the multi-nic case08:34
voidspacedimitern: I'd rather land as is - with working and tested single nic containers08:34
dimiternvoidspace: what did you find about the missing subnet?08:34
voidspacedimitern: not uncovered it yet - still digging08:34
voidspacedimitern: should be done and dusted today though, can't be *that* hard to find :-)08:34
voidspacedimitern: so I'll land as is and land multi-nic tests along with the bug fix (assuming it's not a maas bug)08:35
voidspacedimitern: ok?08:35
dimiternvoidspace: you know what occurred to me yesterday: it might be due to unchecked 0 ids for fabrics or vlans08:35
voidspacedimitern: possibly08:35
voidspacedimitern: I'm going to try always setting VLAN ID even if it isn't changing in that update call08:36
dimiternvoidspace: e.g. fabric-0 is always there, but we might not have meant that08:36
voidspaceyeah08:36
dimiternvoidspace: ok, if you don't mind let me do a quick bootstrap with your branch now08:36
voidspacedimitern: sure08:37
voidspaceI'm doing the same, with modified gomaasapi08:37
dimiternok08:39
voidspaceforcing the VLAN to be specified didn't help08:43
voidspaceadding more debugging08:44
voidspacedimitern: anyway, I'm on it08:44
dimiternvoidspace: can you paste the outputs of 'maas <profile> subnets read', 'fabrics read', and 'machines read' for your maas2?08:45
voidspacedimitern: http://pastebin.ubuntu.com/16076113/08:47
dimiternvoidspace: thanks, here's mine for comparison: http://paste.ubuntu.com/16076129/08:49
voidspacedimitern: I'm going to try allocating the machines and making the maas calls manually08:50
voidspacedimitern: after this bootstrap to confirm it's the CreateDevice call that fails08:51
dimiternvoidspace: sgtm, I'm bootstrapping now08:51
voidspacedimitern: I'd still like to land single nic support08:51
dimiternvoidspace: I don't disagree with that :)08:53
voidspacecool08:53
dimiternvoidspace: are both of your first 2 fabrics managed? (0 and 1)08:54
dimiterni.e. subnets 172.16 and 172.1708:55
voidspacedimitern: gah, master blocked08:55
voidspacedimitern: subnets are managed if that's what you mean08:55
voidspaceI don't know what a managed fabric is08:55
voidspaceboth subnets08:56
voidspacedimitern: ok, I was wrong it gets past CreateDevice and UpdateInterface08:56
voidspacedimitern: so I need to add more instrumentation and redo08:57
voidspacedimitern: I've got this anyway08:57
voidspacedimitern: I'll ping you when I've made progress08:57
dimiternvoidspace: ok, your maas2 setup looks fine - so the issue must be related to how we're calling the api08:57
voidspaceyep08:58
dimiternvoidspace: still the same thing - no params (with vlan) passed to update the primary NIC of the device09:00
voidspacedimitern: standup old boy09:02
TheMuemorning09:21
axwbabbageclunk: it would appear you're the luck OCR today, would you please take a look at http://reviews.vapour.ws/r/4718/diff/#?09:34
axwfixes master blocker09:34
voidspacedimitern: I see vlan=5001 in the params of the PUT09:39
dimiternvoidspace: and I can't :/09:40
dimiternvoidspace: and with the vlan set do you still get 500 ?09:41
voidspacedimitern: wait, that's the wrong vlan though09:42
axwdimitern voidspace: can either of you take a look at the tiny PR above? it should unblock master09:42
axwwell, with the juju/juju change coming after09:42
voidspacedimitern: I do get 50009:42
voidspacedimitern: but I think that's the wrong vlan09:42
voidspacedimitern: interesting09:42
dimiternaxw: LGTM09:42
axwta09:42
dimiternvoidspace: aha!09:43
dimiternvoidspace: 5001 should be the untagged vlan of your fabric-009:43
dimiternvoidspace: and it should be the same as the host's first NIC's VLAN09:43
voidspacedimitern: however this subnet comes straight from MAAS09:44
voidspacebut "spaces read" seems to give the right thing09:44
voidspacedimitern: so in gomaasapi it should be args.Subnet.VLAN() not iface.VLAN()09:46
voidspacedimitern: and in the single NIC case it works because there's only one09:47
voidspacedimitern: trying that09:47
dimiternvoidspace: exactly!09:47
voidspaceI think that's it09:48
voidspacetrying it now09:48
dimiternvoidspace: the iface is the device interface, while args.Subnet.VLAN is the one we want on iface09:48
voidspaceyep09:48
voidspacegaah, that took a long time09:48
voidspaceat least we get to blame Tim09:48
dimitern:)09:48
voidspaceand a chunk of the time was getting a multi-nic MAAS setup which is worthwhile work09:48
dimiternvoidspace: \o.09:49
dimitern\o/ even09:49
dimiternvoidspace: and it also helped your maas2 setup is a bit different than mine09:50
voidspaceyep09:50
dimiternvoidspace: are you using 2.0.0 beta4 more recent than bzr 4936 ?09:51
voidspacedimitern: 494109:52
voidspacedimitern: beta3 though!09:52
voidspacedimitern: I've got past that point with no error09:53
voidspacedimitern: and I see a device with two nics and two IP addresses09:53
dimiternvoidspace: hmm, well you *might* hit this bug 157207009:54
mupBug #1572070: MAAS 2.0 cannot link physical device interfaces to tagged vlans, breaking juju 2.0 multi-NIC containers <juju> <MAAS:Fix Committed by blake-rouse> <MAAS 1.9:Fix Committed by blake-rouse> <https://launchpad.net/bugs/1572070>09:54
babbageclunkaxw: Sure - sorry, missed this until now.09:54
dimiternvoidspace: sweet! then it should work the rest of the way09:54
voidspacedimitern: yep, so I'll propose a fix for gomaasapi and then tests for multi-nic09:54
voidspacefrobware: babbageclunk: it turned out to be a bug in gomaasapi09:55
dimiternvoidspace: but that bug will be relevant with mult-nic only09:55
voidspacedimitern: ok, thanks09:55
voidspacedimitern: the linking is already done (my vlans are untagged)09:55
voidspacedimitern: so I think I've got past that09:55
babbageclunkvoidspace: nice09:55
dimiternvoidspace: well since the physical nics of the host are on untagged VLANs it only will become an issue trying to create a second physical NIC of the device linked to a tagged VLAN09:57
voidspacedimitern: container is running fine09:57
dimiternvoidspace: no WARNINGs in the log around provisioning / PrepareContainerInterfaceInfo ?09:57
voidspacedimitern: only about no DNS settings found09:58
voidspacedimitern: nothing else09:58
babbageclunkaxw: dimitern: d'oh, should've reloaded09:58
voidspacedimitern: and I can ssh fine09:58
voidspacedimitern: case closed on that one09:58
dimiternvoidspace: awesome! so the device has eth0 and eth1 linked to br-eth0 and br-eth1 on the host?09:59
voidspacedimitern: this is e/n/i on the container http://pastebin.ubuntu.com/16076575/10:00
dimiternvoidspace: slightly odd to see `dns-nameservers 172.16.0.2` on eth0 which has address 172.17.0.4/2410:02
voidspacedimitern: it adds the nameservers to the first stanza10:02
dimiternbut otherwise looks solid10:02
voidspaceyeah10:02
dimiternvoidspace: yeah - and only the .16 subnet has dns_servers set?10:02
voidspacedimitern: this is the host http://pastebin.ubuntu.com/16076591/10:02
voidspacedimitern: you only need one nameserver entry10:03
voidspacethey're global10:03
voidspaceneither dns is set in maas (both 0.0.0.0) and both are managed10:04
dimiternvoidspace: I see, ok - does 'ping bbc.co.uk' work while inside the container?10:04
voidspacedimitern: yep10:05
dimiternvoidspace: we're nearly done then :)10:06
voidspacedimitern: can't test that change easily in gomaasapi - you can specify responses in the test server it uses but not verify requests it seems10:09
voidspaceyou can fetch the last request, but it makes another after the update10:10
voidspacelooking to see if I can get at the one before last :-)10:10
voidspacehah, no10:11
voidspaceah, I can check the VLAN10:11
voidspaceshould be ok10:11
dimiternvoidspace: sure, on it10:12
voidspacedimitern: are you doing it?10:18
voidspacedimitern: I have a branch with a fix10:18
dimiternvoidspace: haven't started10:18
dimiterndoing a few things at once as usual10:18
voidspacedimitern: a proper test involves a lot of json (new interface, vlan and subnet in json)10:19
voidspacedimitern: I have this though https://github.com/juju/gomaasapi/compare/master...voidspace:maas2-create-device-vlan10:19
voidspaceas there's only one interface on the test machine the test doesn't fail without the fix10:19
voidspaceI suggest we land this, I'll work on juju and come back for a multi-nic test for gomaasapi later10:20
dimiternvoidspace: looks good10:20
voidspacebabbageclunk: https://github.com/juju/gomaasapi/pull/4710:20
voidspacecoffee10:22
babbageclunkvoidspace: I like it10:34
babbageclunkvoidspace: !10:34
=== akhavr1 is now known as akhavr
=== dimitern is now known as dimitern-afk
babbageclunkvoidspace: ahh, missed your discussion about the test above.11:26
voidspacebabbageclunk: yeah, it needs a better test - but creating a machine with multiple interfaces, subnets and vlans for the gomaasapi test harness is a pain11:48
voidspacebabbageclunk: I'll do it later11:48
voidspacebabbageclunk: it's no worse tested than it was before ;-)11:48
=== dimitern-afk is now known as dimitern
voidspacedimitern: I've updated http://reviews.vapour.ws/r/4700/12:37
voidspacedimitern: includes gomaasapi revision bump and a happy path test for multi-nic12:37
voidspaceis master unblocked yet12:37
voidspacedimitern: still more tests needed12:37
dimiternvoidspace: still looks good to land, and I'll do another quick live test with it12:39
voidspacedimitern: that would be good, see if it works for you12:39
voidspacemaster is still blocked12:46
alexisbvoidspace, dimitern, frobware, babbageclunk please JFDI any maas2 related PRs13:08
alexisbmaster is blocked but maas2 stuff is an exception here13:09
dimiternalexisb: thanks!13:36
dimiternvoidspace: it looks a lot better: bootstrap ok, switch to admin, add-machine, then add-machine lxd, lxc, kvm to both :0 and :113:37
dimiternvoidspace: but only machine-1 containers all came up ok and have expected addresses, the ones on machine failed with host machine device "br-eno2" has no address, and I was digging into the logs to figure out why13:38
mupBug #1575676 opened: Hard to use non-default LXD bridge <landscape> <juju-core:New> <https://launchpad.net/bugs/1575676>13:56
alexisbthank you katco !13:57
katcoalexisb: np... happy that we're giving capacity planning a little more attention13:57
katcoalexisb: also revealing future targets :)13:57
* katco begins her morning routine13:58
voidspacealexisb: ok14:17
voidspacedimitern: machine-0 ones didn't work?14:18
voidspacepicking up daughter from school14:18
voidspaceback in 15mins14:18
dimiternvoidspace: nope, something's odd, still investigating and adding more logging14:20
=== deathpip is now known as ivyharriet
voidspacedimitern: alexisb: frobware: babbageclunk: container support has landed on master15:00
frobwarevoidspace: nice work!15:01
babbageclunkvoidspace: awesome!15:01
=== redir_ is now known as redir
dimiternvoidspace: great!15:03
dimiternI'm still debugging the issue on machine-015:03
voidspacedimitern: ok15:03
voidspacedimitern: I'll try adding a node to my maas with two nics and try that15:03
voidspacedimitern: I've *only* deployed to machine-015:04
dimiternvoidspace: in the admin model?15:06
voidspacedimitern: yep15:06
voidspacedimitern: commissioning an additional node now15:08
alexisb\o/15:09
voidspacedimitern: when I commission a node with two nics the second nic comes up as "unconfigured" (no address) whereas the primary nic is "auto assign"15:12
voidspacedimitern: I can manually change it to auto assign15:12
voidspacedimitern: if I don't do that then I think I only get a single nic on the container15:12
dimiternvoidspace: otp15:13
voidspacesuccessfully created a container with two nics on a new machine not in the admin model15:17
mupBug #1574809 changed: "to: lxc:0" ignored in bundle <bundles> <juju-release-support> <kanban-cross-team> <landscape> <juju-core:Invalid> <https://launchpad.net/bugs/1574809>15:24
dimiternvoidspace: yeah, you can set them to auto or static (unconfigured physical + auto/static VLAN children won't work though)15:31
dimiternvoidspace: nice! I added more logging and now trying again15:31
babbageclunkdimitern, voidspace - hmm, trying to add a machine with a space constraint gives a schema error - it looks like the maas response might have changed since we put the constraint matching code in.15:47
babbageclunkIt's returning an array of interface/device ids, not just one.15:48
babbageclunkI'm going to fix gomaasapi - do you think that just taking the first is the right thing to do? I guess I should ask the MAAS people what it would mean for the result to have more than one value.15:49
dimiternbabbageclunk: can you point me to the code you're talking about (causing the issue)?15:50
babbageclunkdimitern: https://github.com/juju/gomaasapi/blob/master/controller.go#L81015:52
babbageclunkdimitern: compared to this response: http://pastebin.ubuntu.com/16083467/15:53
mgzvoidspace: where is the gomaasapi/bootresource.go stuff meant to come from? bootstrapping complains about missing kflavor schema15:54
babbageclunkmgz - if you do "maas <session> boot-resources read" can you see kflavor in the items that come back/15:57
babbageclunk?15:57
mgzbabbageclunk: a bunch of them do, some do not (centos ones)15:58
dimiternbabbageclunk: hmm15:59
dimiternbabbageclunk: so looking at the response you pasted, the schema seems correct15:59
babbageclunkmgz: that makes it sound like it's an optional field that we didn't know was optional.16:00
mgzbabbageclunk: it does indeed, I'll file a bug?16:00
babbageclunkmgz: yes please!16:01
babbageclunkdimitern: will ForceInt accept an array?16:01
dimiternbabbageclunk: I think the ForceInt applies to the values of the StringMap16:03
babbageclunkdimitern: sure, but the values are lists, right?16:03
babbageclunkdimitern: I'm going to write a little test to check16:04
dimiternbabbageclunk: i.e. given a {"constraints_by_type":{"storage":{"foo":1,"bar":2}},"interfaces":{"aa":1,"bb:2}} it should parse it16:04
mupBug #1575760 opened: Juju switch returns confusing error message <juju-core:New> <https://launchpad.net/bugs/1575760>16:06
babbageclunkdimitern: but the one coming from maas has "interfaces": {"default": [24]}16:06
dimiternbabbageclunk: you're correct! so specifying "interfaces=foo:space=0" gives me multiple items in the list for "foo"16:07
babbageclunkdimitern: is that because any of those interfaces are in the right space?16:08
babbageclunkdimitern: I mean, all16:08
dimiternbabbageclunk: yeah - if you have 1 space only (space-0 a.k.a. default) and you pass that to interfaces, you'll get all nodes back16:08
dimiternbabbageclunk: so I guess it needs to be something like "interfaces": schema.StringMap(schema.List(schema.ForceInt()))16:10
babbageclunkdimitern: yeah, I think so.16:10
babbageclunkdimitern: And I think we need to change gomaasapi.ConstraintMatches to have slices of BlockDevice and Interface as well then.16:11
dimiternbabbageclunk: indeed16:11
babbageclunkdimitern: once it gets into the provider, can we just pick any one of them?16:11
* babbageclunk looks in environ.go for how we use the matches.16:12
dimiternbabbageclunk: and the way ids are handled in the loops below (id := value.(int) -> ids := value.([]int) and range over it)16:12
dimiternbabbageclunk: you mean, if you have more than one interface ID per label?16:13
dimiternbabbageclunk: does not matter if we only want a given space to be accessible on the allocated machine16:14
babbageclunkdimitern: yeah, actually we only use the constraint matches for storage information.16:14
dimiternbabbageclunk: but why do you need those results from constraintsMap ? the 1.0 code path ignores them as we don't care (i.e. we read all interfaces along with which subnets and spaces they're linked to each time we call NetworkInterfaces())16:15
dimiternbabbageclunk: :) yep16:15
dimiternwe probably should at some point, but so far we don't need it16:16
babbageclunkdimitern: ok, in the storage case should that just be another loop over the block devices that come back16:19
babbageclunk?16:19
dimiternbabbageclunk: I suspect so, but have a look how 1.0 code path does it (and its tests)16:20
babbageclunkdimitern: context: https://github.com/juju/juju/blob/master/provider/maas/volumes.go#L29516:20
mgzvoidspace, babbageclunk: filed bug 157576816:22
mupBug #1575768: boot resource 2.0 schema check failed: kflavor: expected string, got nothing <bootstrap> <ci> <maas-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1575768>16:22
babbageclunkdimitern: It was structured differently in the v1 API - looks like it was id -> label, so you could have multiple ids going to the same label16:23
dimiternbabbageclunk: it doesn't look like the 2.0 code path is using physicalblockdevice_set at all16:24
babbageclunkthanks mgz - I'll start on that now.16:24
babbageclunkdimitern: no - gomaasapi handles that lookup16:24
babbageclunkdimitern: in controller.go: parseAllocateConstraintsResponse16:28
babbageclunkmgz: do you know what MAAS version that is?16:30
mgzbabbageclunk: beta3+bzr494116:31
babbageclunkmgz: Thanks.16:32
mgzit's upgraded from 1.9, which would have done the original image imports16:33
dimiternbabbageclunk: I need to go, but in case it might help, here's a couple of outputs with a set storage constraint on 2.0 (http://paste.ubuntu.com/16084450/) and 1.0 (http://paste.ubuntu.com/16084458/)16:33
babbageclunkdimitern: thanks! I'm not going to get to fixing it tonight, should fix mgz's issue first16:34
dimiternmgz: that's a bit too old can't you upgrade to the latest beta4 from the experimental3 ppa?16:34
dimiternbabbageclunk: sounds good, cheers!16:34
babbageclunkdimitern: mgz: I wasn't sure whether that was something I could demand. :)16:35
dimiternaw c'mon mgz's a pal :)16:35
babbageclunkmgz: the version we're working against is beta4+bzr494416:35
mgzdimitern: I can, I didn't see an announcement from roaksoax about it16:36
mupBug #1575764 opened: Juju doesn't detect lxd container IP address changes <juju-core:New> <https://launchpad.net/bugs/1575764>16:36
mupBug #1575768 opened: boot resource 2.0 schema check failed: kflavor: expected string, got nothing <bootstrap> <ci> <maas-provider> <juju-core:Triaged by 2-xtian> <https://launchpad.net/bugs/1575768>16:36
mupBug #1575769 opened: Can't "forget" a controller that I've lost access to <juju-core:New> <https://launchpad.net/bugs/1575769>16:36
dimiternmgz: they don't always mail when they do a point release I think16:36
dimiternanyway, I'm outta here16:37
babbageclunkmgz: it has a few bugfixes we need, so I guess you'll need to upgrade anyway.16:37
mupBug #1575769 changed: Can't "forget" a controller that I've lost access to <juju-core:New> <https://launchpad.net/bugs/1575769>16:39
mgzbabbageclunk: dist-upgrading first16:39
babbageclunkmgz: I'll try uploading a centos image to my local MAAS and see if that also leaves out kflavor.16:40
mupBug #1575769 opened: Can't "forget" a controller that I've lost access to <juju-core:New> <https://launchpad.net/bugs/1575769>16:42
babbageclunkmgz: yup, it still leaves out kflavor on my local beta4 one16:48
voidspacebabbageclunk: have you got a fix for that issue?16:50
mupBug #1575769 changed: Can't "forget" a controller that I've lost access to <juju-core:New> <https://launchpad.net/bugs/1575769>16:51
babbageclunkvoidspace: I think we just need to mark it optional in the schema.16:51
voidspacebabbageclunk: do you have a branch with that?16:52
babbageclunkvoidspace: The provider doesn't use it - we only care about architectures16:52
babbageclunkvoidspace: not with the change yet - just reproducing the bug.16:52
voidspacebabbageclunk: cool16:52
redircherylj: looking16:53
cheryljredir: at what?16:53
cheryljwhat did I say?16:53
* babbageclunk lols16:53
redircherylj: at your PR16:54
cheryljhaha16:54
redir:p16:54
voidspacebabbageclunk: reading scrollback - weird about the device id array16:56
voidspacebabbageclunk: did you ask in the maas folk about that?16:56
voidspaceI've just upgraded to beta4 - was using next-proposed instead of experimental316:57
mgzthere are too damn many maas ppas16:58
babbageclunkvoidspace: no, haven't yet16:59
babbageclunkvoidspace: but the new way is right - if the mapping's gone from {id: label} to being keyed by label, the values need to be lists17:00
mgzbabbageclunk: I don't see a beta4 in any of the ~maas ppas17:01
mgzit's in someones private one?17:01
mupBug #1575769 opened: Can't "forget" a controller that I've lost access to <juju-core:New> <https://launchpad.net/bugs/1575769>17:03
babbageclunkmgz: I think it's this one: ppa:maas-maintainers/experimental317:05
frobwarejam, tych0: PTAL @ http://reviews.vapour.ws/r/4722/17:05
tych0frobware: oh, derp :)17:05
frobwaretych0: you were doing the same thing?17:06
tych0no, just that it's a dumb bug on my part17:06
mupBug #1575769 changed: Can't "forget" a controller that I've lost access to <juju-core:New> <https://launchpad.net/bugs/1575769>17:06
tych0i didn't realize Initialize was called more than once, actually17:06
tych0but it makes sense that it is17:06
tych0frobware: looks good to me17:08
frobwaretych0: ok, will do some testing tomorrow morning (as master is blocked).17:08
frobwaretych0: thx17:08
tych0frobware: np, thanks for the fix17:09
mupBug #1575794 opened: Agent config format version should be changed for 2.0 <juju-release-support> <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1575794>17:12
voidspacebabbageclunk: mgz: that's the right one - I just had to switch to it17:15
voidspacebabbageclunk: ok, the kflavor ones sounds easier17:16
voidspacebabbageclunk: I can propose that17:16
mgzbabbageclunk, voidspace: similar issue with 'mount_point'17:19
mgzon filesystem2_017:20
babbageclunkvoidspace: https://github.com/juju/gomaasapi/pull/4817:21
babbageclunkvoidspace: can you do the mount_point one?17:21
voidspacebabbageclunk: gah, you beat me to it17:23
babbageclunksorry!17:23
voidspacebabbageclunk: mount_point needs to be optional?17:23
mgzwhat command is this coming from?17:23
voidspacebabbageclunk: I fixed it by supplying a default instead17:23
babbageclunkvoidspace: oh, that's nicer17:24
mupBug #1575794 changed: Agent config format version should be changed for 2.0 <juju-release-support> <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1575794>17:24
mgzhm, block-device, which needs a machine17:24
voidspacebabbageclunk: https://github.com/juju/gomaasapi/compare/master...voidspace:maas2-kflavor-optional17:25
voidspacebabbageclunk: and then you always get a value even if it's missing17:25
voidspacemgz: I can make mount_point optional in filesystem17:26
babbageclunkvoidspace: yeah - do that instead17:26
voidspace babbageclunk ok, I'll add making mount_point optional in the same branch17:26
mgzvoidspace: some of my filesystems are null17:26
babbageclunkmgz: you should be able to see it with machines read17:27
voidspacethe whole filesystem?17:27
voidspacemgz: what should we default to for mount_point: "/" ?17:28
mgzvoidspace: http://paste.ubuntu.com/1608574917:28
babbageclunkvoidspace, mgz: sorry, I have to head home17:28
voidspaceI have to go in five minutes too17:29
voidspacemgz: when you say "some of my filesystems are null" you mean mount_point, label and mount_options being null17:29
voidspaceah no17:29
voidspacethe whole filesystem is null17:29
voidspacegeez17:29
mgz:)17:29
voidspacemgz: this is now a tomorrow problem, sorry17:29
voidspacewife is calling me to dinner17:30
mgzvoidspace: I'll file you a bug son17:30
voidspacemgz: can you link to this pastebin on it please17:30
mgzwill also put up a non-voting job for maas 2.017:30
mupBug #1575794 opened: Agent config format version should be changed for 2.0 <juju-release-support> <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1575794>17:30
mgzto avoid cursing on this stuff17:30
voidspacemgz: much appreciated - thanks17:30
voidspacemgz: yeah17:30
voidspaceweird-ass maas configuration17:31
voidspaceright, dinner17:32
voidspacesorry17:32
mupBug #1575797 opened: AddressableContainerSetupSuite.TestContainerInitialised lxc-net: no such file or directory <arm64> <centos> <ci> <regression> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1575797>17:36
mupBug #1575808 opened: filesystem 2.0 schema check failed: mount_point: expected string, got nothing <bootstrap> <ci> <maas-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1575808>18:00
mupBug #1575808 changed: filesystem 2.0 schema check failed: mount_point: expected string, got nothing <bootstrap> <ci> <maas-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1575808>18:03
mupBug #1575808 opened: filesystem 2.0 schema check failed: mount_point: expected string, got nothing <bootstrap> <ci> <maas-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1575808>18:06
redirericsnow: you around?18:31
ericsnowredir: yep18:31
redircan I borrow your eyes for a minute?18:31
redirericsnow: ^^18:32
ericsnowredir: sure18:33
redirericsnow: am in moonstone18:33
natefinchuhh... redir, cherylj, are the tests supposed to pass on xenial?19:56
natefinchI'm getting a lot of this:  obtained string = "xenial"... expected string = "trusty"19:57
natefinchkatco, ericsnow ^ ?   This is just running tests on master19:59
katconatefinch: what does dist-info --lts return for you?19:59
ericsnownatefinch: I don't believe we've landed any fixes for that yet20:00
katconatefinch: sorry distro-info --lts20:00
ericsnownatefinch: redir is working on a comprehensive patch20:00
natefinchahh ok20:00
natefinchkatco: xenial20:00
mupBug #1575895 opened: juju loses apt-http/s-proxy information if a model is deleted and a new one created <juju-core:New> <https://launchpad.net/bugs/1575895>20:01
redirnatefinch: getting close with some help from ericsnow just now. Making sure it works then reviewing previous commits to see if this works on those and reverting them to keep things uniform.20:04
redirHopefully done RSN(tm)20:04
natefinchredir: \o/20:04
redir /o\20:05
cmarsah, resources are awesome20:38
natefinchcmars: glad you like them.  I do think they're pretty great20:39
cmarsnatefinch, updating my mattermost charm to use them20:39
natefinchcmars: nice!20:39
natefinchcmars: let us know if there's any problems or unexpected behavior20:40
katcocmars: :D20:40
=== natefinch is now known as natefinch-afk
perrito666wallyworld: ping me when you are around please21:18
wallyworldperrito666: hey. just about to go into a meeting21:28
perrito666k21:29
mupBug #1575940 opened: LXC containers under MAAS get no "search <domain>" entry in resolv.conf when deployed with juju2 <juju-core:New> <https://launchpad.net/bugs/1575940>21:37
alexisbmenn0, ping22:04
menn0alexisb: hey hey22:04
alexisbare you available to join the leads call22:05
menn0alexisb: ah crap... sorry22:06
cheryljdavecheney: ping?22:10
perrito666wallyworld: lemme know if you have a spot before the standup22:19
wallyworldperrito666: stuck in meetings, will let you know. may have to move standup depending on how meetings go22:20
perrito666k22:20
wallyworldperrito666: axw: anastasiamac_: redir: quick standup between meetings?23:04
cheryljredir: will you need to coordinate with CI to not hack distro-info for your PR?23:06
redircherylj: If I have this right it should pass as the bots are, and when they unhack them as well.23:07
cheryljredir: sweet!23:07
redirso master is blocked23:57
redirshould I target something else for a PR?23:57

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