Description of problem: Engine setup on rhel6.7 engine fails with 'Misc configuration': Command './js-ant' failed to execute Version-Release number of selected component (if applicable): ovirt-engine-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch How reproducible: Always Steps to Reproduce: Installed rhel6.7 on a server 1.Ran the following installations: 2.yum install http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.0/latest_3.6.0/ovirt-release-master-latest.master.noarch.rpm 3.yum clean all && yum makecache 4.yum install ovirt-engine{,-dwh,-reports} 5.engine-setup >>>>> Fails with "Command './js-ant' failed to execute" Actual results: Engine-setup fails Expected results: Engine-setup should install Additional info: From engine.log: BUILD FAILED /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:263: The following error occurred while executing this line: /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:142: Java returned: 255 Total time: 29 seconds 2015-06-01 14:31:40 DEBUG otopi.context context._executeMethod:155 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 145, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py", line 721, in _deploy self._buildJs(config=config, cmd=cmd) File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py", line 212, in _buildJs 'buildomatic', File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 945, in execute command=args[0], RuntimeError: Command './js-ant' failed to execute 2015-06-01 14:31:40 ERROR otopi.context context._executeMethod:164 Failed to execute stage 'Misc configuration': Command './js-ant' failed to execute 2015-06-01 14:31:40 DEBUG otopi.transaction transaction.abort:134 aborting 'Yum Transaction' 2015-06-01 14:31:40 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:95 Yum Performing yum transaction rollback Loaded plugins: product-id, versionlock
Created attachment 1033325 [details] engine setup log
[java] Caused by: java.net.UnknownHostException: RHEL6.7Server: Name or service not known Please make sure your hostname is resolvable (e.g. by dns or /etc/hosts). Thanks! Probably a clone of bug 1113094.
*** Bug 1226907 has been marked as a duplicate of this bug. ***
(In reply to Yedidyah Bar David from comment #2) > [java] Caused by: java.net.UnknownHostException: RHEL6.7Server: Name or > service not known > > Please make sure your hostname is resolvable (e.g. by dns or /etc/hosts). > Thanks! > > Probably a clone of bug 1113094. If it is, we might want engine-setup to alert about this sooner and nicer, and not just close duplicate.
I made the change by adding the host name to /etc/hosts/ and now the setup worked
Ok, so it's a duplicate of bug 1113094. Yaniv, do we want to do anything? Check and abort if hostname is not resolvable?
(In reply to Yedidyah Bar David from comment #6) > Ok, so it's a duplicate of bug 1113094. > > Yaniv, do we want to do anything? > > Check and abort if hostname is not resolvable? How complex will it be to do this?
(In reply to Yaniv Dary from comment #7) > (In reply to Yedidyah Bar David from comment #6) > > Ok, so it's a duplicate of bug 1113094. > > > > Yaniv, do we want to do anything? > > > > Check and abort if hostname is not resolvable? > > How complex will it be to do this? Not that complex.
*** Bug 1243802 has been marked as a duplicate of this bug. ***
Moved to 3.6.1 since it's not a 3.6.0 blocker
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Entering a hostname different (but resolvable) from machine hostname during engine-setup causes ovirt-engine-reportsd service to fail to start (it becomes dead after a while). Machine hostname needs to be set properly in order to run the service. Thus there should be some warning about not matching hostnames as well.
*** Bug 1287006 has been marked as a duplicate of this bug. ***
*** Bug 1113094 has been marked as a duplicate of this bug. ***
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Closing for now. Please reopen if relevant.