Bug 1729699

Summary: Creating key pair during instance launch wizard no longer automatically downloads pem file
Product: Red Hat OpenStack Reporter: Kevin Jones <kejones>
Component: python-django-horizonAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Beth White <beth.white>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: athomas, beth.white, jrist, rdopiera
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-24 10:53:37 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:

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.