Bug 1793138

Summary: Enable SSH key download after creating EC2 CR
Product: Red Hat Satellite Reporter: Stephen Wadeley <swadeley>
Component: Compute Resources - EC2Assignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: UnspecifiedCC: apatel, kgaikwad, lstejska
Target Milestone: UnspecifiedKeywords: Triaged
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: 2024-05-29 20:12:57 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:
Attachments:
Description Flags
Two SSH keys showing on the SSH tab for EC2 CR none

Description Stephen Wadeley 2020-01-20 18:47:05 UTC 
Description of problem:

While creating an EC2 Computer Resource (CR), you can download the SSH keys, but not afterwards.

Asking users to search the database[1] is not user friendly.


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

Sat6.7 Snap 9
[root@dell-r330-12 ~]# rpm -q satellite
satellite-6.7.0-5.beta.el7sat.noarch


How reproducible:


Steps to Reproduce:
1. start the config procedure set up as per guide [1]
2. Before you "Click Submit to save the Amazon EC2 connection", notice SSH keys are downloadable
3. After you "Click Submit to save the Amazon EC2 connection", notice SSH keys are no longer downloadable

Actual results:
SSH keys are no longer downloadable after EC2 CR creation

Expected results:
SSH keys are still downloadable after EC2 CR creation

Additional info:

[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html/provisioning_guide/provisioning_cloud_instances_in_amazon_ec2
Comment 2 Stephen Wadeley 2020-01-20 20:32:25 UTC 
Created attachment 1654028 [details]
Two SSH keys showing on the SSH tab for EC2 CR

Hello Melanie

How did you manage to create two keys?
Comment 3 Melanie Corr 2020-01-20 20:48:01 UTC 
(In reply to Stephen Wadeley from comment #2)
> Created attachment 1654028 [details]
> Two SSH keys showing on the SSH tab for EC2 CR
> 
> Hello Melanie
> 
> How did you manage to create two keys?

Perhaps another bug for you, Stephen. 
When you delete the CR and recreate using the same AWS keys, the old SSH appear within the second CR, but I suspect that might be because the keys are the same. I have no idea if there is any value to keeping this stored in memory after the CR is deleted. I suspect not. It seems like sub-optimal behaviour. 

Thanks, 

Melanie
Comment 4 Stephen Wadeley 2020-01-21 10:30:45 UTC 
Hello

Re comment 2 and comment 3
Given that behaviour, raising priority
Comment 13 Kavita 2020-03-06 12:24:25 UTC 
In addition to my comment 11, I have observed the same behaviour on sat 6.6 and probably it may exists on sat 6.5 as well.
That's why I don't think it is regression/blocker.

There is one more BZ around this - https://bugzilla.redhat.com/show_bug.cgi?id=1757656.
I agree that issue exists and requires a fix to make user interface better.
But as key-pair resource is part of all other CRs, I request to reconsider the priority of this BZ to next version.

Removed regression & triage keywords. 
Thanks!

- Kavita