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

* thumper sighs00:01
thumperwhy oh why is the bot fubared00:01
=== Ursinha is now known as Ursinha-afk
davecheneywallyworld_: thumper sinzui axw https://docs.google.com/a/canonical.com/document/d/1m9R2n6LPLNLGjdopcNkQYVG8D5V4FTyvc1vvn-9ZifM/edit#00:31
wallyworld_davecheney: thanks, will look00:32
thumperdavecheney: ta00:32
wallyworld_thumper: bot is farked because or a tarmac issue00:32
wallyworld_i think00:32
thumper:(00:32
wallyworld_it has merged 4 branches to it's local tree but not pushed to lp00:33
wallyworld_i'm trying to see if those branches actually passed the tests00:33
thumperhaha00:33
wallyworld_if so, i can push manually00:33
wallyworld_thumper: ffs.00:36
wallyworld_2014-03-06 18:39:30 WARNING  ConnectionReset calling 'Branch.last_revision_info', retrying00:36
wallyworld_2014-03-06 18:39:32 WARNING  ConnectionReset calling 'Branch.last_revision_info', retrying00:36
wallyworld_2014-03-06 18:39:35 INFO     Committing to: /home/tarmac/trees/src/launchpad.net/juju-core/00:36
wallyworld_so if it can't push to lp, it gives up and just merges locally00:37
wallyworld_which results in complaining ever after00:37
thumpercan the machine see launchpad?00:37
thumperhang on00:37
thumperit must be able to00:37
wallyworld_it can and has - i think those are transient00:37
thumperotherwise it wouldn't merge...00:37
wallyworld_yep00:37
wallyworld_so transient errors = it's all broken00:38
thumpergah00:38
wallyworld_i'll look for the branches that have passed testing in the log file and push those manually00:38
thumperwallyworld_: while you're in there00:48
wallyworld_that's what she said00:48
thumperwallyworld_: want to 'go get github.com/juju/loggo' ?00:48
wallyworld_sure00:48
thumperta00:48
thumperwallyworld_: so since it failed once, it no longer tried to push to lp?00:49
wallyworld_yep :-(00:49
wallyworld_i had to push manually00:49
wallyworld_there were 5 i think00:49
bodie_trying to take a crack at fixing a few small bugs to get my head in the game with Go -- one problem, i'm not sure which part of the codebase this refers to on Github00:49
bodie_https://bugs.launchpad.net/juju-core/+bug/121786800:50
_mup_Bug #1217868: move from state.D to bson.D <hours> <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1217868>00:50
bodie_it says juju-core, but i'm not seeing a juju-core repo00:50
thumperbodie_: juju-core is still on launchpad00:50
bodie_is there a doc that explains how things are put together?00:50
bodie_ah00:50
thumpergo get launchpad.net/juju-core/...00:51
bodie_alrighty00:51
thumperwallyworld_: I have a physio appt during our standup00:51
thumperwallyworld_: when do you need to finish today?00:51
wallyworld_around 3pm00:52
wallyworld_thumper: when does your appt finish? we can just delay the standup00:53
thumperI should be back just after 3pm my time00:53
thumpernoon your time00:53
waiganithat suits me, I've got a school thing at 2pm00:53
wallyworld_ok, so let's delay by 30 mins then00:53
waiganiwallyworld_: sent you an email.00:53
wallyworld_waigani: changing writeSampleConfig by itself is not sufficient - i was just point out where the config is used00:54
wallyworld_you need to add a method to optionally add to the sample config00:54
wallyworld_do this during set up00:55
waiganiwallyworld_: right, thought so00:55
wallyworld_and have writeSampleConfig use that00:55
thumperwallyworld_: perhaps by 45 minutes00:55
thumperas I need to get home00:55
wallyworld_sure00:55
waiganiaxw: man of the moment! Sorry for spamming your inbox00:55
* axw opens inbox00:56
wallyworld_thumper: btw, i can see the bot landing your latest branch00:56
wallyworld_running tests i mean00:56
wallyworld_axw: waigani: standup will be delayed while thumper gets repaired. approx 45 minutes00:57
axwhehe. no worries00:57
thumperwallyworld_: ok, cool00:57
thumperwallyworld_: we'll see if it pushes when done00:57
wallyworld_yeah00:57
axwwaigani: re "do you think it is worth while making the validation optional but on by default in UpdateEnvironConfig" -- yes, it is already optional, by opening state with a nil policy00:58
waiganiaxw: haha, point taken00:59
waiganiwallyworld_: okay 3:15. My girl asked me to watch her at assembly which is on now. So that works well.01:00
wallyworld_cool :-)01:00
axwwaigani: first, when reopening don't use Initialize, use "Open". second, if you follow through to JujuConnSuite you can see how it opens a state connection. It uses juju.NewConn, passing in the environ01:04
axwwaigani: take a look in juju/conn.go to see what NewConn does, and how it opens a state conn01:05
axwwaigani: you can then do something similar in your test, but pass nil in as the policy01:05
thumperwallyworld_: is the bot finished?01:09
* thumper doesn't see a push01:09
* wallyworld_ looks01:09
wallyworld_thumper: looks like push to lp has failed again01:10
thumper:(01:10
wallyworld_thumper: i'll mention to martin01:10
thumperdoes the bot have a ssh key that lp knows about?01:10
wallyworld_don't know, seems not i guess01:11
wallyworld_actually01:11
thumperwallyworld_: how are you pushing to lp from there?01:11
wallyworld_it must have01:11
wallyworld_cause i'm pushing from the bot01:11
wallyworld_so it just may be a small setup issue01:11
=== Ursinha-afk is now known as Ursinha
* thumper joined standup hangout02:15
waigani_axw: http://pastebin.ubuntu.com/704761502:16
wallyworld_axw: standup time :-)02:19
=== Tribaal_ is now known as Tribaal
=== bodie_ is now known as Guest31737
voidspacehttps://code.launchpad.net/~rogpeppe/juju-core/511-instancepoller-aggregate/+merge/20950509:54
voidspacewwitzel3: https://code.launchpad.net/~rogpeppe/juju-core/511-instancepoller-aggregate/+merge/20950509:54
voidspaceone time special offer09:54
voidspacereview our branch, again!09:54
voidspacehttps://codereview.appspot.com/71490045/09:54
mgzwwitzel3: https://code.google.com/p/irssi-libnotify/09:56
mgzwwitzel3: it's a trap!10:12
natefinchmorning all10:13
wwitzel3Morning natefinch10:13
wwitzel3should we get the video online?10:13
natefinchwwitzel3: yes please10:13
jamnatefinch: https://plus.google.com/hangouts/_/7acpj3k2j7gc114cifi39l6sf010:16
rogpeppewwitzel3:  lp:~rogpeppe/juju-core/512-maas-bootstrap-bridge-utils10:36
rogpeppewwitzel3:  lp:~rogpeppe/juju-core/512-maas-bootstrap-bridge-utils10:37
=== bloodearnest_ is now known as bloodearnest
voidspaceA long and difficult CL for someone11:01
voidspacehttps://codereview.appspot.com/7245004311:01
jamespagemgz, does this look familiar @ 1.17.411:52
jamespageunit-percona-cluster-6: 2014-03-07 11:51:52 ERROR juju runner.go:220 worker: exited "upgrader": cannot read tools metadata in tools directory: open /var/lib/juju/tools/1.17.4-trusty-amd64/downloaded-tools.txt: no such file or directory11:52
jamespageI get that continually from all of my service units11:52
mgzjamespage: bug 128590112:09
_mup_Bug #1285901: error starting unit upgrader on local provider <local-provider> <lxc> <regression> <juju-core:Fix Committed by wallyworld> <https://launchpad.net/bugs/1285901>12:09
jamespagemgz,good oh12:10
jamespageI'll stop making noise12:10
rogpeppevoidspace: https://github.com/golang/lint12:12
fwereadeadeuring, basically LGTM, ping me if any of my suggestions are unclear12:16
fwereadeadeuring, oh! did we want handling for JUJU_TEST_MODE as well?12:16
adeuringfwereade: what do you mean with "handling for JUJU_TEST_MODE"?12:17
fwereadeadeuring, actually forget I said anything12:18
adeuring;)12:18
fwereadeadeuring, it'll cause more problems than it solves12:18
=== smoser` is now known as smoser
cjohnstondimitern: what version of jujuclient were you using yesterday when you deployed trying to reproduce our issue? I'm wondering if you had the newest version which I guess has a workaround for the issue14:25
dimiterncjohnston, i'm using juju-core from trunk14:27
cjohnstondimitern: client... jujuclient14:28
dimiterncjohnston, i don't quite know what's jujuclient14:28
cjohnstonpython-jujuclient ?14:28
dimiterncjohnston, didn't have to install that14:28
cjohnstonwe also started pinning a specific revno from trunk a couple days ago as a work around for this14:28
mgzcjohnston: wat?14:28
mgzwhy not just use one of the released 1.17 ones14:29
mgzor are you talking about kapil's thing?14:29
cjohnstonnot sure what kapil's thing is, but he has been helping us with this issue14:30
mgzcjohnston: specifically, what do you mean by "jujuclient"?14:30
cjohnstonpython-jujuclient14:30
cjohnstonAIUI it has a workaround for the api watcher issue we are hitting..14:30
cjohnstonev, hazmat ^14:30
mgzokay, so you are talking about kapil's thing14:31
hazmatmgz, i had a workaround for the api server going awol and disconnecting all clients14:31
hazmatin python jujuclient  so that it recovered for extant watches and reconnected and restablished the watch14:31
hazmatmgz, i think the question is if the underlying issue of the api server going awol is addressed14:32
cjohnstonmgz: so I am trying to figure out how dimitern tested it, and it appears as though it would need to be retested without hazmat's workaround in order to try to reproduce..14:32
mgzthey've only given us steps to repo that include spinning up 15 manchines14:32
cjohnstonhowever we have a number of people on our team who have been hitting it14:32
mgzso, dimitern has been struggling to actually get traction on it14:32
cjohnstonmgz: that's how we produce the error14:32
hazmatmgz, specifically there's a log entry in syslog showing mongodb with no clients14:33
cjohnstonwe don't have time right now to go look for other ways to produce it.. we have a deadline that we have to meet14:33
hazmatcause of a client error from the api server, which then restarts the api server worker14:33
hazmatmgz, cjohnston i also have no idea how to reproduce this.. it does seem more prevalent on canonistack..14:34
mgzcjohnston: sure, I know you guys are pretty limited in what you can put in here14:34
jamsinzui: bug #1289376   conversation should be here when you're around14:34
_mup_Bug #1289376: Cannot build r2379 on amd64+precise <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1289376>14:34
jamsinzui: so certainly you should have been using newer golang14:34
jambut the failures in that bug look exactly what I would expect if you tried to compile juju-core with go 1.014:35
jam(the default in precise)14:35
jamsinzui: I'd be willing to help debug it with you14:35
sinzuijam, I will look further...oh the makefile didn't exec and add the deps...14:35
sinzuijam, I switched the rules to run tests since I saw failures everywhere...but I didn't switch back the to the makefile tests.14:36
sinzuisorry14:36
jamsinzui: no problem, I'm happy it was easy to fix :)14:36
jamwe'd love to get 1.17.5 today (as a potential 1.18 candidate) though things are looking pretty slim at this ponit14:36
jampoint14:36
jambug #1289316 is serious14:36
_mup_Bug #1289316: lxc not installed from ubuntu-cloud.archive on precise <lxc> <maas> <precise> <regression> <juju-core:Triaged by wwitzel3> <https://launchpad.net/bugs/1289316>14:36
sinzuijam, I will release 1.17.5 when CI blesses a recent rev. It is 7 revs behind as we did rapid landings.14:42
sinzuijam, I will release over the weekend if I need to14:42
jamsinzui: sure, just that if we don't have fixes like bug #1289316 landed, we can't make it 1.18 as it is regressed from 1.16, and arguably we shoudln't make it 1.17.5 either14:44
_mup_Bug #1289316: lxc not installed from ubuntu-cloud.archive on precise <lxc> <maas> <precise> <regression> <juju-core:Triaged by wwitzel3> <https://launchpad.net/bugs/1289316>14:44
sinzuijam, noted14:44
jamsinzui: I'll hopefully have a short list for you as I uncover things, and target them to 1.17.5 as Critical, will that help you ?14:45
jamsinzui: or would you prefer a different way of indicating blockers14:47
jam?14:55
sinzuijam, sorry, distracted by meeting. I would love a list of blockers. we can target the bugs to 1.17.5 to be clear they need to be fixed in it15:04
sinzuijam, https://launchpad.net/juju-core/+milestone/1.17.5 has a few bugs that stakeholders care about. We can push the off to the next release though since I can release every week15:05
=== Guest31737 is now known as bodie_
mgzjam: https://bugs.launchpad.net/juju-core/+bug/128814115:49
jamsinzui: did you start duping the bugs against https://bugs.launchpad.net/juju-core/+bug/1227450 ?15:52
jamwe have probably ~3 bugs I think that are related enough to be a dupe15:52
_mup_Bug #1288141: Errors when a 1.17.4 unit is rebooted <landscape> <reboot> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1288141>16:07
_mup_Bug #1227450: juju does not retry provisioning against transient provider errors <charmers> <landscape> <juju-core:Triaged> <https://launchpad.net/bugs/1227450>16:07
sinzuijam, hazmat did with my blessing.16:07
sinzuijam, looks like CI is catching up I see r2390 has started testing16:07
mgzfwereade_, natefinch, jam: https://codereview.appspot.com/7231004416:19
natefinchmgz LGTM'd.  Thanks.16:26
=== niemeyer_ is now known as niemeyer
wwitzel3mgz: https://codereview.appspot.com/7227004417:45
wwitzel3also dimitern ^17:45

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