Bug 906410

Summary: Generate answer file when running on live mode
Product: Red Hat OpenStack Reporter: Flavio Percoco <fpercoco>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED ERRATA QA Contact: Nir Magnezi <nmagnezi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aortega, derekh, sgordon, ykaul
Target Milestone: snapshot3Keywords: Improvement, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-2012.2.2-0.9.dev406 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-05 21:03:11 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:
Bug Depends On:    
Bug Blocks: 905160    

Description Flavio Percoco 2013-01-31 15:37:46 UTC
Description of problem:

Packstack doesn't generate an answer file when running on live mode. 


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


How reproducible:
Always


Steps to Reproduce:
1. run packstack on live mode
2.
3.
  
Actual results:


Expected results:
An answer file should be generated somewhere in the filesystem in order to allow the user for running packstack again with the same parameters and / or knowing what parameters were used (i.e: automatic generated passwords)


Additional info:

Comment 1 Derek Higgins 2013-02-12 02:18:07 UTC
fix merged upstream
https://review.openstack.org/#/c/21649/

Comment 3 Nir Magnezi 2013-02-17 12:08:54 UTC
Verified NVR: openstack-packstack-2012.2.2-1.0.dev408.el6ost.noarch

1. Ran packstack without answers file.
2. A file named answers.txt was created at the end of the installation by packstack.

Comment 4 Stephen Gordon 2013-02-19 19:30:21 UTC
What happens if the user already has an answers.txt file in the current working directory and/or their home directory? Also given the concerns Kurt has raised with the usage of /tmp elsewhere in packstack should it be in the list to check here (currently it is)?

Comment 7 errata-xmlrpc 2013-03-05 21:03:11 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