Bug 1729699 - Creating key pair during instance launch wizard no longer automatically downloads pem file
Summary: Creating key pair during instance launch wizard no longer automatically downl...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Beth White
Depends On:
TreeView+ depends on / blocked
Reported: 2019-07-13 17:35 UTC by Kevin Jones
Modified: 2019-07-24 11:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-07-24 10:53:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1575913 0 None None None 2019-07-24 10:55:10 UTC

Description Kevin Jones 2019-07-13 17:35:27 UTC
Description of problem:
While going through the launch instance wizard in horizon, there is an option to create a key pair. When doing this key pair creation in past versions, the resulting private pem file would automatically download. This does not happen in RHOSP 13.

Instead the user is presented with the private key and an option to copy to the clipboard. However, there is no option to just download the pem file.

This means the user must copy the key pair and paste into a file somewhere, then get the public key that was generated.

The process when going through the key pairs page directly still downloads the pem file.

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

How reproducible:

Steps to Reproduce:
1. Go through instance launch wizard
2. On the Key Pairs dialog, click create key pair
3. Give the key pair a name and click create

Actual results:
Private key is displayed and there is a button to copy to clipboard, but no download option.

Expected results:
The pem file should automatically download as it has in the past, or there should be an option to download it.

Comment 1 Radomir Dopieralski 2019-07-24 10:53:37 UTC
That change is intentional, and it was introduced in order to fix a security problem.


Note You need to log in before you can comment on or make changes to this bug.