Created attachment 885404 [details] Setup log Description of problem: # rhsc-setup --offline --config=<Answer_File> errors out with "Failed to execute stage 'Setup validation': Cannot find Jboss at /usr/share/jboss-as" Version-Release number of selected component (if applicable): rhsc-2.1.2-0.36.el6rhs.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHS-C 2.1 from the live channel 2. Execute #rhsc-setup --generate-answer=/opt/<Answer_File> 3. Add the entry "OVESETUP_SYSTEM/configureRedhatAccessPlugin=bool:False" in the above generate answer file to bypass Bug 1086718 3. Now use the generated answer file and try to auto install using # rhsc-setup --offline --config=/opt/<Answer_File> Note: "--offline" is used to bypass Bug 1086723 Actual results: Setup validation fails. See below: --------------------- [root@server1 opt]# rhsc-setup --offline --config=/opt/20140411164232-setup.conf [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/opt/20140411164232-setup.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140411165051.log Version: otopi-1.1.2 (otopi-1.1.2-1.el6ev) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Stage: Environment customization --== PACKAGES ==-- --== NETWORK CONFIGURATION ==-- [ INFO ] iptables will be configured as firewall manager. --== DATABASE CONFIGURATION ==-- --== OVIRT ENGINE CONFIGURATION ==-- --== PKI CONFIGURATION ==-- --== APACHE CONFIGURATION ==-- --== SYSTEM CONFIGURATION ==-- [ INFO ] NFS configuration skipped with application mode Gluster --== END OF CONFIGURATION ==-- [ INFO ] Stage: Setup validation [WARNING] Cannot validate host name settings, reason: cannot resolve own name 'server1' [ ERROR ] Failed to execute stage 'Setup validation': Cannot find Jboss at /usr/share/jboss-as [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140411165051.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed --------------------- Expected results: The auto install using an answer file should be successful. Additional info: Adding the following entry in the answer file can be used as a work-around for the time being to complete the auto install. ---- OVESETUP_CONFIG/jbossHome=str:/usr/share/jbossas ---- Setup log is attached.
This issue should be tested in 3.0 Brew build and ensured that it's working fine. If it's not working, this has to be documented along with the workaround given in the bug.
(In reply to Dusmant from comment #1) > This issue should be tested in 3.0 Brew build and ensured that it's working > fine. If it's not working, this has to be documented along with the > workaround given in the bug. This is failing even in the latest RHSC 3.0 build as well. See below: --------- [ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Cannot find Jboss at /usr/share/jboss-as [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140515151507.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140515151532-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed --------- I think it's because of using the flag "--config" as "--config-append" doesn't fail at all. That being said, it's definitely a bug as it's looking for an invalid JBoss path. So IMO, we should fix the bug by updating the JBoss path and also document the correct usage with the right flags for offline installation. What do you think?
We should fix the JBoss path for sure.
dup of bug#1014372, message was fixed at[1] [1] http://gerrit.ovirt.org/#/c/23945/
Please use: # rhsc-setup --offline --config-append=/opt/20140411164232-setup.conf
Shubhendu, can you also fill in the Fixed In Version?
(In reply to Prasanth from comment #6) > Shubhendu, can you also fill in the Fixed In Version? there is no actual fixed version, since initial release the answer file should have been specified using --config-append and not using --config.
(In reply to Alon Bar-Lev from comment #5) > Please use: > > # rhsc-setup --offline --config-append=/opt/20140411164232-setup.conf Alon, can you please specify an use case or an example in which "--config" is used? From "--help" output, it says only the following: ------------ --config=file Load configuration files. ------------
(In reply to Prasanth from comment #8) > Alon, can you please specify an use case or an example in which "--config" > is used? when support is required.
Closing as discussed with NOTABUG. The option --config-append works fine as expected.