| rick_h__ | cjohnston: natefinch veriried that 1.17.3 allows me to deploy. Had to update the juju/devel ppa to get it | 00:26 |
|---|---|---|
| lazyPower | rick_h__: enjoy your weekend when it gets here. o/ thanks again for the help | 00:48 |
| rick_h__ | lazyPower: will do, you have fun as well | 00:48 |
| cjohnston | thanks rick_h__ | 02:09 |
| === arosales__ is now known as arosales | ||
| designated | does anyone have a minute to help me with a juju issue? | 03:05 |
| designated | 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:05 |
| designated | and the node has moved from ready to allocated to user, even though I haven't installed any juju charms on it | 03:07 |
| designated | 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 <config> <cts-cloud-review> <ui> <juju-core:Triaged> <https://launchpad.net/bugs/1178312> | 03:50 |
| === 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 | ||
| cjohnston | hazmat: ping | 21:18 |
| cjohnston | hazmat: when you come around, I just started seeing bug #1269519 again | 21:21 |
| _mup_ | Bug #1269519: Error on allwatcher api <juju-core:Fix Released by rogpeppe> <juju-deployer:Fix Released> <https://launchpad.net/bugs/1269519> | 21:21 |
| hazmat | cjohnston, what of? | 22:19 |
| hazmat | cjohnston, nutshell.. was in comment at end | 22:20 |
| hazmat | 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:20 |
| hazmat | but given core already resolved, upgrades are the best fix.. cjohnston curious though what kind of deploy config is apt to trigger. | 22:21 |
| hazmat | cjohnston, if you can attach logs from machine 0 that would be helpful | 22:33 |
| hazmat | cjohnston, and your deployer logs as well | 22:33 |
| hazmat | i can do the nesc. workaround in deployer.. haven't seen it though.. otoh.. i only really do manual provider atm | 22:34 |
| hazmat | afaics rog's fix should resolve it | 22:34 |
| hazmat | so curious to see the logs | 22:34 |
| cjohnston | ack.. I'll see if I cant get it again | 22:35 |
| cjohnston | hazmat: also.. deployer seems broken from the last release | 22:35 |
| cjohnston | https://code.launchpad.net/~ev/ubuntu-ci-services-itself/pin-juju-deployer-revno/+merge/207805 has the error | 22:35 |
| hazmat | cjohnston, hmm... traceback log? | 22:35 |
| cjohnston | I'm not sure why ev went back to 88 instead of just 100 (IIRC) | 22:35 |
| cjohnston | but we were using trunk and that started popping up | 22:36 |
| hazmat | cjohnston, that's not trunk or last release | 22:36 |
| hazmat | cjohnston, the using runtime now also says the name of the env | 22:37 |
| cjohnston | hazmat: L27 is where he removed trunk to replace it with 88 | 22:37 |
| hazmat | cjohnston, which version of juju-core? | 22:39 |
| hazmat | 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 |
| cjohnston | 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 |
| hazmat | or default in juju env | 22:40 |
| hazmat | .yaml | 22:40 |
| hazmat | 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:41 |
| cjohnston | 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 |
| hazmat | cjohnston, i'll be around for an hr or 2. | 22:42 |
| cjohnston | ok.. | 22:42 |
| cjohnston | destroying, then I'll check things out | 22:42 |
| hazmat | 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 |
| cjohnston | I just don't want to destroy stuff and then findout you need something I missed :-) | 22:43 |
| hazmat | 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 |
| cjohnston | ack | 22:44 |
| cjohnston | bootstrapping now | 22:45 |
| hazmat | 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 <juju-core:Fix Released by rogpeppe> <juju-deployer:Fix Released> <https://launchpad.net/bugs/1269519> | 22:46 |
| cjohnston | hazmat: ok.. first bit of data | 22:49 |
| cjohnston | http://paste.ubuntu.com/6978834/ | 22:49 |
| cjohnston | Package: juju-core | 22:49 |
| cjohnston | New: yes | 22:49 |
| cjohnston | State: installed | 22:50 |
| cjohnston | Automatically installed: no | 22:50 |
| cjohnston | Version: 1.17.3-0ubuntu1 | 22:50 |
| cjohnston | http://paste.ubuntu.com/6978835/ | 22:50 |
| cjohnston | What other info do you need for that one? | 22:50 |
| * hazmat back | 22:54 | |
| hazmat | cjohnston, what version of jujuclient is that? | 22:54 |
| cjohnston | 0.15-0ubuntu1 | 22:55 |
| hazmat | cjohnston, is your environment bootstrapped? | 22:56 |
| hazmat | cjohnston, what version of juju-core? | 22:57 |
| cjohnston | hazmat: I pasted the juju-core version above.. 1.17.3-0ubuntu1 | 22:57 |
| hazmat | basically its saying you have no jenv file, and you have no admin-secret. | 22:57 |
| hazmat | which afaics means at min your not bootstrapped. | 22:57 |
| cjohnston | http://paste.ubuntu.com/6978856/ | 22:58 |
| cjohnston | hazmat: it seems bootstrapped to me | 23:01 |
| hazmat | cjohnston, can.. you run the following | 23:01 |
| hazmat | cjohnston, http://pastebin.ubuntu.com/6978876/ | 23:01 |
| hazmat | 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:01 |
| hazmat | you've just got using runtime.. without the env name, which is suspect to an older version | 23:02 |
| hazmat | of deployer | 23:02 |
| hazmat | ie you've got a current checkout in /tmp.. but depending on old installations, you might be picking up a different version | 23:03 |
| hazmat | cjohnston, hmm | 23:03 |
| hazmat | that is odd | 23:04 |
| cjohnston | hazmat: what's odd tho is if I used the mp from ev which checks out revno 88, it worked | 23:04 |
| hazmat | cjohnston, could you paste bin $ env | grep JUJU | 23:06 |
| cjohnston | env | grep JUJU returns nothing | 23:07 |
| hazmat | cjohnston, cool.. can you pastebin ls of ~/.juju | 23:07 |
| cjohnston | environments environments.yaml ssh | 23:08 |
| hazmat | cjohnston, so i'm going to commit revno 102 | 23:09 |
| hazmat | cjohnston, ic an issue on the traceback which should resolve | 23:10 |
| cjohnston | ok, cool | 23:10 |
| hazmat | pushed | 23:11 |
| cjohnston | testing | 23:11 |
| hazmat | cjohnston, still in forensics mode.. the commit was mostly just correct the traceback | 23:12 |
| hazmat | cjohnston, is | 23:14 |
| cjohnston | hazmat: http://paste.ubuntu.com/6978940/ | 23:14 |
| hazmat | lcy01 your default environment in environments.yaml | 23:14 |
| cjohnston | hazmat: it is | 23:15 |
| hazmat | 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:15 |
| hazmat | cjohnston, pushed fix | 23:17 |
| hazmat | revno 102 | 23:17 |
| hazmat | er. 104 | 23:17 |
| hazmat | er. 103 | 23:17 |
| cjohnston | lol | 23:17 |
| * hazmat gives up and goes back to the bottle | 23:17 | |
| hazmat | cjohnston, that should resolve .. i'll wait around for confirmation | 23:17 |
| cjohnston | not yet! I'm not done with you! | 23:17 |
| cjohnston | lol | 23:17 |
| hazmat | cjohnston, so no juju switch or JUJU_ENV needed with revno 103.. | 23:18 |
| cjohnston | 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 |
| cjohnston | that | 23:22 |
| cjohnston | 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:23 |
| hazmat | 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 |
| hazmat | and cloud-archive... happens to hold openstack.. of which horizon/dashboard uses djanog | 23:24 |
| cjohnston | $%^& timeouts | 23:25 |
| hazmat | ie. 1.17 tries to be explicit about just mongo from cloud archive.. 1.16 picked up django from there. | 23:25 |
| cjohnston | gotcha | 23:25 |
| cjohnston | is there a good workaround for that? | 23:26 |
| hazmat | cjohnston, you mean you need django 1.5 ? | 23:26 |
| cjohnston | yes | 23:26 |
| hazmat | cjohnston, i call it virtualenv ... with offline src install from charm cached src... but ignoring that for the moment.. ppa for django? | 23:27 |
| cjohnston | we can do that, I just wasn't sure if that's the best way | 23:27 |
| hazmat | cjohnston, for py apps.. i'm a bit biased.. i tend to go venv | 23:28 |
| hazmat | biased being a py dev | 23:28 |
| cjohnston | we are wanting to not do venv's | 23:28 |
| hazmat | cjohnston, re ppa.. requires testing to verify on conflicts | 23:28 |
| hazmat | cjohnston, spotify did a nice debian packaging helper based on venv | 23:29 |
| hazmat | https://github.com/spotify/dh-virtualenv | 23:29 |
| hazmat | cjohnston, based on your src paths for deployer your already have way down the rd to venv | 23:30 |
| hazmat | trusty pkgs and juju stable ppa pkgs coming | 23:30 |
| hazmat | for 0.3.4 | 23:30 |
| cjohnston | sweet | 23:30 |
| cjohnston | hazmat: is it possible to get those for saucy and precise as well? | 23:31 |
| hazmat | cjohnston, hence the juju stable ppa | 23:31 |
| cjohnston | ahh | 23:31 |
| cjohnston | wow.. juju/stable has old stuff | 23:32 |
| hazmat | cjohnston, so things working? | 23:32 |
| cjohnston | :-) | 23:32 |
| cjohnston | looks like it | 23:32 |
| hazmat | cool | 23:32 |
| cjohnston | I just got my pgsql-relation-joined error | 23:32 |
| * hazmat uploads 0.3.4 | 23:33 | |
| hazmat | to pypi | 23:33 |
| cjohnston | thanks for your help hazmat | 23:35 |
| === mars is now known as Guest32399 | ||
| hazmat | cjohnston, np. thanks for the feedback. have a good one. | 23:46 |
| cjohnston | you too! | 23:46 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!