[10:29] <magicaltrout> if the charm store says X revisions
[10:29] <magicaltrout> is it possible to find out when the last one was?
[10:43] <kjackal> magicaltrout: try "charm show". There is an "archive-upload-time" field that might be the one you need
[11:13] <rick_h> magicaltrout: so that's going away. It's not really true at this point and is from trying to tie the source control/etc into the charm metadata.
[11:13] <rick_h> magicaltrout: that's a good point if you're looking for some sort of "last time updated" which we can do with when things were pushed to the channel in the store.
[11:54] <magicaltrout> thanks chaps
[13:23] <SimonKLB> tvansteenburgh1 lazyPower bundletester in charmbox still seem to experience https://github.com/juju-solutions/bundletester/issues/108
[13:24] <SimonKLB> bundletester is on 0.12.2 though
[13:25] <lazyPower> SimonKLB: i executed a test on a freshly bootstrapped controller. what is your substrate that you're encountering this issue?
[13:25] <SimonKLB> lazyPower: i think there might be something else that is bringing in the latest version of the websocket-client
[13:26] <lazyPower> i wonder if matrix is bringing that in
[13:26] <lazyPower> but whats weird is that i didn't run into that
[13:26] <lazyPower> nor did kwmonroe_
[13:27] <SimonKLB> lazyPower: im not running matrix
[13:27] <SimonKLB> could it be amulet?
[13:27] <lazyPower> SimonKLB: referring to something else bringing in that latest version fo wsc
[13:27] <lazyPower> SimonKLB: rebuild omitting these lines of the setup https://github.com/juju-solutions/charmbox/blob/master/charmbox-setup.sh#L37-L41
[13:27] <lazyPower> SimonKLB: lmk if that resolves the issue for you
[13:29] <tvansteenburgh1> if it were that, wouldn't it have broken for you too?
[13:29] <lazyPower> it depends on juju and theblues, both of which i believe pull in websocket-client
[13:29] <lazyPower> tvansteenburgh: i woudl think so but i'm unsure if simon is still broken and i wasnt' on a fresh bootstrap
[13:29] <lazyPower> i'm not terribly familiar with this issue
[13:42] <SimonKLB> lazyPower: tvansteenburgh it's libjuju
[13:42] <SimonKLB> or maybe not
[13:42] <SimonKLB> :D
[13:43] <SimonKLB> Collecting websocket-client>=0.18.0 (from jujuclient>=0.53->juju-deployer->-r /tmp/bundletester-KlKNGV/charmscaler/test-requirements.txt (line 3))
[13:43] <SimonKLB>   Downloading websocket_client-0.44.0-py2.py3-none-any.whl (199kB)
[13:43] <SimonKLB> juju-deployer ?
[13:44] <lazyPower> well thats coming from apt
[13:44] <lazyPower> interesting
[13:44] <lazyPower> unless one of these from source installs is overriding it
[13:44] <SimonKLB> lazyPower: i had juju-deployer in my test-requiremets.txt
[13:45] <SimonKLB> that might not even be necessary
[13:45] <SimonKLB> i think it was before i started using charmbox and needed to install it myself?
[13:50] <SimonKLB> lazyPower: removing it made the test run at least, but not sure if the best solution is to remove it since people not running tests inside charmbox will be required to install it via apt first then, right?
[13:50] <SimonKLB> just don't want to shoot myself in the foot here by simply removing it
[13:52] <lazyPower> SimonKLB: fair, can you get a bug filed on the repo? I dont want ot lose track of this and we shoudl collab around it on the issue
[13:52] <tvansteenburgh> wait
[13:52] <tvansteenburgh> there's already a bug
[13:52] <SimonKLB> tvansteenburgh: want me to just mention juju-deployer in the bundletester issue?
[13:53] <tvansteenburgh> sure, that's fine. fixing this https://github.com/juju-solutions/bundletester/issues/108 is the correct fix
[13:54] <lazyPower> tvansteenburgh: is that going to be published to the ppa or should we move charmbox to install from pypi?
[13:55] <tvansteenburgh> what, bundletester?
[13:55] <lazyPower> yes
[13:55] <tvansteenburgh> bundletester has always been installed from pypi, it doesn't exist in a ppa
[13:55] <lazyPower> tvansteenburgh: the thing is juju-deployer is coming from the ppa, bundletester is already being installed from pypi
[13:56] <SimonKLB> https://github.com/juju-solutions/bundletester/issues/108#issuecomment-311365889
[14:12] <vlad___> Hey guys does anyone know of a way to log into a node before juju has acquired it from maas? I can't get an answer in other IRCs and found no docs on it.
[14:13] <rick_h> vlad___: ? juju acquires it pretty much right away. Juju provides init script data as part of starting the machine.
[14:13] <rick_h> vlad___: I think there's some maas script stuff you can inject in there as part of the startup script that can be in addition to
[14:13]  * rick_h goes to look
[14:14] <vlad___> rick_h: Awesome thanks for the quick and informative answer!
[14:15] <rick_h> vlad___: check out https://askubuntu.com/questions/636837/are-there-examples-of-custom-installation-scripts
[14:17] <vlad___> rick_h: Thanks again going under to read
[14:22] <rick_h> vlad___: hmm, so in the maas docs it says "The older debian-installer (preseed) method has been removed. Some remnants of preseed may still be found however. See /etc/maas/preseed directory."
[14:22] <rick_h> vlad___: that seems to be the way to do this type of thing I think per http://caribou.kamikamamak.com/2015/06/26/custom-partitioning-with-maas-and-curtin-2/ and https://www.stackevolution.com/node/17
[14:22] <rick_h> vlad___: best I can come up with atm
[14:25] <vlad___> rick_h: Awesome!
[15:18] <kwmonroe> SimonKLB: i was watching your bundletester chatter with lazyPower, and it just dawned on me.. did you bundletest against a jaas controller?
[16:05] <vds> Hi all, I'm having issues in bootstrapping an openstack cloud: https://paste.ubuntu.com/24964072/
[16:06] <vds> username, password and project id are correct, how do I get more information about what is going wrong
[16:21] <rick_h> vds: so you can try adding --debug but I think it'll show the same. Is the auth endpoint right as well?
[16:23] <vds> rick_h: one thing I don't understand is : 16:21:07 INFO  cmd cmd.go:141 no credentials found, checking environment
[16:23] <vds> rick_h: but I did add the credentials...
[16:24] <rick_h> vds: if you run juju show-credentials they're listed?
[16:24] <rick_h> sorry, juju credentials
[16:26] <vds> rick_h: yep
[16:29] <vds> this is what I get with --debug https://paste.ubuntu.com/24964310/
[16:36] <rick_h> hmm, beisner any hint on the service urls bit from ^ ?
[17:48] <Budgie^Smore> o/ juju world