lxd provider in master
Tim Penhey
tim.penhey at canonical.com
Mon Nov 23 23:53:33 UTC 2015
On 24/11/15 12:47, Tim Penhey wrote:
> On 24/11/15 04:53, Eric Snow wrote:
>> On Sun, Nov 22, 2015 at 8:50 PM, Tim Penhey <tim.penhey at canonical.com> wrote:
>>> Hi all,
>>>
>>> I noticed that the lxd provider was now in master and attempted to use
>>> it to help debug an HA problem.
>>>
>>> In environments.yaml file I added a very simple clause:
>>>
>>> lxd:
>>> type: lxd
>>
>> This is what I've been using. It works fine.
>>
>> This helps identify the problem. The environment you tried to
>> bootstrap has "container: lxd" and there is no "lxd" container type.
>> Perhaps it's an old environment, set up back when the LXD provider was
>> first prototyped (with its own container type)? It does not appear to
>> be the simple "lxd" environment you showed above.
>>
>> Also, FYI, "namespace" is still around but is not necessary. It is
>> useful when you want to have multiple LXD providers running on your
>> local LXD.
>
> found that further down the file I found this:
>
> lxd:
> type: local
> container: lxd
>
> That was causing problems :-)
>
> Got it bootstrapped now.
Oh... spoke too soon. Didn't use --upload-tools and ended up with:
Attempt 1 to download tools from
https://streams.canonical.com/juju/tools/devel/juju-1.26-alpha1-trusty-amd64.tgz...
tools from
https://streams.canonical.com/juju/tools/devel/juju-1.26-alpha1-trusty-amd64.tgz
downloaded: HTTP 200; time 24.512s; size 18804733 bytes; speed
767153.000 bytes/s Tools downloaded successfully.
31d31dd99ba3dd7bbb0671911d9c8fdf4f63e559b7726368c92f3ea76d3231c6
/var/lib/juju/tools/1.26-alpha1-trusty-amd64/tools.tar.gz
2015-11-23 23:48:24 INFO juju.cmd supercommand.go:58 running jujud
[1.26-alpha1 gc]
2015-11-23 23:48:24 DEBUG juju.agent agent.go:525 read agent config,
format "1.18"
2015-11-23 23:48:24 INFO juju.network network.go:242 setting prefer-ipv6
to false
2015-11-23 23:48:24 ERROR cmd supercommand.go:444 no registered provider
for "lxd"
2015-11-23 23:48:25 ERROR cmd supercommand.go:448 failed to bootstrap
environment: subprocess encountered error code 1
$ juju status
-- just hangs
So bootstrap failed, but the provider failed to clean up after itself.
http://pad.lv/1519128
Tim
More information about the Juju-dev
mailing list