[01:43] <jose> tvansteenburgh: I actually forgot to do bzr add and lost the info, BUT had pastebinned it :)
[01:43] <jose> (for the nyancat tests)
[13:50] <rharper> in an openstack environment, can I configure what ssh keys juju uses when deploying services?  I'd like to provide the keypair instead of juju generating one
[14:10] <stokachu> rbasak: do you maintain python-websocket?
[14:15] <jose> marcoceppi: ping, I'm having some problems with my tests
[14:15] <jose> they seem to not pass anymore, not sure why... even though they *did* pass when I wrote them
[14:26] <rbasak> stokachu: I did TIL
[14:27] <rbasak> stokachu: what's up?
[14:27] <stokachu> rbasak: we recently got python3 support in the main source tree
[14:27] <stokachu> rbasak: should i open a bug to get python3 packages built?
[14:28] <rbasak> stokachu: in the websocket-client source tree?
[14:28] <stokachu> rbasak: yea
[14:28] <rbasak> stokachu: ah OK. Yeah we probably need a bug to update to latest upstream then, and to add Python 3 packages.
[14:28] <stokachu> ok ill file one this week for that
[14:29] <rbasak> Looks like Debian need one too
[14:29] <stokachu> ok ill follow up with the Debian maintainer as well
[14:30] <rbasak> stokachu: thanks! Just noticed that https://pypi.python.org/pypi/websocket-client still says 2.7 only - I guess you want to fix that?
[14:31] <stokachu> rbasak: yea ill ask the upstream guy to release a new version
[14:31] <rbasak> Ah
[14:32] <rbasak> Right - I see. 0.13.0 is latest release which we haven't updated either, and 0.14 has Python 3 and needs a release. I get it now :)
[14:32] <stokachu> rbasak: looks like 0.14 will be release may 15th
[14:32] <stokachu> so i can follow up with those bugs after that
[14:33] <stokachu> once this is done then we could look at making the jujuclient python3
[14:33] <stokachu> i think the websocket part was the only blocker
[14:36] <rbasak> Sounds great!
[14:36] <rbasak> Though I wonder if you still want to support 2, for other platforms that don't have 3 yet? Or do they all have 3 now?
[14:36]  * rbasak only uses Ubuntu
[14:43] <stokachu> rbasak: that's a hazmat question re: py2 support :)
[14:43] <stokachu> i dont think any other distro support python3 websocket-client yet
[15:05] <mhall119> jose: marcoceppi: is there a way for me to check the current relation value between 2 services?
[15:05] <jose> mhall119: `relation-get value` will return it
[15:05] <mhall119> jose: from my host, not the instance?
[15:06] <jose> oh
[15:06] <jose> hmm, I think not, maybe Marco will be able to help with that
[15:06] <jose> but if you want to check a consistent value, `juju debug-hooks unit/#` and then `juju set servicename` will get you in a hook environment
[15:07] <jose> actually, debug-hooks and then join the relation or destroy it
[15:25] <jose> mhall119: I'm checking the README and just a few things:
[15:25] <jose> we've moved to Markdown so that won't render properly
[15:25] <jose> and `charm add readme` should give you the boilerplate README to just copy and paste that
[15:26] <jose> also, Contact Information listed there is for upstream (which is good) but we also want people to be able to report bugs on the charm itself
[15:36] <tvansteenburgh> jose: ack. thanks for all the contributions man, you're rockin' it
[15:38] <jose> tvansteenburgh: oh, you have a min?
[15:38] <jose> tests are not going well :(
[15:38] <tvansteenburgh> jose: yep, i got time
[15:38] <jose> well, I'm using *exactly* the same tests as before (which passed) but they're now giving a timeout error
[15:39] <tvansteenburgh> hrm. if you pastebin the test i can try to help debug
[15:39] <tvansteenburgh> or push the branch (if you haven't yet)
[15:39]  * jose does
[15:41]  * tvansteenburgh pulls branch
[15:41] <jose> \o/
[15:50] <tvansteenburgh> jose: had some vm issues, running test now
[15:50] <jose> cool, thank you!
[15:58] <jose> I'm really surprised - the rev queue is now short!
[16:05] <mattrae_> hi guys, i'm using the openstack provider with juju 1.18.. i'm able to bootstrap after doing the metadata setup.. but i'm wondering if i'm doing it the recommended way if someone can review: http://pastebin.com/hERMpCiA
[16:09] <tvansteenburgh> jose: still investigating
[16:09] <jose> np, I have time :)
[16:10] <tvansteenburgh> jose: changing conference rooms, i'll brb
[16:10] <jose> ok!
[16:27] <tvansteenburgh> jose: this is where things are failing for me: http://pastebin.ubuntu.com/7374048/
[16:28] <jose> hmm, maybe you hit a server during downtime?
[16:29] <tvansteenburgh> jose: when your test times out, what's the tail of ~/.juju/local/log/unit-nyancat-0.log ?
[16:29] <jose> I use ec2 for testing :P
[16:30] <tvansteenburgh> ah
[16:30] <jose> local would literally take an hour
[16:31] <jose> it does throw an error, though, let me try and run the test right now
[16:32] <tvansteenburgh> yeah, or ssh to the ec2 instance and check the log there
[16:33] <jose> before it dies
[16:33] <jose> will do
[16:40] <mhall119> just wasted over an hour trying to figure out why my hooks were failing....because I used /bin/sh instead of /bin/bash :(
[16:46] <jose> tvansteenburgh: I think I now found the error
[16:46] <jose> for some reason it's not opening the correct port
[16:49] <jose> it installed correctly, so looks like that prob was on your side
[16:49] <tvansteenburgh> ko
[16:49] <tvansteenburgh> ok
[16:50] <mhall119> jose: `charm add` says invalid subcommand
[16:50] <jose> mhall119: charm add readme?
[16:51] <jose> are you using an updated version of charm-tools?
[16:51] <mhall119> mhall@mhall-thinkpad:~/projects/Ubuntu/summit/charms/trusty/go-pronto$ charm add readme
[16:51] <mhall119> Error: add is not a valid subcommand
[16:51] <jose> looks like charm-tools needs some updating
[16:51] <mhall119> jose: charm-tools: Installed: 1.0.0-0ubuntu2 Candidate: 1.0.0-0ubuntu2
[16:52] <jose> hmm, that's the one I'm using
[16:53] <jose> mhall119: oh, can you try with `juju charm add readme`?
[16:54] <jose> anyways, http://paste.ubuntu.com/7374204/ has the contents
[16:57] <d3lxa> hello, during a juju bootstrap on azure, it does apt-get aptitude but it never returns, any idea please?
[16:59] <jose> d3lxa: can you explain a little bit more, please?
[16:59] <d3lxa> jose: we are using trusty, juju 1.18.2-trusty-amd64
[16:59] <jose> d3lxa: I mean, about the error
[17:00] <d3lxa> when I do a juju debootstrap -e azure, where azure was correctly configured
[17:00] <jose> debootstrap?
[17:00] <d3lxa> jose: there is no error, I looked at the bootstrap logs but nothing expect debug and regular noise
[17:00] <d3lxa> sorry bootstrap*
[17:00] <jose> does 'juju status' show a bootstrapped environment?
[17:01] <tvansteenburgh> jose: nyancat config-changed hook isn't symlinked
[17:01] <d3lxa> jose: yes, it is even usuable as if nothing was wrong
[17:01] <jose> d3lxa: can you go a little bit more in detail about what the *exact* error is?
[17:01] <jose> tvansteenburgh: let me check
[17:01] <d3lxa> but it is hanging somewhere
[17:01] <jose> d3lxa: can you post some logs?
[17:02] <jose> tvansteenburgh: good catch! thanks a lot!
[17:02] <tvansteenburgh> jose: you bet - we both missed the obvious :P
[17:03] <d3lxa> jose: cloud init output on the remote vm http://sprunge.us/BDYU
[17:03] <jose> tvansteenburgh: I'm sure I also missed that one when I forgot bzr adding
[17:03] <jose> d3lxa: checking now
[17:03] <tvansteenburgh> jose: ah, yeah that makes sense
[17:04] <jose> d3lxa: let's be honest, I don't find any errors there
[17:04] <jose> it looks like everything's running smoothly
[17:04] <d3lxa> jose: that's what I'm saying, there is no error but juju bootstrap hang
[17:04] <jose> oh
[17:05] <d3lxa> it never returns after printing "apt-get update"
[17:05] <jose> can you paste the log of the terminal where you ran the bootstrap, please?
[17:05] <d3lxa> so what I've done to bypass, is: to kill juju hardly with -9 or to just put it into backgrond (^Z) and live with that
[17:05] <d3lxa> (kill the juju bootstrap of course, not jujud)
[17:06] <d3lxa> but it wasn't doing this in the old version, so I guess this is a regression
[17:06] <jose> d3lxa: ^
[17:06] <d3lxa> sorry, doing it right now
[17:06] <jose> np :)
[17:06] <d3lxa> jose: http://sprunge.us/hVSC
[17:07] <d3lxa> it was upgrade, my bad
[17:07] <jose> you know what, let me go ahead, get that free azure credit and test for you :)
[17:08] <d3lxa> jose: you have one and you can test? would be great thx
[17:09] <jose> d3lxa: I'll be using their free trial, I'll test as soon as I get it
[17:09] <jose> I'll let you know if I find something
[17:09] <d3lxa> jose: great thx, in that case, will have to report?
[17:10] <jose> d3lxa: yeah, if it repeats here then we'll report a bug
[17:19] <jose> d3lxa: if you give me a moment I'll go ahead and test
[17:19] <jose> I'm finishing to set up
[17:24] <jose> d3lxa: question, still around?
[17:24] <d3lxa> jose: so it doesn't hang on yours?
[17:25] <jose> d3lxa: no, I have a question
[17:25] <d3lxa> yes?
[17:25] <jose> what should I put in storage-account-name? a random value?
[17:25]  * jose has never used azure before
[17:26] <d3lxa> jose: there is a quick guide https://juju.ubuntu.com/docs/config-azure.html very easy
[17:26] <jose> blargh, that happens to me for not checking the docs
[17:26] <jose> thanks!
[17:30] <d3lxa> :)
[17:33] <mattrae_> hi, i exported abundle from juju-gui.. 'juju bundle proof openstack-bundle.yaml' errors with 'FATAL: Not a bundle'
[17:33] <mattrae_> is that supposed to work?
[17:35] <jose> mattrae_: can you please pastebin the contents of the bundle?
[17:36] <jose> tvansteenburgh: around?
[17:36] <mattrae_> jose: here's the bundle http://pastebin.com/ED30UJKg
[17:37] <jose> mattrae_: oh, I think you didn't export a bundle, but exported the environment itself
[17:37] <jose> not sure if it's the same thing
[17:37] <bac> hi mattrae_, the export is jus the yaml file.  to be an actual bundle you've got to put it in a directory
[17:37] <mattrae_> jose: hmm the juju button in juju-gui says "export bundle"
[17:38] <jose> there you go :)
[17:38] <mattrae_> bac: ahh cool
[17:38] <bac> in that dir you have the yaml file named bundles.yaml and you need a README
[17:38] <mattrae_> sweet, i'll give that a try
[17:38] <bac> mattrae_: you can look at some existing bundles to see examples
[17:38] <mattrae_> cool i'll check out some existing bundles. thanks jose and bac
[17:38] <bac> mattrae_: also, you'll need to rename 'envExport' in the yaml file to be a real name
[17:46] <jose> guys, I'm having a problem when bootstrapping with azure
[17:46] <jose> http://paste.ubuntu.com/7374531/
[17:55] <d3lxa> jose: tried?
[17:55] <jose> d3lxa: I get ^ when bootstrapping
[17:56] <sarnold> jose: it might be a good idea to file a bug on that one, I dunno what your configuration looked like but it'd be nice if the parser were extended to handle it better than that :) hehe
[17:57] <jose> sarnold: you mean, for the error I got?
[17:57] <jose> with all that LP stuff?
[17:57] <sarnold> jose: yeah
[17:57] <jose> will do now :)
[17:57] <jose> thanks!
[17:57] <jose> d3lxa: I also recommend you file a bug against that problem, and if anyone else is able to replicate it we'll confirm
[17:57] <jose> sorry for not being able to help right now
[18:09] <jose> sarnold: do you by chance know if destroy-relation == remove-relation?
[18:09] <sarnold> jose: no idea, sorry
[18:09] <jose> np
[18:23] <jose> d3lxa: hey, I'm bootstrapping on azure right now, will see if it presents the same error
[18:26] <jose> d3lxa: I think I reproduced it. congratulations, you found a bug
[18:36] <mattrae_> hmm following the 'juju quickstart bundles.yaml' example from the docs gives error 'unrecognized command; juju quickstart'.. is there a suggested way to deploy bundles?
[18:39] <mattrae_> aha appears there is a juju-bundle command
[18:43] <magicrobotmonkey> whats it mean when my node doesn't reboot after cloud-init?
[18:44] <d3lxa> jose: ok, so I'll need to report the bug?
[18:47] <magicrobotmonkey> I'm having a problem with the cinder charm. My block device isn't in /dev
[18:48] <jose> d3lxa: yep, just go ahead
[18:57] <tvansteenburgh> jose: don
[18:57] <tvansteenburgh> don
[18:57] <tvansteenburgh> dammit
[18:57] <tvansteenburgh> don't forget to push that config-changed symlink
[18:57] <jose> tvansteenburgh: yeah, will do, but looks like it doesn't fix the problem
[18:57] <tvansteenburgh> :(
[18:58] <jose> I'm going to grab lunch and check what's going on after that
[18:58] <tvansteenburgh> kk
[18:58] <jose> should be something pretty easy to fix
[19:00] <jose> tvansteenburgh: symlink pushed anyways
[20:38] <stokachu> is the password in the configuration for juju-gui the password for actually logging into the site?
[20:38] <stokachu> or is it for the api
[20:49] <lazyPower> stokachu: do you mean the admin-secret: value in environments.yaml?
[20:50] <stokachu> lazyPower: yea i believe so
[20:50] <stokachu> in local.jenv its just password:
[20:50] <lazyPower> stokachu: its the password for the GUI
[20:51] <stokachu> lazyPower: ok cool thanks!
[20:52] <lazyPower> np
[21:12] <stokachu> hmm doesn't seem to like that