Hi, I have been able to get a bootable F34 machine on GCP only from an image with the command line:
gcloud compute images create fedora-34 --source-uri gs://backup-715668182/Fedora-Cloud-Base-GCP-34-1.2.x86_64.tar.gz --guest-os-features=UEFI_COMPATIBLE
But after creating VM, the GCP ssh seems to hang on transferring keys; I can connect to the serial console but not able to login with root.
Is this an issue with the image? Otherwise any help appreciated.
Metadata Update from @ngompa: - Issue tagged with: GCP
Metadata Update from @ngompa: - Issue assigned to ericedens
@ericedens Can you take a look at this please?
Taking a look!
First thing to know: The Fedora 34 GCP image used cloud-init. The Fedora 35 GCP image will use the standard GCE guest environment.
Given that, here are two options that are working on my side:
When specifying the SSH key during instance creation, change the username to fedora. Here's an example:
fedora
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCuWmlghfQDUv2FdYkSE1tbXoGp/q7c8KqRB2uo6oe9tR91q9ZcmSdDamA9KqREwYjV1D4z fedora@host
When connecting to the instance, make sure to specify the user as fedora.
Configure the user and its SSH key using cloud-init. Here's a YAML file that worked for me:
cat userdata.yaml #cloud-config users: - name: ericedens ssh_authorized_keys: - ssh-rsa AAAAB3NzaC1yc2EAAAAz ericedens@host
Create the instance with gcloud:
gcloud
gcloud compute instances create fedora-34-gcloud --image fedora-34 --metadata-from-file user-data=userdata.yaml
Hope this helps!
Yes it helped! Awesome. I'm in! Thank you very much!
Metadata Update from @ngompa: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.