[00:26] cjohnston: natefinch veriried that 1.17.3 allows me to deploy. Had to update the juju/devel ppa to get it [00:48] rick_h__: enjoy your weekend when it gets here. o/ thanks again for the help [00:48] lazyPower: will do, you have fun as well [02:09] thanks rick_h__ === arosales__ is now known as arosales [03:05] does anyone have a minute to help me with a juju issue? [03:05] I've installed maas and it seems to be working fine, have comissioned one node but when i do a juju status --debug it hangs at opening state; mongo addresses: [03:07] and the node has moved from ready to allocated to user, even though I haven't installed any juju charms on it [03:50] anyone know how to resolve https://bugs.launchpad.net/juju-core/+bug/1178312 [03:50] <_mup_> Bug #1178312: ERROR state: TLS handshake failed: x509: certificate signed by unknown authority === freeflying_away is now known as freeflying === CyberJacob|Away is now known as CyberJacob === CyberJacob_ is now known as CyberJacob === freeflying_away is now known as freeflying === lifeless is now known as 7JTAAALD7 [21:18] hazmat: ping [21:21] hazmat: when you come around, I just started seeing bug #1269519 again [21:21] <_mup_> Bug #1269519: Error on allwatcher api [22:19] cjohnston, what of? [22:20] cjohnston, nutshell.. was in comment at end [22:20] cjohnston, namely juju 1.17+ fixes.. otherwise not resolved in deployer (fix would be series of short conns there instead of one conn per deploy). [22:21] but given core already resolved, upgrades are the best fix.. cjohnston curious though what kind of deploy config is apt to trigger. [22:33] cjohnston, if you can attach logs from machine 0 that would be helpful [22:33] cjohnston, and your deployer logs as well [22:34] i can do the nesc. workaround in deployer.. haven't seen it though.. otoh.. i only really do manual provider atm [22:34] afaics rog's fix should resolve it [22:34] so curious to see the logs [22:35] ack.. I'll see if I cant get it again [22:35] hazmat: also.. deployer seems broken from the last release [22:35] https://code.launchpad.net/~ev/ubuntu-ci-services-itself/pin-juju-deployer-revno/+merge/207805 has the error [22:35] cjohnston, hmm... traceback log? [22:35] I'm not sure why ev went back to 88 instead of just 100 (IIRC) [22:36] but we were using trunk and that started popping up [22:36] cjohnston, that's not trunk or last release [22:37] cjohnston, the using runtime now also says the name of the env [22:37] hazmat: L27 is where he removed trunk to replace it with 88 [22:39] cjohnston, which version of juju-core? [22:40] cjohnston, the last release has some fixes for juju 1.17+ .. ie. admin-secret auto gen and only in jenv as well as support for juju switch files instead of explicit JUJU_ENV [22:40] hazmat: I don't remember if I got it when I was still on 1.17.x or after I downgraded to 1.16.6 [22:40] or default in juju env [22:40] .yaml [22:41] cjohnston, so if you can reproduce with latest deployer on a 1.17.1+ i can take a look... but at the moment your saying unknown version of juju and old version of deployer. [22:42] hazmat: are you going to be around for a bit? if so, I can destroy what I have and do some deployments and debugging.. if not, we can look at it on Monday [22:42] cjohnston, i'll be around for an hr or 2. [22:42] ok.. [22:42] destroying, then I'll check things out [22:43] cjohnston, feel free to ping whenever.. i keep an irc proxy up that generally works :-) if not i'll ping back on monday. [22:43] I just don't want to destroy stuff and then findout you need something I missed :-) [22:44] cjohnston, mostly i just need confirmation of issue with latest versions.. if its the watcher closed thing i'd like logs from machine 0 / state-server and the deployer log. [22:44] ack [22:45] bootstrapping now [22:46] cjohnston, specifically.. https://bugs.launchpad.net/juju-deployer/+bug/1269519 should not happen with juju core 1.17.1+ and the other issue/merge you linked is resolved in latest release (and afaics applies primarily to 1.17+ releases of juju-core (no admin-secret in environments.yaml) [22:46] <_mup_> Bug #1269519: Error on allwatcher api [22:49] hazmat: ok.. first bit of data [22:49] http://paste.ubuntu.com/6978834/ [22:49] Package: juju-core [22:49] New: yes [22:50] State: installed [22:50] Automatically installed: no [22:50] Version: 1.17.3-0ubuntu1 [22:50] http://paste.ubuntu.com/6978835/ [22:50] What other info do you need for that one? [22:54] * hazmat back [22:54] cjohnston, what version of jujuclient is that? [22:55] 0.15-0ubuntu1 [22:56] cjohnston, is your environment bootstrapped? [22:57] cjohnston, what version of juju-core? [22:57] hazmat: I pasted the juju-core version above.. 1.17.3-0ubuntu1 [22:57] basically its saying you have no jenv file, and you have no admin-secret. [22:57] which afaics means at min your not bootstrapped. [22:58] http://paste.ubuntu.com/6978856/ [23:01] hazmat: it seems bootstrapped to me [23:01] cjohnston, can.. you run the following [23:01] cjohnston, http://pastebin.ubuntu.com/6978876/ [23:01] cjohnston, you seem to be picking up a different version of deployer.. in rev 101.. the log line is Using runtime %s on %s [23:02] you've just got using runtime.. without the env name, which is suspect to an older version [23:02] of deployer [23:03] ie you've got a current checkout in /tmp.. but depending on old installations, you might be picking up a different version [23:03] cjohnston, hmm [23:04] that is odd [23:04] hazmat: what's odd tho is if I used the mp from ev which checks out revno 88, it worked [23:06] cjohnston, could you paste bin $ env | grep JUJU [23:07] env | grep JUJU returns nothing [23:07] cjohnston, cool.. can you pastebin ls of ~/.juju [23:08] environments environments.yaml ssh [23:09] cjohnston, so i'm going to commit revno 102 [23:10] cjohnston, ic an issue on the traceback which should resolve [23:10] ok, cool [23:11] pushed [23:11] testing [23:12] cjohnston, still in forensics mode.. the commit was mostly just correct the traceback [23:14] cjohnston, is [23:14] hazmat: http://paste.ubuntu.com/6978940/ [23:14] lcy01 your default environment in environments.yaml [23:15] hazmat: it is [23:15] cjohnston, ok.. i'll make an egg on face release 0.3.4 which fixes.. you can work around via JUJU_ENV="lyc01" or juju switch lyc01 [23:17] cjohnston, pushed fix [23:17] revno 102 [23:17] er. 104 [23:17] er. 103 [23:17] lol [23:17] * hazmat gives up and goes back to the bottle [23:17] cjohnston, that should resolve .. i'll wait around for confirmation [23:17] not yet! I'm not done with you! [23:17] lol [23:18] cjohnston, so no juju switch or JUJU_ENV needed with revno 103.. [23:22] hazmat: question for you... I haven't investigated much with this yet... when using core 1.17+ to deploy our stuff, I have an issue... we deploy the python-django charm.. for some reason, django stays on 1.3.1 (the precise version) which causes an error when running the postgres changed hook. If I downgrade to core 1.16.6, python-django is the correct version and works.. have you seen/heard of anything like [23:22] that [23:23] when deployed with 1.17+ if I juju ssh into the instance, and do apt-cache policy python-django I do see 1.5.x available, but 1.3.1 is what's installed [23:24] cjohnston, on precise.. juju need cloud archive tools pocket for mongodb.. on 1.16 it installed mongodb from cloud archive.. 1.17 it added cloud-archive but only installed mongodb explicitly from it. [23:24] and cloud-archive... happens to hold openstack.. of which horizon/dashboard uses djanog [23:25] $%^& timeouts [23:25] ie. 1.17 tries to be explicit about just mongo from cloud archive.. 1.16 picked up django from there. [23:25] gotcha [23:26] is there a good workaround for that? [23:26] cjohnston, you mean you need django 1.5 ? [23:26] yes [23:27] cjohnston, i call it virtualenv ... with offline src install from charm cached src... but ignoring that for the moment.. ppa for django? [23:27] we can do that, I just wasn't sure if that's the best way [23:28] cjohnston, for py apps.. i'm a bit biased.. i tend to go venv [23:28] biased being a py dev [23:28] we are wanting to not do venv's [23:28] cjohnston, re ppa.. requires testing to verify on conflicts [23:29] cjohnston, spotify did a nice debian packaging helper based on venv [23:29] https://github.com/spotify/dh-virtualenv [23:30] cjohnston, based on your src paths for deployer your already have way down the rd to venv [23:30] trusty pkgs and juju stable ppa pkgs coming [23:30] for 0.3.4 [23:30] sweet [23:31] hazmat: is it possible to get those for saucy and precise as well? [23:31] cjohnston, hence the juju stable ppa [23:31] ahh [23:32] wow.. juju/stable has old stuff [23:32] cjohnston, so things working? [23:32] :-) [23:32] looks like it [23:32] cool [23:32] I just got my pgsql-relation-joined error [23:33] * hazmat uploads 0.3.4 [23:33] to pypi [23:35] thanks for your help hazmat === mars is now known as Guest32399 [23:46] cjohnston, np. thanks for the feedback. have a good one. [23:46] you too!