Ask Your Question

ssh key-pair big issue

asked 2017-11-07 03:55:45 -0500

LinuxAdmin gravatar image

Dear Members, I have the following issue and its second time i am having the same.

My openstack instance was working fine with the keypair i generated. It worked fine for couple of months and then since yesterday the same keypair is not accepted and prompting me for the password. Instance is running without any issue, but its not letting me in. Debugging ssh also didn't help since its checking for the correct keypair but still asking for the password. I never used or enabled password auth in the instance. I have the physical and admin control of the machine, so i am sure no one changed it.

Any help would be highly appreciated.

Thanks, Sal

edit retag flag offensive close merge delete


The questions is still open...since i am unable to solve. Kindly advise if you can solve such issue. Thanks, Sal

LinuxAdmin gravatar imageLinuxAdmin ( 2017-11-13 05:22:50 -0500 )edit

2 answers

Sort by » oldest newest most voted

answered 2017-11-07 04:01:12 -0500

Deepa gravatar image

Check the console of VM .What is the status ?Did you try rebooting the VM ?If possible try to do it . Also removing and readding dhcp agent under admin-->>network-->dhcp-agent and try to login

edit flag offensive delete link more


Hi ,

Console ask for the password. Since i never set the password , so its no use. I rebooted the machine couple of times, no luck. What will removing and re-adding the dhcp agent will do ? Thanks for the reply.


LinuxAdmin gravatar imageLinuxAdmin ( 2017-11-07 04:16:21 -0500 )edit

DHCP agent communicates with neutron-server over RPC. It ensures network isolation using namespaces, so every network has its own dhcp namepsace. Inside this namespace there is a process called ‘dnsmasq’ and it’s the one that actually serves the DHCP parameters, including the IP address.

Deepa gravatar imageDeepa ( 2017-11-07 04:19:55 -0500 )edit

So sometimes removing and readding can fix ssh /ping issues .

Deepa gravatar imageDeepa ( 2017-11-07 04:20:25 -0500 )edit

Thanks, i have checked there is no issue with that.

LinuxAdmin gravatar imageLinuxAdmin ( 2017-11-07 04:55:05 -0500 )edit

answered 2017-11-07 05:24:50 -0500

If the instance doesn't accept your key, it means that it either has no public key at all or the wrong one. It could also mean that the IP address you are using is, in fact, not the instance's IP address.

Since you can't access the life instance:

You may get some insight from the console log openstack console log show INSTANCE.

You can also create an image from your instance openstack server image create (not sure if that is the correct command), download it and then analyze it with tools like guestfish.

You could find the instance's root disk on the compute node, then use tools like guestfish to analyze it or configure password-based login.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-11-07 03:55:45 -0500

Seen: 139 times

Last updated: Nov 07 '17