[06:27] <anrah> jproulx: are you using openstack?
[09:11] <deanman> lazyPower: As babba pointed out that `tail -n 100` works just fine.
[09:22] <jamespage> cory_fu, tvansteenburgh: urgh
[09:22] <jamespage> theblues.errors.ServerError: Request timed out: https://api.jujucharms.com/v4/~openstack-charmers-next/trusty/cinder/meta/any?include=bundle-machine-count&include=bundle-metadata&include=bundle-unit-count&include=bundles-containing&include=charm-actions&include=charm-config&include=charm-metadata&include=common-info&include=extra-info&include=revision-info&include=stats&include=supported-series&include=manifest&include=tags&include=promulgated
[09:22] <jamespage> &include=perm&include=id timeout: 3.05
[09:22] <jamespage> well at least its having a run at the tests now
[10:55] <stub> Did we have an etcd layer available? I only see the interface, but could have sworn there was a layer
[12:28] <beisner> jamespage, cory_fu - fyi, seeing that in osci too.  the theblues default 3s timeout is increasingly not enough time.  https://github.com/juju/theblues/issues/49
[13:04] <BlackDex> Hello there, how do i select a specific juju version after it has been installed?
[13:04] <BlackDex> i mean charm
[13:04] <BlackDex> so charm-5 is installed and i want to install charm-7 for instance
[13:05] <BlackDex> ah upgrade-charm --revision i think
[13:06] <BlackDex> was searching for a while, and after typing here i got it
[13:37] <junaidali> Hi everyone, is it possible to deploy charms with one bundle and add relations with another one?
[13:39] <anrah> junaidali: yes it is
[13:41] <junaidali> anrah, when i try to add relations with the bundle that only have relations int it,  it gives error that the charm is not defined in the bundle (for each charm relation though the charms are deployed).
[13:41] <junaidali> in it*
[13:42] <anrah> oh sorry, misread your question
[13:42] <junaidali> np :)
[13:43] <anrah> I don't think that is possible, I always introduce the relations on the bundle where I have the applications
[16:39] <beisner> stub, one of the 3 nov 10 commits appears to have broken juju-wait on subordinates.  getting ERROR:root:error: The following run targets are not valid: "" is not a valid unit name
[16:40] <beisner> stub, also, that broke the case where we bootstrap then juju-wait.  in that case there are no applications/services with units.
[16:44] <beisner> stub, https://bugs.launchpad.net/juju-wait/+bug/1641163
[16:44] <mup> Bug #1641163: The following run targets are not valid: "" is not a valid unit name <uosci> <Juju Wait Plugin:New> <https://launchpad.net/bugs/1641163>
[17:39] <stub> beisner: is this from mojo? I didn't think I'd released
[17:40] <beisner> stub, we consume tip of juju-wait ;-)   well, we did.  having to fork, rewind and pin for now to unblock our gate.
[17:41] <stub> ha. ok, thanks for the heads up then. It should be an easy fix.
[17:42] <stub> Its going to bite mojo too, so I'll chase that
[17:43] <beisner> awesome, thanks stub
[19:12] <lazyPower> stub https://github.com/juju-solutions/layer-etcd
[19:18] <Soichi> Is there some guide on how to setup networking so that an LXD charm is accessible from other machines in the network?
[23:20] <bdx> hows it going everyone?
[23:20] <bdx> is it possible to pass a file as a string to an action?
[23:21] <bdx> e.g. juju run-action myapp/0 set-secrets secrets="$(cat barb-test.yaml)"
[23:21] <bdx> I'm getting ERROR json: unsupported type: map[interface {}]interface {}