Bug 1055604
| Summary: | "Failed to execute stage 'Setup validation': Cannot find Jboss at /usr/share/jboss-as" while running engine-setup on Fedora 20 | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Netbulae <info> |
| Component: | ovirt-engine-installer | Assignee: | Sandro Bonazzola <sbonazzo> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kubica <pkubica> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4 | CC: | alonbl, asegurap, didi, gklein, iheim, pstehlik, rbalakri, sbonazzo, tomek, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.5.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | integration | ||
| Fixed In Version: | ovirt-3.5.0-beta1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-17 12:42:39 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: | 1106392 | ||
| Bug Blocks: | 1060198 | ||
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc. Workaround, if the problem is really in the jboss, and the issue is not just alternate location. Download and extract upstream jboss at /opt/jboss... Use: engine-setup --jboss-home=<whatever> jboss is now installed at different location, so the following should work unless there is compatibility issue. # engine-setup --jboss-home=/usr/share/doc/wildfly Sandro Bonazzola 2014-02-11 05:53:16 EST Target Release: 3.4.0 → 3.5.0 Why? we should resolve this for 3.3.z as well. *** Bug 1064522 has been marked as a duplicate of this bug. *** > Sandro Bonazzola 2014-02-11 05:53:16 EST > Target Release: 3.4.0 → 3.5.0 > > Why? we should resolve this for 3.3.z as well. AFAIK, Fedora 20 support is not meant to be available in any version <= 3.4.0. And 3.3.4 should be last 3.3.z since 3.4.0 GA will be out the day before 3.3.4 RC.(In reply to Alon Bar-Lev from comment #4) (In reply to Sandro Bonazzola from comment #6) > > Sandro Bonazzola 2014-02-11 05:53:16 EST > > Target Release: 3.4.0 → 3.5.0 > > > > Why? we should resolve this for 3.3.z as well. > > AFAIK, Fedora 20 support is not meant to be available in any version <= > 3.4.0. > And 3.3.4 should be last 3.3.z since 3.4.0 GA will be out the day before > 3.3.4 RC.(In reply to Alon Bar-Lev from comment #4) There is upstream and there is downstream... if we can issue downstream fedora 20 with only spec fixups, why shouldn't we? (In reply to Alon Bar-Lev from comment #7) > There is upstream and there is downstream... if we can issue downstream > fedora 20 with only spec fixups, why shouldn't we? I'm not sure to have understood what you're meaning. Only way I see to have engine working on f20 right now is installing jboss7 in /opt/something or in its previous position in /usr/share/jboss-as on F20 and run engine-setup --jboss-home=<jboss directory> (In reply to Sandro Bonazzola from comment #8) > (In reply to Alon Bar-Lev from comment #7) > > There is upstream and there is downstream... if we can issue downstream > > fedora 20 with only spec fixups, why shouldn't we? > > I'm not sure to have understood what you're meaning. > Only way I see to have engine working on f20 right now is installing jboss7 > in /opt/something or in its previous position in /usr/share/jboss-as on F20 > and run engine-setup --jboss-home=<jboss directory> yes... and as sysadmin won't you prefer to use f20 even if you install jboss from upstream for now and add --jboss-home to engine setup? this is not a reason for us not to support f20. Re-targeting to 3.4.2, the solution can be backported. Re-targeting to 3.4.3 since we found an issue on upgrade that can't be handled for 3.4.2. (In reply to Sandro Bonazzola from comment #11) > Re-targeting to 3.4.3 since we found an issue on upgrade that can't be > handled for 3.4.2. The change reverting this for 3.4.2 was http://gerrit.ovirt.org/28112 . (In reply to Yedidyah Bar David from comment #12) > (In reply to Sandro Bonazzola from comment #11) > > Re-targeting to 3.4.3 since we found an issue on upgrade that can't be > > handled for 3.4.2. > > The change reverting this for 3.4.2 was http://gerrit.ovirt.org/28112 . re-targeting to 3.5 accordingly. Verified in 3.5.0-0.0.master.20140821064907.gitb794d66.fc20 oVirt 3.5 has been released and should include the fix for this issue. |
Description of problem: I installed ovirt 3.4.0 alpha on fedora 20 and when running engine-setup I get an error about missing jboss. When I check there is no directory /usr/share/jboss-as Version-Release number of selected component (if applicable): ovirt-engine-3.4.0-0.2.master.20140112020536.git9ad8529.fc20.noarch Actual results: --== END OF CONFIGURATION ==-- [ 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-20140120162323.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed From the setup log: 2014-01-20 16:24:18 DEBUG otopi.context context._executeMethod:138 Stage validation METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine_common.config.jboss.Plugin._validation 2014-01-20 16:24:18 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/config/jboss.py", line 62, in _validation osetupcons.ConfigEnv.JBOSS_HOME RuntimeError: Cannot find Jboss at /usr/share/jboss-as 2014-01-20 16:24:18 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Setup validation': Cannot find Jboss at /usr/share/jboss-as Additional info: