menn0perrito666: review done. just some small suggestions. wallyworld should probably take a look too since he's worked on status recently.00:00
ericsnowwallyworld: I've gotta run; could you shepherd those merges?00:04
ericsnow(already kicked off for 1.24 and master)00:04
=== ericsnow is now known as ericsnow_afk
perrito666tx menn0 and waigani00:08
perrito666wallyworld: was a thank you, but your connection problems drive my irc client mad00:08
wallyworldme too :-(00:08
wallyworldit just appears to be irc00:08
wallyworldcan still refresh browser etc ok when irc disconnects00:09
perrito666wallyworld: it is your client acting on too much lag00:09
perrito666your lost connection thresold is too small00:09
wallyworldi'l check client config00:09
perrito666wallyworld: in the mean time, could you clarify your first comment?00:10
wallyworlddefer the legacy status calculation until after agent and workload status are set in the block below00:11
wallyworldthen the special logic in the new method probably is not required00:11
wallyworldjust call translate directly with the agent and workload status values00:11
perrito666duh, ok makes sense and then if the result is error I set workload status to error, did I get it right?00:12
perrito666that function should have been deleted I fisrt tried a more complex solution, because I like to complicate my life00:12
waiganiwallyworld: thanks for review. I'm new to control-bucket. I was just taking the error on face value - It looked like a string that needed to be zero valued to "" instead of nil. Any tips on where to look to grok control-bucket and what it's default value should be?00:51
perrito666waigani: 1.18?00:51
waiganiperrito666: okay00:52
=== kadams54 is now known as kadams54-away
wallyworldaxw: revision 6 of http://reviews.vapour.ws/r/1481/ has the machine manager facade02:08
wallyworldaxw: there's currently work being done to tweak the control bucket logic for ec2, but with tools and charms in storage, we don't need control buckets for new environments anymore. i'm wondering if we shouldn't just delete control bucket creation02:14
axwwallyworld: yes we do, we still need it for the state server list02:14
wallyworldah, yeah, forgot about that02:15
natefinchsinzui: you around?02:29
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
mupBug #1449822 was opened: storage: storage-detached should be storage-detaching <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1449822>03:01
mupBug #1449822 changed: storage: storage-detached should be storage-detaching <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1449822>03:13
mupBug #1449822 was opened: storage: storage-detached should be storage-detaching <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1449822>03:19
axwwallyworld: have you tested your latest change to ff removal against an older juju API server?03:20
wallyworldaxw: yes03:20
axwwallyworld: cool. I thought getting the API would error, rather than returning something with a 0 "best API version"03:21
axwglad to be wrong03:21
=== kadams54 is now known as kadams54-away
menn0wallyworld: looking at the blockdevices upgrade PR now04:31
menn0wallyworld: ship it with some fixes04:47
=== urulama__ is now known as urulama
TheMuemorning o/07:32
=== liam_ is now known as Guest4187
voidspacedooferlad: ping08:58
dooferladvoidspace: hi08:59
voidspacedooferlad: hi, you better today?08:59
TheMueah, he's back. feeling better?08:59
voidspacedooferlad: I assume the answer is yes as you're here :-)08:59
dooferladvoidspace: mostly :-|08:59
dooferladvoidspace, TheMue: hangout time!09:00
Bardhi|2hello i am trying to deploy some services with juju but it gets stucked on allocating units and services are not deployed. i just started using juju and i am not an expert in using it and i dont know very well how it all works but i need this service up and running as soon as possible. if someone could help me i would appreciate it. thank you09:11
axwwallyworld: should cinder be going into 1.24?09:25
axw(since it's not in tree atm)09:26
axw<axw> wallyworld: should cinder be going into 1.24?09:27
axw<axw> (since it's not in tree atm)09:27
wallyworldaxw: yes, we do need it09:28
axwwallyworld: ok, will look at getting that ready for merge next09:28
wallyworldaxw: excellent, ty09:28
perrito666wallyworld: got it, fixing that last bit now09:32
wallyworldperrito666: ty09:32
perrito666a night's sleep does wonders09:33
perrito666s/a night/6 hs/09:33
jamrogpeppe: so ultimately, I feel like if we are "crossing the streams" then we have our layering and abstractions a bit wrong. Like I don't see why API Parameters would be defined in terms of model objects (params depending on charms)12:24
jamhowever, I do feel like your proposal is better than what we have12:24
rogpeppejam: i think that consideration is largely orthogonal to the decisions we're making here12:26
jamrogpeppe: it would let you decouple "params" from "charms" which would let you remove some of the crossing lines12:26
rogpeppejam: even if params didn't depend on the charm package, we'd still need to solve the cyclic issue (params has never been the problem here)12:27
perrito666mgz: morning, ping?12:33
* perrito666 would give his kingdom for more upload speed12:35
rogpeppequick question: is relation-broken the only relation hook for which $JUJU_REMOTE_UNIT is not guaranteed to be set?12:36
rogpeppefwereade: ^12:36
mgzperrito666: yo12:39
perrito666mgz: do you know if this happens going from any contiguous a to b from 1.22 on? https://bugs.launchpad.net/juju-core/+bug/144785312:44
mupBug #1447853: Local charms are not added to storage on upgrade to 1.22.x <charms> <regression> <storage> <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:Triaged by hduran-8> <https://launchpad.net/bugs/1447853>12:44
mgzperrito666: it won't happen if you bootstrapped on 1.22 because your charms will go in mongo straight off12:45
mgzperrito666: it will be an issue if you started on 1.21 or earlier regardless of how you're trying to upgrade12:46
perrito666ah ok, then retrying with 1.2112:46
mupBug #1441811 changed: juju-1.23beta3 breaks glance <-> mysql relation when glance is hosted in a container <charms> <network> <oil> <regression> <juju-core:Invalid by dooferlad> <juju-core 1.23:Fix Released by dooferlad> <https://launchpad.net/bugs/1441811>13:11
jamwallyworld:  or axw: I'm looking at https://bugs.launchpad.net/juju-core/+bug/1410876 and it seems to be trying to download a root.tar.gz from a Juju API server.13:11
mupBug #1410876: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy  snapshot %s - failed to allocate a pty; Insufficent privileges to control  juju-trusty-lxc-template <lxc> <oil> <stakeholder-critical> <trusty> <juju-core:Triaged> <juju-core13:11
mup1.24:Triaged> <https://launchpad.net/bugs/1410876>13:11
wallyworldjam: that looks like a missing cloud images package13:12
wallyworldlet me check the name13:12
jamwallyworld: 500 Internal Server Error is not a good thing to be getting.13:12
jamthough they also couldn't include the all-machines.log because they were trying to "cat" as an unpriviledged user.13:12
wallyworldjam: cloud-image-utils needs to be installed or else the util to determine the lxc file name is missing13:12
wallyworldjam: if they have os-updates false, then juju has a bug it wont install needed packages13:13
wallyworldthat bug is being fixed for 1.2413:13
jamwallyworld: what file are you looking at? I'm looking at "juju_status.yaml" and trying to parse through the agent-state-info error message.13:13
wallyworldjam: i just happen to know/guess the issue13:13
jamwallyworld: so regardless, do we give a better error than 500 ISE if you try to download a cloud image we don't have?13:14
wallyworldif it tries to download just root.tar.gz and not a full lxc image file name, the util is missing13:14
jamwallyworld: its a full name13:14
wallyworldoh i see13:14
jamthat's just a lot to write :)13:14
wallyworldin that case, ignore what i said above13:14
jamwallyworld: but that looks like it is expecting the Juju API server to have the cloud images, right?13:15
jamIs that the changes you made with GridFS storage?13:15
wallyworldjam: the state server is a proxy - if it doesn't have the iages it fetches from cloudimages.ubuntu.com and caches13:15
jamconsole.txt claims it is running juju-1.22-beta2-trusty-amd64.tgz13:15
jamwallyworld: k, well its giving 500 ISE instead :)13:16
wallyworldthe images are cached in gridfs yes13:16
wallyworldthe logs would be useful13:16
jamwallyworld: and we don't have all-machines.log or machine-0.log to know if we're logging a real error internally. (like not being able to access cloud-images, or somesuch.)13:16
jamwallyworld: they tried, but those files are: cat: /var/log/juju/all-machines.log: Permission denied13:17
wallyworldsudo ?13:17
wallyworldfor local provider you need sudo for most things13:17
jamwallyworld: + juju ssh -e maas 0 'cat /var/log/juju/all-machines.log'13:17
wallyworldoh maas13:17
jamIs the "-e maas" to blame ?13:17
wallyworlddon't think so, but is maas is current env, could try leaving it off13:18
wallyworldjuju ssh i think supports -e13:18
wallyworldjam: the lxc-clone error - that nromally happens after the image has been downloaded (via the state server). is there a tarball in /var/cache/lxc/trusty... ?13:21
wallyworldon the maas node13:21
jamwallyworld: so wget for 1/lxc/0 is failing13:25
jamafaict there are no containers on machine-013:25
jamso we don't see errors particularly there13:25
wallyworldwget to state server or from state server out to cloudimages?13:25
jamwallyworld: wget I assume that is to state server13:26
wallyworldwget is written as a bash file to tmp in order to specofy cert to use13:26
jamwallyworld: yeah, there is stuff about tmp files, but the requset13:27
jamthe request *to* the state server causes the state server to return 500 ISE13:27
jamand "juju ssh machine-0" is unable to read /var/log/juju/all-machines.log for debugging info13:28
wallyworldso it seems the secure wget is succeeding, but then the state server fails to reach out to cloudimages to fetch the tarball from there to 1. cache it, and 2. stream it back to wegt13:29
wallyworldwe really need the log files, preferrable with debug on13:29
wallyworldwhat does juju ssh ls /var/log/juju give?13:30
wallyworldis all-machines.log missing13:30
jamwallyworld: the message they got was "Permission Denied" not "no such file"13:33
wallyworldjam: that could be another issue then - if rsyslog pkg is missing, all-machines log won't be written13:34
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
wallyworldthat package is normally installed by cloud init, but not if os-updates-blah is false13:35
wallyworldthat's the bug i mentioned earlier13:35
natefinchdoes $$JFDI$$ not work anymore?  Or did I just mess it up?13:38
perrito666natefinch: aha, trying to jfdi13:38
mupBug #1440940 changed: xml/marshal.go:10:2: cannot find package "encoding" <blocker> <ci> <regression> <test-failure> <juju-core:Fix Released by ericsnowcurrently> <juju-core 1.24:Fix Released by ericsnowcurrently> <juju-release-tools:In Progress by gz> <https://launchpad.net/bugs/1440940>13:41
natefinchericsnow_afk: you around?13:42
natefinchperrito666: looks like it's $$__JDFI__$$  (but then the markup changes that to a bold JFDI)13:45
voidspaceericsnow_afk: ping13:48
voidspacenatefinch: you know anything about systemd?13:48
voidspacenatefinch: anything would be more than me... :-)13:48
=== ericsnow_afk is now known as ericsnow
natefinchvoidspace: LOL   I probably know less than that13:49
voidspacenatefinch: :-)13:49
voidspacenatefinch: looks like I'm stuck with hassling ericsnow ...13:50
natefinchvoidspace: well, I know some of our handling of it.  I just don't know systemd *itself*13:50
natefinchvoidspace: if that makes any sense :)13:50
voidspacenatefinch: right13:50
voidspacenatefinch: the question is about our handling of it, just formulating the question13:50
ericsnowvoidspace: what's up?13:51
voidspaceericsnow: I'm forward porting a networking fix from 1.23 to master (and 1.24)13:51
voidspaceericsnow: I now have a test that fails with this error13:51
voidspaceericsnow: which looks like a systemd change13:51
mgzI have a fix for bug 1446264 in need of kindly review13:52
mupBug #1446264: joyent machines get stuck in provisioning <bootstrap> <joyent-provider> <reliability> <repeatability> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1446264>13:52
voidspaceericsnow: are the two "effectively equivalent", i.e. can I just change the expected value13:52
natefinchvoidspace: lol, I read that as "port forwarding a networking fix"13:52
mgzsinzui: ^ you may like this13:52
voidspaceericsnow: the test specifically is TestShutdownInitCommandsSystemd13:52
sinzuimgz, \o/13:53
voidspacedigging into the test it looks a bit weirder13:53
ericsnowvoidspace: presumably that test is checking the generated script13:54
voidspaceI need to get it to show the whole script13:54
mgzocr: <http://reviews.vapour.ws/r/1519/>13:54
ericsnowvoidspace: got it13:55
mgzwallyworld: did you get my email btw?13:56
voidspaceericsnow: this is the full result13:57
voidspaceit looks reasonable13:57
voidspacethe test is explicitly checking for a chmod though13:57
ericsnowvoidspace: which test?13:58
=== liam_ is now known as Guest38949
=== kadams54 is now known as kadams54-away
voidspacecloudconfig/containerinit/container_userdata_test.go TestShutdownInitCommandsSystemd13:59
natefinchmgz: ship it!14:00
mgznatefinch: merci14:02
ericsnowvoidspace: OTP, now14:04
voidspaceericsnow: np, I'm reading through it14:04
voidspaceericsnow: it might be a genuine failure14:04
voidspaceyeah, it looks like there's definitely a chmod missing that the test expects, trying to work out why :-)14:07
voidspaceericsnow: this is service/systemd/testing/writeconf.go that is expecting a "chmod 0755 " + wct.scriptname()14:14
=== kadams54-away is now known as kadams54
TheMuestrange, router just went into service mode and back14:42
voidspaceericsnow: for the systemd writeconf tests, you don't know where the "chmod 0755" is supposed to be added do you?14:50
ericsnowvoidspace: check out service/systemd/conf.go14:54
ericsnowvoidspace: (in normalize)14:55
voidspaceericsnow: ah, I was grepping for chmod... that helps, thanks14:56
ericsnowvoidspace: np14:56
voidspaceericsnow: hmm... normalize does a 600 though, not an 075515:00
voidspacethat's on the logfile15:00
ericsnowvoidspace: ah15:00
ericsnowvoidspace: see service/systemd/service.go15:01
ericsnowvoidspace: (in InstallCommands)15:01
voidspaceericsnow: indeed15:01
voidspaceericsnow: thank you15:01
ericsnowvoidspace: that bit is triggered when you end up with a complex command15:01
voidspacenow to work out why that isn't being called in this code path15:01
voidspaceit is now *not* being called15:01
voidspaceand it's hard to see why this branch should change that15:02
ericsnowvoidspace: I'm guessing that the command was simplified15:02
TheMuevoidspace: a short review of http://reviews.vapour.ws/r/1521/? it's a forward port of a fix done by Dimiter15:02
voidspacethe execStart of the shutdown commands is different15:02
ericsnowvoidspace: exactly15:02
voidspaceTheMue: looking15:02
voidspaceTheMue: did you have to make any changes?15:02
ericsnowvoidspace: if the command is complex, it gets written out to a script and the path to the script is set to ExecStart15:03
voidspaceericsnow: right15:03
voidspaceericsnow: but the test should handle that15:03
voidspaceericsnow: it has the same if as the InstallCommand branch15:03
voidspaceericsnow: for some reason they're differing15:04
voidspaceTheMue: the way reviewboard renders the diff of that PR is awful :-)15:04
TheMuevoidspace: one moment, hangout15:05
ericsnowvoidspace: what does the equivalent pre-patch output look like? (equivalent  to http://paste.ubuntu.com/10940405/)15:09
voidspaceericsnow: I'll check shortly, doing a review for TheMue currently15:10
voidspaceericsnow: but good thing to check15:10
voidspaceericsnow: and then work out what's changed15:10
ericsnowvoidspace: k15:10
ericsnowvoidspace: yep15:10
voidspaceericsnow: you've given me enough clues to actually understand the code now, which is what I lacked earlier15:10
voidspaceericsnow: I may still hassle you yet though... :-)15:10
ericsnowvoidspace: np :)15:11
TheMuevoidspace: so, back again. no, no changes, only a one to one port of Dimiters changes. but two files have moved15:21
TheMuevoidspace: oh, just read dimiters comment, have to check the commit again. hmm15:24
mupBug #1450092 was opened: juju 1.23 fails to bootstrap with upstart <juju-core:New> <https://launchpad.net/bugs/1450092>15:26
TheMuevoidspace: this is the right one http://reviews.vapour.ws/r/1522/15:30
TheMuevoidspace: chosen master instead of 1.24 accidently15:30
TheMuevoidspace: now it's for the correct branch15:31
voidspaceTheMue: ok, I've been reading it on github anyway15:39
TheMuevoidspace: thx ;)15:40
TheMuevoidspace: https://github.com/juju/juju/pull/216115:40
sinzuinatefinch, Is this like the gccfo import encoding issue? https://github.com/golang/go/issues/1017316:14
=== kadams54 is now known as kadams54-away
sinzui^ that uses the newer compiler that Ubuntu offered to backport16:15
natefinchsinzui: looking16:15
mgzsinzui: looks like something else16:15
mgznatefinch: the issue with your test is it's totally bogus16:16
mgzyou have an amd64 machine with both gccgo and golang-go installed on it16:16
mgzwhich we know works16:16
mgzit's a ppc machine with only gccgo on it that fails16:16
katcomgz: i think we were wondering if you could run that sample program on the ci machine16:16
mgzkatco: I did, it fails16:16
katcomgz: to simplify the conversation16:16
natefinchmgz: that's sort of my point.... the *code* is valid.  There's a problem with the environment in which the code is run on that machine.16:17
mgzyeah, which is called 'gccgo on ppc64el'16:17
katcomgz: so can we take the next step and determine whether this is a CI env. issue, or a gccgo issue?16:18
katcomgz: e.g. is there a way to run that sample program on a ppc machine with gccgo installed as normal?16:18
mgzI don't have a fresh ppc machine to try, but I can try to find one16:18
natefinchmgz: I find it hard to believe that gccgo on powerpc, when properly set up, simply lacks the encoding package16:18
sinzuimgz, natefinch I am reading all the control files for gccgo-based packages. I don't see anything different from our package16:19
voidspaceTheMue: LGTM16:19
TheMuevoidspace: thx16:19
alexisbwwitzel3, ping16:19
mgzi'm out16:19
* katco looks dangerously at her old iBook aging in the corner16:19
=== kadams54-away is now known as kadams54
TheMuekatco: new tasks for old (i)books?16:25
natefinchencoding/json imports the encoding package.... and we import json in juju, so there's definitely some code that is referencing "encoding" indirectly already... but there is notably no other code importing "encoding" directly.16:25
katcoTheMue: yeah... it makes me not feel so bad about having so many old computers around :p16:25
TheMuekatco: hehe16:25
TheMuekatco: but the ibook already has been intel, hasn't it? the powerbooks have been G416:26
katcoTheMue: i think it's a G3, but it was definitely an iBook circa 200416:27
natefinchkatco: compiling juju on that is going to be a blast, I'm sure.16:27
TheMuekatco: oh, long time ago16:27
katconatefinch: hey, go compiles fast, right? :)16:27
katconatefinch: it's not going to happen anytime soon. i'm not even sure if it boots anymore. weekend project for sometime16:28
perrito666sinzui: do you know why my http://reports.vapour.ws/releases/2576 is empty?16:31
=== Spads_ is now known as Spads
sinzuiperrito666, the site can be 30 minutes behind the data that was stored for it to pick up16:39
wwitzel3alexisb: pong16:40
alexisbwwitzel3, I got what I needed thank you16:40
perrito666sinzui: oh, tx16:41
perrito666I am mainly curious why now the windows build is broken since I have not been even closer to what blew16:41
sinzuiperrito666, I suspect bad luck and charms in the aws bundle failure. I will try to retest16:41
sinzuiperrito666, it was a panic. Since we know this test should pass in 1.24, I will increase the reties. It was set to 1 when we knew it wouldn't pass16:43
sinzuiperrito666, a successful run is 90 minutes for windows16:44
mupBug #1450118 was opened: vsphere provider should use OVA instead of OVF from cloud images. <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1450118>16:44
sinzuiperrito666, I don't think there is anything for you to look at. I will whip CI to give a success, or concrete failure results16:45
perrito666sinzui: tx a lot16:46
katcosinzui: will you announce when trunk is open?16:48
sinzuikatco, I will, but I think CI will may do it before me. We installed the automatic unblocking rules this morning16:49
katcosinzui: oh wow, it pings irc now?16:49
sinzuikatco, no, just uses Lp to send out notification about why a bug is fix released16:50
natefinchsinzui: are all the bugs assigned to 1.24-alpha1 required to be fixed for 1.24?  Some of them don't seem like they're in a state to be fixed16:51
katcosinzui: ah gotcha16:51
sinzuinatefinch, I cannot say. when we decided to fork 1.24 from master, all the bugs that said they had to be fixed for the milestone got a new task16:52
sinzuinatefinch, if an issue is not doable to 1.24, then let katco and alexis know to reduce scope16:52
katconatefinch: yeah definitely ping me if you see things that are incomplete so we can further groom that list16:54
natefinchkatco: I doubt this one will ever be understood, certainly it's not fixable on any kind of a short timeline: https://bugs.launchpad.net/juju-core/1.24/+bug/139281016:59
mupBug #1392810: upgrade-juju --upload-tools, using 1.20.11, from 1.18.4 upgraded to 1.19.4 instead <canonical-bootstack> <canonical-is> <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1392810>16:59
katconatefinch: kind of agree... not sure why an --upload-tools bug would block a release since it's a purely dev feature17:00
natefinchsinzui: when's feature freeze and/or code freeze for 1.24?17:01
katconatefinch: last friday17:02
katconatefinch: ff at least17:02
natefinchkatco: ok17:02
sinzuinatefinch, regardless of the freeze, we expect some large branches to "fix" incomplete features.17:03
natefinchsinzui: understood.  I just thought I saw a feature request targeted to 1.24, which obviously won't make it in17:04
katconatefinch: actually that's a great point. we have several things with the feature tag targeted to 1.24-*17:06
katcosinzui: should we re-target those do you think?17:07
sinzuikatco, I do. Lets set honest expectation about what we can do17:07
natefinchsinzui: I keep seeing bugs like this one that say at the bottom "Changed in juju-core: milestone: 1.24-alpha1 → 1.25.0"   but they're still assigned to 1.24-alpha1 as well... are they supposed to be in both?17:13
natefinchsorry this is the bug I mean: https://bugs.launchpad.net/juju-core/1.24/+bug/141262117:14
mupBug #1412621: replica set EMPTYCONFIG MAAS bootstrap <bootstrap> <maas-provider> <mongodb> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1412621>17:14
mupBug #1450129 was opened: vsphere provider is missing firewaller, networking implementations <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1450129>17:14
sinzuinatefinch, that is because of Core policy. Every bug must be assigned to a series (and milestone) to track fixes and forward ports17:15
natefinchsinzui: ok, so... where/when should that bug be fixed? It's confusing when it's assigned to two different milestones.17:16
sinzuinatefinch, By forking long before the branch was stable Juju Core agreed to do double merges fore every issue.17:16
sinzuinatefinch, Core policy is fix it in the oldest stable, then forward port to master. Master is currrently 1.2517:16
natefinchsinzui: ok, so 1.25 and 1.24 just means 1.24 (and of course make sure it's fixed in trunk as well)17:17
sinzuinatefinch, yes exactly that17:18
natefinchsinzui: still doesn't seem like it needs to actually say "1.25" on the bug anywhere.  The "also put in master" should be implied.17:18
sinzuinatefinch, yep, but since 1.22 and 1.23 were troubled by missing merges, the policy was set by wallyworld and alexisb.17:19
* sinzui thinks forking later and asking features to stay in feature branches is easier for everyone17:20
katcotime for lunch17:21
natefinchI don't, because then it's pig-pile on master once the fork is cut, and whoever gets in last gets a merging nightmare of epic proprotions.  By cutting the branch early, work can be ongoing on master and everyone can happily merge incrementally rather than in one hellish lump.  Most things that go in after the branch is cut should be relatively small, in theory.17:22
=== kadams54 is now known as kadams54-away
natefinchsinzui: this bug appears to be mainly a DNS problem in their MAAS setup, not really a juju problem, other than we might be able to improve some error messages: https://bugs.launchpad.net/juju-core/1.24/+bug/141262117:30
mupBug #1412621: replica set EMPTYCONFIG MAAS bootstrap <bootstrap> <maas-provider> <mongodb> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1412621>17:30
sinzuinatefinch, +1. Fix the message and let someone fix their setup!17:31
sinzuinatefinch, I really like saying the bug is not in juju17:31
natefinchsinzui: this one really sounds like it's a maas/networking issue, not really juju: https://bugs.launchpad.net/juju-core/1.24/+bug/135578217:37
mupBug #1355782: Error during bootstrap: TLS handshake failed: x509: certificate signed by unknown authority <bootstrap> <cloud-installer> <landscape> <oil> <juju-core:Triaged> <juju-core 1.24:Triaged> <MAAS:New> <https://launchpad.net/bugs/1355782>17:37
sinzuinatefinch, I and others agree, but I think we need to prove that. Maybe mark it Incomplete and ask for the information needed to confirm the origin.17:40
=== kadams54-away is now known as kadams54
mupBug #1450146 was opened: vsphere provider feature flag should apply only to bootstrap <juju-core:In Progress by ericsnowcurrently> <juju-core 1.24:In Progress by ericsnowcurrently> <https://launchpad.net/bugs/1450146>18:24
sinzuiperrito666, We can now see http://reports.vapour.ws/releases/257619:02
sinzuiperrito666, There are two failures that suspiciously align with addressable containers on maas and aws. We are retesting. maybe the maas 1.7 is ill19:04
perrito666sinzui: tx, why are there keyboard interrupts in the logs?19:04
sinzuiperrito666, We know that 1.23 passed these tests before and after the feature flag. Ans we know the aws fix that went into 1.23 has nto yet merged into 1.24 and master19:04
sinzuiperrito666, timeouts. we try to make tests pass quickly instead of let you wait 5 bours for results19:05
perrito666sinzui: k, Ill be checking for new builds, the errors do seem alien to the previous problem19:05
sinzuiperrito666, in aws the bundle completes between 13 and 17 minutes, with a 30 minutes timeout. I am testing a 45 minute timeout now19:06
perrito666iirc, 372 secons here19:06
perrito666the bundle you provided against aws19:06
sinzuiperrito666, since errors are in the aws containers. I am inclined to escalate the bug that has a fix and mark you bug as fix released. master and 1.24 and blocked, but maybe a merge is only a hour away19:27
perrito666sinzui: I would wait until your EOD arrives19:27
perrito666but in principle, the problem seems to be adifferent bug, which might have been there all the time but masked by this other issue,19:29
=== kadams54 is now known as kadams54-away
perrito666dont you love when everybody you need to ask a question to is in the other side of the globe?19:42
natefinchperrito666: yep, sucks.19:43
sinzuikatco, wallyworld: I believe that perrito666's Megawatcher fix is good, but aws and maas are still broken. 1.24 and master are still blocked. I escalated bug 1442801 which appears to be the aws issue and has an unmerged fix available19:52
mupBug #1442801: aws containers are broken in 1.23 <blocker> <ci> <deployer> <ec2-provider> <lxc> <regression> <juju-core:In Progress by dooferlad> <juju-core 1.23:Fix Released by dooferlad> <juju-core 1.24:Triaged by dooferlad> <https://launchpad.net/bugs/1442801>19:52
katcosinzui: ty19:53
sinzuikatco, wallyworld : We are still looking into the maas, failure, hoping it is a substrate issue, not juju19:53
katcosinzui: fix for 1442801 just hasn't been forward ported to v1.24?19:59
katcoam i reading that right?19:59
sinzuikatco, that is my reading too19:59
natefinchsinzui: is this even really a bug anymore?  https://bugs.launchpad.net/juju-core/1.24/+bug/1442719   it sounds like it was just a problem of using an old version of juju that didn't support windows, so we had to do some rigamarole to do the upgrade.20:00
mupBug #1442719: juju sync-tools fails <sync-tools> <windows> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1442719>20:00
katcooh my goodness... seen in a SetUpSuite(...): cmd := exec.Command("go", "build", "github.com/juju/juju/cmd/jujud")20:22
perrito666yup, the comment above is fantastic20:23
katcoyeah lol20:23
natefinchheh.... I should have figured it was the uniter tests20:25
katcothat is a new one for me20:25
katcoperforming a compile... in a test...20:26
mupBug #1450191 was opened: quickstart cannot talk juju on maas 1.7 <api> <blocker> <ci> <quickstart> <regression> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1450191>20:30
perrito666yay new bug20:30
natefinchkatco, sinzui: this bug appears to be "juju upgrade-juju fails when the disk is full" ... which does not seem to be something we should really care about fixing: https://bugs.launchpad.net/juju-core/1.24/+bug/144191320:32
mupBug #1441913: juju upgrade-juju failed to configure mongodb replicasets <canonical-is> <mongodb> <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1441913>20:32
sinzuinatefinch, *reliability* Juju needs to make a sensible decision when it doesn't have resources to justify starting an upgrade20:33
katcoi can get behind that20:35
sinzuiMongo burned its bridges with me when it filled the disk with db and logs for two different deployments.20:36
natefinchI gotta run, kids are crazy, wife is sick.    I think that's valid, but that's true of every action we'd try to do20:36
alexisbnatefinch, quality software is ... ?20:37
alexisbnatefinch, but go take care of your family first20:37
natefinchalexisb: yes... I am just looking for return on investment20:37
katcoalexisb: we can talk about this on the release call, but nate brought up a great point in that we're past the FF for v1.24, and we should move all new features out past 1.2420:38
* perrito666 calls his isp to negotiate more upload and runs scared20:38
katcoalexisb: not sure if this is a feature or not :)20:38
alexisbyes there can be a fine line between features and bugs, that is fine20:38
alexisbbut we need to be careful to not ignore robustness issues20:39
alexisbit is important20:39
katcoabsolutely it is important20:39
alexisbjuju is awesome because it is so powerful20:39
alexisbbut ...20:39
perrito666robustnes is a feature in terms of adding new failure vectors20:39
alexisbanyhow we can chat about it on the release call20:40
katcoperrito666: that is a great way of putting that20:41
wwitzel3bugs are just incomplete features ;)20:42
perrito666wwitzel3: lol20:42
perrito666wwitzel3: software is like an infinite surface of minesweeper :p20:43
wwitzel3perrito666: any every time you you don't hit a mine, it is just the number 820:44
* katco now knows what wwitzel3 really does during the day20:45
wwitzel3I wonder if that is a thing?20:46
katcoyou can bet in emacs it is20:46
katcoi know emacs has tetris...20:46
katcoour kanban is so useful. it's quite plain to see something is wrong by how all of our bug fixes are blocked.20:47
katco1 liner up for grabs: http://reviews.vapour.ws/r/1523/20:48
perrito666wwitzel3: all it takes for something to come to existence in vim is for someone to wonder if its a thing.20:50
katcough. i really need to take a weekend and set up a bunch of environments that i can use for triaging bugs20:51
perrito666mmpfh,is alt f2 not present in unity for vivid?20:52
katcohow do i disconnect from an lxc console? C-a q isn't working20:59
sinzuikatco, control-d?21:00
katcosinzui: nah that just dumps me back to the login prompt21:00
sinzuikatco, stop the container from another session, then start the container with -n so you can ssh into it21:02
katcosinzui: yeah, just wondering how to exit its jail since i always forget to daemonize it21:02
sinzuikatco, C-a q is correct. I doubt those keys are remapped for you.21:03
katcosinzui: not working... wondering if its because it's for a machine i'm sshed into21:04
perrito666katco: ca aq21:10
perrito666katco: you seem to be suffering of double shell with the same escape clause21:11
katcoperrito666: tried that as well =/21:11
perrito666used to bite me in screen all the time21:11
perrito666tried C-a ?21:11
katcoyeah C-a a q21:12
katcoC-a q21:12
perrito666why in the universe is there no preview in launchpad comments21:13
perrito666is there any kind of formatting on the comments?21:14
katcoperrito666: there is, but i haven't taken the time to figure out what it is21:15
perrito666it has quite a user foe approach21:15
perrito666sinzui: ?21:15
sinzuiperrito666, no formatting supported. It was designed 10 years ago21:16
perrito666sinzui: damn, if only software was updateable...21:16
sinzuiperrito666, I use lots of new lines and many comments honour leading spaces21:16
sinzuiperrito666, If It was I would jump ship to tear down the bug, blueprint, and question trackers21:17
katcowow i'm impressed... my old ibook booted right up. G4 1.07GHz with 768Mb ram21:17
katcoapparently i took really good care of this21:17
perrito666katco: apple did21:18
katcoi do love apple hardware21:18
perrito666ibook g4s where white thinkpads21:18
perrito666the ibook g4 was my all time favorite machine, I almost cried when I replaced it21:18
katcoyeah it was my college machine after some crappy compaq gave up the ghost21:19
katcoi scrimped and saved for it... good investment.21:19
katcohaha... how i know it's old: in my browser history: google reader21:19
sinzuikatco, My daugher might want to buy your old computer. Her favourite marble game doesn't play on the intel Macs21:19
katcosinzui: i am toying with the idea of turning this into a build slave21:20
sinzui katco Power7 and power8 isn't going to help21:20
katcooh =/21:21
sinzuikatco, Ubuntu desupported PPC years ago. P8 is different, more than just the switch in endianess21:21
perrito666debian might, but iirc, by the time I sold the thing the only os running smoothly was osx.. Tiger?21:26
katcoi think this is running mtn. lion21:27
perrito666katco: does it run ok with less than 1g?21:27
katcoseems to21:27
katcoi mean i'm mostly on the terminal, but safari is doing ok21:27
katcoit's a really old version of safari though... i think i'd have to install FF or something if i wanted to browse seriously21:28
sinzuikatco, The community is made trusty for G4 http://cdimage.ubuntu.com/releases/14.04/release/21:29
katcoif anything the original HD is what slows me down the most21:29
katcosinzui: well, no point if i can't use it to test juju21:29
sinzuikatco: true21:29
sinzuikatco, Our current ppc64el machines will be removed in a few months. One option for QA and Core is to use Canonistack, which might get two power8 machines21:30
menn0/wii alexisb21:31
alexisbheya menn021:32
katcosinzui: http://juju-ci.vapour.ws:8080/job/github-merge-juju/2966/ has been running for 5h41m?22:04
sinzuikatco, wow, let me look22:05
katcosinzui: it looks like it might be the new functionality22:05
katcocheck-blockers.py or w/e22:05
sinzuikatco, yes it is22:05
sinzuikatco, oops, it is waiting for human input. I will have this fixed ina  few minutes, but I will need ti resubmit this for the victim22:07
katcosinzui: np22:07
perrito666waigani: ping22:21
waiganiperrito666: pong (or did you mean wallyworld?)22:22
perrito666nope, you22:23
perrito666waigani: https://github.com/juju/juju/commit/45f84f50 is it possible that the step you add in steps121.go was meant for steps122.go?22:23
perrito666I know its an old patch, but its worth trying22:24
perrito666waigani: we will know in like 20 mins anyway :p the test is running with the change applied22:25
waiganiperrito666: cool, reading / remembering. There where a few cases we found where the same upgrade step had to be run for 1.21 and 1.22 - due to the timing of tweaks and releases22:26
waiganiperrito666: so if it does pass, I wouldn't remove it from 1.21, but also add it to 1.22. Does that make sense?22:27
perrito666waigani: the thing is, that patch, and I might be wrong, is not merged into 1.2122:27
waiganiperrito666: ah22:28
perrito666I am right22:28
perrito666My guess, the merging got pushed22:28
perrito666and it entered after 1.21 cut22:28
waiganiright, it would make sense for a 1.21 upgrade step to be on 1.2122:30
waiganiperrito666: shall  I can merge that back into 1.21?22:30
perrito666waigani: mm, I am not sure22:31
perrito666ask sinzui22:31
perrito666btw, kudos on the commit it is very concise it made discovering the issue quite easy when I figured out where it was22:31
waiganithanks :) at least I make my issues obvious ;)22:32
perrito666waigani: anyway, it is, I think, causing https://bugs.launchpad.net/juju-core/+bug/1447853 so I might fix it as part of that once I learn in which versions we want that applied22:35
waiganiperrito666: so you're running tests on 1.23 with the upgrade test targeting 1.22 instead of 1.21?22:35
mupBug #1447853: Local charms are not added to storage on upgrade to 1.22.x <charms> <regression> <storage> <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:In Progress by hduran-8> <https://launchpad.net/bugs/1447853>22:35
perrito666indeed, it was22:35
perrito666waigani: the thing is, all upgrade paths are broken because of that22:36
waiganiperrito666: okay, well if the tests pass, definitely add it as a 1.22 upgrade step22:37
perrito666sinzui: please let me know where can this patch be applied, 1.22, 23 and 24?22:37
perrito666waigani: cheers, thanks a lot22:38
waiganiperrito666: actually, I don't think we need to backport to 1.21. All the charm id changes are in the same PR as the upgrade step - intended to hit 1.21 but ended up in 1.2222:39
alexisbanastasiamac, ping22:48
waiganiwallyworld:  I've reverted http://reviews.vapour.ws/r/1512/  to my original PR. could you take a look at my last comment which explains why and let me know if that makes sense?23:37
wallyworldwaigani: i'm not sure it's correct23:42
wallyworldif cBucket, ok := attrs["control-bucket"]; !ok  <--- this will not result in ok = true if control bucket defaults to ""23:43
wallyworldhence the control bucket will not be generated23:43
waiganiwallyworld: yep, that's what I was thinking and it's why I put that logic in. But the TestPrepareInsertsUniqueControlBucket passes without the logic23:45
wallyworldso the test is wrong23:45
wallyworldhaven't looked23:45
wallyworldi bet if you test live it would fail23:46
waiganiwallyworld: openstack also works like this. It looks like the configDefaults are used for validating unknown attrs - let me track down where the config used in prepare is  being build23:47
waiganiwallyworld: I'll test live too23:47
sinzuiperrito666, 1.24 and 1.25 per the bug. 1.22 is dead to me. 1.23 is doable, though we are not committing to a 1.23.323:52
sinzuiwaigani, we cannot release 1.22 fixes though our PPAs because the version is superseded by 1.23.2. We can merge a fix into 1.23 for 1.23.3, but we are not commiting to a 1.23.3 at this time.23:55
waiganisinzui: okay. How do we resolve this bug then: https://bugs.launchpad.net/juju-core/+bug/1447853, we need to add an upgrade step to 1.22 to fix it?23:59
mupBug #1447853: Local charms are not added to storage on upgrade to 1.22.x <charms> <regression> <storage> <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:In Progress by hduran-8> <https://launchpad.net/bugs/1447853>23:59

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