search

stackhpc / a-universe-from-nothing

Kayobe configuration for the Kayobe workshop "A Universe from Nothing: Containerised OpenStack deployment using Kolla, Ansible and Kayobe"
https://docs.openstack.org/kayobe/latest/
Apache License 2.0
79 stars 26 forks source link

Failed to connect to the host via ssh #164

Open VLadSaln opened 1 month ago

VLadSaln commented 1 month ago

fatal: [seed]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: centos@192.168.33.5: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).", "unreachable": true} Error after kayobe seed host configure

kees-closed commented 1 week ago

Same here, no fix so far?

Alex-Welsh commented 1 week ago

Hi there, can you try setting the user to rocky, cloud-user, or stack instead? Unfortunately the README is a fair way out of date and support for CentOS 8 was dropped a while ago. The drop-in replacement is Rocky 9, and Ubuntu 22.04 also work with a few tweaks.

kees-closed commented 1 week ago

Hi there, can you try setting the user to rocky, cloud-user, or stack instead? Unfortunately the README is a fair way out of date and support for CentOS 8 was dropped a while ago. The drop-in replacement is Rocky 9, and Ubuntu 22.04 also work with a few tweaks.

I'm trying to find the location of this, do you have the path of where this user variable should be changed in the yaml?

Alex-Welsh commented 1 week ago

You can change this line here: https://github.com/stackhpc/a-universe-from-nothing/blob/stable/2023.1/etc/kayobe/seed.yml#L7C2-L7C21 Which will typically be at ~/kayobe/config/src/kayobe-config/etc/kayobe/seed.yml. I think it will need to be rocky.

Changing that line will get you further, however I suspect that you'll hit more issues later. I'm assuming the host machine you are using is CentOS 8? The easiest solution would be to rebuild using Rocky 9.

Setting os_distribution: "rocky" and os_release: "9" under globals.yml may be enough to make it work with CentOS.

kees-closed commented 1 week ago

My host machine is Debian 12. What I did was changing this line to the user 'admin'. Then it continued. But I suppose that's an ugly hack for now? Or maybe a wrong user? Or even wrong host distribution?

Alex-Welsh commented 1 week ago

Debian 12 is very much uncharted territory. You can try setting the *_bootstrap_user variables in seed.yml, compute.yml and controllers.yml to admin if that seems to work for you.

The two host distributions supported by kayobe are Ubuntu 22.04 and Rocky 9. docs link If possible I'd recommend switching to one of those two and use a big VM or similar

kees-closed commented 1 day ago

Changing to Rocky 9 indeed made things smoother! Thanks!