/srv/irclogs.ubuntu.com/2015/03/17/#juju-dev.txt

ericsnow_davechen1y: PTAL http://reviews.vapour.ws/r/1163/ and http://reviews.vapour.ws/r/1164/00:07
* perrito666 hears a kid receiving express education on the house next door00:10
perrito666sitting in my office during the night makes for the most interesting show00:12
jw4perrito666: is that Argentenian for FastMath (tm) ?00:12
jw4s/FastMath/FasttMath/00:16
perrito666jw4: I dont know what FastMat ™ is, but I was referring at hand against kids bottom00:21
jw4perrito666: :-p00:21
jw4I figured as much - I was trying too hard to be funny00:22
perrito666and of course kids screaming reply00:22
ericsnow_perrito666: did http://reviews.vapour.ws/r/1172/ look okay now?00:24
perrito666ericsnow_: yup, you need a senior rubber stamp though00:26
ericsnow_perrito666: thanks00:28
menn0thumper, waigani, davechen1y, wallyworld : refactoring of api.Open: http://reviews.vapour.ws/r/1179/00:40
* thumper looks00:40
thumpermenn0: done00:44
menn0thumper: thanks00:44
perrito666thumper: hey, you owe me an emails answer :) could I collect on that?01:01
thumperperrito666: um... sure01:02
perrito666thumper: the one about the mongo admin user01:02
thumperyeah, I know the one01:02
thumperjust busy right ow01:03
thumperwill get to it shortly01:03
perrito666thumper: well you have a lot of time, I am going to sleep01:03
davechen1ycan anyone else get to the ppc vm's ?01:18
davechen1ysinzu, can you get to your ppc vm's anymore ?01:20
davechen1ylooks like batuan has lost all our keys01:20
wallyworldaxw_: reviewed, just a few questions01:22
axw_wallyworld: cheers01:23
axw_wallyworld: PTAL01:38
wallyworldlooking01:38
wallyworldaxw_: lgtm01:40
axw_thanks01:40
redelmannHi, I have a noob question about hooks01:59
redelmannsomebody can give me a hand?02:00
jw4redelmann: what's your question - we'll try :)02:00
redelmannwant to prevent django migration when new unit is add02:01
redelmannjw4, want to prevent django migration when new unit is add02:01
redelmannjw4, can i set a variable inside the charms?02:02
jw4redelmann: hmm; that's fairly specific to the charm you're using I think02:02
redelmannjw4, im making a custom charm02:02
jw4ah, I see02:02
redelmannjw4, can i change a charm config variable from inside the charm?02:03
jw4redelmann: yes you should be able to - I'll need to dig a bit to see exactly how02:03
redelmannjw4, something like migrate: true?02:03
redelmannjw4, charmhelper does not have something to do that?02:04
jw4redelmann: it's outside my experience, but I can see if I can find more info in the source02:05
redelmannjw4, could use a file, but it is not the most elegant solution02:05
redelmannjw4, ok dont worry. i was asking because i thought there were a direct solution02:07
jw4redelmann: okay - someone else on this channel or on #juju may know off the top of their head02:08
mupBug #1373236 changed: apiserver/backups: backups must be migrated off legacy provider storage <backup-restore> <juju-core:Fix Released by ericsnowcurrently> <https://launchpad.net/bugs/1373236>02:09
redelmannjw4, with direct solution i meant implemened solution in juju02:09
redelmannjw4, thank02:10
jw4:)02:10
jw4redelmann: '$ juju help set' if you haven't tried that yet02:13
wallyworldaxw_: RE persistent attribute, we could use the provider ValidateConfig() to reject attempts to set persistent for providers which don't support it?02:15
redelmannjw4, but i cant run "juju set" inside charm hooks. or i can?02:15
jw4redelmann: that's what I don't know02:15
redelmannjw4, i will try tomorrow at work02:16
jw4kk02:17
redelmannjw4, i'm seeing postgresql charm, i think they use some "state file". Maybe that's the elegant solution02:20
redelmannjw4, thank you.02:20
jw4cool02:22
jw4good luck redelmann02:22
wallyworldaxw_: i've updated the pr to add extra provider validation03:07
thumpergah...03:11
thumpertrying to work out why my test wasn't working03:11
thumperhadn't set the feature flag03:11
thumper...03:12
thumperyay?03:12
jw4thumper: at least you know they work03:21
thumperyeah :)03:21
menn0thumper: it is not my day. due to other branches landing db-log now has merge conflicts again.03:41
thumper:(03:41
menn0thumper: prepare for another PR for you to merge03:41
* thumper braces himself03:41
* thumper is still braced03:59
alexisbthumper, menn0 is helping you with your gym routine ;)04:02
thumperalexisb: heh... kinda04:02
menn0ha :)04:09
menn0thumper: https://github.com/juju/juju/pull/185704:09
thumpermenn0: merged04:10
thumpermenn0: I don't see much point actaully looking at the diff04:10
thumperit isn't like I'd be able to spot anything :)04:11
menn0thumper: there was a conflict due to waigani's most recent change04:11
* thumper nods wisely04:12
menn0thumper: I guess this is one downside of big feature branches. you end up with a much larger "conflict surface" :)04:13
thumpertrue04:13
menn0thumper: not a showstopper (they're still worth it) but something to be aware of04:14
* thumper sighs04:35
thumpermy magic branch to stop serving the initial environment at the root of the api now breaks a shed ton of tests04:35
thumperbecause guess where all the tests connect to...04:36
waigani:(04:42
menn0thumper: woot! db-log branch merged04:48
thumper\o/04:49
menn0thumper: and I have a fix for the intermittent upgrade test failure04:50
thumperdouble \o/04:50
thumper\o/\o/04:50
thumpera ':' bites me again04:51
thumperok, down to four test failures, and I'm sure at least one of them is about logging04:52
thumperFARK!!!04:53
thumpershitty shitty shitt tests04:53
* thumper stabs it through the heart04:53
thumperI'll work out how to write it properly tomorrow04:53
menn0thumper: new logging stuff, or old?04:54
thumperwell, I'm working around the 'response redacted' bti04:54
thumperimplementing it (I think) a little better04:54
thumperbut also, we have tests that assert that we call version 1 of Login04:55
thumpernow I have version 204:55
thumperI want to rewrite the test04:55
thumpernot just change 1 to 204:55
thumperthe test is broken04:55
thumperand testing the wrong behaviour04:55
thumperit obviously don't care that I'm logging in with v1 or v204:55
thumperit actually cares about ipv4 vs ipv604:55
thumperso it should be testing that04:55
thumpernot the version of the login04:56
thumperbah humbug04:56
menn0totally. understood.04:56
thumperok, I'm done04:56
thumperlaters peeps04:56
axw_wallyworld: just got back. will take a look now04:59
wallyworldsure, had to rebase as well04:59
menn0wallyworld: if you have a moment: http://reviews.vapour.ws/r/1184/05:01
wallyworldsure05:01
menn0wallyworld: thanks05:02
axw_wallyworld: still feels a little fragile, as it's opt-out rather than opt-in, so default behaviour would be to "support" the persistent attribute but ignore it. we can iterate on it, what you did with the scope checking is a good step05:04
axw_wallyworld: shipit05:04
wallyworldaxw_: yeah, we need to improve validation a bit, plus add schema support etc05:05
menn0wallyworld: i'm done for the day. if you're happy with that PR would you mind attempting a $$merge$$ on it?05:07
wallyworldmenn0: looks good, did you change the api call for any reason?05:07
wallyworldmenn0: just did a +105:07
wallyworldi can merge05:07
menn0wallyworld: cool thanks... i'll do the merge05:07
wallyworldok05:07
menn0wallyworld: i changed the API because it seemed silly to trigger a possible environment destruction when we still need the env for the test05:08
wallyworldfair point05:08
menn0wallyworld: so I chose a non-destructive yet restricted API call05:08
wallyworld+105:08
menn0wallyworld: cheers05:08
=== anthonyf is now known as Guest1386
axw_wallyworld: FYI, https://github.com/axw/juju/tree/worker-mounter06:40
axw_need to do some more testing before I propose it06:40
axw_it appears that "storage list" is broken, looking into it atm06:41
wallyworldok06:45
axw_wallyworld: still around? http://reviews.vapour.ws/r/1185/08:06
mattywmorning all08:29
voidspacegrrr... someone else landed an upgrade step08:50
voidspacenow I have conflicts to resolve08:50
voidspace*really easy* conflicts, but still...08:50
voidspacedimitern: "addresser"?09:19
voidspacedimitern: or networker/addresses ?09:20
dimiternvoidspace, you mean the name of the worker?09:21
voidspacedimitern: yep09:21
dimiternvoidspace, addresser I think - not in networker though - top level09:21
voidspacedimitern: yep, cool - thanks09:22
TheMueHi folks, greetings from the CeBIT09:51
dimiternTheMue, hey! how's it going there?09:52
TheMueFirst informational talks for me, so far few interested people09:58
TheMueBut this area optically more looks like for recreation instead of a real booth09:58
voidspacedimitern: just you and me for standup I think :-)09:58
TheMueNot well designed09:58
dimiternTheMue, it will pick up as it goes09:58
dimiternvoidspace, omw09:59
TheMueI hope so09:59
natefinchAnyone seen a message like this before?  I'm getting this when destroying a local environment: ERROR while stopping mongod: exec ["stop" "--system" "juju-db-nate-local"]: exit status 1 (stop: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist)10:07
dimiternnatefinch, I've seen this10:19
dimiternnatefinch, is this on vivid?10:20
natefinchdimitern: utopic10:20
dimiternnatefinch,  inside a container?10:21
dimiternnatefinch, perhaps this is relevant - http://ubuntuforums.org/showthread.php?t=159456610:23
dimiternI have seen this error recently, but can't quite recall the circumstances - what I remember is that it has nothing to do with dbus missing or otherwise10:24
natefinchit's just the local provider on my laptop.  Laptop is utopic.  *shrug*10:26
natefinchconnman is not installed, so that link is evidently not applicable10:26
voidspacenatefinch: my laptop arrives today, it will have windows on it10:38
voidspacenatefinch: is installing ubuntu straightforward?10:38
natefinchvoidspace: IIRC it's just a matter of making an ubuntu USB stick and booting with it in10:39
natefinchvoidspace: I don't remember having to twiddle with the bios or anything10:39
voidspacenatefinch: cool, that's what I'm hoping :-)10:39
perrito666morning everyone10:49
voidspaceperrito666: morning10:49
perrito666natefinch: fell off the bed?10:49
natefinchperrito666: nah, I been getting up at 5am for a couple weeks now, trying to get this HA stuff done.. my day is pretty broken up with kids stuff, though, so I'm usually AFK from 7-9:3011:01
voidspacedimitern: do you think "juju add-machine lxc:0" should be sufficient to allocate an IP address?11:04
voidspacedimitern: 1.22, maas11:04
dimiternvoidspace, in 1.22 it won't allocate anything11:05
voidspacedimitern: gah, dammit11:06
dimiternvoidspace, you need 1.23 - then it will work11:06
voidspacedimitern: I should have done 1.2311:06
voidspaceyep11:06
dimitern:)11:06
voidspaceheh, ah well - at least I've got maas working11:06
voidspacedimitern: took a bit of effort - it has a dependency on python-apt that isn't automatically installed11:06
voidspaceso everything was broken until I worked it out11:06
dimiternvoidspace, which one? maas?11:07
natefinchAnyone have an idea of why this worker, when started in MachineAgent.Run() would cause juju to simply not run?  https://github.com/natefinch/juju/blob/ha-to/cmd/jujud/agent/converter.go11:08
voidspacedimitern: yep, maas11:08
voidspacedammit, screwed up my git checkout and now have juju 1.22 local branch named juju-1.23.011:10
dimiternvoidspace, weird.. I haven't seen this with maas before11:10
voidspaceI guessed the tag wrong - should have remembered it wasn't released yet11:10
voidspacedimitern: maybe you had python-apt already installed?11:10
dimiternvoidspace, ah :/11:11
voidspaceit's quite common11:11
voidspaceI just have a kvm image *just* for the maas controller - so only maas dependencies installed11:11
dimiternvoidspace, I've installed what maas packages from the ppa brought over I guess11:11
perrito666natefinch: without any ouput?11:11
voidspacedimitern: me too11:11
wallyworldaxw_: was at soccer, will look soon11:13
wwitzel3that was weird11:19
perrito666wwitzel3: ?11:19
wwitzel3my bnc acted up, can't tell if what I typed was actually sending11:19
wwitzel3did you guys see my comments about using the termination work as a reference piece?11:19
perrito666nope11:20
perrito666I havent seen any comment from you11:20
wwitzel3natefinch: I ran into the same issue11:20
wwitzel3natefinch: I am currently making a barebones working using the termination worker as a reference11:20
wwitzel3natefinch: then I was going to make it watch the jobs collection11:21
wwitzel3natefinch: and just get that starting without hanging11:21
natefinchperrito666: yeah, no output, no logs at all11:21
wwitzel3natefinch: I'll let you know if that works in a second11:22
natefinchperrito666: like, /var/log/juju/ is empty11:22
natefinchwwitzel3: cool11:22
natefinchI gotta go afk for a couple hours.  Kids are up.11:22
voidspacedimitern: how long should it take for a new container to switch from "instance-id: pending" ?11:22
dimiternvoidspace, if it's the first one, a few minutes until it downloads the image11:24
voidspacedimitern: ah11:24
voidspacedimitern: ok11:24
perrito666wallyworld: if you are still around I have answered you on the review and would appreciate an answer to that11:24
wallyworldperrito666: ok, looking11:24
dimiternvoidspace, you could ssh into the host, sudo su -, then look in /var/lib/juju/containers/*/*.log and /var/lib/lxc/*11:24
voidspacedimitern: it's started :-)11:26
voidspacedimitern: and has a dns-name11:26
dimiternvoidspace, it's a great feeling when it works, isn't it? :)11:28
perrito666dimitern: only if you know why11:28
wallyworldperrito666: hmmmm, i think we might want to retain the Stopped state11:28
wallyworldfor that legacy agent-state11:29
voidspacedimitern: upgrade worked fine11:29
voidspacedimitern: and I appear to be able to deploy into the container11:29
voidspacedimitern: so the upgrade didn't break the container11:29
dimiternperrito666, :)11:29
perrito666wallyworld: works for me11:29
dimiternvoidspace, so what was your scenario pre-upgrade?11:30
wallyworldperrito666: let's do it and we'll validate the decision11:30
voidspacedimitern: I just added the container11:30
voidspacedimitern: bootstrap then add container, wait for that to complete, upgrade11:30
voidspacedimitern: I have to go!11:31
voidspacedimitern: see you in a bit11:31
dimiternvoidspace, ok, that's great - need to check with a destroyed container as well11:31
perrito666wallyworld: I believe Ill go with Unknown->Error and Terminated->Terminated11:32
dimiternvoidspace, ping me when you're back11:32
wallyworldperrito666: i don't think Unknown->Error is quite right. we know if start hook has run11:33
wallyworldso unknown maps to pending or started11:33
wallyworldalso, Terminated should ->Stopped11:33
wallyworldto keep using the legacy terminology11:33
axw_wallyworld: I'm thinking of simplifying storage provisioning a bit. I'm thinking of extending the storage.Provider interface to indicate whether or not it supports dynamic provisioning. If it does, provisioning will be done by the storage provisioner, and if it doesn't it'll be done by the machine provisioner11:52
axw_wallyworld: so then there'll be exactly one thing responsible for provisioning a volume11:52
axw_wallyworld: atm there's a race between storage provisioner and machine provisioner, and it's manifesting in the storage provisioner in my testing11:53
wallyworldaxw_: that aspect was starting to occupy my thoughts also11:53
wallyworldnot from anything concrete11:53
wallyworldbut just to eliminate unnecessary complexity11:53
axw_wallyworld: the other thing I was thinking was removing Attachment from VolumeParams and FilesystemParams11:54
wallyworldthat i hadn't been thinking about11:54
axw_wallyworld: so they're always created separately, rather than "maybe with the volume, maybe later on"11:54
wallyworldok11:55
axw_wallyworld: we'd still do both at the same time in the machine provisioner11:55
axw_so there'd be a different type for that11:55
wallyworldok, let's see how it plays out11:55
axw_I'll spike on it tonight/tomorrow, I think I can get something in that makes the storage provisioner more reliable11:56
wallyworld\o/11:57
wallyworldaxw_: i also ran into that attached vs pending bug11:59
wallyworldin this http://reviews.vapour.ws/r/1186/11:59
wallyworldadded a todo12:00
wallyworldcould you look when you get a chance, no hurry12:00
axw_wallyworld: will do12:01
wallyworldta12:01
mattywfwereade, got a moment - irc is fine12:32
fwereademattyw, sure12:32
jw4perrito666: thanks for the review - I think those issues can be dropped... thoughts?12:42
perrito666jw4: if you can say why :p I can certainly agree (but i was meaning to add them as comments not issues)12:43
axw_wallyworld: reviewed12:43
wallyworldty12:43
jw4perrito666: sure - see if my responses make sense and if not we can keep them as issues12:44
perrito666jw4: ill answer in rb so its easier to follow up12:45
jw4perrito666: cool, tx!12:46
jw4thanks perrito666 I'll update the PR with your feedback :)13:08
perrito666jw4: the ones where I said nothing i am fine with dropping13:08
jw4perrito666: cool13:08
wwitzel3natefinch: well I got past juju just out right hanging, now I at least am getting "unknow object type Converter"13:11
wwitzel3natefinch: with an error of not implemented .. but it doesn't tell me what is not implemented13:11
wwitzel3natefinch: but getting closer :)13:12
wwitzel3THere is a way to tell logging not to redact responses right?13:13
natefinchwwitzel3: dunno about redacting responses13:21
wwitzel3natefinch: ok, well I'm trying to figure out what is "not implemented"13:22
=== kadams54 is now known as kadams54-away
wwitzel3natefinch: right now I've got it starting from the machine agent with StartWorker but it is just in a restart loop with that error13:23
wwitzel3natefinch: but again, that is better than hanging completely13:23
wwitzel3natefinch: I can push what I have if you want to look13:23
natefinchwwitzel3: sure13:23
natefinchfwereade: got any time to give us a hand?  We're trying to wire up a watcher, and it's causing the whole of jujud to blow up for some reason.13:24
wwitzel3natefinch: ok, pushed13:25
wwitzel3natefinch: well it isn't blowing up anymore, not it is just in an isolated restart loop :)13:26
wwitzel3improvement!13:26
natefinchwwitzel3: repeated smaller explosions better than one big one?  I guess so :)13:27
alexisbperrito666, you available for cloudbase call?13:30
fwereadenatefinch, go on13:31
fwereadenatefinch, fist guess is that it's returning an error that is somehow triggering the isFatal check in its runner or something?13:31
natefinchfwereade: could be, I'm just surprised that it would kill jujud before it could even write a log file13:32
natefinchfwereade: https://github.com/natefinch/juju/blob/ha-to/cmd/jujud/agent/converter.go13:32
fwereadenatefinch, that ErrTerminateAgent looks to me like the problem13:33
natefinchfwereade: this is a worker for machine agent for when we convert a normal server to a state server13:33
fwereadenatefinch, ErrTerminateAgent means "ok clean yourself up and never run again"13:34
fwereadenatefinch, returning just-some-error will exit nonzero and put ourselves in the hands of the init system, which should then bounce us13:34
=== kadams54-away is now known as kadams54
fwereadenatefinch, so (assuming you do want to restart jujud, which seems sane) create some error that triggers isFatal, but don't use ErrTerminateAgent13:35
natefinchahh ok13:35
wwitzel3oh well that's my fault13:36
wwitzel3reading the code it sure does look like ErrTerminateAgent is handled like the other IsFatal errors13:36
wwitzel3right along side the upgrade error13:37
fwereadewwitzel3, and it is, at the runner level -- but cmd/jujud/agent/machine.go:36013:37
fwereade    case worker.ErrTerminateAgent:13:38
fwereade        err = a.uninstallAgent(agentConfig)13:38
wwitzel3ahh13:38
wwitzel3yeah, we don't want that13:38
fwereadenatefinch, wwitzel3: and FWIW it's my fault for not fixing ErrTerminateAgent when it became clear it was a problem waiting to happen13:38
fwereadenatefinch, wwitzel3: it's a Very Bad Thing that we return it from the Uniter, for example13:40
fwereadenatefinch, wwitzel3: it's not the uniter's job to decide whether the whole process should die13:40
fwereadenatefinch, wwitzel3: it's the uniter's job to inform whatever started it that the unit doesn't need/want to exist any more13:40
fwereadenatefinch, wwitzel3: and that code can then itself make a sober judgement as to whether uninstalling itself is really justified13:41
fwereadenatefinch, wwitzel3: and, if so, itself return ErrTerminateAgent to the top level directly13:41
fwereadenatefinch, wwitzel3: sane?13:41
wwitzel3fwereade: I'm working on a bit of a different problem than natefinch .. I'm refactoring the worker to it properly uses api facade instead of calling state directly as in the proof of concept.13:43
wwitzel3fwereade: but I'm running in to a restart loop with the new converter work, getting back not implemented, but all the params and responses are redacted, so it is a bit hard to tell what's happening13:44
wwitzel3fwereade: peppering logging bits throughout now :)13:45
fwereadewwitzel3, ha13:50
fwereadewwitzel3, that's a good thing in general13:50
wwitzel3fwereade: yeah, well we wanted to get a proof of concept working first, make sure we were on the right path13:52
fwereadewwitzel3, yeah, indeed13:52
fwereadewwitzel3, I don't have any immediate insight there, though, I'm afraid13:52
wwitzel3fwereade: think I found the problem13:53
wwitzel3fwereade: it helps if you declare the facadeVersion in api/facadeversions.go when using a facade13:53
wwitzel3:P13:53
fwereadewwitzel3, haha13:54
wwitzel3I could of sworn I did that13:54
=== kadams54 is now known as kadams54-away
mupBug #1420049 changed: ppc64el - jujud: Syntax error: word unexpected (expecting ")") <deploy> <openstack> <regression> <uosci> <juju-core:Fix Released by axwalk> <juju-core 1.22:Fix Released by axwalk> <https://launchpad.net/bugs/1420049>13:55
mupBug #1428692 changed: cannot boostrap vivid: Operation failed: No such file or directory <ci> <local-provider> <regression> <vivid> <juju-core:Fix Released by ericsnowcurrently> <https://launchpad.net/bugs/1428692>13:55
perrito666natefinch: ?14:09
fwereadeby the way, can I trouble someone for another review of http://reviews.vapour.ws/r/1165/ please?14:10
fwereadeideally someone who's worked in the uniter, but if not I can answer questions14:11
fwereadewwitzel3, perhaps :) ^^14:12
dimiternfwereade, I'll have a look14:14
fwereadedimitern, tyvm14:14
* dimitern learned a new word today - "impending" :)14:15
fwereadedimitern, that word goes very well with "doom" :)14:17
wwitzel3haha14:17
dimiternfwereade, I bet it does :D14:17
dimiternfwereade, in the comment starting at line 56 in modes.go, you mention we shouldn't try to accept leadership if we already did, but the code below doesn't seem to check for that14:22
fwereadedimitern, canAcceptLeader := !opState.Leader14:23
fwereadedimitern, the ordering of the statements in the comment is misleading though14:23
dimiternfwereade, also the check for Kind != Continue looks like we won't try if we're in any hook currently, not just pending hook14:23
fwereadedimitern, hence "eg (= for example) pending hook" not "ie (= that is specifically) pending hook"14:24
dimiternfwereade, right, I'll leave a comment to rephrase the comment a bit to match the impending code below it :)14:24
fwereadedimitern, haha, thanks14:24
dimiternfwereade, ok, fair enough14:24
fwereadedimitern, I should rephrase that too though14:25
fwereadedimitern, "if we're busy doing anything else at all, don't try to accept leadership"14:25
dimiternfwereade, yeah, that'll be much better, cheers14:25
mupBug #1433116 was opened: 386 compilation error: dblogpruner/worker.go:32: constant 4294967296 overflows int <i386> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1433116>14:38
sinzuidimitern, natefinch We need someone to fix this critical ^. CI aborted testing because it cannot build all the packages. I am going to remove 386 from building to allow other tests to run14:39
dimiternsinzui, natefinch, I'll have a look, but unfortunately won't be able to help much about it today14:41
jw4sinzui: can you remind me how to run the tests using the gccgo compiler again?14:47
dimiternjw4, add -compile gccgo14:48
jw4dimitern: ta14:48
dimiternjw4, sorry, -compiler gccgo14:48
jw4kk14:48
mupBug #1433116 changed: 386 compilation error: dblogpruner/worker.go:32: constant 4294967296 overflows int <i386> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1433116>14:50
jw4fwiw, go 1.4 seems incompatible with gccgo14:53
=== urulama is now known as urulama|afk
natefinchjw4: yeah, I ran into that.... brought it up as a problem on golang-dev, and they weren't really interested in fixing it14:56
jw4natefinch: lol, yeah, just noticed you were the reporter :)14:56
natefinchjw4: heh14:56
natefinchjw4: you can install go 1.2 side by side with 1.4 and use 1.2 as needed with gccgo... it's a little annoying, but not the end of the world14:58
jw4natefinch: yeah - I just switched to my laptop with 1.2.1 installed14:58
dimiternperrito666, natefinch, trivial review http://reviews.vapour.ws/r/1187/ - please take a look14:59
mupBug #1433116 was opened: 386 compilation error: dblogpruner/worker.go:32: constant 4294967296 overflows int <i386> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1433116>15:02
natefinchdimitern: ship it!15:02
dimiternnatefinch, cheers!15:02
natefinchalso: good god gomaasAPI is a horrible cluster of a go package15:02
dimiternit really is15:03
dimiternit's written like a c library15:03
natefinchit's written like they just translated the REST API directly into Go calls, so you have to understand the REST API in order to use the package, rather than making the package abstract away the REST API.15:10
dimiternnatefinch, another review - hopefully fixing bug 1433116 - http://reviews.vapour.ws/r/1188/15:19
mupBug #1433116: 386 compilation error: dblogpruner/worker.go:32: constant 4294967296 overflows int <i386> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1433116>15:19
perrito666dimitern: add a comment there, looks like one of those things one would remove upon first sight thinking is a noob error15:21
dimiternperrito666, good point, will do15:22
dimiternperrito666, updated15:24
dimiternperrito666, and I have another one for you - http://reviews.vapour.ws/r/1189/ :) - last one for today I promise15:29
perrito666dimitern: looking15:30
dimiternperrito666, thanks!15:31
perrito666dimitern: btw, int in i386 is int32?15:35
=== kadams54 is now known as kadams54-away
perrito666somehow now I am not sure that your fix fixes the fix as you intend it to be fixed15:37
dimiternperrito666, it is15:37
dimiternperrito666, you mean because it will be negative perhaps?15:38
perrito666dimitern: https://play.golang.org/p/2LEwN2pZ9X15:38
perrito666dimitern: it blows15:39
perrito666at least there15:39
perrito666i wold expect the value to become math.MaxInt3215:39
perrito666actually I dont see a good reason for that value not being uint32 all the way (or in any case, explicit int size)15:40
natefinchdimitern, perrito666 : is there a reason it needs to be typed?15:41
dimiternperrito666, good point - we could constrain it to math.MaxInt32 for i386 or use the 4GB default otherwise15:41
=== kadams54-away is now known as kadams54
natefinch+1 for using a math.Maxsomething15:42
dimiternnatefinch, not that I can think of15:42
perrito666natefinch: yes, I believe its a good practice when the code is going to run in different int size archs to be explicit15:42
perrito666or you are just moving the overflow to the next guy15:42
dimiternperrito666, natefinch, ok, I'll tweak it a bit by initializing the default depending on the arch15:43
natefinchperrito666: constants never overflow, though15:43
perrito666there is explicit information in the type "this number needs a box this big to fit"15:43
perrito666natefinch: so says the doc15:44
perrito666natefinch: you cannot guarantee the use of that constant is going to be given15:45
* perrito666 loves typing things15:45
voidspacedimitern: back15:46
voidspacedimitern: took longer than expected, sorry15:46
voidspacedimitern: I'll have to work tonight15:46
voidspacemy new laptop arrived15:46
voidspacehave to set that up later :-)15:46
perrito666voidspace: congrats, what did you get?15:46
voidspaceperrito666: Dell XPS 1515:48
voidspaceperrito666: it's basically as powerful as my desktop15:48
perrito666nice15:48
voidspacequad-core i7, 16gb ram15:48
dimiternvoidspace, hey, no problem15:48
dimiternvoidspace, I've discovered a nasty bug in our address allocation for maas - see http://reviews.vapour.ws/r/1189/15:49
voidspacedimitern: ah, ok15:49
dimiternvoidspace, can you approve that btw?15:49
voidspacedimitern: was it our bug then, and not theres?15:49
voidspacedimitern: will look15:49
voidspacedimitern: hah, ouch15:49
dimiternvoidspace, yeah, it was - but not because their API docs where clear enough to follow :)15:49
voidspacedimitern: LGTM15:50
dimiternvoidspace, thanks, setting to land15:50
=== kadams54 is now known as kadams54-away
voidspacedimitern: ah, requested_address is actually the param name for claimstickyaddress op15:52
dimiternvoidspace, and for ipaddresses op=reserve as well apparently15:52
voidspacedimitern: ah, I see15:52
voidspaceit's that way round15:52
voidspacedimitern: ip is for release15:52
jw4OCR PTAL http://reviews.vapour.ws/r/1181 (got a round of reviews from perrito666 already, just need graduated reviewer approval)15:53
dimiternjw4, will look shortly15:53
dimiternvoidspace, yeah :)15:53
jw4tx dimitern15:53
dimiternperrito666, natefinch, voidspace - this should be a better fix for bug 1433116 I guess - http://reviews.vapour.ws/r/1188/15:56
mupBug #1433116: 386 compilation error: dblogpruner/worker.go:32: constant 4294967296 overflows int <i386> <test-failure> <juju-core:In Progress by dimitern> <https://launchpad.net/bugs/1433116>15:56
dimiternnatefinch, perrito666, voidspace, no sorry, that's not good enough still - updated http://reviews.vapour.ws/r/1188/ again16:00
natefinchdimitern: I wonder how much we care about the one extra byte on amd64 :/16:02
mupBug #1433161 was opened: feature request: support virtual services <cloud-installer> <juju-core:New> <https://launchpad.net/bugs/1433161>16:02
dimiternnatefinch, you mean 2 bytes I guess?16:02
dimiternif not actually four16:03
dimiternnatefinch, re int vs int32?16:03
natefinchdimitern: nevermind, I was thinking MaxUint32... actually it's a factor of 216:07
dimiternnatefinch, ah, well 4GB limit for logs seems too much to me even on x86_6416:08
natefinch#143311616:08
mupBug #1433116: 386 compilation error: dblogpruner/worker.go:32: constant 4294967296 overflows int <i386> <test-failure> <juju-core:In Progress by dimitern> <https://launchpad.net/bugs/1433116>16:08
voidspacedimitern: LGTM16:09
dimiternvoidspace, thanks!16:10
natefinchdimitern: is there a reason we couldn't change whatever is using int to int64?  I mean...  seems like what we intend, anyway16:10
dimiternnatefinch, that's not for me to say - I intend to fix the build failure on i386, not to change the assumptions16:11
natefinchdimitern: the assumption is that we wqanted 4GB16:11
natefinchdimitern: the architecture problem just shows why using "int" was a bad idea16:11
natefinchdimitern: having the log half as big because you're on a different architecture does not seem like a design decision anyone would intentionally make16:12
perrito666natefinch: we are punishing users for actually still use i38616:12
natefinchperrito666: heh16:12
voidspaceperrito666: yep, that sounds reasonable16:12
natefinchdimitern: seriously, though.  The fix to just change LogPruneParams to int64 seems way more simple and obvious16:13
voidspacedimitern: you wanted me to repeat the upgrade test with a destroyed container16:13
voidspacedimitern: and then see if the IPAddress is marked as Dead?16:13
perrito666voidspace: off course it is, no savvy user should use archs older than the ony my mom uses, and she has x86_6416:14
dimiternnatefinch, ok, can I ask you to comment on the proposal then and I won't land it as is, will leave it for thumper or menn0 to decide16:14
dimiternvoidspace, yes please16:14
voidspacedimitern: I'll have to use direct mongo access to see I guess...16:15
voidspacedimitern: unless you have a better idea16:15
dimiternvoidspace, not really16:15
dimiternvoidspace, you could just add more logging :)16:15
voidspacedimitern: hah, well if we're going to trust *code* to tell us16:15
voidspacedimitern: we could just trust the test16:15
voidspacedimitern: but that's not a bad idea16:16
dimiternvoidspace, I forgot to mention that earlier actually - it's good to have logs during upgrade steps lest it goes wrong16:16
voidspacedimitern: I'll create a new branch and add logging16:16
dimiternnatefinch, thanks!16:16
dimiternvoidspace, sounds good16:16
natefinchdimitern: welcome, sorry to be a pain in the butt :)16:16
dimiternnatefinch, not at all - I prefer a better solution than a quick and dirty fix :)16:22
dimiternjw4, reviewed16:25
jw4dimitern: gratzie16:25
perrito666ok ill be OoO for a moment, be back later16:26
jw4dimitern: I think the first two issues can be dropped?  I'll work on the third.16:30
jw4dimitern: and yes, I'm also waiting for a sanity check from fwereade16:30
dimiternjw4, let me have another look16:31
jw4dimitern: ta16:31
dimiternjw4, yeah, sounds good re the first two issues16:31
jw4dimitern: cool16:31
dimiternjw4, sorry, so do you intend to keep the second assert there?16:32
jw4dimitern: it seems reasonable to me - it's asserting a subtly different thing than the first assert16:33
dimiternjw4, if you need to verify the cause as well and there's a specific error you can check for, better use jc.Satisfies16:33
jw4dimitern: oh, interesting16:33
jw4dimitern: since I only touched this because wording changed elsewhere, I'm not keen to change the tests too much.16:33
jw4dimitern: but I'm willing if you feel strongly about it16:34
dimiternjw4, not that strong :)16:34
jw4dimitern: k16:34
dimiternvoidspace, I guess you're afk now16:35
voidspacedimitern: no, here16:37
dimiternvoidspace, ah, ok :)16:37
frankbanocr could you please take a look at https://github.com/juju/charm/pull/94 when you have time? thanks!16:48
voidspacehmmm... so the bad news is that maas seems to have crapped out pretty badly and looks like I need to reinstall17:32
voidspacethe good news is that I've started the ubuntu install on the xps 15...17:32
voidspacehah, although looks like I need a mouse as the trackpad isn't working17:32
voidspaceor maybe I can proceed without it17:33
mattywvoidspace, any idea if dimitern has gone for good?17:34
mattyw(for good meaning - today)17:34
voidspacescreen is lovely17:34
voidspacemattyw: yes, gone for the day17:34
mattywvoidspace, ok thanks - screen as in < tmux?17:35
mattywperrito666, you available to do a review for me?17:35
perrito666mattyw: sure17:35
perrito666mattyw: shoot17:35
mattywperrito666, http://reviews.vapour.ws/r/1005/17:35
mattywperrito666, thanks very much17:35
mattywperrito666, it has an LGTM but I made some largeish changes since17:36
perrito666mattyw: it has a ship it17:36
perrito666ah ok17:36
* perrito666 wonders how mattyw did large changes in such a short patch17:37
mattywperrito666, I try to keep my patches short and focused17:37
mattywperrito666, it was largish in that it was > 60% of the patch changed17:37
perrito666so to make a change large you add a lot and then remove it? :p17:37
voidspacemattyw: screen as in - the physical screen on my new laptop (Dell XPS 15 - currently installing ubuntu on it)17:38
mattywvoidspace, oh right, I saw you twittering about that I think17:38
mattywvoidspace, be interested to see how you get on, I like dells - and I think I'm due a new one at the end of the year17:38
ericsnow_voidspace, mattyw: natefinch and I have that same laptop, I believe17:40
ericsnow_voidspace, mattyw: and axw too17:41
mattywericsnow_, is that the one you had in brussels?17:41
ericsnow_mattyw: yep17:41
mattywericsnow_, ah yes - on the laptop with the insane resolution :)17:42
ericsnow_mattyw: to which I forgot the power cord and had to beg hits off the other two guys :)17:42
perrito666mattyw: I have some concerns I reviewed it17:49
mattywperrito666, ok thanks17:50
mattywperrito666, yeah - that type thing is the thing that's keeping me from landing this branch - everyone has a different idea for how it should look - and it started off not being part of my change :)17:51
mattywperrito666, good shout about the maps - I'd forgotten about that17:51
perrito666mattyw: in my pov this opens the possibility of garbage strings comming down the line, the speciffic type sends a message of what you are expecting to come down the line17:52
perrito666mattyw: that is the justification for my objection , in case it helps17:52
mattywperrito666, that's right, but so does type MeterStatusCode string17:52
mattywperrito666, I don't disagree with you at all17:53
mattywperrito666, I'm just trying to find a way of fixing it17:53
perrito666mattyw: well a function expecting to receive (or return) a string is much less useful in terms of information than one expecting MeterStatusCode17:53
perrito666you are making a statement in terms of the content of that string :)17:54
perrito666natefinch: you can break the tie?17:54
perrito666anyway, i need to get afk for a moment, bbl17:54
mattywperrito666, no problem17:54
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
natefinchperrito666:  reading scrollback18:07
=== anthonyf is now known as Guest85523
=== kadams54 is now known as kadams54-away
natefinchwwitzel3: any luck?18:28
mupBug #1433254 was opened: manual provider on trusty/precise syntax error near unexpected token `then' <manual-provider> <ppc64el> <systemd> <juju-core:In Progress by ericsnowcurrently> <juju-core 1.23:In Progress by ericsnowcurrently> <https://launchpad.net/bugs/1433254>18:32
marcoceppiI've got a general golang question18:47
marcoceppiI want to get the http status code of a URL, I'm guessing this is the http library but I'm not sure how to check response code18:48
jw4marcoceppi: golang.org/pkg/net/http/#Get18:51
jw4when you issue the Get on the url you get back a *Response18:52
jw4which has Status among other things18:52
marcoceppijw4: awesome, thanks! I'll give that a /go/18:52
marcoceppibwhahah18:52
jw4lol18:52
natefinchyou can tell a newbie gopher by all the bad jokes19:00
=== kadams54-away is now known as kadams54
jw4natefinch: lq - marcoceppi is a ninja so I'm going to lq (laugh quietly) instead of lol19:01
=== kadams54 is now known as kadams54-away
mupBug #1433244 was opened: MAAS should handle RAM upgrades without decommissioning / recommissioning existing nodes <openstack> <uosci> <juju-core:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1433244>19:42
mupBug #1433244 changed: MAAS should handle RAM upgrades without decommissioning / recommissioning existing nodes <openstack> <uosci> <juju-core:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1433244>19:48
ericsnow_OCR: PTAL http://reviews.vapour.ws/r/1190/19:57
ericsnow_perrito666: ^^^19:58
ericsnow_good morning, thumper20:00
thumpero/20:00
ericsnow_thumper: when you get settled, I have a quick question for you20:00
thumperbetter be quick20:00
thumperstand up is now20:00
ericsnow_thumper: I can wait20:02
mupBug #1433244 was opened: MAAS should handle RAM upgrades without decommissioning / recommissioning existing nodes <openstack> <uosci> <juju-core:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1433244>20:03
=== ericsnow_ is now known as ericsnow
ericsnowmenn0, perrito666: PTAL http://reviews.vapour.ws/r/1190/20:47
menn0ericsnow: i'll take a look after i've finished with the review i'm currently looking at20:49
ericsnowmenn0: thanks!20:49
perrito666ericsnow: I added one comment to the bash stuff but my brain is jello I cannot in good concience review embedded bash and produce useful output20:57
=== kadams54-away is now known as kadams54
ericsnowperrito666: np :)20:57
thumpercmars: chat today?21:01
rick_h_thumper: he's out this week21:03
thumperrick_h_: cheers, I guess that is a no then :)21:03
thumperrick_h_: my daughter is wanting me to help with a school thing on Friday21:04
thumperrick_h_: any chance we can reschedule our meeting?21:04
rick_h_thumper: we can try tomorrow but have to ask urulama|afk as it's late late his time21:05
thumperrick_h_: ok21:05
thumperrick_h_: alternatively I could try to make it earlier21:05
thumperrick_h_: say... if I got up at 6am for the call21:05
thumperrick_h_: it would make it earlier for urulama|afk and you21:06
thumperas long as it doesn't clash with other calls you may have21:06
thumperrick_h_: so... 3 or 3.5 hours earier than currently specified21:06
rick_h_thumper: well I'm booked honestly. You can see if there's a slot that works for you but my wed/thurs are call days21:06
thumperah21:06
* thumper tries to see rick_h_'s calendar21:06
rick_h_thumper: if you can find a slot happy to move it around21:07
thumperrick_h_: I see a slot there...21:07
* thumper calculates timezones21:07
thumperrick_h_: are you EDT?21:07
rick_h_thumper: yep21:08
rick_h_feel free to take it then21:08
thumper1pm? your time21:08
rick_h_thumper: wfm21:08
rick_h_and urulama|afk looks open21:08
thumperI think that would be 6 or 7pm for ubuntulog221:08
rick_h_so happy to move it earlier then21:08
rick_h_lol21:08
thumperok, lets do it for this week21:08
* thumper moves21:08
* thumper sighs21:08
thumperperhaps ubuntulog2 doesn't want to come21:08
thumperunless it can automatically minute our meeting21:09
thumperrick_h_: moved21:10
rick_h_thumper: yay, I can't wait :)21:10
thumperheh21:20
menn0ericsnow: done. lots of problems with the bash code unfortunately.21:38
ericsnowmenn0: k, thanks21:38
=== kadams54 is now known as kadams54-away
mupBug #1433336 was opened: juju deploy tags are persistent accross juju deploys <cts> <juju-core:New> <https://launchpad.net/bugs/1433336>21:54
ericsnowmenn0: are you sure about `[[ ! $? ]]` ?21:55
ericsnowmenn0: I'm pretty sure you're right in the case of a single bracket, but the double bracket works21:56
menn0ericsnow: yep. I just included an example in reply to your comment.21:56
ericsnowmenn0: weird. your example works for me22:08
ericsnowmenn0: ah, it's the ! that is messing things up22:09
thumperericsnow: thing I found with bash is always use -ne or -eq22:09
thumpernever test unaddorned22:10
thumperalso, I always quote args, "$1"22:10
thumpernever just $122:10
ericsnowthumper: yep22:10
thumperin [[ ]] at least22:10
ericsnowbash is a minefield22:10
thumperalso... I hate bash scripts22:10
thumpertrue that22:10
ericsnowmenn0's got my back :)22:10
alexisbwallyworld, ping22:11
wallyworldalexisb: hey22:11
alexisbheya22:11
alexisbI just sent you a mail22:11
wallyworldok, looking22:12
alexisbthe error looks familiar22:12
alexisbdoes it to you as well?22:12
menn0ericsnow: strange that it works differently for you22:12
menn0ericsnow: could be a bash version thing or a shopt thing22:13
menn0ericsnow: i'd still play it safe and use the more conventional check22:13
ericsnowmenn0: no, it was only without ! that it worked the way I expected22:13
ericsnowmenn0: agreed22:13
wallyworldalexisb: the series string is missing from the binary version22:14
wallyworldwhat are they running juju on?22:14
alexisba maas setup on a VM22:14
alexisband I cant repo in on my env22:15
ericsnowmenn0: all fixed22:15
wallyworldalexisb:  no, not surprised, it's a setup issue of some sort, but i'll need to dig a little to find root cause22:15
alexisbI dont want to bother youm but can you give me some pointers on what to look at?  It is on a partners test setup in class and it is bugging me that I cant figure out what he has done different22:16
menn0ericsnow: looking again22:16
ericsnowmenn0: ta22:16
wallyworldalexisb: no problem at all. can we run sync-tools with --debug22:17
wallyworldso we can see where it's looking for the tools tarballs22:18
wallyworldit could be a badly named file22:18
thumperericsnow, menn0: what is the first line of the discovour script?22:19
thumperby default, it runs through /bin/sh right?22:19
thumperwhich is dash on some servers22:19
thumpernot bash22:19
menn0#!/usr/bin/env bash22:19
thumperjust a query, but I do wonder if bash is really bash on some servers22:20
thumperit may not be22:20
menn0it would be pretty awful if it wasn't22:20
thumperyes22:20
thumperperhaps it was changing sh for dash not bash22:20
thumperthat I recall22:20
ericsnowthumper: that sounds plausible22:21
* menn0 nods22:21
menn0what you get with /bin/sh is a little "flexible"22:21
alexisbwallyworld, getting logs for you22:21
menn0but is supposed to be posix compatible sh22:21
* thumper sighs22:21
thumperapiserver tests take over two minutes22:22
wallyworldalexisb: ty, and then pastebin please22:22
thumperI wish this was faster22:22
menn0directly asking for bash should be safe enough though22:22
alexisbo crap wallyworld I just emailed22:23
wallyworldalexisb: never minds, email works :-)22:25
* thumper swears at the tests22:26
ericsnowdavecheney: could you take another look at http://reviews.vapour.ws/r/1172/?22:29
wallyworldalexisb: just for kicks, can you please try "sudo apt-get install distro-info-data" \22:29
wallyworldon the machine running ysnc-tools22:29
alexisbyep one sec22:30
wallyworldi suspect the machine doesn't know about vivid22:30
alexisbwallyworld, already installed22:32
alexisbdidn't make a difference22:32
menn0ericsnow: done. just one question but ship it otherwise.22:32
ericsnowmenn0: thanks22:32
wallyworldalexisb: ok, i'll dig into the code and get back to you22:32
wallyworldalexisb: also, bug 1433336 - it's working as designed, constraints used at bootstrap time become default constraints from then on22:33
mupBug #1433336: juju deploy tags are persistent accross juju deploys <cts> <juju-core:New> <https://launchpad.net/bugs/1433336>22:33
alexisbwallyworld, thanks, not urgent, just bugging us :)22:34
wallyworldso if you want to bootstrap to a machine using tags, you'll need to set the constraints again afterwards22:34
alexisbwallyworld, can you add a note to bug 14333622:34
mupBug #143336: __bobo_traverse__ and ftp/webdav <bug> <zope> <Zope 2:Invalid> <https://launchpad.net/bugs/143336>22:34
wallyworldyep22:34
alexisbthanks22:34
wallyworldi'l find this current issue first22:34
alexisbwallyworld, I know you guys are busy, so really not urgent stuff, but we got lots of feedback from classmates on juju stuff (from core to gui) so I was trying to get info back to the team22:35
wallyworldalexisb: that sort of feedback is very much desired22:35
wallyworldwas just giving you a heads up on the reason for the bug22:36
wallyworldi agree the usability kinda sucks in that case22:36
thumperoh for the love of <insert deity>22:40
* thumper headdesks22:40
wallyworldalexisb: i think that the maas machine needs to have that distro info package installed as well22:41
wallyworldalexisb: i suspect the standard maas images don't have it22:41
alexisbwallyworld, I installed distro info on both the maas machine and the bootstrapped machine that has the maas image, and it makes no difference.22:48
=== kadams54-away is now known as kadams54
wallyworldalexisb: trouble is, juju will now have cached it's knowledge of the distro info, so you will need to bounce the agent22:49
wallyworldsudo service juju-agent restart   <-- i can't recall OTTOMH what the exact service name is22:50
wallyworldlook in /etc/init22:50
menn0ericsnow: I just added one more comment. Summary: you should use utils.ShQuote instead of %q or "%s"23:05
wallyworldalexisb: how'd you get on? ping if you're still stuck23:07
=== kadams54 is now known as kadams54-away
alexisbstill not working23:16
alexisbbut they are going to kick us out soon23:16
alexisbwallyworld, I will try to repo tomorrow23:16
wallyworldalexisb: ok, let me know how you go etc23:17
ericsnowmenn0: would you mind also taking a look at http://reviews.vapour.ws/r/1172/23:26
wallyworldthumper: perrito666 says you owe him an email?23:46
thumperyeah...23:46
* thumper has been distracted23:46
thumperohh... shiney23:47
menn0ericsnow: will do. i just have to take care of a few other things first.23:47
ericsnowmenn0: no worries :)23:47
=== kadams54-away is now known as kadams54

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