Red Hat Bugzilla – Bug 823635
Always Retrieve New SSH key in RHEL AMIs
Last modified: 2014-06-02 09:01:57 EDT
+++ This bug was initially created as a clone of Bug #823634 +++
Description of problem:
If an SSH already exists on a RHEL AMI instance, it will not attempt to download another one. This is problematic for rebundles, even though one should be careful to remove their SSH keys anyway. It would be better if a warning was issued instead.
Steps to Reproduce:
1. Boot an AMI
2. Use ec2-create-image to rebundle it
3. Boot that new AMI with a different key
Cannot log in since the new key was not retrieved.
Issue a warning and then download the new key anyway.
The cloud-init package may solve this behavior for us. (see rhbz 770467)
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Adding Jerome to make the call.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).