anastasiamac | menn0: ping | 00:19 |
---|---|---|
anastasiamac | tanzanite was planning to do the renaming of all env to model once controller-rename branch gets into master | 00:20 |
menn0 | anastasiamac: pong | 00:20 |
menn0 | anastasiamac: how were you going to handle things like DB collections? | 00:20 |
menn0 | anastasiamac: and what about API names? | 00:21 |
anastasiamac | menn0: we have not gotten to the point of actually discussing it yet as controller-rename branch is still pending in limbo somewhere... | 00:21 |
menn0 | anastasiamac: ok np | 00:21 |
anastasiamac | menn0: i suspect that we will have a brief next week where we'll discuss the approach | 00:21 |
anastasiamac | menn0: i'd love to get anyone who is interested involved | 00:22 |
anastasiamac | (u sound like one) | 00:22 |
anastasiamac | involved in discussion that is :D | 00:22 |
menn0 | anastasiamac: would you mind replying to my email then... if there's going to be a major rename effort so that "environment" goes away completely then I'm fine with using "model" everywhere | 00:23 |
menn0 | anastasiamac: I think the rename is going to be hard to get right | 00:23 |
anastasiamac | menn0: k. and I agree.... hence i think we should brain-storm before we dive into actual rename \o/ | 00:24 |
menn0 | anastasiamac: but if anyone can do it it's your squad :) | 00:24 |
anastasiamac | wot?! | 00:24 |
menn0 | anastasiamac: I'm happy to participate in the discussion and planning | 00:24 |
anastasiamac | i think with onyx's experience and the lessons learnt from controller-rename, ur squad is very well positioned to do it ;D | 00:24 |
anastasiamac | awesome! | 00:24 |
menn0 | anastasiamac: onyx has been banned from working on anything but model migrations | 00:25 |
menn0 | anastasiamac: but since this affects model migrations I think we can at least be involved in the discussion | 00:25 |
anastasiamac | menn0: k. xross-squad pairing sounds awesome :D | 00:26 |
menn0 | sure :) | 00:26 |
menn0 | probably not going to happen though | 00:26 |
anastasiamac | :( i can dream | 00:26 |
anastasiamac | i have a dream?... | 00:26 |
menn0 | :) | 00:28 |
davecheney | cherylj: chasing this https://bugs.launchpad.net/juju-core/+bug/1534394 | 00:53 |
mup | Bug #1534394: trusty/i386 test failure <juju-core:New> <https://launchpad.net/bugs/1534394> | 00:53 |
cherylj | davecheney: I think that waigani already fixed that bug. | 01:00 |
cherylj | bug 1532777 | 01:01 |
mup | Bug #1532777: undertakerSuite.TestEnvironConfig fails <blocker> <ci> <regression> <unit-tests> <juju-core:Fix Committed by waigani> <https://launchpad.net/bugs/1532777> | 01:01 |
cherylj | davecheney: the current things we're blocked on may be CI test issues. So at this point, I don't have specific bugs for you. | 01:01 |
cherylj | we will need some help with wily / xenial unit tests on 1.25 as we're extending its support for a while | 01:01 |
cherylj | but I've been focused on 2.0-alpha1 right now and don't have a list of those bugs yet | 01:02 |
cherylj | davecheney: so I don't need you right now. | 01:03 |
cherylj | was that rambling enough? | 01:03 |
mup | Bug #1534394 opened: trusty/i386 test failure <juju-core:New> <https://launchpad.net/bugs/1534394> | 01:09 |
davecheney | cherylj: noted | 01:18 |
davecheney | i'll move on to something else | 01:18 |
ericsnow | katco: crickets | 01:51 |
mup | Bug #1534394 changed: trusty/i386 test failure <juju-core:New> <https://launchpad.net/bugs/1534394> | 05:07 |
mup | Bug #1534480 opened: LXD: bootstrap error: no registered provider <juju-core:New> <https://launchpad.net/bugs/1534480> | 07:52 |
mup | Bug #1534511 opened: Support for multiple apt sources and apt keys in isolated environments <cpe> <stakeholder> <juju-core:New> <https://launchpad.net/bugs/1534511> | 09:19 |
frobware | dimitern, voidspace, dooferlad: will be 10-15 mins late for standup. | 09:46 |
dooferlad | frobware: I am happy to start late | 09:46 |
dooferlad | frobware: ping us when you are ready? | 09:46 |
dimitern | sure | 09:54 |
frobware | dimitern, voidspace, dooferlad: ready | 10:13 |
* dooferlad joins hangout | 10:14 | |
voidspace | omw | 10:18 |
voidspace | dimitern: frobware: dooferlad: still need a review by the way: http://reviews.vapour.ws/r/3534/ | 10:19 |
mup | Bug #1534480 changed: LXD: bootstrap error: no registered provider <juju-core:Invalid> <https://launchpad.net/bugs/1534480> | 10:31 |
voidspace | frobware: dimitern: dooferlad: so in the merge provider/maas/environ.go is fairly screwed | 11:07 |
voidspace | this is becauase a bunch of code was broken out into separate files on maas-spaces | 11:08 |
voidspace | but fixes applied to master (for default gateway stuff) | 11:08 |
mgz | bless on controller-rename btw | 11:17 |
voidspace | frobware: dimitern: dooferlad: coffee | 11:51 |
voidspace | dimitern: frobware: dooferlad: still need a review by the way: http://reviews.vapour.ws/r/3534/ | 12:50 |
frobware | voidspace, ack | 12:50 |
voidspace | dimitern: frobware: dooferlad: my merge branch now compiles, except for the tests | 12:50 |
voidspace | which are still pretty screwed | 12:50 |
frobware | voidspace, nice | 12:51 |
voidspace | as soon as they compile I can see what's broken | 12:51 |
voidspace | I'm worried that fixes that landed on master in code that was extracted into separate files on maas-spaces might get lost | 12:51 |
voidspace | that's the biggest danger | 12:51 |
voidspace | *hopefully* the tests will pick that up | 12:51 |
voidspace | but tests got moved too | 12:51 |
voidspace | so it'll need a good review to make sure we haven't lost fixes in the merge | 12:51 |
cherylj | can I get a review? http://reviews.vapour.ws/r/3546/ | 13:31 |
cherylj | It's a quick one | 13:31 |
mup | Bug #1521777 changed: Allow for upgrades to 2.0 <juju-core:Fix Released by cherylj> <juju-core 1.25:Fix Released by cherylj> <https://launchpad.net/bugs/1521777> | 13:38 |
dimitern | voidspace, you've got a review btw | 13:55 |
perrito666 | lazyPower: ping | 14:17 |
voidspace | dimitern: cool - thanks | 14:17 |
voidspace | dimitern: ah, I didn't know about the "if !c.Check(...) {continue}" trick | 14:18 |
voidspace | dimitern: that's why I wasn't using check in that loop | 14:19 |
voidspace | thanks | 14:19 |
dimitern | voidspace, :) yeah - it's useful | 14:20 |
frobware | dimitern, voidspace, dooferlad: let's use https://plus.google.com/hangouts/_/canonical.com/juju-sapphire | 14:30 |
voidspace | frobware: really? | 14:30 |
voidspace | I'm already in the one you linked to | 14:30 |
voidspace | ah well. | 14:30 |
voidspace | omw | 14:31 |
frobware | voidspace, ah, sorry. I tried to change it to that but the juju-sapphire URL but it obviously didn't work. | 14:31 |
dimitern | frobware, omw, 2m | 14:32 |
lazyPower | perrito666 pong | 14:40 |
mgz | cherylj: lgtm | 14:45 |
cherylj | thanks, mgz | 14:45 |
natefinch | chery, sorry I missed your emssage last night. Yes, that's what I'm doing now. Trying to repro with the steps in the bug. I reviewed fwereade's patch, which looks pretty sane... but I haven't been able to reproduce the bug yet, so it's hard for me to tell if the fix will fix it. | 14:54 |
natefinch | cherylj: ^ | 14:54 |
cherylj | natefinch: thanks for the update! | 14:55 |
mgz | oh, I thought we were all calling her 'chery' now... | 14:57 |
mup | Bug # opened: 1534610, 1534619, 1534620, 1534623 | 15:23 |
mup | Bug #1534626 opened: provisionerSuite.SetUpTest fails because connection reset <ci> <intermittent-failure> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1534626> | 15:29 |
mup | Bug #1534627 opened: Destroyed models still show up in list-models <juju-core:Triaged> <https://launchpad.net/bugs/1534627> | 15:29 |
perrito666 | lazyPower: sorry I solved itt myself, thank you anyway | 15:29 |
lazyPower | ah bueno perrito666 :) | 15:30 |
perrito666 | that is pretty much like throwing a wrench into my brain gears | 15:31 |
perrito666 | I was considering for a moment what channel was this | 15:31 |
mup | Bug #1534626 changed: provisionerSuite.SetUpTest fails because connection reset <ci> <intermittent-failure> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1534626> | 15:32 |
mup | Bug #1534627 changed: Destroyed models still show up in list-models <juju-core:Triaged> <https://launchpad.net/bugs/1534627> | 15:32 |
mup | Bug #1534626 opened: provisionerSuite.SetUpTest fails because connection reset <ci> <intermittent-failure> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1534626> | 15:38 |
mup | Bug #1534627 opened: Destroyed models still show up in list-models <juju-core:Triaged> <https://launchpad.net/bugs/1534627> | 15:38 |
mup | Bug #1534626 changed: provisionerSuite.SetUpTest fails because connection reset <ci> <intermittent-failure> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1534626> | 15:41 |
mup | Bug #1534627 changed: Destroyed models still show up in list-models <juju-core:Triaged> <https://launchpad.net/bugs/1534627> | 15:41 |
mup | Bug #1534626 opened: provisionerSuite.SetUpTest fails because connection reset <ci> <intermittent-failure> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1534626> | 15:44 |
mup | Bug #1534627 opened: Destroyed models still show up in list-models <juju-core:Triaged> <https://launchpad.net/bugs/1534627> | 15:44 |
mup | Bug #1534626 changed: provisionerSuite.SetUpTest fails because connection reset <ci> <intermittent-failure> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1534626> | 15:47 |
mup | Bug #1534627 changed: Destroyed models still show up in list-models <juju-core:Triaged> <https://launchpad.net/bugs/1534627> | 15:47 |
mup | Bug #1534626 opened: provisionerSuite.SetUpTest fails because connection reset <ci> <intermittent-failure> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1534626> | 15:50 |
mup | Bug #1534627 opened: Destroyed models still show up in list-models <juju-core:Triaged> <https://launchpad.net/bugs/1534627> | 15:50 |
mup | Bug # opened: 1534632, 1534636, 1534637, 1534643 | 15:53 |
mup | Bug # changed: 1534632, 1534636, 1534637, 1534643 | 15:56 |
mup | Bug # opened: 1534632, 1534636, 1534637, 1534643 | 15:59 |
cherylj | can I get another easy review? http://reviews.vapour.ws/r/3549/ | 16:21 |
natefinch | cherylj: ship it | 16:30 |
cherylj | thanks, natefinch! | 16:30 |
natefinch | katco, ericsnow: someone needs to make a "let me man pages that for you" | 17:05 |
natefinch | fwereade: I don't suppose you have a test charm that exercises leadership? | 17:07 |
lazyPower | natefinch: i have one | 17:50 |
mup | Bug #1534757 opened: Attempting to run charm before unit provisioned, 1.26 <juju-core:New> <https://launchpad.net/bugs/1534757> | 17:57 |
natefinch | lazyPower: I actually figured out that I don't need a special charm... every charm gets a leader, most charms just don't care :) | 18:08 |
natefinch | lazyPower: so I can just use a dummy charm and juju run is-leader on it, and that's sufficient for my purposes :) | 18:08 |
beisner | mgz, cherylj - still re-confirming, but two bootstrap attempts with 1.25.2 + 1.9 give me a bootstrap timeout. the machine comes online, maas state is deployed. it's reachable for a bit, then no-talky from then on. http://pastebin.ubuntu.com/14506872/ | 18:21 |
mgz | beisner: thanks | 18:31 |
mgz | beisner: what does maas say about it? | 18:32 |
beisner | mgz from maas perspective, it is "deployed" | 18:32 |
beisner | i've backed out to 1.25.0, same procedure, same maas, bootstraps ok | 18:33 |
beisner | i suspect juju bridge foo is the moment we lose network | 18:33 |
beisner | unfortunately, i can't inspect the aftermath b/c i can't reach it. i've got SOL / ipmi, and can see that it is up at the login screen. but of course no user/pwd login enabled. | 18:34 |
mgz | can you ssh in parallel when it's installing and stuff and hold that connection? | 18:34 |
mgz | I'd be interested to see logs/networking config changes on the box | 18:35 |
beisner | me too. i shall keep trying. do you have 1.9 maas that you can try a bootstrap against? | 18:35 |
mgz | beiser: see http://reports.vapour.ws/releases/3511/job/maas-1_9-OS-deployer/attempt/181 | 18:37 |
mgz | log in with sso and go to that page | 18:37 |
mgz | that's our result for 1.25.2 on maas 1.9 deploying your trusty-liberty bundle | 18:38 |
beisner | mgz, that's using 1.25.3 | 18:40 |
beisner | i'm using 1.25.2 from ppa:juju/proposed, plus agent-stream: proposed | 18:40 |
mgz | ah, whoops, wrong rev, go back to /releases/3506 and attempt/163 | 18:41 |
mgz | which is the same code, though not literally the same binaries | 18:41 |
mgz | our maas is certainly not your maas though | 18:42 |
mgz | beisner: I'm presuming you don't have any of the feature flags on as well? | 18:42 |
beisner | mgz right, just as a vanilla new user | 18:42 |
beisner | ok, i'll fire off a fresh bootstrap with 1.25.2 and see if i can sneak onto that unit before it goes lalalala | 18:43 |
mgz | as soon as it starts the apt installing stuff you should be good, note you'll want the same ssh key/juju env key available | 18:44 |
beisner | ha. i got this seconds before the first reboot. http://pastebin.ubuntu.com/14507351/ /me watches closely... | 18:56 |
beisner | ok mgz. i had a total of ~10s of reachability, then unreachable. i did establish ssh in that window, did another `ip a` and got as far as the b in `brctl show` when it cut me off: | 19:01 |
beisner | http://pastebin.ubuntu.com/14507430/ | 19:01 |
beisner | so before maas' first reboot, sane. | 19:01 |
beisner | after maas' first reboot, sane. | 19:01 |
beisner | after juju init stuff, no connectivity. | 19:02 |
perrito666 | oh great someone did the same I was doing | 19:02 |
mgz | so, session did get cut off, that pretty much does mean this is a interface reconfiguration | 19:03 |
katco | natefinch: planning | 19:05 |
natefinch | katco: oops, coming | 19:06 |
mgz | beisner: I think we need a bug to track. probably want maas network output included. | 19:07 |
beisner | mgz, yep i'm raising one now. | 19:08 |
frobware | beisner, can I give you a binary that would allow console login | 19:11 |
beisner | frobware, yes please & thx | 19:11 |
frobware | beisner, you would obviously have to bootstrap with --upload-tools | 19:12 |
beisner | fyi: bug 1534795 | 19:12 |
mup | Bug #1534795: unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 <maas-provider> <uosci> <juju-core:New> <https://launchpad.net/bugs/1534795> | 19:12 |
beisner | frobware, ack | 19:12 |
frobware | beisner, ok give me 10-15mins - will verify locally | 19:13 |
beisner | thx frobware | 19:13 |
beisner | mgz, frobware - good news: in our openstack-provider automation, things are looking good so far :) | 19:15 |
frobware | beisner, so any clue as to why the other setup is borked? different MAAS setup? | 19:15 |
beisner | frobware, two different providers. | 19:15 |
mgz | frobware: using the maas provider rather than openstack provider | 19:15 |
frobware | beisner, on the MAAS side what's the network config look like? VLANs? Bonds? straight-forward eth0? | 19:16 |
frobware | beisner, and version of MAAS? | 19:17 |
beisner | maas: 1.9.0+bzr4533-0ubuntu1~trusty1 | 19:18 |
beisner | juju: 1.25.2-0ubuntu1~14.04.1~juju1 | 19:18 |
frobware | beisner, ack | 19:18 |
beisner | frobware, eth0, untagged | 19:19 |
frobware | beisner, so as vanilla as it gets.... sigh. | 19:19 |
frobware | beisner, amd64? | 19:19 |
beisner | yep amd64 | 19:19 |
frobware | beisner, just checking. ;-) | 19:19 |
beisner | frobware, yep, np | 19:20 |
frobware | beisner, what's the easiest way to get binaries to you? | 19:21 |
beisner | i've used our private chinstrap in the past for that. i've not used the new private-fileshare bits yet, though we can try that. | 19:22 |
beisner | frobware ^ | 19:22 |
frobware | beisner, any other interfaces or just eth0? | 19:26 |
mup | Bug #1534795 opened: unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 <maas-provider> <uosci> <juju-core:New> <https://launchpad.net/bugs/1534795> | 19:27 |
beisner | frobware, machine has 4 nics, only eth0 and eth1 are cabled up. we've only ever used eth0 on these particular machines. | 19:27 |
beisner | frobware, mgz: oo interesting ... note that on my 2nd paste in the bug, eth1 is up for some reason. | 19:29 |
beisner | that is unexpected | 19:29 |
frobware | beisner, http://178.62.20.154/~aim/juju-bin.tar.bz2 | 19:35 |
frobware | beisner, that's 1.25.2 but before juju has a little play with /e/n/i is does `passwd -d ubuntu' - so you should be able to login on the console. | 19:36 |
frobware | mgz, ^^ | 19:37 |
mgz | frobware: thanks for helping out | 19:37 |
beisner | thx, grabbing the bin now frobware | 19:38 |
frobware | mgz, beisner: I'm very tempted to make that a capability behind a flag... as we run into it too often and it's difficult to diagnose once it goes wrong. | 19:43 |
frobware | mgz, beisner: the issue of course is security | 19:43 |
beisner | that would be a good t-shooting tool indeed. but yep, that. | 19:43 |
frobware | beisner, I just tried with two NICs configured and it bridged eth0 OK | 19:47 |
beisner | frobware, so i have two nics CONNECTED, but not two nics configured. | 19:48 |
beisner | frobware, ie. http://pastebin.ubuntu.com/14508207/ | 19:48 |
frobware | beisner, so when I say configure, in MAAS 1.9 parlance, they're configured and both have static ip assignment when looking in the MAAS UI | 19:48 |
beisner | yet eth1 winds up UP | 19:48 |
beisner | frobware, https://launchpadlibrarian.net/234276622/network.png | 19:52 |
frobware | beisner, let's see what happened to e/n/i once you bootstrap and can login | 19:52 |
frobware | beisner, but I see no smoking gun there | 19:53 |
beisner | frobware, \o/ i'm in via ipmi | 19:53 |
beisner | sol that is | 19:53 |
beisner | with that bin | 19:53 |
frobware | beisner, the binary I sent you didn't work? | 19:55 |
beisner | frobware, yes. it let me log in with ubuntu. now poking around in it. | 19:55 |
beisner | frobware, eth0 is down; eth1 is up; no bridges. no ipv4 addresses. | 19:59 |
beisner | grabbing /etc, /var/log, anything else? | 19:59 |
frobware | beisner, can you send me /etc/network/interfaces* | 19:59 |
mup | Bug #1534804 opened: debug-log is unstable with LXD local provider <docteam> <juju-core:New> <https://launchpad.net/bugs/1534804> | 20:00 |
frobware | beisner, and capture ip route | 20:00 |
frobware | beisner, is is possible to HO? | 20:01 |
beisner | frobware, https://plus.google.com/hangouts/_/canonical.com/andrew-mcdermot?authuser=1 | 20:06 |
beisner | wow `ip route` blank | 20:07 |
beisner | that's a new one | 20:07 |
frobware | beisner, in there | 20:07 |
frobware | beisner, mgz: http://pastebin.ubuntu.com/14509474/ | 20:19 |
beisner | frobware, added tarball to bug. woot. thx again for your help. & mgz | 20:35 |
frobware | beisner, mgz: I know exactly what the bug is. | 20:39 |
frobware | beisner, mgz: fixed in maas-spaces, doesn't help... however, we ran into the same issue a week ago on maas-spaces - and we had not seen it there for > 1 month. Something changed upstream so that we get dns-nameserver entries partwya through /e/n/i and we don't parse that correctly. | 20:40 |
perrito666 | :| ubuntu does not define xdg_config_home ? | 20:41 |
beisner | frobware, excellent. and yep, i'll do a maas non-juju deploy of that machine and collect the same in a bit. | 20:42 |
frobware | beisner, pretty sure you won't need to do that. uploading a new binary for you to try. | 20:43 |
frobware | beisner, I'll leave the `passwd -d ubuntu' in just to help out. | 20:45 |
frobware | beisner, I still don't understand why my MAAS setup doesn't give me the same dns-nameserver entries other people get. | 20:46 |
cherylj | frobware: I'm really happy you're still up to look at this :) I saw the bug report while at the doctor's office | 20:49 |
frobware | beisner, http://178.62.20.154/~aim/juju-bin.tar.bz2 | 20:52 |
frobware | beisner, md5sum a2d16e6f3993cc56e7c998aadfe48b74 | 20:52 |
beisner | frobware, thx. will grab and run it shortly | 20:54 |
frobware | cherylj, https://bugs.launchpad.net/juju-core/+bug/1534795/comments/7 | 21:36 |
mup | Bug #1534795: unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 <maas-provider> <uosci> <juju-core:Confirmed for frobware> <https://launchpad.net/bugs/1534795> | 21:36 |
frobware | cherylj, https://bugs.launchpad.net/juju-core/+bug/1534795/comments/8 | 21:36 |
frobware | beisner, see my updates to the bug ^^ | 21:37 |
cherylj | frobware: thanks so much! | 21:37 |
beisner | frobware, cherylj - cycling now. it's progressed to pkg installation and maintained connectivity thus far \o/ | 21:38 |
frobware | beisner, great. I would really appreciate if you could try it again with http://178.62.20.154/~aim/juju-bin-lp1534795.tar.bz2 as this is a build from the proposed PR. | 21:38 |
frobware | beisner, I'll hang around for 10-15 mins to hear your "BOOTSTRAPPED!" message. :) | 21:39 |
frobware | cherylj, beisner: the only thing I would point out about my binary build is it is based on the tip of 1.25... not the 1.25.2 tag. Caveat Emptor! | 21:42 |
katco | ericsnow: natefinch: what was your alternative proposal for "juju charm --resources"? | 21:45 |
natefinch | katco, ericsnow: anything else | 21:48 |
natefinch | katco, ericsnow: uh... maybe just charm-resources? | 21:48 |
ericsnow | natefinch: I actually think it fits well, even if it requires a new juju sub-command | 21:49 |
natefinch | ericsnow: I can't abide adding a new subcommand that doesn't do anything, just so it can have a flag that does something. That's terrible. | 21:49 |
ericsnow | katco, natefinch: yeah, ideally charm-resources | 21:49 |
katco | ericsnow: natefinch: ok, i'll float the suggestion. it's entirely possible that we intend to expand on the charm command | 21:52 |
natefinch | katco: I'd be fine with it if juju charm was a command that was goign to do other things.... though I'm generally against using flags to do completely different things... that's what subcommands are for | 21:53 |
natefinch | katco: so like, if juju charm cs:foo gave you generic info about the charm, and juju charm --resources gave you info about the charm's resources, that's cool | 21:54 |
perrito666 | please dont add an empty command, that is counter intuitive | 21:54 |
katco | perrito666: we're fighting it | 21:54 |
perrito666 | charm-resources sounds a bit less painful | 21:55 |
perrito666 | my kingdom for an unblocked master | 21:56 |
natefinch | ditto | 21:56 |
beisner | frobware, 0 started 1.25.2.1 fat-machine.dellstack | 21:57 |
katco | perrito666: natefinch: it's not going to unblock until cherylj decides we're good for stabilizing 2.0-alpha1: http://pad.lv/1533750 | 21:57 |
natefinch | looks like just this left: https://bugs.launchpad.net/juju-core/+bug/1534201 | 21:58 |
mup | Bug #1534201: TestHelpAddImage fails <ci> <regression> <test-failure> <windows> <juju-core:In Progress by cherylj> <https://launchpad.net/bugs/1534201> | 21:58 |
cherylj | yeah, I need to add back in the feature flag without breaking windows | 21:59 |
anastasiamac | cherylj: it's staurday here but.. i can look at it at my monday | 21:59 |
anastasiamac | cherylj: did u get a chance to progress this bug? | 21:59 |
frobware | beisner, that's booted OK then? | 22:00 |
natefinch | later all, dinner time | 22:00 |
cherylj | anastasiamac: I haven't yet. going to this evening | 22:00 |
cherylj | anastasiamac: did you have anything to hand off? | 22:00 |
mup | Bug #1532777 changed: undertakerSuite.TestEnvironConfig fails <blocker> <ci> <intermittent-failure> <regression> <test-failure> <juju-core:Fix Released by waigani> <https://launchpad.net/bugs/1532777> | 22:00 |
anastasiamac | cherylj: k.. keep me posted | 22:00 |
anastasiamac | cherylj: jsut an idea on how to fix it from tim... | 22:00 |
anastasiamac | cherylj: the fundamental problem is tests should not touch external singleton resources, such as the windows registry | 22:01 |
cherylj | yeah... | 22:01 |
anastasiamac | cherylj: this is why all the tests use the environment for feature flags | 22:01 |
anastasiamac | cherylj: i suspect that the base test suite for these commands needs to be re-written | 22:02 |
anastasiamac | cherylj: but i was going to see if i can re-run juju tests on my wndows | 22:03 |
anastasiamac | cherylj: and had trouble getting it going | 22:03 |
mup | Bug #1532777 opened: undertakerSuite.TestEnvironConfig fails <blocker> <ci> <intermittent-failure> <regression> <test-failure> <juju-core:Fix Released by waigani> <https://launchpad.net/bugs/1532777> | 22:03 |
cherylj | anastasiamac: yeah, thanks to sinzui, I have a windows machine I can use for unit tests | 22:03 |
anastasiamac | cherylj: \o/ | 22:04 |
perrito666 | oh, blessed master | 22:04 |
anastasiamac | cherylj: neeed to go to have a weekend :/ will check back in on monday and pick it up if needed | 22:05 |
sinzui | cherylj: master is reightfully bless. I parused CI because I am looking to move some jobs to other public clouds since Joyent hasn't fixed the firewall yet | 22:05 |
beisner | frobware, yessir | 22:05 |
cherylj | thanks anastasiamac! have a good weekend! | 22:05 |
anastasiamac | cherylj: thanks \o/ you as well! | 22:05 |
frobware | beisner, excellent. | 22:06 |
* frobware is gone gone gone! | 22:06 | |
cherylj | thanks, frobware! | 22:07 |
mup | Bug #1532777 changed: undertakerSuite.TestEnvironConfig fails <blocker> <ci> <intermittent-failure> <regression> <test-failure> <juju-core:Fix Released by waigani> <https://launchpad.net/bugs/1532777> | 22:09 |
perrito666 | oh great, juju home is not defined by a single source of truth | 22:09 |
beisner | cherylj, frobware, mgz - ok i'm eod + eow. off monday, US holiday. i can commit to cycling the 3rd bin (http://178.62.20.154/~aim/juju-bin-lp1534795.tar.bz2) at some point this weekend and chiming in on the bug with how that went. | 22:20 |
cherylj | thanks, beisner! | 22:21 |
perrito666 | ok, this got into my nerves, EOW | 22:23 |
beisner | yw, cherylj o/ have a nice weekend, all | 22:23 |
=== ericsnow is now known as ericsnow-afk |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!