Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1757656 - Satellite using deleted ssh keypair for provisioning EC2 instance and failing with Failed to create a compute instance xxxx: The key pair 'foreman-xxx' does not exist
Summary: Satellite using deleted ssh keypair for provisioning EC2 instance and failing...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - EC2
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-02 02:34 UTC by Anto P Joseph
Modified: 2022-09-02 20:08 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-02 15:17:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4459151 0 None None None 2019-10-02 03:04:42 UTC

Description Anto P Joseph 2019-10-02 02:34:50 UTC 
Description of problem:

Satellite using wrong/invalid/deleted ssh keypair and failing EC2 provisioning with following error:

----
Unable to save
Failed to create a compute aws+cr2 (us-west-2-EC2) instance carla-hritz: The key pair 'foreman-20b156c25-b77a-4534-9c9e-da60c1695849' does not exist
----

REASON:
 Satellite use ssh-key name "foreman-xxx" which was created by Satellite upon creating EC2 compute resource. key contents are available in satellite DB and AWS>Keypairs


If above keypair is deleted from AWS Console, Satellite fails with this error.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create AWS compute resource: 
  
          WebUI: Compute Resources > aws CR > SSH Keys > you can find associated ssh keypair.(foreman-xxx)

2. Goto AWS Console (AWS > EC2 > Key Pairs) and delete mentioned keypair(foreman-xxx) and try to provision Ec2 instance.

3. 

Actual results:

Satellite will still look for DELETED KeyPair and fail.

Expected results:

Satellite Should give us option to CREATE NEW keypair. OR 
Give OPTION to choose NEW/Different keypair.

Additional info:


WORKAROUND:

-------
# hammer compute-resource list
                - Copy exact NAME of the compute resource from the list  Example: aws_cr


# foreman-rake console
# ComputeResource.find_by(:name =>'aws_cr').send(:destroy_key_pair)
# ComputeResource.find_by(:name =>'aws_cr').send(:create_key_pair)
-------

Goto: Satellite WebUI: Compute Resource > Select AWS compute resource > SSH_Keys > Now here you will have the option to create new SSH Key.
Comment 6 Mike McCune 2022-07-08 17:15:31 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 7 Brad Buckingham 2022-09-02 20:08:50 UTC 
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Note You need to log in before you can comment on or make changes to this bug.