[03:24] <mattyw> morning folks
[03:25] <mattyw> juju status
[03:25] <mattyw> hmmm
[03:25] <mattyw> anyone seen this before? http://paste.ubuntu.com/9875907/
[03:46] <axw> mattyw: looks like the critical bug in the channel subject
[03:46] <mattyw> axw, sorry - yeah just saw, looks like the fix is having trouble landing as well
[03:46] <mattyw> axw, https://github.com/juju/juju/pull/1480
[03:46] <axw> mattyw: yeah, not sure what that is all about
[03:46] <mattyw> axw, I've managed to recover lxc - which is what I needed for now
[08:04] <jam1> just checking if this message gets through. I'm trying to set up an IRC proxy because my normal connection is being terrible now.
[08:25] <jam> menn0: ping (just in case you are on, I'm just checking that everything is working)
[08:26] <menn0> jam: pong
[08:26] <jam> thanks menn0
[08:26] <menn0> jam: np
[10:58] <anastasiamac> dimitern: thnx u for committing the fix for blocker :D do we have an eta for a free for all CI?
[11:03] <dimitern> anastasiamac, well it's up to the CI jobs passing cleanly first IIRC
[11:04] <dimitern> anastasiamac, but I'll follow closely those jobs and make sure to unblock it ASAP
[11:06]  * anastasiamac signs and waitd
[11:15] <anastasiamac> dimitern: thnx for keeping an eye out
[11:15] <anastasiamac> dimitern: it's the end of public holiday here
[11:15] <anastasiamac> dimitern: and one of my son's is starting another school year tomorrow
[11:15] <anastasiamac> dimitern: so m on and off
[11:15] <anastasiamac> dimitern: but really want to land couple of things :D
[11:16] <anastasiamac> dimitern: so i'll keep my eyes open for a while :
[11:16] <dimitern> anastasiamac, sure, I know how frustrating it can be to try to land stuff with a block on :/
[11:20] <axw> dimitern: what caused that weird error about extant dir?
[11:20] <dimitern> axw, no idea - but I suspect it's a lander script issue
[11:21] <axw> dimitern: so you just retried and it worked?
[11:21] <anastasiamac> dimitern: m not frustrated... yet :D
[11:21] <anastasiamac> dimitern: ask me in a few months time...
[11:24] <dimitern> axw, retrying didn't help yesterday :) so I suppose somebody fixed the lander between yesterday and today
[11:25] <dimitern> anastasiamac, :)
[11:25] <axw> righto
[11:25] <dimitern> mgz, hey, are you around?
[11:26] <dimitern> it seems publish-revision job fails with a surprising error - cp: cannot stat `/var/lib/jenkins/streams/juju-dist/devel/tools/releases/juju-*.tgz': No such file or directory
[12:08] <perrito666> morning
[12:25] <mgz> dimitern: hey, checking it out
[12:27] <dimitern> mgz, thanks!
[13:41] <dimitern> mgz, any update on the publish-revision job failing?
[13:43] <mgz> dimitern: we haven't changed the code or the job as far as I see, looking at the machine currently
[13:44] <dimitern> mgz, ok, cheers
[13:44] <dimitern> mgz, it seems to be looking for a devel tarball, but looking at the whole log I can't see any getting generated - can this be related with 1.21's release?
[13:45] <mgz> everything pulled down seems to be in testing, not devel
[13:46] <mgz> it's seems possible a release process thing has left the script broken, but I'm failing to see how currently
[13:51] <dimitern> mgz, what's the difference between testing and develop?
[13:51] <mgz> actually, maybe it is a change curtis made to the assemble streams script over the weekend
[13:51] <dimitern> that's more likely :)
[13:52] <mgz> I'm a bit loath to just revert and see as I'm not sure if other changes were made elsewhere
[13:52] <mgz> but can probably fix
[13:56] <rogpeppe> anyone know about juju-core plans for cli 2.0 ?
[13:56] <rogpeppe> dimitern: ^
[13:56] <rogpeppe> fwereade: ^
[13:57] <dimitern> rogpeppe, I think thumper is in charge of this IIRC
[13:57] <rogpeppe> dimitern: yeah, but i'm never in at the same time as him unfortunately
[13:58] <dimitern> rogpeppe, o'rly? :)
[13:58] <dimitern> well, you can always send him a mail I guess
[13:59] <rogpeppe> dimitern: yeah. i was hoping for a very quick clarification though.
[13:59] <dimitern> rogpeppe, fwereade might know more; sorry I can't help you there :/
[14:00] <rogpeppe> dimitern: np, thanks!
[14:00] <mgz> dimitern: trying a rebuild with older code.
[14:01]  * dimitern crosses fingers and hopes for the sweet unblock
[14:13] <sinzui> dimitern, we are waiting for ci to bless the build before letting developers merge. Ci is actually broken at the moment so the QA team are meeting to fix the issue
[14:14] <dimitern> thanks sinzui
[14:18] <fwereade> rogpeppe, I don't have anything newer than ~brussels there I'm afraid
[14:18] <rogpeppe> fwereade: ok, thanks
[14:18] <rogpeppe> fwereade: just wanted to confirm that we weren't planning on doing "juju <id> operation"
[14:19] <fwereade> rogpeppe, confirmed :)
[14:19] <rogpeppe> fwereade: thanks :)
[14:25] <axw> rogpeppe: "juju add-machine" is now "juju machine add" with an alias. new commands follow that style, but I don't think any of the other existing commands have been updated
[14:26] <rogpeppe> axw: ok cool
[15:00] <perrito666> ericsnow: wwitzel3 brt
[15:32] <cherylj> Is there someone around who can help me with a merge question?
[15:35] <perrito666> cherylj: i might and also congratulations
[15:35] <cherylj> thanks, perrito666 :)
[15:36] <cherylj> I submitted a merge request, and got this error:  Build failed: Does not match ['fixes-1414016']
[15:36] <cherylj> perrito666: do I need to rebase?
[15:37] <perrito666> cherylj: does your pr fix that bug?
[15:37] <cherylj> no
[15:37] <perrito666> cherylj: then you cannot merge :)
[15:37] <perrito666> you see, whenever there is a critical bug/regression CI becomes blocked so we dont pile on top of already existing brokenness
[15:37] <cherylj> aahhh
[15:38] <perrito666> so until someone submits the fix to said bug[s] nothing goes in
[15:38] <cherylj> perrito666, that would explain it :)
[15:38] <perrito666> I believe dimitern was trying to fix that
[15:38] <cherylj> perrito666, thanks!
[15:38] <perrito666> when you do submit that fix, instead of merge you use $$fixes-1414016$$ instead of whatever else inside the $ signs
[15:39] <perrito666> cherylj: there is abit more to it but I am sure in the induction sprint someone will explain the whole process
[15:39] <cherylj> perrito666, good, because being new to git, this is all voodoo to me :)
[15:39] <perrito666> heh, that is all our own doing, for once git is not the culprit
[15:39] <dimitern> perrito666, the fix *is* committed, but CI is broken right now apparently
[15:45] <aznashwan> ericsnow: you there?
[15:45] <ericsnow> yeah
[15:47] <dimitern> voidspace, https://github.com/dimitern/juju/tree/wip-ec2-addressable-containers
[15:47] <aznashwan> so I updated the PR but there's some things left hanging I want to get back on
[15:48] <aznashwan> ericsnow: http://reviews.vapour.ws/r/671/
[15:48] <ericsnow> aznashwan: yeah, saw that :)
[15:48] <aznashwan> ericsnow: got a minute?
[15:48] <ericsnow> aznashwan: OTP
[15:48] <ericsnow> aznashwan: I'll ping you when I'm done
[16:23] <aznashwan> ericsnow: sadly I have to log off right now, be back in a couple of hours in the vain hope you'll be here :D
[16:23] <ericsnow> aznashwan: I'll be here
[16:23] <ericsnow> aznashwan: sorry about missing you :(
[16:41] <voidspace> dimitern: https://github.com/voidspace/juju/compare/wip-networkinterfaces-ec2
[16:42] <mgz> dimitern: I'm curious, your branch to fix bug 1414016 did you actually change anything for the build dep error on merging or did it just work in the end?
[16:42] <mup> Bug #1414016: Local-provider lxc Failed to create lxc_container <ci> <local-provider> <lxc> <regression> <juju-core:Fix Committed by dimitern> <https://launchpad.net/bugs/1414016>
[16:44] <dimitern> mgz, no changes to deps - just modified how we handle lxc config on createContainer / clone
[16:45] <mgz> I'm wondering what changed between when the merge job rejected it and when it landed, Ian asked Curtis about it
[16:45] <dimitern> mgz,that *indeed* is curious :)
[16:45] <mgz> (I have a change to the script I wanted anyway which I'll land shortly)
[16:46] <mgz> just not sure exactly what triggered the error if you don't either :)
[16:46] <dimitern> mgz, it's not something I did though - could it be one of the deps getting updated
[16:46] <dimitern> the actual subrepos, not the .tsv file
[16:46] <mgz> that does sound possible, a rev in another dep - but I don't see it from the go get log clearly
[16:47] <mgz> anyway, will fix (I'll add you to the mp for your edification :)
[17:26] <jam> heya mgz, how goes? haven't said hi in a while
[17:27] <mgz> hey jam! I've seen the good news
[17:27] <perrito666> hi jamcongrats
[17:27] <jam> thanks perrito666 and mgz
[17:27] <perrito666> now imagine thatif I had pressed the space bar
[17:27] <jam> perrito666: I'll just go by jamcongrats :)
[17:29] <mgz> you guys are sprinting currently?
[17:29] <jam> mgz: I'm not, dimiter is with his group
[17:29] <perrito666> jam: you are in dubai?
[17:29] <jam> perrito666: yes
[17:30] <perrito666> jam: isn't like the middle of the night for you?
[17:30] <jam> its late in my evening (21:30), but this is after my son sleeps and I have a chance to do meetings with the US
[17:30] <perrito666> you know since I work here i suck at calculating your current time :p
[17:30] <mgz> ah, so you've already made dimiter take all the responsibility? :)
[17:30] <jam> mgz: :)
[17:30] <jam> perrito666: I find it much more useful to just go to UTC offsets
[17:31] <jam> I'm +4
[17:31] <perrito666> Im -3
[17:31] <jam> its 2:30 for you and 9:30 for me
[17:31] <perrito666> my first interview with you was at a time that was both inconvenient for you and for me because we both did that calculation wrong :p
[17:32] <perrito666> we use utc+- tzs here its you guys that use the smaller only us set, which btw, I still dont know how to use
[17:32]  * perrito666 adds us tzs to his clock
[17:36] <perrito666> well, clock in vivid is broken
[18:21] <rogpeppe> i've updated the gnuflag package to merge in changes from Go core, in case anyone fancies having a look: https://codereview.appspot.com/199070043/
[18:57] <aznashwan> ericsnow: ping
[18:57] <ericsnow> aznashwan: hi
[18:57] <aznashwan> ericsnow: hey, sorry for the delay, you got a minute? :D
[18:57] <ericsnow> aznashwan: sure
[18:58] <aznashwan> ericsnow: so, about the PR, i don't know if you got round to looking through the changes, which, although very few, looked absolutely horrendous...
[18:59] <ericsnow> aznashwan: haven't looked yet
[19:00] <aznashwan> ericsnow: well, let me just say that the library was made for the low-level stuff the CoreOS guys are doing with it and was really ugly to use...
[19:00] <ericsnow> aznashwan: that's a shame
[19:00] <aznashwan> ericsnow: apart from that, everything looks decent, did a test run (with two echo lines, but still) and everything worked
[19:01] <aznashwan> ericsnow: just need a go-ahead from you guys and i'll get to adapting the tests
[19:01] <ericsnow> aznashwan: cool, I'll take a look at some point today
[19:02] <hazmat> sounds like part of systemd assimilation
[19:03] <aznashwan> ericsnow: also, fair warning, I could not figure out how to do get the enabled/disabled status for a service with the library, so our options are either to look for the symlinks in systemd's paths, or do an exec call for it (which is how I have left it for now)
[19:03] <ericsnow> aznashwan: yeah, I was wondering about that
[19:04] <aznashwan> ericsnow: you judge for yourself whether it's acceptable or not, and please let me know on the PR if there's any other issues
[19:04] <ericsnow> aznashwan: will do
[19:05] <aznashwan> much obliged :D
[19:26] <thumper> o/
[19:28] <natefinch> howdy thumper
[20:17] <sinzui> thumper, can you or a member of your squad help triage bug 1413752 ?
[20:17] <mup> Bug #1413752: Bootstrapping to Openstack Environment fails with "no instances found" <hyperscale> <openstack-provider> <juju-core:New> <https://launchpad.net/bugs/1413752>
[20:56] <thumper> :-(
[20:56] <thumper> goose collectInstances swallows errors from nova
[20:56] <thumper> doesn't log nor return them
[20:57]  * thumper files a bug
[20:57] <thumper> oh... that isn't goose, that is juju
[21:02] <thumper> sinzui: looked at that bug
[21:02] <thumper> sinzui: and we just aren't logging enough information to work out what is going on
[21:02] <sinzui> thumper, :(
[21:03] <thumper> I've commented on the bug, and filed another
[21:03] <thumper> in the openstack provider, where we are looking for instances
[21:03] <thumper> we are ignoring the errors from nova
[21:03] <thumper> so if there were issues, we can't tell what they are
[21:03] <thumper> since the provider has obviously started a machine, and we are trying to bootstrap it
[21:04] <thumper> there must be a problem with the call to nova to describe the instance
[21:04] <thumper> but since we are throwing away the error...
[21:04] <thumper> not much we can do
[21:36] <sinzui> thumper, natefinch , do you have a minute to review http://reviews.vapour.ws/r/807/
[21:37] <thumper> shipit
[21:45] <sinzui> thank you thumper