[00:13] <wililupy> Question: I just installed juju on 16.04 from repo (juju 2.0 beta15) and when I try to connect to the gui, it says connecting to Juju model and never goes past. Nothing in the logs looks suspicious other than in the machine-0.log there is an entry about reconfiguring lxd using dpkg and setup lxcbr0 which I do, but still nothing. Rebooted the controller and I had to tell Firefox to delete the SSL certificate for the server and
[00:13] <wililupy> have it re-issue it so that I could connect again, but same results.
[00:13] <bdx> wililupy: add juju/stable first ...
[00:13] <wililupy> bdx even on xenial?
[00:13] <bdx> wililupy: `sudo add-apt-repository ppa:juju/stable`
[00:14] <bdx> wililupy: yea ... not for much longer I think ..
[00:22] <wililupy> bdx: I'm updating it right now. Do I have to re-bootstrap?
[00:22] <bdx> wililupy: yes
[00:22] <bdx> wililupy: `rm -rf ~/.local/share/juju` too
[00:22] <wililupy> bdx: ack.
[00:47] <wililupy> bdx: That fixed it. Thank you so much. I eventually probably would have done that, but I was hoping not having to add a ppa.
[08:55] <admcleod_> magicaltrout: yep
[08:56] <magicaltrout> unlucky
[17:22] <bdx> lutostag, beisner, marcoceppi: where might one find the interfaces for the charm-jenkins charm?
[17:25] <beisner> marcoceppi, bdx, it looks like they're not in http://interfaces.juju.solutions  :-/
[17:27] <beisner> marcoceppi, bdx, i previously built using https://github.com/freeekanayaka/interface-jenkins-slave, which really should make it into jenkins upstream along side the jenkins-charm layer repo.
[17:29] <bdx> beisner: nice, thanks
[17:29] <bdx> looks like free has the other interfaces stashed there too :-)
[17:34] <jamespage> cory_fu, so the tweaks to bundletester config did not explode in the gate - https://review.openstack.org/#/c/395574/
[17:35] <cory_fu> jamespage: That's good.  We didn't get that rabbitmq branch into CWR, though, unfortunately.  Is that still something you need?
[17:36] <jamespage> cory_fu, it would be helpful to get this right first time - however if its alot of effort, we can probably get away with landing the changes and testing in stable, but that's not ideal
[17:37] <kwmonroe> cory_fu: jamespage:  the rabbit charm made it into cwr, just not in time for the overnight runs.  i'm pretty sure it'll be picked up when they kick off today.
[17:38] <jamespage> kwmonroe, based on my test charm under ~james-page right?
[17:38] <kwmonroe> correct jamespage
[17:38] <kwmonroe> cs:~james-page/rabbitmq-server-requirement
[17:38] <cory_fu> Yeah, sorry, I meant what kwmonroe said
[17:39] <cory_fu> jamespage: It will be run automatically this evening, but if need be, we could kick it off manually sooner, though I think it would still take a while before it actually runs
[17:39] <cory_fu> That CI infra is pretty over-committed, from what I can tell
[17:40] <jamespage> cory_fu, I just synced it up so I'll look am tomorrow
[17:40] <kwmonroe> tvansteenburgh1: it appears i'm hosting a timtimtim model in azure-east.  pretty sure that was for long-ago k8s test.  cool if i destroy that?
[17:40] <cory_fu> Ok
[17:40] <tvansteenburgh1> kwmonroe: yes
[17:40] <kwmonroe> thx
[17:41] <beisner> woot thanks jamespage cory_fu
[18:11] <deanman> Does anyone have a sample of yaml config file to be used during bootstrap. Cannot find any reference on the docs, only for charms.
[18:25] <lazyPower> deanman - its just a key: value map.   http://paste.ubuntu.com/23457321/
[18:26] <deanman> lazyPower: ok got it! Thanks
[18:47] <deanman> lazyPower: Can you put comments and/or environmental variables as values?
[18:47] <lazyPower> in yaml?
[18:48] <lazyPower> no, you would need to render it through a template wizard like envtemplate or something.
[18:48] <lazyPower> however, comments should be just fine, you can prefix a comment in yaml with #
[18:48] <deanman> lazyPower: ok thats seems reasonable!
[20:11] <deanman> Is it possible to `juju run` using a command that takes arguments? A simple `tail -f` seems to give an error with "flag provided but not defined: -f"
[20:13] <lazyPower> deanman - you'll need to quote the command
[20:13] <lazyPower> eg: juju run --application foobar "ls -al && whoami"
[20:16] <lutostag> any way to move bootstrap to a different ip/machine on 1.25.x? Our bootstrap node has run out of disk space. (Or a way to purge unused data from /var/lib/juju would work too)?
[20:17] <deanman> lazyPower: Shouldn't this work ? juju run -m controller --machine 0 "tail -f /var/log/juju/machine-0.log"
[20:17] <lazyPower> lutostag - thats rough, i think the option is to either go HA (probably not going to solve disk space issues) or to purge the cache/logs/whatever-is-using-the-diskspace
[20:17] <deanman> it just hangs
[20:17] <lazyPower> deanman - its async i think,s o you wont see the output until the command terminates
[20:17] <lazyPower> deanman - you should probably juju ssh into the unit if you need to tail logs.
[20:18] <deanman> ok lazyPower
[20:19] <lutostag> lazyPower: is /var/lib/juju/charm-get-cache safe to boot into the bit-bucket in the sky?
[20:20] <lazyPower> i think so, i'm fairly certain it will just replace whatever it needs that it doesn't find in the cache
[20:20] <lazyPower> *but*
[20:20] <lazyPower> with that being said, i haven't done it myself, so it might break things in unexpected ways
[20:20] <lazyPower> lutostag - i would highly recommend we file a bug about this so we can add an operational action to the controller to purge temporary/unneccesary data in the event this happens
[20:20] <lutostag> lazyPower: ack will find/create a bug
[20:23] <deanman> lazyPower: somehow even juju run -m controller --machine 0 "ls -al" hangs there.
[20:23] <lazyPower> mattrae ping
[20:36] <babbageclunk> deanman: does `juju ssh -m controller 0` work?
[20:38] <lazyPower> deanman - yeah that doesn't sound good. give babbageclunk's suggestion a go
[20:48] <deanman> babbageclunk: it does but i have since restarted the VM and now even run works
[20:48] <babbageclunk> deanman: sounds like sshd was having a bad time.
[20:49] <deanman> babbageclunk: it does take though like 5 seconds for a whoami
[20:49] <deanman> babbageclunk: is that normal?
[20:52] <babbageclunk> deanman: no that sounds very slow...
[20:54] <deanman> babbageclunk: http://paste.ubuntu.com/23457920/
[20:54] <deanman> seems like the previous command "tail -f" makes it unresponsive
[20:56] <babbageclunk> deanman: yeah, I see the same behaviour - can you file a bug for that?
[20:57] <deanman> `juju ssh` makes it recover somehow
[20:57] <deanman> sure babbageclunk !
[20:58] <babbageclunk> deanman: Thanks!
[20:59] <deanman> babbageclunk: can you `time juju run -m controller --machine - "whoami" for me and tell me what's your average?
[21:00] <deanman> i get 2-5 secs
[21:01] <babbageclunk> deanman: yeah, I get the same - 5 seconds sounded slow until I tried it.
[21:08] <deanman> babbageclunk: https://bugs.launchpad.net/juju/+bug/1640938
[21:08] <mup> Bug #1640938: `juju run` becomes unresponsive in consecutive runs when previous command passed is `tail -f` <juju:New> <https://launchpad.net/bugs/1640938>
[21:09] <babbageclunk> deanman: great thanks
[21:09] <deanman> Cheers!
[21:15] <lazyPower> babbageclunk - that tail -f doesn't exit, and i'm pretty sure that its just hanging the ssh session until timeout
[21:15] <lazyPower> deanman - humor me and try the tail with something like a -n 100  and omit the -f
[21:16] <babbageclunk> lazyPower: Oh, I think that's right, I'm just surprised that killing the run command doesn't kill the tail.
[21:25] <jproulx> Having trouble with image-metadata bootstrapping private cloud, have meta data json in ~/simplestreams as described in "getting" started but no matter how I feed it in keep getting
[21:25] <jproulx>  ERROR failed to bootstrap model: no image metadata found
[21:25] <jproulx> tried both --metadata-source=~/simplestreams and webserver using --config image-metadata-url=https://people.csail.mit.edu/jon/simplestreams amoung other things....Help?
[21:25] <jproulx> oh juju-2.0 on xenial
[21:30] <lazyPower> jproulx - i'm not as familiar with the clouds that require manual provisioning of simplestreams, however if you dont get an answer here in a timely fashion, the mailing list is an excellent resource for help with problems like that. https://lists.ubuntu.com/mailman/listinfo/juju
[21:31] <jproulx>  lazyPower: thanks for the pointer
[21:40] <mattrae> lazyPower: hey saw your ping :)
[21:40] <lazyPower> mattrae - found the answer already, thanks for pong'ing
[21:40] <mattrae> cool no problem :)