Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1113537

Summary: rhel-osp-installer fails if no ssh key is provided
Product: Red Hat OpenStack Reporter: Mike Burns <mburns>
Component: rhel-osp-installerAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.0 (RHEL 7)CC: dnavale, dradez, mburns, mhulan, rhos-maint, sasha, sgordon
Target Milestone: ga   
Target Release: 5.0 (RHEL 6)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhel-osp-installer-0.0.25-4.el6ost Doc Type: Bug Fix
Doc Text:
internal only, no doc text needed
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-04 18:35:10 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:

Description Mike Burns 2014-06-26 11:27:02 UTC
Description of problem:
The ability to add ssh pubkey auth to provisioned hosts in the RHEL-OSP installer causes the installer to fail if no pubkey is provided.  

Version-Release number of selected component (if applicable):
rhel-osp-installer-0.0.25-2.el6ost

How reproducible:
always

Steps to Reproduce:
1.run rhel-osp-installer
2.don't enter an ssh-key
3.

Actual results:
fails

Expected results:
works and does not set ssh key

Additional info:

Comment 1 Marek Hulan 2014-06-26 13:07:55 UTC
Merged in master https://github.com/theforeman/foreman-installer-staypuft/pull/31

Comment 2 Mike Burns 2014-06-26 19:53:32 UTC
*** Bug 1113738 has been marked as a duplicate of this bug. ***

Comment 4 Alexander Chuzhoy 2014-06-30 16:56:48 UTC
Verified: rhel-osp-installer-0.0.25-5.el6ost.noarch


The installation completes successfully without providing an SSH key.

Comment 7 errata-xmlrpc 2014-08-04 18:35:10 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.

http://rhn.redhat.com/errata/RHEA-2014-1003.html