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

Bug 906006

Summary: The --gen-answer-file parameter does not understand the ~ shortcut for home.
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED ERRATA QA Contact: Nir Magnezi <nmagnezi>
Severity: low Docs Contact:
Priority: medium    
Version: 2.1CC: aortega, derekh, fpercoco, ykaul
Target Milestone: snapshot3Keywords: Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-2012.2.2-0.9.dev406 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-05 21:03:08 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 Stephen Gordon 2013-01-30 15:44:38 UTC 
Description of problem:

When running packstack --gen-answer-file='~/answer.txt' I get an error. If I use './answer.txt' from the home directory it works:

# echo $HOME
/root
# pwd
/root
# packstack --gen-answer-file='~/answer.txt'
[Errno 2] No such file or directory: '~/answer.txt'
Please check log file /var/tmp/71bd87d1-576a-4d64-89bc-0b0d0c47691b/openstack-setup_2013_01_29_22_41_48.log for more information
# packstack --gen-answer-file='./answer.txt'
#

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

openstack-packstack-2012.2.2-0.2.dev211.el6ost.noarch

Actual results:

packstack --gen-answer-file='~/answer.txt' fails with file not found.


Expected results:

packstack --gen-answer-file='~/answer.txt' creates $HOME/answer.txt.
Comment 1 Derek Higgins 2013-01-30 21:41:52 UTC 
Fix submitted upstream
https://review.openstack.org/20830
Comment 3 Nir Magnezi 2013-02-17 10:33:11 UTC 
Verified NVR: openstack-packstack-2012.2.2-1.0.dev408.el6ost.noarch

Verification steps based on Comment #0
Comment 5 errata-xmlrpc 2013-03-05 21:03:08 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