I cannot login into new image created to rebuild my instance

Asked by Nureni Adekunle Adeyemo on 2018-09-19

I wanted to run some binary files on my VMs but could not do that because of the size of the image (ubuntu test image) that I used to launch my VMs in earlier stage of the project. I created another image yesterday based on the recommendation from the OpenStack documentation (Ubuntu: xenial-server-cloudimg-amd64-disk1.img). The VMs are running with the new image and can ping but could no longer remotely login into them using ssh -i cloud-key Newimage@vm-ip-address. I do not know the login credentials of this new image (username and password) and I have not been able to find any reasonable command to extract this information. Can you please assist me with this or tell me a way I can set the username and password for the image?

Question information

Language:
English Edit question
Status:
Answered
For:
Glance Edit question
Assignee:
No assignee Edit question
Last query:
2018-09-19
Last reply:
2018-11-06

I have used ubuntu as the username as recommended in ( https://ask.openstack.org/en/question/46416/not-able-to-ssh-into-vm/) but the vm is still asking for the password, when I supplied the root password of my ubuntu linux, what I get is Permission denied, please try again. Can someone please help?

Launchpad Janitor (janitor) said : #2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

This isn't really a Glance question ... Glance stores and catalogs images, but doesn't control their content or how they are configured.

That being said, I think that Ubuntu cloud images are set up so that they assume that you're going to inject an ssh key when you create your instance and will then use that key to connect as the 'ubuntu' user. So your 'ssh -i cloud-key ubuntu@vm-ip-address' should work. ssh is pretty picky, so try using the absolute path to your key (for example, /home/username/.ssh/cloud-key) and also make sure that the file containing your private key is protected so that it's readable only by you (permissions set to 600 on linux).

If that doesn't help, your best bet is to ask or search on the Ubuntu community forum; they'll know the most about how the Ubuntu images they supply are configured.

Can you help with this problem?

Provide an answer of your own, or ask Nureni Adekunle Adeyemo for more information if necessary.

To post a message you must log in.