/srv/irclogs.ubuntu.com/2014/03/20/#juju-dev.txt

stokachuanyone know what "juju.container interface.go:55 unused config option: "use-clone" -> "false"" is referring to?00:08
sinzuistokachu, I think thumper added a feature for trusty users to make lxc fast using the lxc-clone feature00:12
stokachusinzui: ah this error shows up during kvm deploys00:12
stokachuwhich makes sense if this is only for lxc00:12
stokachuand only seems to show up when i set container: kvm in the environments.yaml for local00:14
stokachuotherwise lxc is used for bootstrap while the others are kvm based00:14
sinzuistokachu, its a warning isn't it?00:15
stokachusinzui: yea looks to be just a warning im running into issues where kvm instances aren't starting up though00:15
stokachuhttp://paste.ubuntu.com/7122808/00:16
sinzuiI see lots of warning because my configs are 1.16.6 and 1.17.600:16
stokachuif i dont set container: kvm then i can deploy kvm's just fine, however, they dont honor the machine constraints00:16
sinzuistokachu, I think the clone issue is just juju being verbose00:17
stokachuok cool, ill dig some more to see why i cant get these instances started00:18
sinzuistokachu, the constraint issue may be bug 129478300:18
_mup_Bug #1294783: deploy to kvm does not honor --constraints <cloud-installer> <constraints> <kvm> <local-provider> <cloud-installer:New> <juju-core:Triaged> <https://launchpad.net/bugs/1294783>00:18
stokachuyea i filed that one lol00:18
sinzuistokachu, sorry, my listing doesn't show reporters00:19
stokachuwas trying to work around it with using kvm as the bootstrap node00:19
thumperstokachu: the fact that it is showing up is a bug00:26
thumperstokachu: it shouldn't be00:26
* thumper thinks...00:27
thumperyeah00:27
thumperit should omit it if it isn't there00:27
stokachuyea looks like it did omit it as i got the kvm instances deployed, unfortunately, i coudn't get it to honor the constraints still00:28
thumperstokachu: what are you trying to do?00:28
thumperwith the local provider, the host is the bootstrap node00:28
stokachuso im working on a cloud-installer project where the single installer bootstraps juju onto a kvm instance and deploys openstack charms on separate instances00:28
stokachuah ok00:29
stokachuso with that said im trying to get the kvm instances deployed with a --constraints mem=1G00:29
stokachuive tried juju set-constraints mem=6G and used juju deploy <charm> --to kvm:0 --constraints mem=1G00:30
stokachuthinking i had to set the machine constraints to something that would allow 1G instances00:30
thumperumm...00:30
stokachuonly thing i haven't tried is juju add-machine --constraints mem=1G00:31
thumperyou can't deploy onto machine 0 with the local provider00:31
thumperor at least you shouldn't be able to...00:31
stokachuthe containers are what im deploying to00:31
stokachuunder machine 000:31
thumperright, nope, that's not supported00:31
thumperif you are trying to do crazy stuff like that, the manual provider is the recommended way00:32
bodie_anyone got a clue how to propose a merge from a remote dev box?00:32
stokachuhttp://paste.ubuntu.com/7122846/ - thats not supported?00:32
stokachumachine 0 is the host machine which connects to libvirt to create the containrrs00:32
thumperstokachu: the fact that it works is mildly surprising to me00:33
stokachuit actually works better than lxc lol00:33
thumperbut it isn't supported...00:33
thumperas in, I've not made sure it works00:33
bodie_pardon my frustration, i've been sitting on this commit for like an hour while I eat dinner, hoping to get it at least proposed by the end of the night00:33
stokachuso both lxc/kvm are not supported as containers to be deployed to on machine 0?00:34
thumperno00:34
thumperI guess it works00:34
thumperbut it isn't supported00:34
thumperthe networking isn't guaranteed to work for a start00:34
thumperif it does, it's a fluke00:34
thumperstokachu: the local provider works by creating containers "as machines"00:35
thumperso machine 1 on the local provider is normally lxc00:35
thumperstokachu: AFAIK, you are the first crazy person to try this00:35
stokachudo i unlock an achievement award or anything? :D00:35
thumpersure...00:36
* thumper hands stokachu an award00:36
stokachulol00:36
thumperhowever...00:36
stokachuso with manual provider do i need to do anything special to deploy to kvm only?00:37
thumperyou have successfully worked out how to have a mixed container local provider00:37
thumperwith no extra work from me00:37
stokachuhah yea i mixed kvm/lxc together on machine 000:37
thumperno...00:37
thumperdo this00:37
* thumper thinks...00:37
thumperactually, I should probably check this out locally first00:38
thumperthe thing is,00:38
thumperthe containers inside machine 000:38
thumperare just using the default dhcp00:39
* thumper thinks harder00:39
* thumper goes to read the source00:39
stokachuyea whatever virbr0 is00:39
stokachui think00:39
stokachuit creates a bunch of vnetX interfaces on the host machine too00:39
thumperright00:41
thumperso it is using the default bridge for kvm on the host00:41
thumperand lxc container would be using lxcbr000:41
thumperyou could... make them talk00:41
stokachuyea i didnt test if they could talk to each other00:41
thumperby changing 'lxc-bridge' -> virbr000:41
stokachuooo00:42
sinzuibodie_, I am not current with what your stuck on, and I try to avoid lbox. Do you have a bzr issue?00:42
thumperin the config00:42
stokachuim going to try that00:42
thumperthen the lxc containers would use the same host bridge00:42
thumperstokachu: you are crazy btw00:42
stokachuhaha im not even sure how i got on this path00:42
stokachuit just happened00:42
bodie_sinzui, I'm working on a remote VPS because my local machine isn't passing tests due to the mongo stuff.00:43
thumperstokachu: and also, AWESOME00:43
bodie_I have a bzr branch ready to lbox propose, but it wants me to use the web browser on the host00:43
stokachuhaha ty00:43
thumperwaigani: I think I need to log into the bot and blow away the pkg dir00:43
bodie_which is headless00:43
thumperwaigani: it has to do with some things not being rebuilt that should be IMO00:44
thumperwaigani: still referring to types that aren't there any more00:44
thumperwaigani: not sure why go isn't rebuilding them properly00:44
bodie_I tried using bzr, but I'm not sure what the workflow should be, and I'm getting stuck on bzr register-branch00:44
waiganithumper: right, I should probably learn how to do that sometime00:44
thumperbodie_: what are you doing?00:45
bodie_I got it logged in to Launchpad.net on the remote via w3m, but it gets grumpy when I try to register-branch00:45
sinzuibodie_, does bzr whoami agree with your email on lp00:45
bodie_yeah00:45
sinzuibodie_, does bzr lp-login prompt for you password00:45
sinzuiand doe you agree lp has your keys00:45
bodie_bzr lp-login just shows my username00:46
sinzuiis so, I push branches to Lp before using lp everything, but lbox suck green donkey's ****00:46
bodie_maybe the ssh key on my remote isn't my user's key00:46
bodie_lol00:46
thumperstokachu: ok, and that warning you were getting for the kvm local provider, that is fixed in trunk00:46
waiganithumper: do I need to pass lxc Start a configFile/consoleFile or is it smart enough to read the ones passed in on creation?00:47
sinzui`bzr push` works for me, though I have my bzr locations setup to push to the project, You can be explicit though....00:47
* thumper looks00:47
sinzuibodie_, ... bzr push lp:~binary132/juju-core/my-branch00:47
thumperwaigani: take what is now in the create container for the start bit, and move it into start container00:47
thumperwaigani: then have create container call start container00:48
waiganithumper: sure00:48
bodie_thanks sinzui.  I owe you00:48
bodie_now what?00:48
stokachuthumper: sweet thanks00:49
stokachuthumper: im actually testing that network-bridge option now00:49
sinzuibodie_, I think lbox will honour where you put the branch so...can run00:49
thumperstokachu: so what does your provider config look like now?00:49
sinzuibodie_, lbox propose -cr00:50
stokachuthumper: http://paste.ubuntu.com/7122907/00:50
thumperstokachu: FWIW, you don't need either of these two: "default-series: precise" or " authorized-keys-path: ~/.ssh/id_rsa.pub"00:51
stokachuthen i just do juju deploy <charm> --to [kvm|lxc]:000:51
stokachuah ok good to know00:51
sinzuiThat will probably run some  tests in a tainted environment, and if satisfied will crate the LP MP, followed by the RV...and then I fail half the time because it want me to login with an identity and password I try never to use00:51
thumperstokachu: for kvm, use --to kvm:000:51
thumperstokachu: for lxc, just do as normal00:51
thumperjuju deploy foo00:51
* thumper shakes his head00:51
bodie_woohoo! https://code.launchpad.net/~binary132/juju-core/fix-bson-references/+merge/21184700:51
* thumper mutters ""crazy shit"00:51
bodie_I did that via web portal00:51
stokachulol will be awesome if it works00:52
thumperbodie_: or as we like to refer to it as "launchpad"00:52
bodie_ahhh SHIT!  I didn't see there were conflicts.....00:52
sinzuibodie_, :( conflicts.00:52
thumperwallyworld: got the bot ip address?00:52
thumperbodie_: always with conflicts00:52
thumperall the time00:52
thumper\o/00:52
wallyworld10.55.61.11800:52
bodie_sigh00:53
sinzuibodie_, just push the updates, Lp will see the change and update the diff00:53
bodie_:) looks like very few conflicts00:54
bodie_ok00:54
* thumper makes an alias gobot='ssh ubuntu@10.55.61.118'00:55
thumperwallyworld: how can I tell if the bot is currently trying to merge?00:55
wallyworldthumper: i just tail the log file in ~tarmac/logs00:56
thumperwaigani: reapprove your branch now00:57
bodie_sinzui -- so I need to merge trunk into my branch?00:57
waiganithumper: done00:57
bodie_then I'll see the conflict and fix it00:57
bodie_or do I need to branch trunk, merge my branch into that00:57
sinzuibodie_, that right, merge trunk. the conflicts will be listed edit each file then use `bzr resolve` then `bzr commit`00:58
bodie_ok00:59
thumpersinzui: https://bugs.launchpad.net/juju-core/+bug/129333001:08
_mup_Bug #1293330: trusty charms are not deployable on ec2, causes provisioner to go into a restart loop <juju-core:Triaged> <https://launchpad.net/bugs/1293330>01:08
thumpersinzui: you said ec2 trusty CI all green01:08
sinzuiIt is, and you might see I tested it locally with the RC candidate. It passed01:09
thumpersinzui: can you try ap-southeast-201:09
sinzuiI will01:09
thumpersinzui: the regions shouldn't be different, but they are01:09
waiganithumper: landed!01:12
stokachuthumper: looks like setting the network-bridge to virbr0 doesn't start lxc containers01:19
thumperstokachu: status?01:19
stokachukvm starts but lxc containers sit in a pending state01:19
stokachulooking through the logs now to see whats going on01:20
thumperstokachu: is it downloading the lxc cloud image?01:20
thumperstokachu: are you on raring?01:20
thumperraring? no trusty01:21
stokachuthe host is saucy01:21
stokachuit downloads the lxc-ubuntu-cloud image01:21
thumperrun sudo lxc-ls --fancy01:21
stokachuhah http://paste.ubuntu.com/7122992/01:21
stokachui guess it does work01:21
stokachuand juju ssh works01:22
stokachuohh and juju status updated its info from pending to started after i juju ssh'd01:22
stokachutesting the trusted wordpress+mysql deployment :X01:23
bodie_ok, think I cleared up the merge conflicts01:24
bodie_ready for review! https://code.launchpad.net/~binary132/juju-core/fix-bson-references01:24
bodie_really dumb fix01:24
stokachusweet01:32
stokachuthumper: http://paste.ubuntu.com/7123027/01:32
stokachuworks01:32
thumperstokachu: awesome01:33
stokachuso what doesn't work is deploying to lxc on machine-001:38
stokachubut everything else started up like a champ01:38
thumperyeah, don't do that01:38
thumperstokachu: because the lxc containers on machine 0 are using lxcbr001:39
thumperso on a different network01:39
stokachuah ok01:39
sinzuithumper, I can reproduce the issue with ap-southeast-2. I attached the only log I could see to take https://bugs.launchpad.net/juju-core/+bug/129333001:42
_mup_Bug #1293330: trusty charms are not deployable on ec2, causes provisioner to go into a restart loop <juju-core:Triaged> <https://launchpad.net/bugs/1293330>01:42
thumpersinzui: ta01:42
stokachuthumper: i guess my last question is should i keep my findings to myself? :)01:43
thumperstokachu: no01:44
stokachucool, i was thinking about a blog post but with a huge disclaimer lol01:45
sinzuiaxw, regarding bug 1293198,  I could try setting termination protection on the instance as juju is setting up. The call to destroy the machine will fail, so we can do an autopsy on the machine.01:49
_mup_Bug #1293198: cannot bootstrap with win-client <ci> <regression> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1293198>01:49
axwsinzui: one other thing you could do is run juju bootstrap with --debug01:51
axwsinzui: then we can see what commands are being executed01:51
sinzuiaxw, It didn't show me anything different before the error...it was identical to show-log from the call to apt-get update01:52
sinzuiI can get you the debug log in a few minutes though01:52
waiganithumper: ping01:53
thumperwaigani: ya01:53
waiganipmed you01:53
waiganiI'm probably off the bottom of your screen01:54
bodie_I assume that by making a merge proposal it'll catch someone's attention soon enough?  or do I need to ping people in here to get it reviewed?01:54
axwsinzui: there should be a "Running script on..." line before any of the apt-get, etc. feedback01:55
thumperbodie_: mostly01:57
thumperyes01:57
bodie_all righty02:02
sinzuiaxw, I attached the debug log to the bug02:07
axwsinzui: thanks02:07
axwsinzui: mkdir -p '\var\lib\juju\agents\machine-0'02:08
axw:(02:08
axwshould be easy to fix02:08
sinzuiha ha02:08
axwI'll get on that02:08
thumperaxw: approved02:23
axwthumper: thanks, just fixing ssh now...02:25
thumpersinzui: I just want to confirm something02:29
thumpersinzui: our trusty CI tests have trusty bootstrap nodes, yes?02:29
sinzuithumper, status says so02:30
thumpersinzui: ok, cheers02:30
thumperjust rebutting a bug02:30
sinzuithumper, it download the precise?02:30
sinzuiI think so02:30
thumpersinzui: https://bugs.launchpad.net/juju-core/+bug/1293330/comments/202:30
_mup_Bug #1293330: trusty charms are not deployable on ec2, causes provisioner to go into a restart loop <juju-core:Triaged> <https://launchpad.net/bugs/1293330>02:30
thumperthat is your status02:30
thumpershowing bootstrap on trusty02:31
thumperwhich is good, because it matches the code02:31
sinzuithe checksum didn't match. I was going to download it and run sha25602:31
thumperkk02:31
thumperwallyworld: where is the supported series stuff for providers?02:31
wallyworldum02:32
wallyworldthere isn't really02:32
wallyworldyou ask for an image for a series and it tells you if it has one02:32
thumperhmm...02:33
wallyworldeg you deploy cs:trusty/myql02:33
wallyworldit looks for a trusty image02:33
wallyworldif there's none there, then no deployed charm for you02:34
thumperwallyworld: I'm looking at the bootstrap issue02:34
thumperlets say I'm on a power machine02:34
thumperand I want to bootstrap to ec202:34
thumperec2 doesn't have power02:34
wallyworldthere, the series comes from denv config default-series02:34
thumperI don't think we should fail by default02:34
wallyworldpower is the arch though02:35
thumperif they have explicitly specified an arch02:35
thumperthen we can fail if it can't find one02:35
thumperif they didn't specify, then we should try with amd6402:35
wallyworldthat's what we do02:35
thumperhmm... no it isn't02:35
thumperbecause the tests fail02:35
thumperI think it is what we said we should do02:36
thumperbut I don't think anyone has implemented it02:36
wallyworldso you saying it looks for an image with arch ppc6402:36
wallyworldif none is specified02:36
axwthumper: https://codereview.appspot.com/7807004302:37
thumperlooing02:37
thumperwallyworld: yep02:37
thumperwallyworld: and I'm saying that if we don't find ppc64, we should try amd6402:37
wallyworldthumper: that's what constraints are for i guess02:37
sinzuiwallyworld, thumper . I just ran curl to get the tools again on the pending machine. My call got tools that passed the sah256sum02:37
thumpersinzui: that is just weird02:38
sinzuiCI was idle. It was publishing new tools...02:38
wallyworldi'm glad we put in the checksum then02:38
sinzuibut if a proxy is involved, maybe it delivered a version from a few hours ago02:38
sinzuiwell I can deploy again and see if it works02:39
wallyworldturn it off and on again02:39
wallyworldthumper: the default fallback arch could be amd64, or it could be an env config just like "default-series" is02:40
thumperwallyworld: I think amd64 would be a good fallback02:41
thumperit has support everywhere02:41
wallyworldyes but i'm not sure explicit is always good02:41
wallyworldimplicit imean02:41
wallyworldymmv02:42
sinzuiI meant to say CI was idle, it was NOT publishing. I wouldn't have deployed using the release candidate if it was about to mutate02:42
sinzuiwallyworld, thumper, I deploy the charm again. It was successful. I think network/proxy is in play and my chosen test with a volatile version of juju is a factor02:48
wallyworldat least that explains it02:49
sinzuithumper, I don't think bug 1293330 is critical, and I am not even sure it is high.02:54
_mup_Bug #1293330: trusty charms are not deployable on ec2, causes provisioner to go into a restart loop <juju-core:Triaged> <https://launchpad.net/bugs/1293330>02:54
thumpersinzui: me neither02:55
thumpersinzui: it is an ec2 issue?02:55
thumperor was it a tools sync issue?02:55
sinzuiI used streams02:56
sinzuiI suspect a proxy. I wouldn't work on this bug unless it was affect tools that had been release unchanged for a few days02:57
thumperwallyworld: https://codereview.appspot.com/78030044/03:05
thumperwallyworld: it is small03:05
thumperand needed shortly by wai03:05
thumperwaigani03:05
wallyworldok03:05
thumperboo yeah03:09
thumperwallyworld: patching version.Current in two places fixes the bug03:10
wallyworld\o/03:10
thumperwallyworld: it was just finding out where to put them :-)03:10
wallyworldi thought i got them all03:10
wallyworldclesrly not03:10
thumperconfirmed fixed on power03:10
wallyworldthumper: reviewed with bikeshed03:11
thumperyou know how much I love bikesheds03:11
wallyworldi think it is a good suggestion03:12
wallyworldmuch clearer intent03:12
thumperyeah, looks fine03:12
wallyworldto me03:12
thumperI'll paste you this other real simple branch as soon as lbox is done03:12
thumperhttps://code.launchpad.net/~thumper/juju-core/fix-ec2-test-isolation/+merge/21185503:12
thumperor you can just look there03:12
* wallyworld waits with baited breath03:12
* thumper goes to make coffee03:13
wallyworldthumper: only if you have time. it's smaller than it looks because deletions. https://codereview.appspot.com/7803004503:28
wallyworldotherwise i'll bother someone in europe to look03:28
thumperwallyworld: I have time03:45
wallyworldok, ta03:45
thumperdavecheney: why did you change the importance and milestone of https://bugs.launchpad.net/juju-core/+bug/1293330 after sinzui?04:30
_mup_Bug #1293330: deploys may fail on ec2 when the juju tools are new. <ec2-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1293330>04:30
davecheneythumper: 'cos I think the bug is more serious04:34
davecheneysomething is corrupting tools on download04:34
thumperdavecheney: what makes you think that?04:34
thumperdavecheney: no, nothing is corrupting it04:34
thumperthe tools were changing04:34
davecheneyfine, change it back04:34
davecheneynot even going to ask why tools are being overwritten04:35
thumperI think it is part of the daily building of the latest code04:35
thumperthe CI for tip04:35
* davecheney puts fingers in ears04:35
wallyworldthumper: do you just want a comment for VType? the code has been there for a while04:40
thumperwallyworld: I just didn't know what it was04:40
wallyworldwe were just not marshalling it04:40
thumperok04:40
thumperno comment needed04:40
wallyworldta04:40
thumpersimplestreams can remain a black box :)04:40
wallyworldwell, it's not simplestreams per se04:41
wallyworldit came from the old cloud init data format04:41
wallyworldbefore simplestreams04:41
wallyworldi'll make it more verbose04:41
wallyworldthumper: the pass by pointer question - not my code, but at a guess, we tend to pass structs by pointer in may places04:42
wallyworldwhy not there04:43
thumpersometimes we do, sometimes we don't04:43
wallyworldwell, it is sorta my new code04:43
thumperif it is always passed04:43
thumperthen that's fine04:43
thumperconsider a lot of our XXXParams structs04:43
thumperthey are always pass by value04:44
thumpernot reference04:44
wallyworldis there a clear idiom04:44
wallyworldi prefer pass by pointer out of C++ habits04:44
thumperwallyworld: I prefer pass by reference04:45
thumpercan't be nil04:45
thumperin C++04:45
wallyworldtrue04:46
* axw enjoys not having to think too much about object ownership05:07
=== OutOfControl is now known as benonsoftware
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|away
=== vladk|away is now known as vladk
=== thumper is now known as thumper-afk
jam1wallyworld: I'm running into a problem where your new UploadTools logic is refusing to bootstrap the local provider. Have you run into this ?06:15
wallyworldjam1: have you pulled trunk? I fixed that first thing this morning06:16
jam1wallyworld: no I hadn't, that's why I was asking. Thanks06:16
wallyworldnp. i refactored about 3 lots of the same logic together in one method and misinterpreted a flag06:16
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
vladkgood morning08:06
dimiternmorning vladk08:11
rogpeppedimitern, vladk: mornin'08:16
dimiternhey rogpeppe :)08:16
dimiternthumper-afk, when you can please check cadmin, I filled some leave for approval08:24
=== vladk is now known as vladk|offline
jam1morning dimitern, rogpeppe08:29
rogpeppejam1: hiya08:29
=== vladk|offline is now known as vladk
rogpeppejam1, dimitern, fwereade: currently looking for a review on this, if you have a little time: https://codereview.appspot.com/7760004808:30
dimiternrogpeppe, looking08:30
rogpeppedimitern: ta08:30
axwrogpeppe: are you working on https://bugs.launchpad.net/juju-core/+bug/1271144? I'll take a look if you're not08:32
_mup_Bug #1271144: br0 not brought up by cloud-init script with MAAS provider <cloud-installer> <landscape> <local-provider> <lxc> <maas> <regression> <juju-core:Triaged by rogpeppe> <juju-core (Ubuntu):Triaged> <juju-core (Ubuntu Trusty):Triaged> <https://launchpad.net/bugs/1271144>08:32
rogpeppeaxw: wwitzel3 has been looking at that, i believe08:32
axwokey dokey08:32
rogpeppeaxw: you might also want to take a look at https://codereview.appspot.com/77600048 BTW08:33
axwrogpeppe: sure, will take a look08:33
voidspacemorning all08:34
rogpeppeaxw: last i heard, people were confused about the cause of the br0 issue. wwitzel3 checked it and it worked on his setup. but it failed for ahasenack. unless you have access to a MAAS, you'll find it difficult to test.08:34
vladkmorning jam1 voidspace08:34
rogpeppevoidspace: mornin'08:34
axwmorning voidspace08:34
voidspacevladk: axw: rogpeppe: morning08:35
axwrogpeppe: yeah, I don't at the moment08:35
sparkiegeekrogpeppe: axw: I can help with debugging that if you need it08:35
axwrogpeppe: the specific problem I was going to look at was bridge-utils not installing08:35
rogpeppeaxw:  yeah08:35
rogpeppeaxw: that's the issue that was being looked at08:35
sparkiegeekaxw: I can reproduce it every time :)08:35
axwsparkiegeek: thanks, I'll make sure I'm not duplicating effort first :)08:36
axwthat helps08:36
axwrogpeppe: ok08:36
rogpeppeaxw: do we set AptUpdate in the cloud-init we produce at bootstrap time?08:36
axwrogpeppe: no, it's done in the synch phase08:37
rogpeppeaxw: ah, that may well be the problem08:37
axwrogpeppe: the simplest change would be to do it in both08:37
rogpeppeaxw: yeah08:37
axwrogpeppe: I was going to modify the MAAS provider code to add it in specifically for MAAS though08:37
axwanyway, will wait to see if wwitzel3 has it under control08:38
rogpeppeaxw: ok, why don't you do that?08:38
rogpeppeaxw: given that we've got sparkiegeek around and eager to test for us :-)08:38
axwrogpeppe: why don't I do what?08:38
sparkiegeekaxw: I tried compiling 1.17.5 but I got a failure with gwacl, if you give me a binary I can run with it08:38
axwsparkiegeek: okay cool, I'll try and knock one up08:38
rogpeppeaxw: add AptUpdate to the cloud-init for maas08:38
axwsparkiegeek: got somewhere I can dump the binary?08:38
jam1rogpeppe: hopefully one final review of https://codereview.appspot.com/76120044/ ?08:48
rogpeppejam1: already done08:49
jam1sparkiegeek: you should be able to cd $GOPATH/src/launchpad.net/gwacl; bzr update -r 23108:50
jam1we are using a slightly older version from tip because there are changes in progress08:50
jam1(or bzr pull . -r 231 --overwrite, if update doesn't work)08:50
jam1anyone have any ideas on: "... cannot use 37017 as state port, already in use"08:52
jam1I'm trying to bootstrap the local provider08:52
jam1and everything has been destroyed08:52
jam1there is no local.jenv, and no jujud processes are running.08:52
jam1now, I *can* telnet localhost 3701708:53
jam1but I don't think anything is actually running there08:53
jam1ahh... hmmm. mongod is still running08:54
jam1and destroy-environment --force isn't killing it08:54
dimiternrogpeppe, reviewed08:55
rogpeppedimitern: ta!08:55
dimiternmgz, how's it going with https://codereview.appspot.com/77270046/ ?08:57
sparkiegeekjam1: so that moved me a little further along, but now I get http://paste.ubuntu.com/7124257/08:58
jam1sparkiegeek: well, the easiest thing is to use 'godeps', so "go get launchpad.net/godeps" and then "cd $GOPATH/src/launchpad.net/juju-core; godeps -u dependencies.tsv"08:59
jam1which will set all your dependencies to the right version.08:59
jam1rogpeppe: I think I'm comfortable enough doing "godeps -u" in the bot now, however we'll want to make sure it gets installed as part of the setup script. Do you have access to the Juju environment?09:00
sparkiegeekjam1: I was just following the README (hint hint, nudge, nudge)09:00
rogpeppejam1: the gobot juju environment?09:00
jam1rogpeppe: yeah09:00
rogpeppejam1: funnily enough, i was at that very moment about to look at the gobot with a view to doing just that09:01
rogpeppejam1: (because i want to update the code to use a more recent version of the ratelimit package)09:01
rogpeppejam1: i do have access, yes09:01
rogpeppejam1: (at least, i did last time i looked)09:02
axwrogpeppe: sparkiegeek has live tested my change and it works, so I've reassigned that bug to myself now - proposing a fix now09:12
rogpeppemgz, jam: i'm thinking that after doing juju set on the gobot environment, we should probably do a "swift upload tarmac gobotnext.yaml" of the same data, right?09:12
rogpeppeaxw: thanks!09:12
jam1rogpeppe: yes09:13
axwfwereade: if you didn't see, I came up with a less stupid name for the API/param field: DistributionGroup09:17
axwwell I think it's less stupid anyway09:17
fwereadeaxw, yeah, iliked that09:17
axwfwereade: also updated the code to do the right thing for env managers09:18
fwereadeaxw, I'm just pondering notfound vs unauthorized for unknown machines -- probably nbd but I need to think it through a bit09:18
axwfwereade: no worries, no rush. this stuff is hanging around till 1.19 anyway09:21
axwrogpeppe: do yo uhave a moment to look over https://codereview.appspot.com/77890045/ ?09:21
rogpeppeaxw: looking09:22
jam1mgz: where is https://bugs.launchpad.net/juju-core/+bug/1291165 at ?09:23
_mup_Bug #1291165: empty .jenv file breaks destroy-environment and bootstrap <ppc64el> <juju-core:Triaged> <https://launchpad.net/bugs/1291165>09:23
wwitzel3hello09:33
=== thumper-afk is now known as thumper
rogpeppeaxw: reviewed09:42
axwrogpeppe: thanks09:42
axwrogpeppe: you make a good point about just configuring the cloudinit.Config. ideally we would do both SetAptUpdate and AddPackage there, for MAAS only09:45
axwrogpeppe: I'd rather get this fixed though, so I'll add a tech-debt bug09:45
rogpeppeaxw: sgtm09:45
jammorning wwitzel3, you should probably sync up with axw about the MaaS br0 bugs09:47
jamwwitzel3: axw has a patch, which should be landing now09:47
axwhey wwitzel3, just about to land https://codereview.appspot.com/77890045/09:47
axwwwitzel3: fixes the apt-get bits, and uses ifdown/ifup instead of service networking restart09:47
dimiternjam, fwereade, I was thinking of creating a blueprint for MaaS VLAN support, so we can track the progress more easily09:48
fwereadedimitern, +10009:48
jamdimitern: you can do so if you want, but *I* certainly find dragging cards on the Kanban board easier than editing the WIP of a blueprint09:48
dimiternjam, I'll take care of updating it regularly09:49
wwitzel3axw: I was actually just reviewing that :)09:49
axwwwitzel3: ah, shall I hold off on approving then?09:49
wwitzel3axw: I am pulling down that branch and will give it a go on my MaaS. I node that I setup with fastpath/curtin so I can verify the fix.09:50
axwwwitzel3: no idea what fastpath/curtin is, but sounds good - thanks09:51
axwwwitzel3: it has been live tested on Garage MAAS, fwiw09:51
wwitzel3axw: well the OP of the bug was using the fastpath installer for maas, which turns out was the main difference in why my maas node had already run apt-get update and theirs had not.09:52
sparkiegeekwwitzel3: ahhh, that's what it was09:52
axwwwitzel3: ah, I see. thanks, would be good to know it still works in that mode then09:52
sparkiegeekaxw: FWIW, it wasn't Garage MAAS, but A.N.Other MAAS09:53
axwsparkiegeek: oops, thanks for correcting me :)09:53
perrito666good morning09:53
wwitzel3sparkiegeek: yep, that was what we narrowed it down to09:53
wwitzel3morning perrito66609:53
sparkiegeekaxw: fastpath (AKA Curtin) is download an image and dd it on to the disk, non fast path is regular debootstrap09:53
axwsounds nifty, I'll have to take a look09:54
sparkiegeek(i'm being a bit loose on the exact behaviour, but it's broadly like that)09:54
rogpeppemgz, jam: where's a good place to install godeps on the 'bot so that it's accessible from tarmac verify scripts?09:58
jamrogpeppe: ~/.local/bin IIRC09:58
jamrogpeppe: we have some other stuff in there already, so it is in the $PATH for cron09:59
rogpeppejam: ah, great, that's just what i needed to know. i was trying to think of a way of working out what $PATH was in that context09:59
jamrogpeppe: crontab -l09:59
jamrogpeppe, wwitzel3, dimitern, waigani: standup time10:00
rogpeppevladk: ^10:02
rogpeppehttps://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.sbtpoheo4q7i7atbvk9gtnb3cc10:02
wwitzel3jam: hangouts is being a pest10:03
wwitzel3attempting to get in there10:03
jamwwitzel3: you probably have to be on your canonical account10:03
jamwe are over the 10 user threshold10:03
jamso it is a @canonical only hangout to get to 1510:03
axwwwitzel3: thanks for the comments. I'll land what I've got and then look at refactoring. Probably trivial, but needs more testing10:06
rogpeppevoidspace: there's a meeting currently10:07
rogpeppevoidspace: see above10:07
voidspaceah10:07
voidspacethursday early meeting!10:08
voidspacerogpeppe: thanks10:08
rogpeppevoidspace: yeah10:08
rogpeppevoidspace: you will *just* fit in if you arrive now10:08
axwalexisb: if you're awake ^^10:08
voidspacerogpeppe: too late I think10:09
voidspace"you aren't allowed to join this call"10:09
voidspacemaybe the wrong identity, will try again10:09
jamvoidspace: you have to join as your @canonical10:09
jamvoidspace: easiest IME is to use the calendar event10:09
jamsince it should be on the right calendar for you10:09
rogpeppevoidspace: add "?authuser=1" to the url10:09
voidspacejam: yea, that's what I did - thanks10:09
voidspacein10:09
dimiternvladk, found a nice tiny bug 1227074 we can quickly pair on later, if you want10:45
_mup_Bug #1227074: runtime panic when running any juju command in a deleted directory <juju-core:Triaged> <https://launchpad.net/bugs/1227074>10:45
perrito666dimitern: nothing that has panic on the title can be nice and tiny :p10:46
vladkdimitern: fine, but probably tomorrow, I am going on meeting with Mike Baker today10:47
dimiternvladk, sure, np10:47
dimiternperrito666, it's a silly panic anyway :)10:47
vladkdimitern: do we need that juju works from deleted directory or just change a panic to error?10:52
dimiternvladk, the latter10:52
perrito666to test things with ec2, do we have an amazon account purposed for testing or should I use my own?10:55
jamdimitern: is there anything in juju that actually cares about $CWD?10:56
jamI don't really care if we fail, but it seems very spurious10:56
natefinchperrito666: use your own and expense it10:56
dimiternjam, apparently we just panic in that case10:56
jam(I know metadata generate-image cares, but aside from that)10:56
perrito666natefinch: ack10:56
jamperrito666: I can give you creds for the shared account10:56
wallyworldmramm: bug 124833210:57
jamyou're allowed to use your own and expense10:57
_mup_Bug #1248332: user doc for simplestreams metadata and private clouds <docs> <juju-core docs:Triaged by evilnick> <https://launchpad.net/bugs/1248332>10:57
jambut I can give you creds as well10:57
perrito666jam: as you prefer, both are the same to me, I guess Ill go with mine, since I only set it up for this and it is already set in juju10:58
dimiternjam, it seems the issue is cmd.DefaultContext includes the dir and that's why it reads os.Getwd() and panics10:58
jamperrito666: sure, you'll just have to go through the expensing it at the end of every month (which is a bit of a pain)10:58
* perrito666 thinks that if he yawns a little bit more he will eat his coffee cup10:58
perrito666jam: I guess it is analog to the pain I had loading my national holidays :p10:59
jamperrito666: but you get to do it every month, and have to copy your receipts to expenses@canonical.com10:59
natefinchperrito666: I highly suggest setting up an alert for if your monthly bill goes over a certain amount (like $100).11:00
natefinchperrito666: (I had a $1000 bill a couple months ago due to forgetting about machines)11:00
natefinch0.11:00
natefinch211:00
perrito666natefinch: dont worry, .ar govt takes care of making a big fuzz every time I spend US dollars11:00
natefinchperrito666: heh11:01
wallyworldfwereade: i can land this for 1.17.6 if you +1 it https://codereview.appspot.com/78030045/11:01
dimiternwwitzel3, i might be able to help you with bug 1294776 if you get stuck btw11:03
_mup_Bug #1294776: No debug-log with MAAS, 14.04 and juju-core 1.17.5 <logging> <regression> <juju-core:Triaged by wwitzel3> <https://launchpad.net/bugs/1294776>11:03
wwitzel3dimitern: I have to get it setup a bit first, as my local maas is running precise11:04
wwitzel3dimitern: but that shouldn't take took long11:05
dimiternwwitzel3, np11:05
rogpeppewallyworld: so does something like this look plausible? http://paste.ubuntu.com/7124711/11:07
wallyworldlooking11:07
wallyworldrogpeppe: almost. the tools metadata is generated off tarballs, not just jujud. so we need to add a tar step11:08
wallyworldi'd have to look at the juju build tools code to see exatly what goes into a tarball11:09
wallyworldi think we could extend the generate-tools to doa build step11:09
fwereadewallyworld, +1, so long as it's explicit11:10
wallyworldyep11:10
fwereadewallyworld, it's the inscrutable magic in upload-tools that, uh, screws us11:10
wallyworldyeah11:10
fwereadewallyworld, https://codereview.appspot.com/78030045/ reviewed, no real blockers but I'd like a chat, brb for that11:11
wallyworldsure11:11
rogpeppewallyworld: right, so that's the kind of thing i'm thinking of that we should really make trivial to do, and it doesn't appear to be currently11:11
wallyworldthere would be release scripts for it too11:11
wallyworldsince that's what the guys use for CI11:12
wallyworldso we could look at packaging those11:12
wallyworldso far there's been no need to do it externally (apart from release) because upload tools does it11:12
wallyworldbut if we get rid of upload tools, i agree 100% we need to add tooling support11:13
rogpeppewallyworld: it would actually be useful even without --upload-tools11:14
rogpeppewallyworld: i mean, even *with* --upload-tools11:14
rogpeppe:-)11:14
dimiternrogpeppe, fwereade, mgz https://codereview.appspot.com/76910044 - Client.ServiceDeployWithNetworks API11:14
wallyworldsure :-)11:14
wallyworldrogpeppe: the release scripts are hosted on lp, i can't recall the branch name right now11:15
wallyworldfwereade: if you wanted a quick hangout to clarify the branch, i can do that. ping me when you are redy11:17
fwereadewallyworld, I'm back in the meeting hangout11:18
fwereadeah no11:18
fwereaderog/michael are there, let's start a new one11:18
wallyworldok11:18
fwereadewallyworld, https://plus.google.com/hangouts/_/76cpi6pcd36amc6k6f520f6lq8?hl=en11:18
=== vladk is now known as vladk|away
=== vladk|away is now known as vladk
=== vladk is now known as vlad|lunch
rogpeppemgz: does this look reasonable as a gobot config setting? http://paste.ubuntu.com/7124775/11:31
rogpeppemgz: i've11:34
rogpeppemgz: here are the diffs: http://paste.ubuntu.com/7124790/11:34
rogpeppejam: ^11:34
mgzhavin' a look11:34
mgzso, apart from being in the wrong format for juju set, amd I don't understand the diff at all11:36
mgzI'm oretty terriffied of go get as a tarmac test step11:36
rogpeppemgz: oh shit, it contains private keys11:37
rogpeppemgz: go get doesn't get anything if it's not already there11:37
mgzyeah, that sound have been paste.canonical.com :)11:37
rogpeppes/not //11:37
rogpeppemgz: do we need to change those keys now11:37
rogpeppe?11:37
mgzdoesn't matter too much as we don't give the bot a public ip, so only people in canonical could screw us anyway11:37
mgzrogpeppe: nah, just get IS to take the paste down11:38
mgzoh, well, the launchpad private key is bad11:38
mgzthat's free access to our trunk11:38
mgzhey everyone, come modify juju-core11:39
=== vlad|lunch is now known as vladk|away
jamrogpeppe: I would *not* do go get as a test step11:39
jamthat, and it looks like you're wrapping the commands?11:39
jamnot sure why it looks that way11:39
rogpeppejam: i can't see how to get around it - how else do we add a new dependency without manually editing the configuration script?11:40
rogpeppejam: and go get is a no-op unless we've added a new dependency11:40
jamrogpeppe: we have to do the work when updating a dep anyway11:40
jamsince you aren't doing -u11:40
fwereademgz, hey, btw, joyent-provider-storage still seems to be hanging around11:41
fwereademgz, we fixed the deps, right?11:41
rogpeppejam: when we update a dep, we can just do juju set tarmac bogus=foo11:41
jamrogpeppe: well, we could do that anyway then11:41
rogpeppejam: to poke the bot into running the config-changed hook11:41
rogpeppejam: that doesn't help when we add a new dependency11:42
rogpeppejam: because the dependency won't be in trunk11:42
rogpeppejam: so go get -u .../juju-core/... won't fetch it11:42
jamrogpeppe: I'm willing to have some potentially dangerous operations be manual, tbh11:42
jamif it isn't something that happens all the time11:42
rogpeppejam: i'm not sure what you mean by "wrapping the commands" BTW. are you referring to the yaml quoting wrapping?11:42
rogpeppejam: why is this potentially dangerous?11:43
jamrogpeppe: your diff has certain "verify_command" lines on 2 lines11:43
rogpeppejam: yaml quoting concatenates lines that aren't separated by a blank line11:43
jamrogpeppe: it is downloading 3rd party code without a human actualyl running the command11:43
rogpeppejam: so is the "go get -u .../juju-core/...11:44
rogpeppe"11:44
jamrogpeppe: we initi11:45
jaminitiate it manually by changing config11:45
jamvs everytime the bot sees a branch to merge11:45
rogpeppejam: maybe we should have a separate config setting holding additional branches to go-get11:46
jamrogpeppe: that sounds like a good way to trigger it.11:46
rogpeppejam: in fact, that would be trivial to do, i think11:46
rogpeppejam: i don't think it requires any changes to the charm11:47
* perrito666 wishes he would stop writing git pull when he tries to bzr pull11:49
mgzperrito666: `alias git="echo use bzr you fool"`11:51
jammgz: that won't work for *too* much longer :)11:51
perrito666mgz: that is actually an idea I am really considering11:51
mgzyou just need a noreallygit alias too :)11:51
jammgz: well "\git" is that in bash, IIRC11:52
perrito666heh, I will only have this machine until friday so I could very well do that11:52
rogpeppejam, mgz: ok, how about this? http://paste.ubuntu.com/7124845/11:52
jamyou can certainly do "\rm foo" to get around "alias rm=rm stuf"11:52
* rogpeppe only just manages to avoid pasting private keys again :-)11:52
mgzrogpeppe: where is that unzip mongodb-server coming from11:53
rogpeppeunalias -a is my friend11:53
perrito666I could actually do a wrapper that checks in what kind of repo I am and do the proper thing without making me feel bad for misspelling bzr :p11:53
mgzrogpeppe: I nearly poked you :)11:53
rogpeppemgz: that's already there11:53
rogpeppemgz: it's actually the end of an apt-get install line11:54
rogpeppemgz: those are two packages that it's apt-get installing11:54
mgzoh dear god the diff syntax11:54
mgzI see11:54
mgzthanks11:54
rogpeppemgz: but yaml has wrapped the line, oh so helpfully11:54
rogpeppedimitern: i've made (almost) all the changes pwd12:10
rogpeppedimitern: ignore me for the moment12:10
rogpeppedimitern: PTAL  https://codereview.appspot.com/7760004812:13
rogpeppemgz: so does it look ok?12:13
rogpeppemgz: if so, i'll try it out12:13
fwereadebodie_, ping12:14
mgzperrito666: it seems you have bzr whomai borked on your local machine12:14
mgzit's "Horacio n <horacio.duran@canonical.com>Dur"12:14
perrito666mgz: ah, marvels of intermachine encoding12:14
mgzI guess macs suck with non-ascii? :P12:14
fwereademgz, did I miss a response to the joyent-storage question?12:14
perrito666mgz: that is actually ubuntu server12:14
bodie_fwereade, what's up :)12:15
perrito666which does indeed suck with a few things non ascii12:15
mgzfwereade: probaly not, it just needs landing12:15
mgzsomething's been borked whenever I've tried, but I could actually force it through12:15
fwereadebodie_, hey, i saw just looking at your MP -- would it be possible to get lbox set up so I can do shiny happy line-by-line comments on the review?12:15
fwereadebodie_, to be fair, I haven't seen anything that needs commenting yet12:16
perrito666mgz: thanks for the heads up, Ill fix it12:16
mgzperrito666: r2437.3.3 is fine, and that's the one *I* committed on ubuntu server :)12:16
fwereadebodie_, but referencing particular bits of code inLP reviews is really tedious ;)12:16
bodie_Understand, what's missing for me to be fully set up?12:17
bodie_Rietveld?12:18
perrito666mgz: again, my ubuntu server :p12:18
rogpeppenatefinch: ping12:20
fwereadebodie_, in one of the docs -- possibly CONTRIBUTING? it describes lbox setup12:20
fwereadebodie_, I'm pretty sure you just need to auth with google on the CLI to use it12:21
natefinchrogpeppe:  sorta here12:21
rogpeppenatefinch: if you had a moment, i wondered if you could join this call for a few moments to discuss bootstrap-state12:22
fwereadebodie_, it also enforces description format and lets you auto-link bugs and stuff12:22
rogpeppewwitzel3 too, presuming you're pairing with nate currently12:22
bodie_fwereade, the problem is that I'm working on a headless remote host configured with 13.10 since my local workstation is on 14.04 and refuses to play nice12:22
rogpeppehttps://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.sbtpoheo4q7i7atbvk9gtnb3cc?authuser=112:22
bodie_I tried using the happy MP technique in the doc and it asked me to open a web browser, which was impossible...12:23
wwitzel3rogpeppe: I'm here12:23
fwereadebodie_, you don't need to do anything *right now*, I've just approved it for you12:23
fwereadebodie_, for which, tyvm12:23
fwereadebodie_, sorry brb12:23
rogpeppewwitzel3: could you join us?12:23
rogpeppedimitern: any chance of a LGTM on that branch you reviewed?12:25
wwitzel3rogpeppe: keep getting not allowed to join12:25
natefinchrogpeppe: joining12:25
rogpeppewwitzel3: try changing authuser=1 to authuser=012:25
rogpeppewwitzel3: in the URL12:25
jamwwitzel3: probably need to be in your canonical account12:25
wwitzel3yep on my canonical account12:26
wwitzel3rogpeppe: can you send me an invite12:26
jamwwitzel3: the account is hard-coded in that URL (the first or second login with "authuser")12:26
jamI usually strip that off12:26
perrito666mgz: apparently "I am in argentina but set this up as an english server" confused a little bit the settings and it let me without proper LC_ALL12:27
wwitzel3jam: it tells me I am the first one there, then I join, and then I get the not allowed message, this is on my canonical account, tried authuser=0 and removing it al ltogether12:28
jamwwitzel3: I just invited your Canonical account12:29
wwitzel3jam: thanks12:29
jamwwitzel3: well, the link worked for me, but meh :)12:29
bodie_http://blog.labix.org/2011/11/17/launchpad-rietveld-happycodereviews12:31
bodie_anyone know if there's a way to do this in headless mode?12:31
bodie_I'm working on a remote while we get 14.04 mongo nonsense up to speed12:31
bodie_speaking of which, here's today's 14.04 mongo nonsense if anyone has a few brain cells to spare: http://paste.ubuntu.com/7124946/12:32
dimiternrogpeppe, i was mostly concerned with not using statetesting12:35
dimiternrogpeppe, LGTM12:36
dimiternrogpeppe, fwereade, I still need a review on https://codereview.appspot.com/76910044 please12:37
fwereadebodie_, is that consistent? we have intermittent "no reachable servers"es that nobody's managed to get to the bottom of12:37
dimiternmgz, ping12:38
mgzdimitern: hey12:38
bodie_i'll double-check, but i'm pretty sure this is what I got last time12:38
jamfwereade: bodie_: that particular test can just be run again, we haven't managed to track down why it takes >45s to start up the server.12:38
jamit doesn't usually12:38
dimiternmgz, I was wondering about your serviceNetworks branch12:38
rogpeppedimitern: thanks!12:38
fwereadejam, wrt dimitern's review, I feel like we *really* need API versioning :/12:39
dimiternmgz, how far away are you from landing it?12:39
mgzdimitern: yeah, I need to add a test and land it, have just been poking jenv things12:39
fwereadedimitern, and I'm afraid I have to eat, cath's just back12:39
mgzif it's blocking your path I'll go ahead and do that12:39
dimiternfwereade, sure, when you can12:39
dimiternmgz, almost - i can land mine without yours and then do a follow-up12:39
dimiternto integrate12:40
mgzdimitern: I'll go ahead and finish it up12:40
dimiternmgz, cheers!12:40
dimiternperrito666, are you working on "CLI "juju deploy --network/--exclude-network"" card?12:40
perrito666dimitern: I began last night but reached nothing in the time I had, I am now with the bug fwereade just threw at me, you can take it if you want (I just assigned to myself next available task, I have no particular interest in it"12:42
perrito666)12:42
dimiternperrito666, not to worry, just checking to update the blueprint12:42
fwereademgz, can you handle the joyent call tonight? I need to stop a bit early12:49
mgzfwereade: sure12:49
bodie_newest 14.04 mongo stuff (you were right jam, the timeouts went away on their own -- this is what I was seeing yesterday)12:55
bodie_http://paste.ubuntu.com/7125084/12:55
=== vladk|away is now known as vlad|lunch
=== vlad|lunch is now known as vladk|away
=== vladk|away is now known as vlad|lunch
=== vlad|lunch is now known as vlad|
=== vlad| is now known as vladk|offline
=== vladk|offline is now known as vladk
dimiternrogpeppe, do you have time to look at https://codereview.appspot.com/76910044 ?13:07
rogpeppedimitern: am currently pairing with voidspace; should be able to have a look later.13:08
dimiternrogpeppe, ok then13:08
rogpeppedimitern: could we not just add IncludedNetworks and ExcludedNetworks to params.ServiceDeploy, and make sure that the behaviour when they're empty is the same as the current behaviour of Deploy?13:32
rogpeppedimitern: i.e. keep the existing API call13:32
dimiternrogpeppe, except we can't verify if the apiserver actually did anything when we set these13:33
dimiternrogpeppe, (i.e. an old server will just ignore them)13:33
dimiternrogpeppe, hence the new API call - we can test whether it's supported13:34
rogpeppedimitern: if we're talking to an old server, is giving an error actually better than doing something without networks?13:35
rogpeppedimitern: (given that we can't specify networks on that server)13:35
bodie_did anyone have any thoughts on that test report?13:35
bodie_oh13:36
bodie_it's the mapreduce issue with not having the js engine13:36
dimiternrogpeppe, yes, because we can detect and report it immediately, rather than hitting issues later13:36
dimiternrogpeppe, if the server does not support it, that's fine - we can't do it, but it's better to know early from UX perspective13:37
bodie_should I open a bug report for the issue?13:38
dimiternbodie_, it seems you're using the juju-mongodb package?13:40
dimiternbodie_, it doesn't have the v8 js engine built-in, hence the error13:40
bodie_right13:40
bodie_so that's a bug, right?13:40
dimiternbodie_, please file one, yes13:41
bodie_I know natefinch and a couple of others were discussing this yesterday13:41
bodie_now, I'm not getting this error on my 13.10 instance13:42
bodie_even though it is configured the same way (with juju-mongodb)13:42
dimiternthat's because the package in saucy is probably different?13:43
bodie_however, I think its version of juju-mongodb is different -- 2.4.613:43
bodie_yeah13:43
rogpeppedimitern: ok, i guess that's fair enough13:45
rogpeppedimitern: i don't see why we don't make DeployWithNetworks backwardly compatible with Deploy though13:46
dimiternrogpeppe, what do you mean?13:47
rogpeppedimitern: well, you currently require some networks to be set13:47
rogpeppedimitern: i don't really see that's necessary13:47
dimiternrogpeppe, that's the only thing different from servicedeploy13:48
dimiternrogpeppe, why'd you call it otherwise?13:48
rogpeppedimitern: if it wasn't for the backward compatibility issue, we'd just call it Deploy, right?13:48
rogpeppedimitern: in some ways it would just be better to call this DeployV2 or something13:48
rogpeppedimitern: from a client point of view, they could *always* call DeployWithNetworks rather than Deploy13:49
natefinchbodie_: the current position is that juju-mongodb is *only* for trusty, and older versions should use regular mongodb (with SSL)13:49
dimiternrogpeppe, yeah13:49
rogpeppedimitern: (and that's true for our client code too)13:49
dimiternrogpeppe, and if we *had* api versioning it would've been even easier13:49
natefinchbodie_: sorry... you hit us just as this stuff was stabilizing (but before it was actually stable)13:50
rogpeppedimitern: not sure about that - if we went william's direction, you'd need to copy the entire API code13:50
bodie_all good, I got my remote working so I'm happy13:51
bodie_natefinch, isn't the juju-mongodb on Saucy just a repackaging of the system default?13:52
dimiternrogpeppe, any api should have means of telling you "i support this" for a specific version13:52
bodie_https://bugs.launchpad.net/juju-core/+bug/1295140 <--- filed bug13:52
_mup_Bug #1295140: Trusty juju-mongodb map-reduce fails due to lacking js engine <js> <mongodb> <trusty> <juju-core:New> <https://launchpad.net/bugs/1295140>13:52
natefinchbodie_: I have no idea. Possibly.13:52
dimiternrogpeppe, and the ability to change the interface between versions13:52
dimiternesp. one we need to support for 5y13:52
bodie_another question: let's say I want to run "real" mongo on my workstation (I'm working on another project that uses it, which might need the js engine.)  Can I have both packages installed?13:53
rogpeppedimitern: for this specific thing, i had in mind that we could ask the API what calls it supports, and potentially what the argument and return types look like13:53
bodie_also, hullo13:53
rogpeppedimitern: that would have made it easy to add arguments to the call and still preserve the ability to check that the API implements it correctly, without needing versioning13:53
rogpeppedimitern: one other thing: you can embed params.ServiceDeploy into params.ServiceDeployWithNetworks13:54
dimiternrogpeppe, yeah, that will save us a lot of boilerplate in the long run13:54
dimiternrogpeppe, i did that initially, but didn't like it very much13:55
natefinchbodie_: no idea about having multiples.  I just have one, which is real mongodb built with SSL.  That's probably your best bet.13:55
dimiternrogpeppe, wasn't sure it'll serialize properly as well to be honest13:55
rogpeppedimitern: it serialises correctly13:55
rogpeppedimitern: here's another possibility: just add the parameters to Deploy13:55
rogpeppedimitern: but also add DeployWithNetworks as an alias for Deploy13:56
bodie_yeah, that would be nice to get working13:56
bodie_but since make install-dependencies installs juju-mongodb, I feel like that should work before I go tweaking things to make it work13:56
dimiternrogpeppe, hmm.. that's a interesting possibility13:56
bodie_I have my remote working, so I'm content until that gets cleared up13:56
rogpeppedimitern: then clients that care can call DeployWithNetworks; eventually we can deprecate DeployWithNetworks.13:56
dimiternbodie_, it should be possible to have both packages running, since they use different ports for mongo, but i doubt anyone tested this13:57
dimiternrogpeppe, ok, write that in the review pls13:57
dimiternrogpeppe, i'll get to it once mgz lands his state changes13:58
rogpeppedimitern: ok, will do13:58
bodie_thanks :) I think I'll wait to make sure the packaged version works before changing anything13:58
bodie_i've just spent a week trying to get my tests to pass at all13:58
bodie_so, the fewer degrees of freedom, the better13:58
dimiternbodie_,  :) fair enough13:58
=== vladk is now known as vladk|offline
wwitzel3dimitern: for bug 1294776 does the node itself need to also be 14.04? I upgraded my MAAS provider to 14.04 but I have an all-machines log14:18
_mup_Bug #1294776: No debug-log with MAAS, 14.04 and juju-core 1.17.5 <logging> <regression> <juju-core:Triaged by wwitzel3> <https://launchpad.net/bugs/1294776>14:18
dimiternwwitzel3, istm you need 1.17.5 juju client bootstrapping on a 14.04 (v1.5 I think?) maas env14:20
sinzuimgz, how goes bug 1291165 ?14:20
wwitzel3dimitern: yeah, that is what I have .. 14.04 maas, 1.17.5 client, precise node ... I will install a trusty node as well and try it there.14:22
dimiternwwitzel3, if've sure you rebuilt cmd/juju & cmd/jujud before bootstrapping with --upload-tools?14:24
mgzsinzui: doing a little juggling, will try to land today14:25
wwitzel3dimitern: yeah I removed them before I re-ran go install.14:27
sinzuimgz, wwitzel3 . I think CI will pass the current rev. I will defer your bugs to the next release (which might be tomorrow if your fixes land...or I call it 1.18.014:29
wwitzel3sinzui: thanks for the update14:30
mgzsinzui: that sounds okay14:30
perrito666Hey I am trying to run  script for a test and, at some point the script creates an instance of amazon and tries to run "juju --show-log upgrade-juju -e amazon --version 1.17.6" which fails saying there are no matching tools available, I am running juju from trunk14:34
perrito666any hints?14:34
dimiternperrito666, better use --debug than --show-log, and put it after the command; you won't need -e envname if "amazon" is your current (juju switch)14:40
perrito666dimitern: Ill make the changes, altough that is run by the testing script (which is not mine)14:41
dimiternperrito666, then --version is not really needed (unless you want to force a specific version). paste the log you're getting? paste.ubuntu.com14:41
perrito666dimitern: tx, Ill re run with the debug flag14:41
niemeyerMorning all14:41
dimiternhey niemeyer14:42
rogpeppeniemeyer: hiya14:42
wwitzel3hi niemeyer14:43
niemeyerYos!14:45
natefinchrogpeppe: I updated our code with your pastebin, and modified it so it compiles.... I think it's the right translation to actual code, but when we do environs.NewFromAttrs() it says "Environment is not prepared"  Which is like... uh, yeah, how can I prepare it before I have it to prepare?14:49
natefinchrogpeppe: the new code: http://paste.ubuntu.com/7125553/14:49
rogpeppenatefinch: ah, i think you probably need to call environs.Provider(cfg.Type(), and then call prov.Prepare on the provider14:51
natefinchrogpeppe: ahh14:51
perrito666dimitern: http://paste.ubuntu.com/7125593/14:52
rogpeppenatefinch: alternatively you could use configstore.NewMem to create a configstore.Storage and call environs.Prepare14:53
rogpeppenatefinch: i'm not sure that's worth doing though14:54
perrito666dimitern: ignorethe python traceback there14:54
mgzrogpeppe: (or anyone) do you remember where we got to with a juju-level error for doing retries of provider transient issues at the sprint?14:55
mgzwe don't seem to have landed anything14:55
rogpeppemgz: i can't quite remember if we wanted to land that on the providers themselves, or the code that calls them14:56
mgza bit of both14:56
rogpeppemgz: did those gobot changes look ok to you in the end, BTW?14:57
mgzrogpeppe: I have some general fears still, but I'm happy to let you try blowing things up :)14:58
dimiternperrito666, are you sure there are actually 1.17.6 tools available?14:58
mgzand have confidence We Can Rebuild It14:58
rogpeppemgz: i don't do the go get any more in verify, FWIW14:58
perrito666dimitern: ¯\_(ツ)_/¯ most likely not14:58
rogpeppemgz: (but i'm sure you saw that)14:58
mgzyeah, last version seemed much less risky14:59
dimiternperrito666, what's this script testing?14:59
perrito666dimitern: backup/restore14:59
perrito666For what I see in their jenkins logs they where running this with .514:59
rogpeppemgz: cool. i'll push it and see what happens.15:00
perrito666perhaps I should try to fetch that rev15:00
dimiternperrito666, I see15:06
dimiternperrito666, try looking in the bucket for what tools are there15:07
rogpeppeoh ffs, you can't do juju set with the output of juju get15:14
rogpeppethat is really crappy behaviour15:14
rogpeppeand the error is really not obvious15:14
natefinchrogpeppe: that is ugly15:16
rogpeppehuh, but... it must've worked before15:17
rogpeppei must be doing something wrong15:17
mgzrogpeppe: right, it sucks15:17
rogpeppemgz: ah, no i wasn't doing anything wrong15:18
rogpeppemgz: yes it does15:18
mgzyou need to dedent everything a level and remove all the config junk15:18
rogpeppemgz: yeah15:18
rogpeppemgz: i remember going on about this before, but it stayed the same for compatibility reasons15:18
rogpeppemgz: but having encountered it for real, it really does suck badly15:18
* rogpeppe writes a little shim to automate the crappy editing required15:19
natefinchrogpeppe: do I need to prepare the environment after calling provider.Prepare?  provider.Prepare returns an environ... seems like it would be weird to call environs.NewFromAttrs() to make a new environ again15:25
rogpeppenatefinch: no, Prepare prepares the environment, not unsurprisingly15:26
natefinchrogpeppe: ok, so, when the tests run, they're still getting a "environment not prepared" error15:26
rogpeppenatefinch: where are you getting the environment config attributes from?15:27
voidspacenatefinch: you were obviously never a boy scout then15:27
natefinchvoidspace: I quit after cub scouts, it's true15:27
voidspace"always be prepared"...15:27
voidspacebdum-tish15:27
natefinchrogpeppe: from dummy.sampleconfig15:32
rogpeppenatefinch: right - they need to come from the environment15:34
natefinchrogpeppe: I think they do?  http://paste.ubuntu.com/7125800/15:36
natefinchrogpeppe: full file: http://paste.ubuntu.com/7125804/15:37
rogpeppenatefinch: no, they don't15:37
rogpeppenatefinch: configs are immutable15:37
rogpeppenatefinch: you need to get the env returned by Prepare and call Config on it to get the config15:38
natefinchrogpeppe: ahh, ok.  weird. Sure.15:39
dimiternrogpeppe, updated https://codereview.appspot.com/76910044 - is it better now?15:42
rogpeppedimitern: looking15:42
natefinchrogpeppe: ok, now the tests are saying environment destroyed, which is progress, sorta.15:42
rogpeppedimitern: reviewed15:45
dimiternrogpeppe, cheers15:48
* dimitern is away for 2h15:48
rogpeppemgz: a little workaround for juju's misbehaviour: http://paste.ubuntu.com/7125888/15:53
rogpeppemgz: i've named it "juju-set"15:53
voidspaceanyone using goimports with vim?15:55
natefinchvoidspace: probably a lot of people, but not me :)15:56
voidspacehah15:56
voidspaceI'm currently failing to get it working15:56
natefinchvoidspace:  I had thought it was a drop in replacement for gofmt15:57
natefinchvoidspace: haven't actually used it15:58
voidspacenatefinch: you have to tell vim to use goimports instead15:58
voidspaceand the docs say: For vim, set "gofmt_command" to "goimports":15:58
natefinchvoidspace: or just rename it and put it ahead in the path? :)15:58
voidspacebut not actually showing how to do that15:58
voidspacenatefinch: hah15:59
bodie_I was just thinking about goimports15:59
natefinchvoidspace: linux people are bad at directions.  I don't know why15:59
bodie_would have made my first commit a lot lazier15:59
bodie_but I don't trust it15:59
bodie_I had to insert an import by hand into 20 files :P16:00
arosalesmgz: fwereade: do you guys have time to sync up with dstroppa on the joyent provider?16:00
natefinchbodie_: I trust it, but I prefer to see the information about imports going into and out of the code... it's important information at times16:00
arosalesmgz: fwereade I have a conflict but it would be nice to see where the joyent provider currently is.16:00
rogpeppemgz: how do i get ssh access to gobot node 0 (so i can run debug-log)?16:01
voidspaceah, to set a variable in .vimrc you don't use set you use let16:04
voidspacenow it works16:04
rogpeppemgz: hmm,16:04
rogpeppe2014-03-17 11:53:25 INFO juju.worker.uniter context.go:255 HOOK # cd /home/tarmac/gwacl-trees/src/launchpad.net/gwacl; bzr pull --overwrite16:04
rogpeppe2014-03-17 11:53:25 INFO juju.worker.uniter context.go:255 HOOK Unable to obtain lock  held by go-bot@bazaar.launchpad.net on taotie (process #31845), acquired 3 seconds ago.16:04
_mup_Bug #31845: Debian sync too soon renders uninstallable in dapper <pdp (Ubuntu):Fix Released> <https://launchpad.net/bugs/31845>16:04
rogpeppe2014-03-17 11:53:25 INFO juju.worker.uniter context.go:255 HOOK See "bzr help break-lock" for more.16:04
rogpeppe2014-03-17 11:53:25 INFO juju.worker.uniter context.go:255 HOOK bzr: ERROR: Could not acquire lock "(remote lock)": bzr+ssh://bazaar.launchpad.net/%2Bbranch/gwacl/16:04
perrito666brb, lunch16:40
rogpeppemgz: i'm seeing lots of this kind of thing on the 'bot: http://paste.ubuntu.com/7126134/16:50
rogpeppemgz: are the "could not acquire lock" messages expected, or do i need to manually break the lock?16:51
sinzuihi rogpeppe, natefinch : Do either you you have a minute to review this branch that increments the version: https://codereview.appspot.com/7832004316:52
rogpeppesinzui: LGTM16:53
sinzuithank you rogpeppe16:53
rogpeppenatefinch: how's it going?16:58
natefinchrogpeppe: I think it's working, our code just expects an instance to have been created, so I have to figure out how to get one of those in the environment (our code call env.Instances)17:00
rogpeppenatefinch: you should be able to call StartInstance on the Environ17:01
rogpeppenatefinch: you could perhaps do that directly after you call Prepare17:05
natefinchrogpeppe: I'm surprised at how hard this is.  Is there something that'll return the right StartInstanceParams that'll give me a generic machine?  I don't know what fields to fill out, and an empty one just fails.17:19
rogpeppenatefinch: your best bet is to look inside the dummy.StartInstance implementation, i'm afraid17:19
rogpeppenatefinch: i could tell you what to do, but i'd have to do that first...17:19
natefinchrogpeppe: that's fine17:20
wwitzel3rogpeppe: aww, but I like hand holding, makes me feel safe17:21
rogpeppewwitzel3: :-)17:21
natefinchrogpeppe, wwitzel3: from the package docs: The configuration YAML for the testing environment must specify a "state-server" property with a boolean value. If this is true, a state server will be started the first time StateInfo is called on a newly reset environment.17:31
rogpeppenatefinch: i think you'll find that there is a state-server property already there17:32
natefinchrogpeppe: yep, it's there and defaulted to true.  But calling it returns "dummy environment has not state configured."  sigh17:34
natefinchit's like no one's ever actually tried to *use* this package17:34
rogpeppenatefinch: calling what returns that?17:35
natefinchrogpeppe: env.StateInfo() after calling Prepare().  DOcs made it sound like it would start up a dummy state machine.17:35
rogpeppenatefinch: why are you calling StateInfo?17:36
natefinchrogpeppe: "If this is true, a state server will be started the first time StateInfo is called on a newly reset environment."17:36
rogpeppenatefinch: (BTW i'm pretty sure the code i gave you (largely inherited from before) sets state-server to false17:37
rogpeppenatefinch: why do you want a state server?17:37
natefinchrogpeppe: you're right, I missed that it was setting state server to false17:37
natefinchrogpeppe: setting that to true makes StateInfo return "environment is not bootstrapped" which at least makes sense.17:37
rogpeppenatefinch: why are you calling StateInfo?17:38
rogpeppenatefinch: FWIW the docs are out of date - the state server is now started when Bootstrap is called17:38
natefinchrogpeppe: I was trying to find a shortcut around having to write out a whole StartInstanceParam with MachineConfig, since I had no clue as to how to populate them correctly17:38
rogpeppenatefinch: the dummy environment never creates instances unless you call StartInstance17:39
rogpeppenatefinch: if you look in dummy.environ.StartInstance, it looks pretty clear which fields need to be set17:39
natefinchrogpeppe: yes, but it's dumb that I have to look at the implementation to figure out what to set all those things to.  Why not just set them for me if they're not set?  Like I said, it's like no one has ever actually used this package.17:40
rogpeppenatefinch: looks like MachineNonce, StateInfo.Tag, APIInfo.Tag17:40
rogpeppenatefinch: mostly StartInstance is not called directly, but by higher level code that is expected to set those fields17:41
rogpeppenatefinch: what you're doing is unusual, but i don't think you'll find it's that hard17:41
rogpeppenatefinch: MachineConfig{MachineNonce: "bootstrap-nonce", &state.Info{Tag: "machine-0}, &api.Info{Tag: "machine-0"}} might do the job17:42
rogpeppenatefinch: oh, and MachineId: "0"17:43
natefinchrogpeppe: it needs machineId, too.  Yes, it's not hard, I guess I just would have assumed someone would have made a helper method that would just set some reasonable defaults for people who don't care about the particulars of the bootstrap node.17:44
rogpeppenatefinch: if it was done in more than one place, it would be worth doing17:44
rogpeppenatefinch: once upon a time i seriously considered making the dummy environment create an instance at bootstrap time, but it broke loads of tests, so i didn't17:45
rogpeppenatefinch: i guess you could add it as a config option17:46
natefinchrogpeppe: now that I know what to look for, I see several tests are doing this, actually17:46
rogpeppenatefinch: which ones, out of interest?17:46
natefinchrogpeppe: worker/provisioner/kvm-broker_test.go   has a startInstance method that does it.  same with the lxc broker17:47
natefinchrogpeppe: environs/jujutest/livetests  does the same sort of "make up all the fake info and call startinstance"  though, modifying it to fail on purpose17:49
natefinchrogpeppe: I guess that's not several, but it's a few17:49
rogpeppenatefinch: the broker tests aren't calling the dummy environ17:50
rogpeppenatefinch: and in the end, there's no really good default for those parameters - they are genuine parameters to the StartInstance call17:51
natefinchrogpeppe: I can make a function that takes a single string for machine id and defaults all the rest of it... that seems pretty defaultable.17:52
rogpeppenatefinch: i guess if you want fake values for APIInfo and StateInfo, and the same nonce for all instances17:53
natefinchrogpeppe: you just make the nonce "foobar-" + machineId17:54
natefinchrogpeppe: Though to be fair, I don't really know what we use the nonce for.17:54
rogpeppenatefinch: it's only used to guard against an extremely unlikely case17:55
rogpeppenatefinch: that will probably never actually happen17:55
rogpeppenatefinch: if the provisioner dies just after it's started the instance but before it's recorded the instance id in the state17:55
rogpeppenatefinch: then when it starts again, it'll start another instance17:56
rogpeppenatefinch: the nonce means that we can know when that old instance connects, that it's not the one we're expecting17:56
rogpeppenatefinch: so for testing purposes, it can be anything tbh17:57
rogpeppenatefinch: i wouldn't be against a testing.FakeMachineConfig(machineId string) *cloudinit.MachineConfig function FWIW17:57
natefinchrogpeppe: I see. Thanks for the explanation.  And yeah, that's basically all I really wanted.  And maybe something in dummy to start up an environment easily.  I just don't want anyone to have to go through my pain again.17:59
rogpeppenatefinch: BTW i'm seeing replicaset test failures in the 'bot: https://code.launchpad.net/~rogpeppe/juju-core/521-peergrouper-publish/+merge/211785/comments/500728/+download17:59
natefinchrogpeppe: that's annoying and sucky.  I haven't really had a chance to go back and try to make them more reliable.18:01
* rogpeppe is done for the day18:03
perrito666such is my luck, found a bug by fixing another :p18:03
natefinchrogpeppe: btw, there's juju/testing/instance.go which has a StartInstance method that takes an environment and a machineid :)   It doesn't quite work,  but it's close18:04
natefinchs/method/function/18:04
rogpeppenatefinch: ah, i guess it needs tools18:05
natefinchrogpeppe: yep18:05
rogpeppenatefinch: i think you'll find that's more hassle than it's worth18:06
natefinchrogpeppe: probably18:06
perrito666hey what is under cmd/plugins, it it made by us too?18:10
perrito666I see that restore backup seems to be re-implementing ssh and scp which are under utils18:10
natefinchperrito666: yeah, it's made by us.  I'm not entirely sure why it's reimplementing those things18:14
perrito666natefinch: apparently it is reimplementing scp without using the identity file from ~/.juju which fails, at least on ec2 with a very sad and undescriptive error :p18:15
natefinchperrito666: bzr blame to figure out who to complain to ;)18:16
mfoordrogpeppe: well done on fixing the bot :-)18:17
perrito666natefinch: roger.p but I am not sure if he is the author or just someone who moved stuff18:18
natefinchperrito666: I think roger wrote at least some of it.  send an email to juju-dev@lists.ubuntu.com if you want more information, I think most of the UK guys are out for the day by now.18:20
perrito666natefinch: what would be roger.p name expanded? :p18:34
natefinchperrito666: sorry, Roger Peppe, aka rogpeppe on irc18:34
natefinchperrito666: he's in the UK.18:34
perrito666ah I should have figured that on my own (who he is, not where)18:34
natefinchperrito666: it's ok, there's a lot of people on the team18:35
wwitzel3done for the day19:31
thumpero/19:42
natefinchthumper: morning19:47
wwitzel3hey thumper19:47
* thumper is off to a physio appt20:20
=== thumper is now known as thumper-physio
=== BradCrittenden is now known as bac
thumper-physiomramm: ping21:05
=== thumper-physio is now known as thumper
thumpersinzui: how close are you to writing the release notes?21:08
thumpersinzui: I should write up something on the proxy support21:09
sinzuithumper, streams.canonical.com did not update, so the release is stalled.21:09
sinzuiyou can add to https://docs.google.com/a/canonical.com/document/d/1CAN-tmQYGLdy1Dd6Ra13EjzqYDivfVZnwRhTfjAdlOQ/edit21:09
sinzuiand I can revise if needed21:10
thumperok, will do now21:10
thumpersinzui: can you make it so I can edit?21:10
sinzuioops21:10
sinzuithumper, reload21:11
thumperta21:11
bodie_I want to make sure I understand this bit about dynamic type.21:11
bodie_http://golang.org/ref/spec#Type_assertions21:11
bodie_the phrasing of this is kind of unclear.21:11
bodie_"x.(T) => "asserts that the dynamic type of x is identical to the type T.""21:12
bodie_I thought Go didn't have dynamic types at all21:12
bodie_therefore, isn't this really saying: "interfaces are a container type; empty interfaces are satisfied by all types, and so can contain any type"21:12
bodie_so it's not REALLY dynamic, just.... virtually dynamic.21:17
thumperbodie_: x needs to be an interface21:17
bodie_yeah21:17
bodie_the phrase "dynamic type of x" threw me off, I guess21:18
thumpersinzui: can you look over the addition there?21:20
thumpersinzui: actually, time to write some more21:20
sinzuiI will21:20
thumpersinzui: look ok? also added a section for lxc-clone21:29
sinzuiI see21:29
sinzuithumper, this is all goos21:32
sinzuigood21:32
thumpercool21:33
perrito666sinzui: ping?22:01
sinzuiperrito666, hello22:03
perrito666have a moment for me?22:03
sinzuiMaybe in 15 minutes22:03
perrito666sinzui: no hurry, it can wait22:03
perrito666thank you22:03
=== vladk|offline is now known as vladk
=== marrusl is now known as marrusl_afk
=== marrusl_afk is now known as marrusl
sinzuihi perrito66622:21
perrito666ji, sorry for the impolite ping instead of hello, I was paying attention at something else22:21
perrito666say, I am working in https://bugs.launchpad.net/juju-core/+bug/129102222:22
_mup_Bug #1291022: Cannot restore a state-server on ec2 and openstack <backup-restore> <ec2-provider> <hp-cloud> <regression> <juju-core:Triaged by hduran-8> <https://launchpad.net/bugs/1291022>22:22
* sinzui nods22:22
perrito666sinzui: yet, I am getting completely different errors :|22:23
perrito666http://pastebin.ubuntu.com/7127660/22:23
perrito666can you tell me the specs of the installation where you ran the restore that you pasted on the ticket?22:23
perrito666It would seem that it goes trough machine 0 setup and it blows on machine 122:24
* perrito666 wonders if anyone ever managed to restore an ec2 using this22:24
sinzuiperrito666, 1. you get the crucial error I see when working with hp or aws22:24
sinzuiperrito666, The instrumentation of failure might be different because of the credentials and my version of euca/nova?22:25
sinzuiperrito666, the specs? do you mean the env.yaml I used22:26
perrito666sinzui: 1) ah I thought that was part of the test given the message on line 15522:27
fwereadethumper, you know the uniter/debug timeouts -- I have a paste that says where they are when they timeout, in case you don't and it rings any bells: http://paste.ubuntu.com/7127717/22:28
sinzuiperrito666, This cam from juju. I saw it on my command line for hp and ec2. I put the test into juju CI anyway wondering if I had a local setup problem:22:29
sinzuierror: cannot restore bootstrap machine: cannot get public address of bootstrap machine: machine "0" has no public address22:29
sinzuiperrito666, juju did standup a state server though. you can even get the status if it.22:29
perrito666sinzui: I encountered some other issues (besides yours) that is what puzzled me22:29
sinzuimaybe juju is impatient. the public address will be available if it waits a little longer22:30
perrito666sinzui: I think that is the problem, perhaps a race condition, altough, after that there is another bug which I solved on my local version :)22:30
perrito666so you would not have arrived much further22:30
perrito666perhaps it works here bc of the lag to the server22:31
perrito666sinzui:  http://pastebin.ubuntu.com/7127730/22:31
sinzuithat's promising22:32
fwereadeperrito666, sinzui: fwiw we obviously *do* have that public address *somewhere* because we just sshed to it -- can we get it from there, instead of whatever we're using to look it up that's racy/faily?22:32
perrito666fwereade: I think the issue is different22:33
perrito666fwereade: I am in south américa and my connection to amazon is rather slow :) that gives the machine time to be provisioned and get an ip22:33
fwereadeperrito666, fwiw I have certainly run backup/restore against ec2, and seen it work, in the past22:33
perrito666fwereade: my guess if that even if we could get hold of the ip (which I think we can) we would need to wait anyway22:34
perrito666fwereade: well, running 1.7.6 here I found out that restore reimplements ssh/scp but omits to use identity file22:35
perrito666at least in the context of the test, where an id_rsa is created for it22:35
fwereadeperrito666, ha, good catch22:35
fwereadeperrito666, that's worth a fix independent of anything else22:35
perrito666other parts use utils/ssh which does use the right id_rsa and work22:35
perrito666so for the sake of fixing this particular issue I hardcoded a few things on my local version to see if I could get to the end of the actual restore22:35
=== vladk is now known as vladk|offline
fwereadeperrito666, am I right in thinking that it's the rsyslog stuff that's failing there on machine 1?22:39
fwereadeperrito666, but regardless, that "need to wait anyway" is interesting,expand please?22:39
perrito666sorry I was tending the laundry22:41
perrito666fwereade: well, I was not able to reproduce the actual error reported by sinzui22:41
sinzuiperrito666, Since I have never seen a pass of my test, there are some lines that I assume will work. If the exit code of the restore is 0, the script calls status until it sees all the machines and unit agents have started. That has a 10 minute timeout.22:41
perrito666I need to look into it but I guess that -> cannot get public address of bootstrap machine: machine "0" has no public address22:43
sinzuiperrito666, you have an error none-the-less. juju-backup exited and stated the update failed22:43
perrito666means that it has to wait a bit more since the only difference between me and the test machines is a extrmely poor connection22:43
perrito666I will take a deeper look22:44
sinzuiperrito666, this is the test run from a few hours ago: http://ec2-54-84-137-170.compute-1.amazonaws.com:8080/job/functional-backup-restore-devel/86/console22:44
perrito666sinzui: I do get the connection error, which is strange because after that all marks success22:46
perrito666well back to the research then :) I guess Ill tackle those one by one I only wish the test would not take so long22:47
perrito666sinzui: thank you you have been very helfpul22:52
perrito666fwereade: btw, aren't you on holiday22:57
perrito666or was that yesterday?22:57
fwereadeperrito666, that was yesterday :)22:57
perrito666agh, that always happens to me when I work from home22:58
fwereadeperrito666, it's ok, I'm actually programming this evening, and that makes me happy22:59
fwereadeperrito666, it must be late for you too ;p22:59
perrito666well, I am debugging, which makes me happy, so we are all happy22:59
perrito666fwereade: yes it is almos 8pm22:59
perrito666got caught with this bug23:00
fwereadeperrito666, if you're still around when axw shows up he might have something useful to say about the rsyslog complaints on machine 123:00
fwereadeperrito666, maybe drop him an email when you stop if he's not around yet23:00
perrito666fwereade: sure, can you translate axw into a real name.lastname :p ?23:00
fwereadeperrito666, ha, sorry, it's andrew wilkins23:01
* fwereade thinks, and has a sudden crisis of faith23:01
* fwereade was right23:01
davecheneypop quiz: is floating point a valid configuration value type23:32
davecheneymarco-traveling: and I think no23:32
davecheneywould anyone care to refute that point ?23:32
davecheneythumper: https://bugs.launchpad.net/juju-core/+bug/129542023:48
_mup_Bug #1295420: local environment does not survive reboot on ppc64el <ppc64el> <juju-core:Triaged> <https://launchpad.net/bugs/1295420>23:48
davecheney^ i'm confused about this one23:48
davecheneythe units appear to be up23:48
davecheneyand there is no indicatoin that they are looping trying to reconnect23:48
davecheneyin their logs23:48

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