openstack team mailing list archive

[Sébastien Han <han.sebastien@xxxxxxxxx>]

Perfect!
Yes in a multi-host scenario it's the IP address of the compute node itself
:)

Cheers!

On Thu, May 24, 2012 at 5:34 PM, Leander Bessa Beernaert <
leanderbb@xxxxxxxxx> wrote:

> Just a question i forgot, on a multi-host senario, the IP_CURRENT_NODE is
> the compute node's ip right? Currently i'm only running everything on a
> single host.
>
>
> On Thu, May 24, 2012 at 4:32 PM, Leander Bessa Beernaert <
> leanderbb@xxxxxxxxx> wrote:
>
>> Adding the following to my config file solved my problem!! Thanks!!
>>
>>    - routing_source_ip=IP_CURRENT_NODE
>>    - --my_ip=IP_CURRENT_NODE
>>
>> Regards,
>>
>> Leander
>>
>> On Thu, May 24, 2012 at 4:24 PM, Sébastien Han <han.sebastien@xxxxxxxxx>wrote:
>>
>>> It's not an open-ssh issue.
>>> Your virtual machine simply can't fetch the metadata, cloud-init can't
>>> to be more accurate. Without this your ssh key is not imported. This is why
>>> the machine is well running, you can ping it but you can't access it
>>> because the authorized_keys file on the vm is not fulfill.
>>> If you are only running a nova-compute node, installing
>>> nova-api-metadata will do the trick!
>>>
>>> Also verify those values in your nova.conf :
>>>
>>>    - --vncserver_proxyclient_address=IP_CURRENT_NODE
>>>    - --vncserver_listen=IP_CURRENT_NODE
>>>    - --ec2_dmz_host=IP_CURRENT_NODE
>>>    - --routing_source_ip=IP_CURRENT_NODE
>>>    - --my_ip=IP_CURRENT_NODE
>>>
>>> Let us know a little more about your setup :)
>>> Cheers!
>>>
>>>
>>>
>>> On Thu, May 24, 2012 at 4:01 PM, Leander Bessa Beernaert <
>>> leanderbb@xxxxxxxxx> wrote:
>>>
>>>> Compute log: Log: http://paste.openstack.org/show/18149/
>>>>
>>>> I've tried bot root and ubuntu as account names (ssh -i key.pem
>>>> root@10.1.2.3 and  ssh -i key.pem ubuntu@10.1.2.3) and the result is
>>>> still "Read from socket failed: Connection reset by peer"
>>>>
>>>>
>>>> On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert <
>>>> leanderbb@xxxxxxxxx> wrote:
>>>>
>>>>>
>>>>> Complete log: http://paste.openstack.org/show/18144/
>>>>>
>>>>> On Thu, May 24, 2012 at 1:49 PM, Anton Haldin <
>>>>> ahaldin@xxxxxxxxxxxxxxxx> wrote:
>>>>>
>>>>>> you can try to look in  console.log for this instance
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert <
>>>>>> leanderbb@xxxxxxxxx> wrote:
>>>>>>
>>>>>>> No, at the moment the vnc console isn't working yet. I haven't
>>>>>>> gotten that far yet.
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 24, 2012 at 1:29 PM, Anton Haldin <
>>>>>>> ahaldin@xxxxxxxxxxxxxxxx> wrote:
>>>>>>>
>>>>>>>> t can be an issue on OS side in instance ?
>>>>>>>>
>>>>>>>> do you have vnc access for this instance?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert <
>>>>>>>> leanderbb@xxxxxxxxx> wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I'm having trouble sshing into the created instances. At first i
>>>>>>>>> was getting the following error:
>>>>>>>>>
>>>>>>>>> ssh -i testkey.pem root@10.1.1.3 -v
>>>>>>>>>>
>>>>>>>>>> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
>>>>>>>>>>
>>>>>>>>>> debug1: Reading configuration data /etc/ssh/ssh_config
>>>>>>>>>>
>>>>>>>>>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>>>>>>>>>>
>>>>>>>>>> debug1: Connecting to 10.1.1.3 [10.1.1.3] port 22.
>>>>>>>>>>
>>>>>>>>>> debug1: Connection established.
>>>>>>>>>>
>>>>>>>>>> debug1: identity file testkey.pem type -1
>>>>>>>>>>
>>>>>>>>>> debug1: identity file testkey.pem-cert type -1
>>>>>>>>>>
>>>>>>>>>> debug1: Remote protocol version 2.0, remote software version
>>>>>>>>>>> OpenSSH_5.8p1 Debian-7ubuntu1
>>>>>>>>>>
>>>>>>>>>> debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH*
>>>>>>>>>>
>>>>>>>>>> debug1: Enabling compatibility mode for protocol 2.0
>>>>>>>>>>
>>>>>>>>>> debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
>>>>>>>>>>
>>>>>>>>>> debug1: SSH2_MSG_KEXINIT sent
>>>>>>>>>>
>>>>>>>>>> Read from socket failed: Connection reset by peer
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> I then proceeded to reboot the machine and all it's services.
>>>>>>>>> However, now i can't even get that far. I'm alway faced with a connection
>>>>>>>>> refused.
>>>>>>>>>
>>>>>>>>> I've added the permissions for port 22 and icmp in the default
>>>>>>>>> security group and i'm also able to ping the instances.
>>>>>>>>>
>>>>>>>>> I'm using the openstack packages provided with ubuntu 12.04.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Leander
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Mailing list: https://launchpad.net/~openstack
>>>>>>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>>>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>