/srv/irclogs.ubuntu.com/2017/09/21/#juju-dev.txt

axwbabbageclunk: https://github.com/juju/1.25-upgrade/issues/32 <- huh? what do you mean we don't use the local juju client? the plugin is called by it...02:15
axwbabbageclunk: or do you just mean, other than the calling into the plugin02:15
babbageclunkaxw: I mean, the plugin doesn't run juju - so it doesn't matter how they're installed.02:16
axwbabbageclunk: okey dokey02:16
babbageclunkaxw: sorry, those are mostly notes for myself for things that have occurred to me while testing with xavpaice02:16
axwbabbageclunk: np02:17
babbageclunkaxw: although, one I wanted to ask you about was the lxc-lxd conversion - it seemed like it didn't leave the containers running?02:17
axwbabbageclunk: yeah just saw that, that's odd - it's always worked for me...02:18
babbageclunkaxw: I haven't had a chance to dig in there - he's had to go do some real work02:18
axwyou can see in the code that we start the LXD containers and wait for them to be accessible02:18
axwbabbageclunk: in fact, the migrate-lxc command actually runs an SSH command to check that they're acccessible02:18
babbageclunkHmm02:19
babbageclunkHe ran that without showing me output. Next time I do it I'll get him to pastebin it so we can see.02:19
axwbabbageclunk: okey dokey02:20
babbageclunkaxw: how was assembly? Heather and I had a fun chat-meeting.02:20
axwbabbageclunk: not bad, just went because Charlotte was getting a certificate. the class item was a bit meh :)02:23
babbageclunkstink02:23
axwbabbageclunk: did I miss anything? how're things going?02:23
babbageclunkGoing through an upgrade with xav has been super helpful - no blockers yet, I've been adding issues for things that could be smoothed out as they come up.02:25
axwveebers: what's up with the "Can one of the admins verify this patch?" message from the bot? what does that even mean?02:26
babbageclunkThe lxc migration and import's done, but upgrade-agents hasn't been finished yet - we were just manually restarting the lxds and about to retry when he got interrupted by other stuff.02:27
babbageclunkI'm getting set up with canonistack to test the fixes I'll make to openstack tagging.02:27
veebersaxw: where are you seeing that?02:40
veebersaxw: I'm trying out some jenkins things, I had assumed I had correctly limited it to just my one test branch02:40
veebersaxw: to answer your question, the plugin I'm testing apparently has a whitelist of 'admin' that can actually trigger a build (and thus asks for one of them to comment on the PR)02:42
veebersOh, I see where that might have leaked though. Sorry, that should be plugged now02:44
axwveebers: no worries, was just curious - thank you02:53
veebersaxw: I think I've removed all instances of the message. Sorry for the noise :-P02:54
axwall good :)02:54
babbageclunkaxw: w00t - blahdeblah is happy with his upgraded canonistack model (modulo the security group problem)03:29
* blahdeblah does a little dance03:29
axwbabbageclunk: sweet :) nice work03:29
blahdeblah\o\ /o/ \o\ /o/03:29
axwblahdeblah: was there any lxc in your environment?03:30
babbageclunkno03:30
axwokey dokey03:30
blahdeblahaxw: zarroo lxcs present!03:30
babbageclunkthat's the thing i'm working on now with xavpaice03:30
* axw nods03:30
babbageclunkaxw: actually, any ideas about this? https://pastebin.canonical.com/198968/03:31
babbageclunkspecifically the ssh errors at the end03:31
axwbabbageclunk: the ssh_exchange_identification?03:32
babbageclunkyup03:32
axwbabbageclunk: might be that the container's still initialising. try running migrate-lxc again, should resume from the right place03:32
axwoh but... already migrated03:32
axwso I guess that's what you/he just did03:32
babbageclunkI can ask him to try it again again though03:33
axwbabbageclunk: doesn't hurt I suppose... but if that's what was already done, I wouldn't expect a change03:34
axwbabbageclunk: strange that it only happens on a subset of containers tho03:35
axwmaybe they are still coming up, and those ones are lagging behind the others03:35
axwbabbageclunk: the loop in waitLXDContainerReady was supposed to prevent this ... :/03:38
babbageclunkaxw: Looking at this, https://unix.stackexchange.com/questions/156908/intermittent-ssh-exchange-identification-connection-closed-by-remote-host-err03:58
babbageclunkWhat if we're creating too many connections to the host and overloading it?03:58
axwbabbageclunk: you mean to the host of the lxc container? possible04:00
babbageclunkyeah04:00
axwbabbageclunk: get him to try with --match=x/lxc/y04:00
axwto match just one container that's failing04:00
babbageclunkaxw: he got this before (not with --match) https://pastebin.canonical.com/198977/04:01
axwbetter04:01
babbageclunkbut still one failure even though it didn't need to migrate any04:01
axwbabbageclunk: yeah it still needs to stop the juju agents though04:02
babbageclunkok04:02
babbageclunkOh, for idempotence?04:02
axwbabbageclunk: yup04:02
babbageclunkyeah, makes sense although wasn't obvious to me at first.04:03
babbageclunkaxw: If I want to throttle the max connections per host, what's a good way to structure that in Go?04:11
babbageclunkaxw: might be easier to just do a max number of concurrent exec tasks, rather than per-host.04:11
axwbabbageclunk: not sure there's a one size fits all, I think I'd just batch the errgroup.Go's and call Wait when the limit is hit04:17
babbageclunkaxw: ok, thanks04:18
babbageclunkaxw: I was looking at this: http://jmoiron.net/blog/limiting-concurrency-in-go/ but it seems a bit lower level - mixing it with errgroup seems clumsy.04:20
axwbabbageclunk: actually that's probably not a bad approach. fill up a channel to whatever capacity, take one on entry to Go, immediately after defer adding one back04:22
axwbabbageclunk: you could have a map of channels keyed on host addr too04:23
babbageclunkyeah, makes sense - I might try that.04:24
babbageclunks/ might/'ll/04:24
babbageclunkaxw: ha ha, fast05:30
axw:)05:30
axwreviewing the other now05:30
babbageclunkaxw: Thanks05:31
babbageclunkaxw: mostly wondering about the panicking/timing out stuff. Actually I think I'll change the panics to errors.05:32
axwbabbageclunk: sounds fine, I don't mind either way - it's a case where panic is reasonable, but we don't really do panics05:32
babbageclunkjust feels a bit icky to have panics and lots of goroutines05:34
axwbabbageclunk: your call, code looks sound anyway05:35
babbageclunkcool, thanks05:35
axwbabbageclunk: did you find out about your flight yet?05:41
babbageclunkaxw: no, not yet05:48
axwbabbageclunk: hope you're not too tired for the tour. I guess we'll all be jet lagged anyway though.05:50
babbageclunkI think the worst-case scenario is that thumper and I have to get the flight that gets into NYC at about 5 - in that case I'll probably bail on the tour.05:51
axwouch, yeah05:52
babbageclunkthe advisory at the moment lists our flight NZ8 as one of the ones not needing a refuelling stop - but it doesn't say whether that's for all days or just for now05:54
=== frankban|afk is now known as frankban
=== frankban is now known as frankban|afk
balloonsthumper, what happened to github.com/juju/loggo/loggocolor20:49
thumperum... what do you mean?20:49
balloonsgithub.com/juju/loggo/loggocolor is a 404 now20:50
thumperit is there for me20:51
balloonsthumper, can you check the repo settings perhaps? unless I'm crazy20:52
thumperhttps://github.com/juju/loggo has it20:52
thumperwhere are you seeing it missing?20:52
balloonsI can't import it20:52
thumperlast commit into loggo was 5 june20:53
balloonsso my build fails20:53
balloonsI guess it's me.. has been all along20:53
balloonsthumper, specifically cmd/juju/commands/debuglog.go import fails, which actually is the only place it's imported20:57
thumperwhich branch?20:58
thumperand where?20:58
balloonsthumper, this is the archive package. I'm going to assume it's just more annoyingness20:58
thumperballoons: check the dependencies are updated properly20:59
balloonsthumper, ack, I don't doubt it because we're building debs, snaps, and I can build manually myself.20:59
balloonsbut no dice for archive builders20:59
thumperdoes the commit hash of loggo match the dependencies.tsv20:59
balloonsthumper, I'm willing to bet it's the debian rules messing with things21:01
balloonsthumper, anyways, I'll head back to it21:02
* thumper nods21:02
thumperok21:02
balloonsand yes, it matches21:02
thumperwat?...21:02
thumperFFS21:02
balloonsohh yep, it's debian/rules21:02
* thumper feels his head is close to exploding21:33
babbageclunkOh dear21:36
babbageclunkI mean, I feel like that too, but just because I'm getting so smart these days!21:37
thumperbabbageclunk: care to be a teddybear?21:53
babbageclunkthumper: of course!21:53
thumperhttps://hangouts.google.com/hangouts/_/canonical.com/stuff21:53
thumperbabbageclunk: ^^21:54
babbageclunkdid you just ragequit23:37
babbageclunkthumper: ?23:37
thumperback23:39
thumperno it went to sleep (or thought it did)23:40
thumperI was thinking and talking, and didn't realise you weren't there for a while23:40
thumperbabbageclunk: ^^23:40
babbageclunkthumper: I dropped anyway - team meeting soon23:40
thumperyeah23:40
thumperok23:40
thumperbabbageclunk: meeting?23:46

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