[Touch-packages] [Bug 1968360] Re: jammy daily won't accept EC2 publickey (suspect cloud-init failure)
Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3967 ** Bug watch added: github.com/canonical/cloud-init/issues #3967 https://github.com/canonical/cloud-init/issues/3967 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1968360 Title: jammy daily won't accept EC2 publickey (suspect cloud-init failure) Status in cloud-init: Invalid Status in openssh package in Ubuntu: Invalid Bug description: amazon-ebs: output will be in this color. ==> amazon-ebs: Prevalidating any provided VPC information ==> amazon-ebs: Prevalidating AMI Name: packer-honeycomb-arm-1649438444 amazon-ebs: Found Image ID: ami-03c980393156217bb ==> amazon-ebs: Creating temporary keypair: packer_62506eec-8c01-8c21-b199-32a96021bd7a ==> amazon-ebs: Creating temporary security group for this instance: packer_62506eee-c3da-1eb2-6e81-baa0c5ccfdfc ==> amazon-ebs: Authorizing access to port 22 from [0.0.0.0/0] in the temporary security groups... ==> amazon-ebs: Launching a source AWS instance... ==> amazon-ebs: Adding tags to source instance amazon-ebs: Adding tag: "Name": "Packer Builder" amazon-ebs: Instance ID: i-01158f222c8664f0c ==> amazon-ebs: Waiting for instance (i-01158f222c8664f0c) to become ready... ==> amazon-ebs: Using SSH communicator to connect: 54.173.181.221 ==> amazon-ebs: Waiting for SSH to become available... ==> amazon-ebs: Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> amazon-ebs: Terminating the source AWS instance... ==> amazon-ebs: Cleaning up any extra volumes... ==> amazon-ebs: No volumes to clean up, skipping ==> amazon-ebs: Deleting temporary security group... ==> amazon-ebs: Deleting temporary keypair... Build 'amazon-ebs' errored after 2 minutes 42 seconds: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Wait completed after 2 minutes 42 seconds ==> Some builds didn't complete successfully and had errors: --> amazon-ebs: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Builds finished but no artifacts were created. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1968360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968360] Re: jammy daily won't accept EC2 publickey (suspect cloud-init failure)
https://github.com/hashicorp/packer/issues/11656#issuecomment-1076175764 found my problem. packer generates temporary ssh-rsa keys which are disallowed by the 22.04 default SSH key policy. ** Changed in: openssh (Ubuntu) Status: New => Invalid ** Changed in: cloud-init Status: Incomplete => Invalid ** Bug watch added: github.com/hashicorp/packer/issues #11656 https://github.com/hashicorp/packer/issues/11656 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1968360 Title: jammy daily won't accept EC2 publickey (suspect cloud-init failure) Status in cloud-init: Invalid Status in openssh package in Ubuntu: Invalid Bug description: amazon-ebs: output will be in this color. ==> amazon-ebs: Prevalidating any provided VPC information ==> amazon-ebs: Prevalidating AMI Name: packer-honeycomb-arm-1649438444 amazon-ebs: Found Image ID: ami-03c980393156217bb ==> amazon-ebs: Creating temporary keypair: packer_62506eec-8c01-8c21-b199-32a96021bd7a ==> amazon-ebs: Creating temporary security group for this instance: packer_62506eee-c3da-1eb2-6e81-baa0c5ccfdfc ==> amazon-ebs: Authorizing access to port 22 from [0.0.0.0/0] in the temporary security groups... ==> amazon-ebs: Launching a source AWS instance... ==> amazon-ebs: Adding tags to source instance amazon-ebs: Adding tag: "Name": "Packer Builder" amazon-ebs: Instance ID: i-01158f222c8664f0c ==> amazon-ebs: Waiting for instance (i-01158f222c8664f0c) to become ready... ==> amazon-ebs: Using SSH communicator to connect: 54.173.181.221 ==> amazon-ebs: Waiting for SSH to become available... ==> amazon-ebs: Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> amazon-ebs: Terminating the source AWS instance... ==> amazon-ebs: Cleaning up any extra volumes... ==> amazon-ebs: No volumes to clean up, skipping ==> amazon-ebs: Deleting temporary security group... ==> amazon-ebs: Deleting temporary keypair... Build 'amazon-ebs' errored after 2 minutes 42 seconds: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Wait completed after 2 minutes 42 seconds ==> Some builds didn't complete successfully and had errors: --> amazon-ebs: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Builds finished but no artifacts were created. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1968360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968360] Re: jammy daily won't accept EC2 publickey (suspect cloud-init failure)
I've checked all of the following jammy daily images, and all of them fail to correctly install the EC2 metadata supplied SSH key such that it is possible to ssh ubuntu@host after startup. Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220323ami-0320e0e27a2e26467 Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220405ami-028c98d9274336455 Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220406ami-0cb3473d91f8f239d Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220407ami-03c980393156217bb Both of these do install the SSH key for ubuntu@ from AWS metadata fine: Amazon AWS us-east-1 impish 21.10 arm64 hvm-ssd 20220309 ami-0a4b1fdc2301bf1f1 Amazon AWS us-east-1 impish com.ubuntu.cloud.daily:server:21.10 arm64 hvm-ssd 20220319ami-09ce10196abcc5dc4 ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1968360 Title: jammy daily won't accept EC2 publickey (suspect cloud-init failure) Status in cloud-init: Incomplete Status in openssh package in Ubuntu: New Bug description: amazon-ebs: output will be in this color. ==> amazon-ebs: Prevalidating any provided VPC information ==> amazon-ebs: Prevalidating AMI Name: packer-honeycomb-arm-1649438444 amazon-ebs: Found Image ID: ami-03c980393156217bb ==> amazon-ebs: Creating temporary keypair: packer_62506eec-8c01-8c21-b199-32a96021bd7a ==> amazon-ebs: Creating temporary security group for this instance: packer_62506eee-c3da-1eb2-6e81-baa0c5ccfdfc ==> amazon-ebs: Authorizing access to port 22 from [0.0.0.0/0] in the temporary security groups... ==> amazon-ebs: Launching a source AWS instance... ==> amazon-ebs: Adding tags to source instance amazon-ebs: Adding tag: "Name": "Packer Builder" amazon-ebs: Instance ID: i-01158f222c8664f0c ==> amazon-ebs: Waiting for instance (i-01158f222c8664f0c) to become ready... ==> amazon-ebs: Using SSH communicator to connect: 54.173.181.221 ==> amazon-ebs: Waiting for SSH to become available... ==> amazon-ebs: Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> amazon-ebs: Terminating the source AWS instance... ==> amazon-ebs: Cleaning up any extra volumes... ==> amazon-ebs: No volumes to clean up, skipping ==> amazon-ebs: Deleting temporary security group... ==> amazon-ebs: Deleting temporary keypair... Build 'amazon-ebs' errored after 2 minutes 42 seconds: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Wait completed after 2 minutes 42 seconds ==> Some builds didn't complete successfully and had errors: --> amazon-ebs: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Builds finished but no artifacts were created. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1968360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
