Red Hat Bugzilla – Bug 893107
Openstack-packstack: The installation log file is available at </path> - is empty, ( when not using '--debug=true') .
Last modified: 2016-04-26 21:57:51 EDT
Description: ------------- Openstack-packstack: Additional information should not address to an empty installation log file when running packstack installer without '--debug=true'. **** Installation completed successfully ****** (Please allow Installer a few moments to start up.....) Additional information: * To use the command line tools source the file /root/keystonerc_admin created on 127.0.0.1 * To use the console, browse to http://127.0.0.1/dashboard * The installation log file is available at: /var/tmp/c02179d7-c27e-4776-a7ce-69c23f01c166/openstack-setup_2013_01_08_13_45_13.log " Actual Results: ---------------- * The installation log file is available at </path> - is empty. Expected results: ----------------- In case running packstack without --debug=true, Either remove this message, or at least mention that the log file is available only in case packstack was executed with --debug=true.
This started occurring as a consequence of adding the --debug flag. perhaps we could add relevant info messages?
We could definitely add some INFO message at the beginning / end of each plugin process, even though, I think the most relevant info can be found in the remote work dir. Hiding this path from the output when --debug is not set won't hurt.
Patch submitted upstream that changes default log level to info and only output logging to log file https://review.openstack.org/#/c/20816/ The file is not longer empty and more info messages can be added without polluting stdout. Flavio if this merges if you added info message this might help the case.
Verified - openstack-packstack-2012.2.3-0.1.dev454.el6ost.noarchm/ Installation log file could be found under the suggested path.
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-0671.html