Bug 1757656
| Summary: | 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 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Anto P Joseph <ajoseph> |
| Component: | Compute Resources - EC2 | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Lukáš Hellebrandt <lhellebr> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.5.0 | Keywords: | Triaged |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-02 15:17:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. 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. |
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.