Bug 1089067 - Invalid target of --generate-answer option causes error indicating the entire installation has failed
Summary: Invalid target of --generate-answer option causes error indicating the entire...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: RHGS 3.0.0
Assignee: Shubhendu Tripathi
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-17 19:44 UTC by Wesley Duffee-Braun
Modified: 2018-12-06 16:19 UTC (History)
8 users (show)

Fixed In Version: rhsc-3.0.0-0.5.master.el6_5.noarch.rpm
Doc Type: Bug Fix
Doc Text:
Previously, there was no error handling capability for the command: "rhsc-setup --generate-answer=<answer-file>". If an invalid answer file was provided, the Red Hat Storage Console setup script would fail with an error. With this release, the error is handled while writing the answer file. If an invalid path is provided, the setup reports the error as a warning and continues to function as expected.
Clone Of:
Environment:
Last Closed: 2014-09-22 19:08:27 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:1277 0 normal SHIPPED_LIVE Red Hat Storage Console 3.0 enhancement and bug fix update 2014-09-22 23:06:30 UTC
oVirt gerrit 27731 0 master MERGED setup: Write the answer file if file path is valid Never

Description Wesley Duffee-Braun 2014-04-17 19:44:28 UTC
Description of problem:
When an invalid target is used for the --generate-answer file, the entire RHSC installation will fail.

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

How reproducible:
Always

Steps to Reproduce:
1. Run an installation command similar to rhsc-setup --generate-answer=root/rhsc-answer-file-2.1u2
[note the missing / before root in the above]
2. Complete installation as normal 
3. Receive a "setup failed" error

Actual results:
[ INFO  ] Starting engine service
[ INFO  ] Restarting httpd
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140402113337-setup.conf'
[ INFO  ] Generating answer file 'root/rhsc-answer-file-2.1u2'
[ ERROR ] Failed to execute stage 'Closing up': [Errno 2] No such file or directory: '/root/root/rhsc-answer-file-2.1u2'
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140402112906.log
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

Expected results:
Errors and/or warnings that look like the 

Additional info:
The current error is concerning to customers because it looks like their entire installation has failed, and they may not be sure what to do next to salvage their deployment.

Comment 2 Dusmant 2014-04-29 06:36:27 UTC
Installation framework has changed from RHSC Corbett (2.1 U2) to RHSC Denali (3.0), because of underlying ovirt install framework change. 

This case will be tested by Prasanth and he will let us know, if this issue is resolved in RHSC 3.0 or not and if not, then we need to document it along with the required work around.

Comment 3 Shubhendu Tripathi 2014-05-14 13:47:06 UTC
Need help from Alon to understand, if there is a mechanism to raise a warning only if a certain stage fails during engine setup and not to fail to overall setup process.

Comment 4 Alon Bar-Lev 2014-05-14 20:33:33 UTC
(In reply to Shubhendu Tripathi from comment #3)
> Need help from Alon to understand, if there is a mechanism to raise a
> warning only if a certain stage fails during engine setup and not to fail to
> overall setup process.

self.logger.warning() ?

Comment 5 Prasanth 2014-05-23 18:12:05 UTC
Verified as fixed in rhsc-3.0.0-0.5.master.el6_5.noarch.rpm

----------------------
# rhsc-setup --generate-answer=root/rhsc-answer-file-2.1u2
...
          --== END OF SUMMARY ==--
         
[ INFO  ] Starting engine service
[ INFO  ] Restarting httpd
          Make sure the managed nodes get migrated to RHS-3.0 to get monitoring enabled for them.
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140523164316.log
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140523164900-setup.conf'
[ INFO  ] Generating answer file 'root/rhsc-answer-file-2.1u2'
[WARNING] Cannot write to answer file: root/rhsc-answer-file-2.1u2 Error: [Errno 2] No such file or directory: '/etc/yum.repos.d/root/rhsc-answer-file-2.1u2'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ INFO  ] Execution of setup completed successfully

----------------------

Comment 6 Pavithra 2014-07-09 06:22:46 UTC
Shubhendu,

Please review the edited doc text for technical accuracy and sign off.

Comment 7 Shubhendu Tripathi 2014-07-09 06:36:49 UTC
doc-text looks fine

Comment 9 errata-xmlrpc 2014-09-22 19:08:27 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-1277.html


Note You need to log in before you can comment on or make changes to this bug.