Manual provisioning - feedback wanted

Andrew Wilkins andrew.wilkins at canonical.com
Tue Sep 10 01:08:44 UTC 2013


On Mon, Sep 9, 2013 at 9:39 PM, Andreas Hasenack <andreas at canonical.com>wrote:

> Here is what I just tried with juju-core trunk (r1772):
>

Thanks for trying it out.


> $ sudo $(which juju) bootstrap
> $ juju status
> environment: local
> machines:
>   "0":
>     agent-state: started
>     agent-version: 1.15.0.1
>     dns-name: 10.0.3.1
>     instance-id: localhost
>     series: raring
> services: {}
> $ sudo lxc-list
> WARNING: lxc-list is deprecated, please use lxc-ls --fancy.
>          This symlink will be dropped in LXC 1.0.
>
> NAME       STATE    IPV4       IPV6  AUTOSTART
> ----------------------------------------------
> precise-1  RUNNING  10.0.3.53  -     NO
> saucy      STOPPED  -          -     NO
>
> $ juju add-machine ssh:andreas at 10.0.3.53 -v
> 2013-09-09 13:35:41 INFO juju.provider.local environprovider.go:32 opening
> environment "local"
> 2013-09-09 13:35:41 INFO juju.state open.go:68 opening state; mongo
> addresses: ["10.0.3.1:37017"]; entity ""
> 2013-09-09 13:35:41 INFO juju.state open.go:106 connection established
> 2013-09-09 13:35:41 INFO juju.provider.local environprovider.go:32 opening
> environment "local"
> 2013-09-09 13:35:41 ERROR juju supercommand.go:282 command failed: machine
> is already provisioned
> error: machine is already provisioned
>
> Was this supposed to work?
>

I take it you had an existing container? One of the first things
"add-machine ssh:..." will do is execute "ls /etc/init/juju*". If it comes
back non-empty, then it won't let you proceed. Is your container a leftover?

Cheers,
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130910/8f4f53c9/attachment.html>


More information about the Juju mailing list