I am deploying Openstack(I tried victoria and ussuri) with kolla-ansible on 3 CentOS 8 Nodes (1=Control+Compute,2 and 3=Compute). Deployments works fine without any problems but when I create a new VM with an ubuntu image (focal-server-cloudimg-amd64.img) from here it looks like it doesn't come up cleanly. This causes that the cloud-init script cannot finish and so the configured SSH-key is not set inside of the VM so I am not able to login.
ubuntu@10.20.34.137: Permission denied (publickey).
But its ip address is pingable and all network rules (security groups and so) are okay. Now the strange part begins. If I now do a Hard Reboot Instance, it comes up cleanly and I am able to login via SSH. Has anyone seen this issue before, because I have another/older instance of OpenStack ussuri running (from about 15 months ago) and there the same ubuntu image works well(I also verified this).
log output of the first run (only last lines):
-----END SSH HOST KEY KEYS-----
[ 49.380046] cloud-init[1387]: Cloud-init v. 21.4-0ubuntu1~20.04.1 running 'modules:final' at Wed, 05 Jan 2022 11:17:08 +0000. Up 49.23 seconds.
[ 49.380186] cloud-init[1387]: ci-info: no authorized SSH keys fingerprints found for user ubuntu.
[ 49.380481] cloud-init[1387]: Cloud-init v. 21.4-0ubuntu1~20.04.1 finished at Wed, 05 Jan 2022 11:17:08 +0000. Datasource DataSourceNone. Up 49.37 seconds
[ 49.380779] cloud-init[1387]: 2022-01-05 11:17:08,288 - cc_final_message.py[WARNING]: Used fallback datasource
log output after Hard Reboot Instance (only last lines):
-----END SSH HOST KEY KEYS-----
[ 15.105333] cloud-init[851]: Cloud-init v. 21.4-0ubuntu1~20.04.1 running 'modules:final' at Wed, 05 Jan 2022 11:46:21 +0000. Up 14.95 seconds.
[ 15.106253] cloud-init[851]: Cloud-init v. 21.4-0ubuntu1~20.04.1 finished at Wed, 05 Jan 2022 11:46:22 +0000. Datasource DataSourceOpenStackLocal [net,ver=2]. Up 15.10 seconds
[[0;32m OK [0m] Finished [0;1;39mExecute cloud user/final scripts[0m.
[[0;32m OK [0m] Reached target [0;1;39mCloud-init target[0m.
Ubuntu 20.04.3 LTS asdfff ttyS0
asdfff login:
So I also tested a debian image(debian-10-openstack-amd64.qcow2) from here and it worked fine with the first startup.
Has anyone else seen this behaviour? Or maybe see something I can do to work around this.
Kind regards,
Michael