Manual provisioning - feedback wanted

Andrew Wilkins andrew.wilkins at canonical.com
Mon Sep 16 01:38:44 UTC 2013


Hi Matt,

It looks like a bug with address resolution. IF you have a DNS entry for
your digital ocean box, please try using that in the "ssh:..." target.
I'll try and reproduce the issue later - I've logged a bug for now.

Cheers,
Andrew


On Mon, Sep 16, 2013 at 4:59 AM, Matthew Williams <
matthew.williams at canonical.com> wrote:

> Sounds like a cool feature. I tried bootstrapping in aws then adding a
> machine supplied by digital ocean. I got an invalid domain error. Any idea
> what I was doing wrong?
>
> juju add-machine -v ssh:root at 162.243.10.110
> 2013-09-15 20:06:07 INFO juju.provider.ec2 ec2.go:187 opening environment
> "amazon"
> 2013-09-15 20:06:12 INFO juju.state open.go:68 opening state; mongo
> addresses: ["ec2-54-221-71-210.co
> mpute-1.amazonaws.com:37017"]; entity ""
> 2013-09-15 20:06:15 INFO juju.state open.go:106 connection established
> 2013-09-15 20:06:18 INFO juju.provider.ec2 ec2.go:187 opening environment
> "amazon"
> 2013-09-15 20:06:18 ERROR juju supercommand.go:282 command failed: lookup
> 162.243.10.110: invalid dom
> ain name
> error: lookup 162.243.10.110: invalid domain name
>
> Matt
>
>
>
> On Tue, Sep 10, 2013 at 10:56 AM, Andreas Hasenack <andreas at canonical.com>wrote:
>
>> On Tue, Sep 10, 2013 at 10:17 AM, Andrew Wilkins <
>> andrew.wilkins at canonical.com> wrote:
>>
>>> On Tue, Sep 10, 2013 at 4:18 PM, Andreas Hasenack <andreas at 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 at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130916/28edca0b/attachment.html>


More information about the Juju mailing list