| redir | axw: can I borrow you to clarify a couple things? | 00:02 |
|---|---|---|
| rick_h_ | thumper: do you have a sec to peek at https://github.com/juju/utils/pull/226/files and ship if it's ok today please? | 00:35 |
| rick_h_ | sorry, that's not the RB link but close enough | 00:35 |
| thumper | rick_h_: ack | 00:43 |
| redir | bbiab | 00:49 |
| === veebers2 is now known as veebers | ||
| === natefinch-afk is now known as natefinch | ||
| thumper | menn0: I found out why that ARCH patch was there... | 02:16 |
| thumper | menn0: fails on s390 | 02:16 |
| thumper | without it | 02:16 |
| menn0 | thumper: argh right | 02:21 |
| thumper | proposing fix now | 02:21 |
| * menn0 doesn't really understand why | 02:21 | |
| menn0 | but fair enough | 02:22 |
| thumper | menn0: http://reviews.vapour.ws/r/5314/ | 02:23 |
| menn0 | thumper: should that setup live in SetUpTest or will that cause other problems? | 02:26 |
| menn0 | thumper: never mind... looking at the code it's only done in one other place | 02:27 |
| thumper | my gut tells me it may cause other problems | 02:27 |
| menn0 | better to just do it when necessary | 02:27 |
| menn0 | thumper: ship it with one sugestion | 02:28 |
| * thumper looks | 02:28 | |
| thumper | ack | 02:28 |
| axw | redir: sorry was out before. if you're still around I'm here now | 02:33 |
| axw | thumper: I don't really understand why your change was needed. we're already setting agent-version earlier in the function -- why doesn't that work? | 02:35 |
| axw | thumper: ahh, because building the tools bumps the version? | 02:35 |
| thumper | yep | 02:35 |
| redir | axw: np, I'll just dig in tomorrow. | 02:40 |
| mup | Bug #1607161 opened: generate-image metadata command help needs updating <helpdocs> <juju-core:Triaged> <https://launchpad.net/bugs/1607161> | 04:01 |
| mup | Bug #1607161 changed: generate-image metadata command help needs updating <helpdocs> <juju-core:Triaged> <https://launchpad.net/bugs/1607161> | 04:10 |
| mup | Bug #1607161 opened: generate-image metadata command help needs updating <helpdocs> <juju-core:Triaged> <https://launchpad.net/bugs/1607161> | 04:13 |
| menn0 | thumper: apiserver changes for migration status in the FullStatus response | 04:24 |
| menn0 | http://reviews.vapour.ws/r/5315/ | 04:24 |
| * thumper looks | 04:24 | |
| mup | Bug #1607170 opened: enable-ha requires '-m controller' (i.e. doesn't do the 'right thing' by default). <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1607170> | 04:37 |
| menn0 | thumper: by error state do you mean ABORT? | 04:38 |
| menn0 | if so yes it is (well actually ABORTDONE is the final, terminal phase) | 04:38 |
| thumper | menn0: chat? | 05:08 |
| thumper | abort done is only set after aborting is finished? | 05:15 |
| thumper | I was thinking about an intermediate error state | 05:15 |
| menn0 | thumper: sure | 05:33 |
| menn0 | going to to 1:1 | 05:33 |
| mup | Bug #1605986 opened: Creating container: can't get info for image 'ubuntu-trusty' <oil> <oil-2.0> <juju-core:Triaged> <https://launchpad.net/bugs/1605986> | 08:58 |
| ejat | <ejat> 2016-07-28 08:04:34 INFO config-changed subprocess.CalledProcessError: Command '['/opt/opendaylight-karaf/bin/client', '-r', '20', '-h', 'localhost', '-a', '8101', '-u', 'karaf', 'feature:list']' returned non-zero exit status 1 | 09:09 |
| ejat | odl-controller charm | 09:09 |
| ejat | anyone can help me ? | 09:09 |
| babbageclunk | ejat: If you run that command on the machine, do you get any useful output? | 09:19 |
| ejat | u mean this : /opt/opendaylight-karaf/bin/client', '-r', '20', '-h', 'localhost', '-a', '8101', '-u', 'karaf', 'feature:list | 09:20 |
| ejat | or '['/opt/opendaylight-karaf/bin/client', '-r', '20', '-h', 'localhost', '-a', '8101', '-u', 'karaf', 'feature:list']' | 09:20 |
| babbageclunk | ejat: yes, but without the quotes and commas. | 09:20 |
| ejat | /opt/opendaylight-karaf/bin/client -r 20 -h localhost -a 8101 -u karaf feature:list <-- ? | 09:21 |
| babbageclunk | ejat: yes | 09:21 |
| ejat | $ /opt/opendaylight-karaf/bin/client -r 20 -h localhost -a 8101 -u karaf feature:list | 09:22 |
| ejat | client: JAVA_HOME not set; results may vary | 09:22 |
| ejat | Logging in as karaf | 09:22 |
| ejat | 175 [pool-2-thread-2] WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at localhost/127.0.0.1:8101 presented unverified key: | 09:22 |
| ejat | Error executing command: java.lang.NullPointerException | 09:22 |
| ejat | juju not set the java_home ? | 09:22 |
| babbageclunk | ejat: It sounds more like there's a problem with the key, but I don't know anything about opendaylight. | 09:24 |
| babbageclunk | ejat: You might be better asking in #juju - there are more openstack people and charmers there. | 09:25 |
| ejat | ok thanks babbageclunk | 09:25 |
| babbageclunk | ejat: good luck! | 09:26 |
| ejat | grattitude | 09:26 |
| babbageclunk | voidspace: welcome back! Just around for 2 days? | 10:22 |
| babbageclunk | frobware, voidspace: a couple of reviews if you have a moment? http://reviews.vapour.ws/r/5312/ and http://reviews.vapour.ws/r/5317/ | 10:25 |
| frobware | babbageclunk: will get to it later; syncing with macgreagoir | 10:27 |
| babbageclunk | frobware: cool, thanks - no big rush | 10:28 |
| mup | Bug #1607000 changed: Immortal zombie Juju controller on MAAS <landscape> <juju-core:Invalid> <https://launchpad.net/bugs/1607000> | 10:35 |
| mup | Bug #1607303 opened: Help text for juju kill-controller needs to point to unregister <landscape> <juju-core:New> <https://launchpad.net/bugs/1607303> | 10:35 |
| frobware | macgreagoir: combined patch updated - https://github.com/frobware/juju/tree/master-lp1566801-strike3%2Blp1602054 | 10:42 |
| macgreagoir | frobware: FTR, woo hoo! | 11:12 |
| === tinwood is now known as tinwood-lunch | ||
| voidspace | babbageclunk: yeah, just here for a couple of days | 11:29 |
| voidspace | babbageclunk: off to cornwall with my dad for a week after that | 11:29 |
| babbageclunk | voidspace: nice | 11:30 |
| voidspace | babbageclunk: looks like everything changed whilst I was away... | 11:32 |
| babbageclunk | voidspace: of course! | 11:32 |
| voidspace | babbageclunk: your doing no doubt... | 11:32 |
| voidspace | babbageclunk: I got a microbit from EuroPython! | 11:33 |
| voidspace | babbageclunk: I haven't played with it yet though | 11:33 |
| voidspace | babbageclunk: I'm currently trying to fix MAAS (again) | 11:34 |
| voidspace | babbageclunk: a recent update broke my install | 11:34 |
| babbageclunk | voidspace: stink. I recently redid my MAASes using frobware's scripts - took a bit of time to get set up, but now I can add/remove nodes really easily. | 11:36 |
| voidspace | babbageclunk: ah cool - got a link | 11:36 |
| voidspace | babbageclunk: I'll try and get that working | 11:36 |
| babbageclunk | voidspace: In KVMs, or hardware? | 11:37 |
| voidspace | babbageclunk: KVM | 11:37 |
| babbageclunk | I hacked this one up: https://github.com/frobware/ubuntu-fan-hacks | 11:37 |
| voidspace | babbageclunk: have you pushed your changes anywhere, or are they babbageclunk specific? | 11:38 |
| frobware | babbageclunk, voidspace: I should really update the docs there .... | 11:38 |
| babbageclunk | ...to get the initial VM, then installed maas manually. | 11:38 |
| babbageclunk | then used https://github.com/frobware/kvm-maas with minimal hacks to add nodes. | 11:38 |
| frobware | babbageclunk: what changes did you need for kvm-maas? | 11:39 |
| babbageclunk | frobware: checking - only cut down the disk sizes a bit - I couldn't get it to respect the env vars. Nothing that needs pushing. | 11:40 |
| frobware | babbageclunk: hmm - I wonder why | 11:41 |
| babbageclunk | voidspace: The only tricky thing with the initial maas controller setup is that you need a hacked cloud image from frobware that enables cloud-init to do network setup in a network where there's no dhcp | 11:42 |
| voidspace | babbageclunk: ah, right | 11:42 |
| frobware | babbageclunk: so I'm relibably informed that that's now the default | 11:43 |
| babbageclunk | voidspace: ok - so that might be fixed! | 11:43 |
| frobware | voidspace: if that's not true there's always my enhanced version: http://178.62.20.154/~aim/xenial-server-cloudimg-amd64-disk1.img | 11:43 |
| voidspace | frobware: babbageclunk: cool, thanks - will have a play | 11:43 |
| babbageclunk | voidspace: hang on, I'll push my hacked (and now badly named) ubuntu-fan-hacks branches - I've got one for maas2 and one for maas1.9 | 11:44 |
| mattyw | frobware, hey there, are you OCR today? | 11:46 |
| frobware | mattyw: yes | 11:47 |
| mattyw | frobware, I have a tiny one for you. http://reviews.vapour.ws/r/5319/. I'm about to got afk but if you had any questions I'll be back in an hour or so | 11:47 |
| mattyw | frobware, but if you're busy - it's not that urgent :) | 11:48 |
| frobware | mattyw: me too - lunch is required | 11:48 |
| mattyw | frobware, I'm planning on combining it with a cycle as the sun is out :) | 11:48 |
| frobware | babbageclunk: running VIRT_DISK_SIZE=12 ./add-node disk-size-tes maas19-net maas19 | 11:48 |
| frobware | babbageclunk: gives me: http://178.62.20.154/~aim/disk-test.png | 11:48 |
| frobware | mattyw: heh, sounds fab! | 11:49 |
| babbageclunk | frobware: yeah, I may have been getting confused by something VMM was telling me - I think that's working fine. | 11:49 |
| babbageclunk | voidspace: https://github.com/babbageclunk/ubuntu-fan-hacks/tree/maas-2-vm | 11:50 |
| * frobware really really really goes for lunch. Really. Almost. Really. | 11:50 | |
| voidspace | babbageclunk: thanks | 11:50 |
| babbageclunk | voidspace: https://github.com/babbageclunk/ubuntu-fan-hacks/tree/maas-2-vm | 11:50 |
| babbageclunk | voidspace: https://github.com/babbageclunk/ubuntu-fan-hacks/commit/5f5b736308bfdfb15af84fe7986d252b7ef0990b | 11:51 |
| babbageclunk | voidspace: That should show the kinds of things you're likely to need to change. | 11:51 |
| voidspace | babbageclunk: cool | 11:51 |
| babbageclunk | voidspace: Still need to install maas manually and click around in the admin a little bit, but it's a bit simpler. | 11:52 |
| voidspace | babbageclunk: I'm just doing the mass install at the moment | 11:52 |
| voidspace | frobware: what's the right ppa for the latest and greatest maas | 12:16 |
| voidspace | frobware: ah, experimental3 | 12:16 |
| === tinwood-lunch is now known as tinwood | ||
| mup | Bug #1607347 opened: Password for juju-gui not showing up after a change <cpe-sa> <juju-core:New> <https://launchpad.net/bugs/1607347> | 12:23 |
| mup | Bug #1607362 opened: TestMachinerMachineNotFound agent should be terminated <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607362> | 13:05 |
| mup | Bug #1607362 changed: TestMachinerMachineNotFound agent should be terminated <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607362> | 13:11 |
| macgreagoir | frobware: I think I'm showing --bind working here (with your latest eth0 patch and an lp:1603473-like net config): https://pastebin.canonical.com/161866/ | 13:18 |
| frobware | macgreagoir: yes, looks good | 13:19 |
| mup | Bug #1607362 opened: TestMachinerMachineNotFound agent should be terminated <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607362> | 13:23 |
| mup | Bug #1607365 opened: PresenceSuite.TestScale reported false <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607365> | 13:23 |
| mup | Bug #1607368 opened: bootstrapSuite.TestBootstrapUploadTools model "foo" of type dummy does not support instances running on "ppc64el" <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607368> | 13:23 |
| mup | Bug #1607365 changed: PresenceSuite.TestScale reported false <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607365> | 13:32 |
| mup | Bug #1607368 changed: bootstrapSuite.TestBootstrapUploadTools model "foo" of type dummy does not support instances running on "ppc64el" <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607368> | 13:32 |
| mup | Bug #1607365 opened: PresenceSuite.TestScale reported false <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607365> | 13:35 |
| mup | Bug #1607368 opened: bootstrapSuite.TestBootstrapUploadTools model "foo" of type dummy does not support instances running on "ppc64el" <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1607368> | 13:35 |
| frobware | katco: standup? | 14:04 |
| frobware | rick_h_: you doing standup today? | 14:05 |
| natefinch | sinzui, mgz: it looks like we're building the CI tests with an old version of go? | 14:09 |
| sinzui | natefinch: ouch, I will look into it. Which test/host? | 14:10 |
| natefinch | sinzui: http://juju-ci.vapour.ws:8080/job/github-merge-juju-utils/125/console | 14:10 |
| sinzui | natefinch: not ci then | 14:10 |
| natefinch | sinzui: oh, right, landing bot, sorry | 14:10 |
| sinzui | natefinch: found the problem. Not every merge job has the path set right. I can fix this job in a minute. I need to review about 8 jobs though | 14:11 |
| natefinch | sinzui: ok... glad to help find problems :) | 14:12 |
| sinzui | natefinch: replaying the job with the right juju http://juju-ci.vapour.ws:8080/job/github-merge-juju-utils/126/console | 14:13 |
| natefinch | sinzui: yay, thanks. And glad that we'll be using the right version of Go. I intentionally removed the guardrails for go 1.2 vs 1.6 in this change.... we really just won't build with go 1.2 anymore. | 14:13 |
| babbageclunk | Is there anything that logs the actual userdata we send when starting an instance (particularly in maas)? | 14:29 |
| sinzui | babbageclunk: natefinch are your bugs the same: bug 1604474 and bug 1605777 | 14:46 |
| mup | Bug #1604474: Juju 2.0-beta12 userdata execution fails on Windows <azure-provider> <juju2.0> <oil> <oil-2.0> <windows> <juju-core:In Progress by natefinch> <https://launchpad.net/bugs/1604474> | 14:46 |
| mup | Bug #1605777: munna/juju2 is too slow to deploy windows images <ci> <maas-provider> <regression> <windows> <juju-ci-tools:Triaged> <juju-core:Triaged by 2-xtian> <https://launchpad.net/bugs/1605777> | 14:46 |
| babbageclunk | sinzui, natefinch - I think they are, yes. | 14:49 |
| babbageclunk | Good spotting! | 14:49 |
| babbageclunk | sinzui: Should I just mark 5777 as a duplicate of 4474? natefinch's quite far along with it, as far as I can see. | 14:52 |
| sinzui | babbageclunk: yep. | 14:52 |
| mup | Bug #1605777 changed: munna/juju2 is too slow to deploy windows images <ci> <maas-provider> <regression> <windows> <juju-ci-tools:Triaged> <juju-core:Triaged by 2-xtian> <https://launchpad.net/bugs/1605777> | 15:08 |
| voidspace | natefinch: ping - some advice | 15:19 |
| voidspace | natefinch: if you have the mental bandwidth (juju advice - not life advice, don't worry) | 15:19 |
| voidspace | for that I go to babbageclunk | 15:19 |
| babbageclunk | voidspace: for *bad* life advice | 15:24 |
| perrito666 | uh uh uh, bad life advice, I can do that, who is in need? | 15:25 |
| voidspace | babbageclunk: well, naturally... | 15:28 |
| voidspace | perrito666: hah, thanks - if the advice from babbageclunk ever turns out to not be bad enough I'll turn to you | 15:28 |
| voidspace | perrito666: babbageclunk: frobware: juju bug 1599972 | 15:29 |
| mup | Bug #1599972: juju2 beta11 unable to parse PORT during a maas bootstrap <2.0> <conjure> <maas-provider> <juju-core:In Progress by mfoord> <https://launchpad.net/bugs/1599972> | 15:29 |
| voidspace | perrito666: babbageclunk: frobware: the bug is that specifying the MAAS server in the form cloud.lol:5240 doesn't work | 15:29 |
| voidspace | with an error that it's a malformed url | 15:29 |
| voidspace | perrito666: babbageclunk: frobware: specifying instead http://cloud.lol:5240 however works | 15:30 |
| voidspace | do you think that is worth fixing or should be a "won't fix"... | 15:30 |
| frobware | voidspace: is 'cloud.lol:5240' actually a URL? | 15:30 |
| voidspace | frobware: well it is is you have cloud.lol in /etc/hosts | 15:30 |
| voidspace | which I do | 15:30 |
| voidspace | frobware: because ip:port worked so I needed a domain | 15:31 |
| frobware | voidspace: I'm really asking do you need http:// or ftp:// or ... | 15:31 |
| voidspace | frobware: if you don't specify the scheme but do specify a port then the url is "incorrectly" parsed | 15:31 |
| frobware | voidspace: so GIGO | 15:32 |
| voidspace | frobware: yep | 15:32 |
| stokachu | maas/172.0.0.1:5240 doesn't work | 15:32 |
| voidspace | stokachu: ah, it worked for me - trying again | 15:33 |
| perrito666 | voidspace: cloud.lol is a hostname | 15:33 |
| perrito666 | http://cloud.lol is a url | 15:33 |
| perrito666 | voidspace: cloud.lol:port is incredibly ambiguous as it could be both | 15:33 |
| stokachu | oh maybe I'm mistaken | 15:33 |
| stokachu | maas/cloud.lol:5240 is what doesn't work | 15:33 |
| stokachu | and you're saying that we should be using maas/http://cloud.lol:5240? | 15:34 |
| voidspace | stokachu: yep | 15:34 |
| voidspace | stokachu: what I'm *really* saying is that if you don't specify a malformed url you won't get the "malformed url" error... ;-) | 15:35 |
| voidspace | stokachu: but I was trying not to be a dick about it | 15:35 |
| perrito666 | stokachu: voidspace I was just clarifying why the erorr makes sense, I lack context for more detail | 15:35 |
| voidspace | not trying very hard though... :-p | 15:35 |
| voidspace | stokachu: although cloud.lol:5240 is what I would have tried as well | 15:35 |
| frobware | voidspace: in the same vein that $(firefox cloud.lol:5240) would just work, should juju? | 15:36 |
| voidspace | frobware: it would be nice if it did | 15:37 |
| perrito666 | frobware: firefox is lenient, if you put $(firefox agoogleableterm) will also work | 15:37 |
| voidspace | frobware: I don't think it's a critical bug that it doesn't | 15:37 |
| frobware | voidspace: nope, but I do like DWIM | 15:37 |
| perrito666 | this said, we should be a bit nicer in how we treat urls, if we expect a url and its not a url we could try a hostname | 15:38 |
| voidspace | perrito666: frobware: on error just adding http:// and retrying would work - if it still fails return the original error | 15:38 |
| natefinch | voidspace: sorry, was afk. | 16:51 |
| natefinch | sinzui: are we sure that #1605777 is the same as the bug I fixed? The bug I fixed was not that windows was slow - it was entirely broken | 16:52 |
| mup | Bug #1605777: munna/juju2 is too slow to deploy windows images <ci> <maas-provider> <regression> <windows> <juju-ci-tools:Triaged> <juju-core:Triaged by 2-xtian> <https://launchpad.net/bugs/1605777> | 16:52 |
| mup | Bug #1607457 opened: juju migrate fails to find model after migration <migration> <juju-core:Triaged> <https://launchpad.net/bugs/1607457> | 16:57 |
| sinzui | natefinch: The bug does not say windows is slow, It says juju 2. cannot deoploy a windows machine by 1.25 can. The suibstrate is known to be slow | 17:00 |
| natefinch | sinzui: I don't know what munna is, I assumed it was a windows machine in CI | 17:02 |
| natefinch | sinzui: regardless, it sounds like it's completely different from the bug that I fixed, which was that the userdata script we run on windows couldn't connect to the controller to download the jujud binary, because we didn't support a ciphersuite that windows supported. | 17:04 |
| sinzui | natefinch: okay. The issue we see is that the machine agent never comes up. Looks like a cloud init issue | 17:06 |
| natefinch | sinzui: that *could* be the same problem, then, since it's the userdata script failing. But it would have been a new failure around July 7th | 17:09 |
| natefinch | That's when we broke windows with the thing I just fixed | 17:10 |
| sinzui | natefinch: We first see the issue in July 15 http://reports.vapour.ws/releases/issue/5789759d749a5616aa83b491 We stopped testing on the host last week. The previous failures were timeouts, but machine want not checked | 17:13 |
| sinzui | natefinch: The last pass of the test for juju 2 was jujy 7! the first failure is on the 8th http://reports.vapour.ws/releases/4121/job/maas-1-9-deploy-win2012hvr2-amd64/attempt/624 | 17:15 |
| natefinch | sinzui: sound suspicious :) Let's try it again with this fix and see how it goes. | 17:16 |
| natefinch | / Fields holds a map from attribute name to information about that attribute. | 18:39 |
| natefinch | ....so why isn't it called Attributes? :/ | 18:39 |
| perrito666 | Bbl | 19:02 |
| redir | brb reboot | 20:16 |
| thumper | natefinch: ping | 20:23 |
| thumper | natefinch: re: https://github.com/juju/utils/pull/226#event-737900037 I saw this fail to land yesterday, and don't see a change in code, did the landing bot change? | 20:23 |
| thumper | sinzui: ^^ | 20:23 |
| natefinch | thumper: yep | 20:24 |
| thumper | was it using an older go? | 20:24 |
| natefinch | thumper: yep | 20:24 |
| thumper | ok | 20:25 |
| natefinch | thumper: so, win-win... it landed and now we have a canary for jobs that use a too-old version of go. | 20:25 |
| natefinch | I had intentionally removed the guardrails for some go 1.6 code in there, since we officially support it everywhere now. | 20:26 |
| sinzui | natefinch: I updated all the merge jobs to include go 1.6 in the path. We wont see any go 1.2 in the current jobs | 20:31 |
| natefinch | sinzui: huzzah | 20:33 |
| natefinch | man I hate middle-click paste | 20:55 |
| natefinch | simple PR for anyone - https://github.com/juju/schema/pull/13 | 20:58 |
| === natefinch is now known as natefinch-afk | ||
| redir | anyone here know anything about the model-config-tree details? | 21:35 |
| redir | natefinch-afk: LGTM, FWIW | 21:38 |
| mup | Bug #1607557 opened: wrong JSON field for storage endpoint in API <juju-core:New> <https://launchpad.net/bugs/1607557> | 23:01 |
| menn0 | thumper: addition MigrationMaster.SetStatusMessage API (small and boring): http://reviews.vapour.ws/r/5324/ | 23:04 |
| redir | axw: same bat station? | 23:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
