On Thu, Aug 22, 2024, at 2:06 AM, Junya Noguchi (Fujitsu) wrote:
Dear Mr. Boylan
Thank you for your reply.
I created a VM using "openSUSE-Leap-15.6-aarch64-NoCloud.qcow2" and tried to log in using SSH key, but the login failed. x86 cloud version "openSUSE-Leap-15.2-OpenStack.x86_64.qcow2" could be logged in the same way.
・Image Creation Command $ openstack image create openSUSE-Leap-15.6-aarch64-NoCloud --file openSUSE-Leap-15.6.aarch64-NoCloud.qcow2 --disk-format qcow2 --property architecture=aarch64 --container-format bare
It would also be useful to know how you are creating the instance to double check the key is associated properly.
・SSH connection task $ ssh -i "keyname.pub" opensuse@xxx.xxx.xxx.xxx The authenticity of host 'xxx.xxx.xxx.xxx (<no hostip for proxy command>)' can't be established. ED25519 key fingerprint is SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'xxx.xxx.xxx.xxx' (ED25519) to the list of known hosts. (opensuse@xxx.xxx.xxx.xxx) Password: (opensuse@xxx.xxx.xxx.xxx) Password: (opensuse@xxx.xxx.xxx.xxx) Password: opensuse@xxx.xxx.xxx.xxx: Permission denied (publickey,keyboard-interactive).
This indicates you got an ssh hostkey which means networking was working well enough to connect you to the remote system then authentication failed. Authentication could fail for a number of reasons. Perhaps cloud-init didn't run at all, maybe the ssh key you booted the instance with isn't the same key as the one you tried to authenticate with, or maybe the opensuse username is incorrect for that image's cloud-init setup. You may be able to debug some of that via the instance's console log (as cloud-init should record the work it is doing in that log file). Otherwise, as mentioned previously, you may have better luck using openSUSE's support forums (mailing list, forum, reddit). Also note that when you use `ssh -i` with a public key file instead of a private key file the man page indicates it will look up that key in your ssh-agent. Not sure if the key was loaded in your agent, but maybe you need to provide the private key file instead to make that work.
Best regards, Junya Noguchi.