[13:15] <imrankhakoo> hello, i'm having issues bootstrapping a bionic juju controller. I'm not seeing anything obviously wrong in  the cloud-init logs of the bootstrap node, but it's stuck with the following output:
[13:16] <imrankhakoo> Launching controller instance(s) on maas...
[13:16] <imrankhakoo>  - xbcq4n (arch=amd64 mem=4G cores=1)
[13:16] <imrankhakoo> Installing Juju agent on bootstrap instance
[13:16] <imrankhakoo> Fetching Juju GUI 2.12.1
[13:16] <imrankhakoo> Waiting for address
[13:16] <imrankhakoo> Attempting to connect to 10.1.1.118:22
[13:16] <imrankhakoo> Connected to 10.1.1.118
[13:16] <imrankhakoo> Running machine configuration script...
[13:17] <imrankhakoo> any ideas? This worked fine 2 weeks ago. i did do an apt upgrade in the meantime, so possibly a regression?
[13:31] <gnuoy> Am I right in thinking there is no way to influence where juju looks locally for a charm? I have a bundle that references a local copy of a charm and I'd like the ability to influence where juju looks for that local charm. There used to be JUJU_REPOSITORY env variable or juju deploy --repository= but it seems both are gone
[13:31] <gnuoy> https://jujucharms.com/docs/2.3/reference-environment-variables#juju_repository-(deprecated)
[13:51] <balloons> gnuoy, you can specify path to the charm when deploying. Does that help?
[13:51] <gnuoy> balloons, in a bundle ?
[13:51] <balloons> imrankhakoo, does the container have networking connectivity if you ssh in?
[13:51] <balloons> imrankhakoo, are you running lxd 3.0 now?
[13:52] <gnuoy> balloons, actually, the desire is that the bundle has "charm: ./myapp" rather than any other path
[13:53] <balloons> gnuoy, I think this will help: https://jujucharms.com/docs/2.3/charms-offline-deploying
[13:58] <gnuoy> balloons, I've been a bit vague about my use case, sorry. Basically I want to include an example bundle with a charm and be able to run it irrespective of where the charm has been downloaded too. I had originally used a relative path in the bundle "charm: ../../app" but I'd rather do "charm: ./app" and somehow manipualte where juju looks for the local charm. I'm really after exactly what JUJU_REPOSITORY env variable used to do
[14:31] <cory_fu> jamespage: Any objection to me cutting a release of charmhelpers?  It seems that https://github.com/juju/charm-helpers/pull/150 at least is critical for several charms, including CDK
[14:39] <balloons> gnuoy, sadly I don't know the answer, but I think it should be possible
[14:54] <cory_fu> I'll take that as "no problem"  ;)
[15:05] <cory_fu> Cynerva, tvansteenburgh: 0.18.8 is release
[15:05] <cory_fu> d
[15:06] <Cynerva> thanks cory_fu