Bug 1490979
Summary: | [RFE] With CF generated keypairs for OSP, you are unable to download the Private key | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Saif Ali <saali> |
Component: | Appliance | Assignee: | Sam Lucidi <slucidi> |
Status: | CLOSED ERRATA | QA Contact: | Jad Haj Yahya <jhajyahy> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 5.8.0 | CC: | abellott, dluong, jhajyahy, jhardy, lavenel, obarenbo, ohochman, saali, simaishi, slucidi |
Target Milestone: | MVP | Keywords: | FutureFeature |
Target Release: | 5.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.10.0.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-07 23:02:46 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | Openstack | Target Upstream Version: | |
Embargoed: |
Description
Saif Ali
2017-09-12 16:33:09 UTC
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set it to Low/Low. I've got PRs up for this: https://github.com/ManageIQ/manageiq-ui-classic/pull/3957 https://github.com/ManageIQ/manageiq/pull/17439 There is a caveat however. The Openstack API only returns the private key when the key pair is created, and it cannot be requested at any other time. If Cloudforms is used to create the key, then Cloudforms will save it and it will be available for download, but Cloudforms won't be able to access any pre-existing keypairs that it did not create, and if the Cloudforms database is lost for some reason, the key will not be retrievable again. Verified on 5.10.0.3 Verified on 5.10.0.23 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 |