Thank you very much guys Sébastien and Leander
It was very interesting case.
I thought if I see this lines in compute.log then sshkey injection was
successfully
1fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap qemu-nbd
-c /dev/nbd15 /var/lib/nova/instances/instance-000c/disk
It depend on your image, but if you picked an image from the ubuntu cloud
image repo you should use the 'ubuntu' user to ssh connect otherwise won't
be able to connect to your instance.
Hope it helps!
On Fri, May 25, 2012 at 11:04 AM, Anton Haldin ahal...@griddynamics.comwrote:
Thank you very
Thank you Sébastien
yes I see. It looks like ssh key injection through nbd is not sufficient
for using ubuntu login.
On Fri, May 25, 2012 at 1:10 PM, Sébastien Han han.sebast...@gmail.comwrote:
It depend on your image, but if you picked an image from the ubuntu cloud
image repo you should
On Fri, 25 May 2012, Anton Haldin wrote:
Thank you very much guys Sébastien and Leander
It was very interesting case.
I thought if I see this lines in compute.log then sshkey injection was
successfully
Given functional metadata service,
ssh key injection from the host is not necessary
Thank you Scott for your answer
Now I think I have full understanding of this case.
Without keys openssh server would reset ssh session immediately.
On Fri, May 25, 2012 at 6:01 PM, Scott Moser smo...@ubuntu.com wrote:
On Fri, 25 May 2012, Anton Haldin wrote:
Thank you very much guys
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
leande...@gmail.com wrote:
Hello,
I'm having trouble sshing into the created instances. At first i was
getting the following error:
ssh -i
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 ahal...@griddynamics.comwrote:
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
you can try to look in console.log for this instance
On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert
leande...@gmail.com 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
Complete log: http://paste.openstack.org/show/18144/
On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.comwrote:
you can try to look in console.log for this instance
On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
No, at the moment
it can be an issue of openssh:
one more link
http://www.gossamer-threads.com/lists/openssh/dev/51483?do=post_view_threaded#51483
On Thu, May 24, 2012 at 5:48 PM, Anton Haldin ahal...@griddynamics.comwrote:
what you can try to do:
you can mount machine image and check /var/log/auth.log
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
I've formatted the host machine and reinstalled openstack, just in case.
Now i am only getting connection refused.
On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Compute log: Log: http://paste.openstack.org/show/18149/
I've tried bot root and ubuntu as
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
On Thu, 24 May 2012, Leander Bessa Beernaert 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
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.sebast...@gmail.comwrote:
It's not an open-ssh issue.
Your virtual machine simply can't
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
leande...@gmail.com wrote:
Adding the following to my config file solved my
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
leande...@gmail.com wrote:
Just a question i forgot, on a multi-host senario, the IP_CURRENT_NODE is
the compute node's ip right? Currently
Maybe you missed the rules of security group?
Rogério Gonçalves
roge...@gmail.com
Cel: (11) 8840-9790
On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
I've formatted the host machine and reinstalled openstack, just in case.
Now i am only getting
First rule of security group. Do not talk about security group. j/k
On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves roge...@gmail.comwrote:
Maybe you missed the rules of security group?
Rogério Gonçalves
roge...@gmail.com
Cel: (11) 8840-9790
On Thu, May 24, 2012 at 12:12 PM,
Why did you reinstall everything?
There is no just in case, I mean you solved your issue, it was from your
configuration not from openstack :)
It's a routing issue, same as earlier.
Check again those parameters, specially the first one:
- --routing_source_ip=IP_CURRENT_NODE
-
I'm in no way saying that openstack is to blame for the current problem,
but it occurred to me that my install could have script failed somewhere
along the way without me knowing (i might have forgotten to mention that in
the previous post :s).
Adding those two lines solved my problem. I've
Ok ok, no offense in my previous emails :)
Good to know that everything is working.
Cheers.
On Fri, May 25, 2012 at 1:00 AM, Leander Bessa Beernaert
leande...@gmail.com wrote:
I'm in no way saying that openstack is to blame for the current problem,
but it occurred to me that my install
22 matches
Mail list logo
