Bug 1520930 - [RFE] Newly created ec2 key pair is not downloadable
Summary: [RFE] Newly created ec2 key pair is not downloadable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.10.0
Assignee: Julian Cheal
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ui:cloud:ec2
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-05 13:28 UTC by Matouš Mojžíš
Modified: 2019-02-07 23:00 UTC (History)
6 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:00:45 UTC
Category: ---
Cloudforms Team: AWS
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:00:51 UTC

Description Matouš Mojžíš 2017-12-05 13:28:29 UTC 
Description of problem:
When I create key pair in AWS console private key is downloadable with the request.
In CLI it's returned as response.

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

How reproducible:
Always

Steps to Reproduce:
1. Add ec2 provider
2. Go to Compute -> Cloud -> Key pairs
3. Add a key pair

Actual results:
No prompt to download key pair so newly created key pair is absolutelly useless because we have no way to get private key.

Expected results:
There should be prompt to download key pair.


Additional info:
Comment 3 Julian Cheal 2018-06-05 14:34:56 UTC 
This has been fixed with this PR https://github.com/ManageIQ/manageiq-ui-classic/pull/3957
Comment 4 Matouš Mojžíš 2018-06-21 16:20:28 UTC 
Verified in 5.10.0.1. Key pair is downloadable after creation.
Comment 5 errata-xmlrpc 2019-02-07 23:00:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:0212
Note You need to log in before you can comment on or make changes to this bug.