Bug 907624 - Misleading message when generating public key.
Summary: Misleading message when generating public key.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: snapshot3
: 2.1
Assignee: Martin Magr
QA Contact: Nir Magnezi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-04 20:43 UTC by Stephen Gordon
Modified: 2022-07-09 06:03 UTC (History)
4 users (show)

Fixed In Version: openstack-packstack-2012.2.2-0.9.dev406
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-05 21:03:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-16332 0 None None None 2022-07-09 06:03:54 UTC
Red Hat Product Errata RHSA-2013:0595 0 normal SHIPPED_LIVE Moderate: openstack-packstack security and bug fix update 2013-03-06 02:00:00 UTC

Description Stephen Gordon 2013-02-04 20:43:13 UTC 
Description of problem:

When presented with the question "Enter the path to your ssh Public key to install on servers" I pressed enter. Packstack then displayed this message:

"Packstack changed given hostname to IP address /home/shadowman/.ssh/id_rsa.pub."

I suspect we are combining the wrong message strings here.

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

openstack-packstack-2012.2.2-0.8.dev346.el6ost.noarch
Comment 1 Derek Higgins 2013-02-11 18:04:56 UTC 
The print that was output this has now been removed
Comment 3 Omri Hochman 2013-02-24 13:49:44 UTC 
Verified with - openstack-packstack-2012.2.2-1.0.dev408.el6ost.noarch

Following to:
--------------
"Enter the path to your ssh Public key to install on servers":

The new message:
-----------------
"Packstack changed given value  to required value /root/.ssh/id_rsa.pub"
Comment 5 errata-xmlrpc 2013-03-05 21:03:14 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/RHSA-2013-0595.html
Note You need to log in before you can comment on or make changes to this bug.