/srv/irclogs.ubuntu.com/2013/12/20/#juju-dev.txt

wallyworld_thumper: hey. can you look at a simple mp? https://codereview.appspot.com/4442004400:35
sinzuiha ha. I am preparing a release and Azure is having network issues.00:44
wallyworld_sinzui: is this 1.17?00:44
sinzuiwallyworld_, I mean azure, not juju.00:44
wallyworld_no i mean is the release you are preparing a juju 1.17 release?00:45
sinzuiCI failed 2166 for azure with networking errors. When I logged into azure, they said they were having networking issues00:45
wallyworld_:-(00:46
sinzuiI am going to replay the tests, but given that azure is wobbling, I may need to wait00:46
sinzuiwallyworld_, I am going to release 1.17.0 CI loves juju at the moment so I have let every keep landing (I can have a lot of good revisions to choose from).00:48
wallyworld_great :-)00:49
wallyworld_sinzui: btw, there is a mp for a restore plugin in progress. so backup/restore will definitely be ready for 1.17.1 i think00:49
sinzuirock00:49
wallyworld_sinzui: i forget who's court the proverbial ball is in - streams.canonical.com still has our test data we did at the sprint. were there plans to get that sorted out for the 1.17 release also?00:54
sinzuiwallyworld_, yes, Ben is on holiday and didn't want to touch it while other staff were also missing00:54
wallyworld_ok, np :-)00:54
sinzuiwallyworld_, We have the build/release process tested and will set everything on the first week of Jan00:55
wallyworld_\o/00:55
sinzuiwallyworld_, oh, actually...00:55
sinzuiThe lost os images on azure happened when Azure added Japan  regions00:56
sinzuiI need to add them to the mirror's file00:56
wallyworld_ah00:56
thumperhi wallyworld_01:02
wallyworld_hey01:02
thumperwallyworld_: reviewed01:09
thumperwallyworld_: just a small thing01:09
wallyworld_great thanks01:09
wallyworld_thumper: so i hacked up some code for charm version in status - it shows version info for both service and units since i figure units can before out of date separate to service if node is down and service is updated01:11
thumperyeah...01:11
wallyworld_but i need martin's stuff to land before i can go any further01:11
thumperI was thinking about that01:11
wallyworld_so i'll park it for now01:11
thumperwell, mgz is off now01:11
wallyworld_:-(01:11
wallyworld_too bad status didn't get done01:11
wallyworld_thumper: i could propose against trunk as is maybe01:12
wallyworld_i would need to clean up my code - i just hacked it together01:12
thumperat least we'll get it done for 1.1801:12
thumperI'd like to talk through the status before you ran with it01:13
wallyworld_sure, next year then :-)01:13
wallyworld_or we can talk now01:13
thumperwe can chat now01:17
wallyworld_thumper: i don't understand "otherwise if you get a comment that starts with a space, you return it."01:17
thumperdo you still have that pastbin?01:18
wallyworld_yeah01:18
thumperlet's hangout01:18
wallyworld_https://pastebin.canonical.com/102221/01:18
thumperI still have it open too01:18
wallyworld_https://plus.google.com/hangouts/_/7ecpi24kekk8g5rnnpd44j64e001:18
bradmhttps://pastebin.canonical.com/102275/ <- interesting response to a juju destroy-environment01:25
thumperbradm: :-(01:33
bradmlooks like swift is a bit confused with whats in that bucket01:34
bradmswift download tells me there's files not found01:34
bradmfwiw juju seems to have done the right thing, and blown away my environment, just the swift bucket still exists with some dodgy content01:35
bradminterested in any debugging from this?  otherwise I'll just blat the swift bucket01:38
=== gary_poster is now known as gary_poster|away
wallyworld_bradm: 409 normally means there's content inthe container that's being asked to be deleted. not sure how that happened unless a call to delete a file in the container failed. i wonder if anything was logged?01:47
wallyworld_thumper: changes pushed01:47
thumperalready approved01:47
bradmwallyworld_: I can't see anything, and if I rebootstrap, then destroy-environment, it looks clean01:50
wallyworld_blame it on santa's elves or something01:50
bradmseems as good a reason as any!01:51
wallyworld_if it happens more regularly we can look at it01:51
bradmdefinately, I'd hate to file a bug for an unreproducible issue, just wastes everyones time01:53
wallyworld_axw: i've landed a change to more robustly ignore empty lines in the auth keys string in juju env config02:33
axwwallyworld_: thanks!02:34
wallyworld_i meant to do it right the first time but clealr didn't02:34
axwno worries02:34
axwI mean to do lots of things right the first time but clearly don't ;)02:35
wallyworld_don't we all :-)02:37
axwthumper: do you have any juju-run things you'd like me to do while you're off? otherwise I have manual-provider destroy-environment, and Windows SSH/bootstrap stuff to work on02:44
wallyworld_thumper: also, don't forget to email us the hotel details02:46
thumperwallyworld_: ok02:57
thumperaxw: work on the windows bootstrapping and ssh stuff02:57
thumperaxw: I'm parking the rest of the juju run client until after the break02:57
axwthumper: okey dokey02:59
thumperaxw: how do I get the long hash for the tip of go.crypto?03:00
thumperhg tip just shows the short hash03:00
axwthumper: not sure sorry, I've just used "godeps -t" in the past03:00
* axw looks at the source03:00
thumper-t?03:00
axwthumper: -t generates the contents of dependencies.tsv03:01
axwgodeps -t <some package that imports go.crypto/ssh>03:01
thumperI don't have godeps installed03:01
axwthumper: hg log -l 1 -r . --template "{node} {rev}\n"03:02
axwthat's what godeps does03:02
thumpercheers03:03
thumperaxw: where is godeps? and is its use documented?03:04
axwthumper: go get launchpad.net/godeps03:04
axwthumper: there's a bit about it in our README I think03:04
thumperta03:04
axwthumper: juju-core/CONTRIBUTING03:04
axwright at the bottom03:04
jamespagewallyworld_, its not canonistack - jam + mgz have access to it08:09
rogpeppethumper: the -t flag asks for testing dependencies to be included (probably not necessary in your case)08:42
rogpeppethumper: (but was undocumented - i've just fixed that)08:42
dimiternthumper, you around?09:33
dimiternthumper, I'm thinking of taking over martin's branch about status via the api and landing it09:33
axwwallyworld_: am I a bit thick, or is the authorized_keys updater modifying /root/.ssh, rather than ~ubuntu/.ssh?09:37
axwwallyworld_: I can't see where the ubuntu user is specified09:38
rogpeppeaxw: ping10:38
axwrogpeppe: pong, sorta. holding my baby, may take a while to respond10:38
rogpeppeaxw: np10:38
rogpeppeaxw: just a quick question on dying environments10:38
rogpeppeaxw: what operations is a dying environment supposed to forbit?10:39
rogpeppeforbid, even10:39
axwrogpeppe: machine and service creation10:39
rogpeppeaxw: what about container creation?10:39
rogpeppeaxw: i.e. nested machines10:39
axwrogpeppe: hmm, I think I had intended it to, but now I'm not sure it's necessary10:40
rogpeppeaxw: i just noticed that there's no check for that, and it'll be awkward to do...10:40
axwrogpeppe: since taking down the instances will take out the containers, I think it doesn't matter10:40
rogpeppeaxw: ok, that's good10:41
axwrogpeppe: will it be difficult to retrofit if I think of a reason? ;)10:42
rogpeppeaxw: not *too* bad - it would just need to go in about three or four different places10:42
rogpeppeaxw: one other thing: i was wondering about caching the Environment object in the state, so we don't have to fetch it every time we add a machine. is there anything about it that can change?10:42
axwok10:42
axwrogpeppe: only life at the moment10:43
axwso yeah, that's probably a good idea10:43
rogpeppeaxw: if it was an object in the state, it would make the retrofitting easier, because we wouldn't need to go through the environment object fetching dance in each place10:44
axwrogpeppe: that'll work for now, but maybe not when JAAS comes along10:44
axwbut of course we can deal with that when it comes10:44
rogpeppeaxw: i suspect that we'll want to maintain a one-to-one State<->Environment mapping10:45
rogpeppeaxw: and add a higher level object.10:45
rogpeppeaxw: or perhaps rename State to Environment10:45
rogpeppeaxw: otherwise every single method gets a new argument, and that seems wrong10:45
axwrogpeppe: yeah, makes sense10:46
rogpeppeah, standup10:46
dimiternrogpeppe, jam, others? last standup of the year! get it while it's hot https://plus.google.com/hangouts/_/calendar/am9obi5tZWluZWxAY2Fub25pY2FsLmNvbQ.mf0d8r5pfb44m16v9b2n5i29ig10:46
axwgotta go - have a nice Christmas all10:47
rogpeppeaxw: you too10:47
rogpeppeaxw: have fun!10:47
dimiternaxw, all the best!10:47
axwthanks :)10:47
rogpeppenatefinch: what would you think about moving the replicaset to juju-core/replicaset, or perhaps juju-core/utils/replicaset ?12:39
rogpeppenatefinch: environs doesn't seem quite right as a place, as it's a building block and doesn't really have any logic related to juju environments12:40
rogpeppelunch13:04
=== gary_poster|away is now known as gary_poster
natefinchrogpeppe: juju-core/replicaset works.  environs was a suggestion by I forget who.  Ideally I'd just move it out to be a standalone package, but no time etc13:43
sinzuirogpeppe, dimitern, Do either of you expect to land anything in the next 2 hours?13:53
dimiternsinzui, yes, status using the API13:54
dimiternsinzui, I'm proposing it now13:54
sinzuisweet. I will wait.13:54
dimiternthanks sinzui13:55
rogpeppesinzui: i'm also expecting a couple of branches to land, but the bot seems stalled currently - i've had them approved for the last hour13:58
dimiternrogpeppe, I'll look into the bot13:59
=== BradCrittenden is now known as bac
sinzuirogpeppe, thank you.14:02
dimiternrogpeppe, in the mean time, can you take a look at the status CL: https://codereview.appspot.com/3842004614:05
rogpeppedimitern: looknig14:05
rogpeppedimitern: reviewed14:08
dimiternrogpeppe, thanks14:08
dimiternrogpeppe, mongod on the bot seems to have hung, so I killed it and removed the sockets, now it seems it works again14:14
rogpeppedimitern: ok, thanks14:14
* rogpeppe should work out how to do that some time14:14
sinzuijcsackett, can you take some time to read my propose juju-core 1.17.0 release notes? https://docs.google.com/a/canonical.com/document/d/1-xisuLkhozMm40e4w5M_Nl1l4yzBBxhzrYhj5eGUoas/edit14:21
dimiternrogpeppe, I usually check for a lot of /tmp/gocheck-* or /tmp/test-mgo-* dirs, which sometimes take up all the space, then I look at ~/.bash_history to see what the others are doing :) - mainly tail -f ~/tarmac/tarmac.log14:22
dimiternrogpeppe, btw, now I can feel what you were saying about waiting forever for lbox to finish - it seems on a weak wireless link it really takes 5m to run, if not more14:23
rogpeppedimitern: i don't actually know how to log in to see what the bot is doing14:29
rogpeppedimitern: or look at its files14:29
dimiternrogpeppe, just a sec14:30
dimiternrogpeppe, you need to source a file like this (sent you a pm)14:30
dimiternrogpeppe, then if you have the nova python client, you can do "nova list" and should see 2 machines, the bot is running on the second one14:31
dimiternrogpeppe, and you'll need to setup your canonical sshbang stuff, so you can do ssh 10.55.x.x (whatever the ip is14:32
rogpeppedimitern: what do you mean by "sshbang"?14:35
natefinchrogpeppe: https://wiki.canonical.com/InformationInfrastructure/IS/SSHebang14:36
dimiternnatefinch, rogpeppe, yeah - you need to se14:36
dimiternsetup chinstrap access, so you can ssh tunnel to canonistack machines14:36
natefinchor you can just ssh into chinstrap and ssh from there to the machine14:37
jcsackettsinzui: release notes look good.14:49
sinzuithank you jcsackett14:50
=== teknico_ is now known as teknico
dimiternnatefinch, once it's merged it's gone btw15:20
dimiternnatefinch, you can't re-merge it15:21
natefinchdimitern, aww, there's no way to modify it and merge it in again, I have to make a new branch?15:23
dimiternnatefinch, yes, sorry :)15:24
natefinchdimitern, bah15:24
natefinchdimitern, at least it's a trivial change15:24
sinzuinatefinch, dimitern rogpeppe. I just disabled CI auto build so that I can start the builds. CI takes about 30 minutes. I want to start the CI in the next 60 minutes to verify tip is ready for release15:28
dimiternsinzui, I'm done with my stuff, the CLI API has all landed15:29
sinzuithank you very much dimitern15:29
rogpeppesinzui: you'd better go ahead without my juju-restore then, because that'll take at least 15 minutes to merge15:29
sinzuirogpeppe, I can wait a bit. I am ever so hopeful that this release will take less than 4 hours, most of the time being spent waiting for the packages to reach the archives15:30
natefinchsinzui: the stuff I've landed isn't actually used yet, so no worries from my end15:33
sinzuithank you natefinch15:33
rogpeppesinzui: well, it's approved, and hopefully will land soon15:35
sinzuiexcellent15:36
dimiternrogpeppe, ah, Client().Status(nil) is what you need for that build failure15:38
rogpeppedimitern: oh damn, another merge problem15:38
rogpeppeapproved again15:41
rogpepperight, that's cool. i now have a "watchgobot" script that i can run to tail the tarmac log file15:44
dimiternrogpeppe, nice!15:45
rogpeppedimitern: http://paste.ubuntu.com/6606340/15:45
natefinchdimitern, rogpeppe: can you check this out https://codereview.appspot.com/34660045 ...you can't tell from the diff, but I did a bzr mv environs/replicaset ./replicaset  (you can tell if you browse the code on the branch: http://bazaar.launchpad.net/~natefinch/juju-core/027-mongoha2/files15:45
rogpeppedimitern: the "gobot" script just runs a command with the env vars you gave to me set15:46
rogpeppenatefinch: looking15:46
rogpeppenatefinch: LGTM15:46
rogpeppenatefinch: thanks15:47
dimiternrogpeppe, heh, nice script, too bad it won't work out of the box on bash :)15:47
rogpeppedimitern: oh, sorry15:47
rogpeppedimitern: rc is my default shell scripting language15:48
dimiternrogpeppe, np, it's trivial to change it so15:48
rogpeppedimitern: you'll need to change the sed command so it takes the argument that allows extended regexps15:48
dimiternrogpeppe, i tend to stay away from bash and any shell scripting language that's not at least python :)15:48
natefinchdimitern: ditto.  bash is one step below perl in my book.... and I hate perl15:49
rogpeppedimitern: for trivial stuff that's just calling commands, rc works pretty well15:49
rogpeppedimitern: and is a bunch better than sh15:49
dimiternnatefinch, oh, perl is somewhere far down on my list, a bit higher than java15:49
natefinchseriously, what the hell is this doing?  if(! ~ $#* 0) {15:49
rogpeppenatefinch: ! is not15:49
rogpeppenatefinch: ~ is the pattern matching operator15:50
rogpeppenatefinch: $#var gives the number of elements in a variable (all variables hold lists)15:50
rogpeppenatefinch: $* are the arguments15:50
dimiternyeah, weird i tell you..15:50
rogpeppeif len(os.Args) > 1 {15:51
dimiternyep15:51
dimiternand looks sooo much better :)15:51
rogpeppedimitern: yeah, that's not a fantastic idiom, although the primitives are simple15:51
rogpepperc is actually *really* simple15:52
dimiternrogpeppe, I got my share of bash (and the like) highly arcane stuff some years back, I was never the same person since :)15:52
rogpeppedimitern: the main problem with bash is the hideous quoting rules15:53
rogpeppedimitern: it's almost impossible to deal well with stuff that has spaces in15:53
dimiternrogpeppe, and let's not even get into arrays and fancy substitutions15:53
rogpeppedimitern: ha15:53
rogpeppedimitern: i still use vanilla bourne shell when writing bash15:54
rogpeppedimitern: apart from $( )15:54
dimiternthat's useful, as is ``15:54
rogpeppedimitern: thing is with bash, it seems that almost noone knows about the crucial role of "$@"15:54
rogpeppesinzui: $() is better than ` `; that's why i use it15:55
rogpeppes/sinzui/dimitern/15:55
sinzuirogpeppe, I also agree. I cannot tell backticks from specs of dust om my screen15:55
rogpeppesinzui: merged15:56
dimiternrogpeppe, I can show you some CMD batch files I had to write like 10 ago, which make bash look a really sensible language15:56
rogpeppethe main reason it's better is that it nests correctly15:56
* sinzui once scrubbed his screen for 10 minutes, then released the script had a backtick in it15:56
rogpeppedimitern: ha, .bat is utterly braindead15:56
dimiternbut backticks are so much easier to write, and with proper vi syntax highlighting it's a breeze15:56
dimiternrogpeppe, .bat was the precursor to .cmd and the "extensions" winNT introduced15:57
rogpeppedimitern: ah, i don't know about that15:57
rogpeppedimitern: the basic syntax of sh is actually quite nice15:58
natefinchI only use bash scripts for putting together commands that I would actually type out on the commandline otherwise. If I need branching or looping, I use a real language. Same for batch scripts on windows15:58
rogpeppedimitern: i'm still happy with the shell i wrote. i will probably port it to unix at some point.15:58
rogpeppesinzui: you can go ahead with the release now if you like, BTW15:59
dimiternanyway16:00
dimiterni think i'll sign off for this year16:00
sinzuirogpeppe, I expect CI to see the new revs in a minute http://162.213.35.54:8080/16:00
rogpeppedimitern: ok16:00
dimiternwith the warm fuzzy feeling we did all we could :)16:00
rogpeppedimitern: have a great christmas16:01
sinzuiif not, I will force a build16:01
rogpeppedimitern: and holidays afterwards16:01
dimiternthanks!16:01
rogpeppedimitern: thanks for all your work16:01
dimiternhave great holidays all of you guys!16:01
dimiternrogpeppe, cheers, thanks for all the reviews and help ;)16:01
dimitern(but remember, I'm coming BACK :)16:02
rogpeppedimitern: np. hope i wasn't too harsh :-)16:02
dimiternrogpeppe, it's fine, not to worry :) i appreciate it16:02
rogpeppenatefinch: FYI here's something nice someone wrote about my shell: http://debu.gs/entries/inferno-part-1-shell16:03
natefinchrogpeppe: pretty cool16:10
rogpeppenatefinch: it had one or two warts, but it was actually amazingly powerful for its size16:12
natefinchrogpeppe: very cool. When did you write it?16:14
sinzuirogpeppe, natefinch 2173 is hated by CI http://162.213.35.54:8080/job/prepare-new-version/540/console16:14
sinzuiwas juju-update-bootstrap moved?16:15
* sinzui can update packaging rules if so16:15
rogpeppenatefinch: the initial version was probably written around '97, but it was developed over a few years16:15
rogpeppesinzui: yeah, juju-update-bootstrap was moved to juju-restore16:16
rogpeppesinzui: sorry, i didn't realise it needed an explicit rule16:16
rogpeppenatefinch: the core shell is still only ~2700 lines though16:16
natefinchrogpeppe: that's not bad at all16:16
sinzuirogpeppe, packaging rules from ubuntu make it explicit. We just inherit it. This is good because we can tell jamespage to review our packaging changes when we release 1.18.016:17
rogpeppenatefinch: it would probably be smaller in Go, although there are some things Go can't do that are kinda fundamental to it16:17
rogpeppenatefinch: and in Go you'd have to deal with all the hideous unix process group management16:18
natefinchyeah, but if it was written in go, you could call it gosh :)16:19
natefinchinferno doesn't even have sh in it... I don't know how it can be considered a valid shell ;)16:19
rogpeppenatefinch: :-)16:19
sinzuirogpeppe, natefinch: Do either of you have time to review the 1.17.1 inc branch? I want to land it the moment I release 1.17.0. https://codereview.appspot.com/4460004417:04
natefinchsinzui, sure17:04
rogpeppesinzui: i'll look too17:05
natefinchsinzui, what's with the change in client.go?17:06
sinzuinatefinch, lbox reported this when I proposed my number changes http://pastebin.ubuntu.com/6606702/17:07
sinzuinatefinch, I am on trusty which provides golang 1.2, which I think is the reason for the message17:08
rogpeppesinzui: i'd prefer to just delete one of those lines. i said that in the code review, but didn't check that it had been done.17:08
rogpeppesinzui: but tbh i don't mind17:09
rogpeppesinzui: we'll fix it in trunk17:09
rogpeppenatefinch, sinzui: trivial review of fix for the above? https://codereview.appspot.com/4462004417:29
sinzuirogpeppe, LGTM17:34
rogpeppesinzui: thanks17:34
sinzuiWe are release r2173 as 1.17.0. CI loves it17:35
sinzuirogpeppe, do you mind landing your import errors fix before me. I can reconcile conflicts then land mine18:06
rogpeppesinzui: ha, i thought i'd approved it some time ago, but i'd only set the commit message18:07
sinzuithat is also my secret technique for not accomplishing anything18:08
nate_finchrogpeppe: anything you want me to look into in the next couple days? I'll be working on EnsureMongoServer, but if that goes faster than expected, I might have some time.18:13
* rogpeppe thinks18:13
rogpeppenate_finch: API server address caching, perhaps?18:16
rogpeppenate_finch: essentially you just need to call configstore.EnvironInfo.SetAPIEndpoint at the right time18:17
nate_finchrogpeppe hmm, ok18:18
rogpeppenate_finch: you might also want to think about how we might do agent failover.18:19
=== nate_finch is now known as natefinch
rogpeppenatefinch: it's a little tricky and i'm not sure of the best approach there18:19
natefinchrogpeppe: yeah, I can see it being pretty tricky18:20
=== gary_poster is now known as gary_poster|away
rogpeppenatefinch: i just did a little bit of mongo stats digging - if we deploy a service with one unit, the API server does 170 consecutive round trips to mongo18:39
natefinchrogpeppe: dang!  That's um... a lot18:45
rogpeppenatefinch: at least they're all round trips to localhost (in the non-HA case anyway)18:46
natefinchrogpeppe: right... not the end of the world, still, seems like a lot18:49
rogpeppenatefinch: indeed18:49
rogpeppenatefinch: takes about 30ms all told18:50
rogpeppenatefinch: (but that is on an otherwise empty database)18:50
rogpeppenatefinch: sorry, 40ms18:51
natefinchrogpeppe: any idea how it scales?18:51
rogpeppenatefinch: linearly i imagine18:51
rogpeppenatefinch: pretty much18:51
rogpeppenatefinch: our database is pretty tiny, even with a large env18:52
natefinchrogpeppe: yeah, I was assuming that.  We just don't have that much information to keep in there.  Honestly, barely even need a DB.18:53
rogpeppenatefinch: indeed. there would be no problem with holding the whole thing in memory if we wanted to18:53
rogpeppenatefinch: i occasionally think about redoing the whole of state with a much simpler in-memory representation and a raft protocol to keep state servers in sync18:54
rogpeppenatefinch: in time, that's definitely something we should consider - it would speed things up by a couple orders of magnitude i think18:55
rogpeppenatefinch: because the db operations could be juju-specific18:55
sinzuiwe may have a problem with 1.17.019:35
sinzuirogpeppe, natefinch My own upgrades to 1.17.0 results in config errors in to services. I cannot destroy the environments. CI didn't see this/19:36
rogpeppesinzui: darn19:37
rogpeppesinzui: what errors?19:37
rogpeppesinzui: i've really got to go though19:38
sinzuirogpeppe, I wont keep you then. I have not released the packages yet. The tools are there and I have 1.17.0 installed using them19:38
natefinchrogpeppe: I can work with him on it.  No sense staying late on the friday before vacation week19:38
natefinch(any later than it already is over there)19:39
rogpeppenatefinch: ok19:40
sinzuinatefinch, rogpeppe : http://pastebin.ubuntu.com/6607413/19:40
rogpeppesinzui: those aren't errors AFAICS19:41
rogpeppesinzui: it's just warning you about deprecated fields in your configuration19:41
sinzuithe agent did upgrade, but each service shows config-changed hook failed19:41
sinzuiThis is on aws, hp, azure, and canonistack19:41
rogpeppesinzui: that's probably unrelated to what you pasted19:42
rogpeppesinzui: the paste is about environment config19:42
rogpeppesinzui: a hook is about service config19:42
sinzuirogpeppe, that is all that all-machines-log reports for each19:42
rogpeppesinzui: could you paste the entire all-machines.log ?19:43
rogpeppesinzui: or actually19:43
rogpeppesinzui: just the log for a single machine with a failed hook would be better19:43
rogpeppesinzui: the uniter log in particular19:43
sinzuithis is the all. I will get the unit http://pastebin.ubuntu.com/6607428/19:44
sinzuinatefinch, rogpeppe, this is the machine-log http://pastebin.ubuntu.com/6607431/19:45
rogpeppesinzui: the machine log won't tell us anything about failed hooks19:46
natefinchrogpeppe: required environment variable not set for credentials attribute: User19:46
rogpeppenatefinch: where's that from?19:47
natefinchrogpeppe: the machine log19:47
natefinchhttp://pastebin.ubuntu.com/6607431/19:47
rogpeppenatefinch: oh yes, i see it19:47
natefinchseems like there's an environment variable for the openstack user that isn't set19:48
rogpeppenatefinch: i wonder how it worked before19:48
rogpeppenatefinch: the agents should not rely on env vars19:48
sinzuisorry rogpeppe, natefinch I typed too fast and went to the wrong machine. This is better http://pastebin.ubuntu.com/6607451/19:48
natefinchrogpeppe: maybe a red herring, then19:49
sinzuinatefinch, this was an upgrade from 1.16.5 to 1.17.0. I am tempted to take the azure stack down and do a simple deploy with 1.17.019:49
rogpeppehmm, the error seems to be that config-get couldn't find the charm: "cs:precise/mysql-31"19:50
natefinchrogpeppe: yeah, was looking at that19:50
sinzui1.16.5 can destroy the envs. A small plus.19:53
rogpeppeoh frick, i know the problem19:54
rogpeppesinzui, natefinch: it's related to dimiter's work on charm uploads19:54
rogpeppei *think* the problem is on this line:19:54
rogpeppeerr := st.charms.Find(D{{"_id", curl}, {"pendingupload", false}}).One(cdoc)19:54
rogpeppein State.Charm19:55
sinzuiI am going to test a simple 1.17.0 deploy of the samething to aws. If it goes well, I will update the release notes to state upgrade from stable to 1.17.0 are note supported19:56
natefinchrogpeppe: why is that wrong?19:57
rogpeppenatefinch: sorry, had a call20:06
rogpeppebecause i think that won't match charm docs with no pendingupload field (the old environment won't have that field)20:07
rogpeppenatefinch: because false!=nil20:07
natefinchahh20:07
rogpeppenatefinch: i think it should be an easy fix20:07
natefinchrogpeppe, yeah20:08
rogpeppenatefinch: could you take it forward please - i'm done20:08
rogpeppenatefinch: it'd first be worth verifying if that is actually the problem20:09
rogpeppeg'night all.20:09
rogpeppesinzui: hope you manage the release...20:09
sinzuirogpeppe, It still looks good20:09
sinzuinatefinch, simple deploys look very good with the new data. Since we don't officially support stable to dev upgrades, I am going to add a disclaimer to not upgrade, it is no supported20:11
rogpeppesinzui: sgtm20:23
natefinchsinzui: sounds good.  We should still fix it, though, and like Roger said, it's not hard20:25
sinzuinatefinch, +1 for a fix. It can go out in 1.17.120:26
natefinchsinzui:  I can get it done for Monday morning if that works?  I'm short on time today.20:27
sinzuinatefinch, I think I can manage that.20:27
sinzuiMost of my time is still spent waiting for builders and azure to do something20:27
rogpeppesinzui: BTW this problem will occur upgrading from 1.17.0 to 1.17.1 too; i don't know if that's a problem20:33
sinzuirogpeppe, noted20:33
natefinchsinzui, rogpeppe: I gotta run, but I'll submit a fix, it's very easy20:35
sinzuinatefinch, thank you.20:35
natefincher, I'll submit a fix this weekend / early monday morning20:35

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