On Tue, Sep 10, 2013 at 10:17 AM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> On Tue, Sep 10, 2013 at 4:18 PM, Andreas Hasenack
> <andr...@canonical.com>wrote:
>
>> The 10.0.3.53 "machine" is a new container I brought up manually with
>> lxc-create and lxc-start. lxc-list above shows all containers, and it was
>> the only one running.
>>
>> Right now I have this output for that ls command:
>> # ls /etc/init/juju*
>> /etc/init/juju-agent-andreas-local.conf
>> /etc/init/juju-db-andreas-local.conf
>>
>
> As discussed on IRC: the command will be run in the target (the
> container), not the local host.
>
>
>> juju lxc is bootstrapped, but no units are running, and lxc-list shows
>> my both containers stopped.
>>
>
> I'm creating a new container on my laptop now, using your configuration.
> I'll let you know what I find.
>
>
It's because of this ssh warning:
$ ssh 10.0.3.230 "ls /etc/init/ | grep juju.*\\.conf || exit 0"
Warning: Permanently added '10.0.3.230' (ECDSA) to the list of known hosts.
$
The code grabs both stderr and stdout and checks for len > 0:
out, err := cmd.CombinedOutput()
(...)
return len(strings.TrimSpace(string(out))) > 0, nil
> Cheers,
> Andrew
>
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
