Bug 1226910

Summary: Fail nicely on hostname not resolvable
Product: [Retired] ovirt-engine-reports Reporter: Kevin Alon Goldblatt <kgoldbla>
Component: GeneralAssignee: Yedidyah Bar David <didi>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: bugs, didi, gklein, kgoldbla, lsurette, pmatyas, pstehlik, rbalakri, sbonazzo, sradco, srevivo, ykaul, ylavi
Target Milestone: ---Keywords: EasyFix
Target Release: ---Flags: ylavi: ovirt-4.1?
ylavi: planning_ack?
sbonazzo: devel_ack+
ylavi: testing_ack?
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-30 12:23:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1258789    
Attachments:
Description Flags
engine setup log none

Description Kevin Alon Goldblatt 2015-06-01 12:23:31 UTC
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

Comment 1 Kevin Alon Goldblatt 2015-06-01 12:45:33 UTC
Created attachment 1033325 [details]
engine setup log

Comment 2 Yedidyah Bar David 2015-06-01 12:59:32 UTC
     [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.

Comment 3 Yedidyah Bar David 2015-06-01 13:01:18 UTC
*** Bug 1226907 has been marked as a duplicate of this bug. ***

Comment 4 Yedidyah Bar David 2015-06-01 14:23:02 UTC
(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.

Comment 5 Kevin Alon Goldblatt 2015-06-02 12:31:01 UTC
I made the change by adding the host name to /etc/hosts/ and now the setup worked

Comment 6 Yedidyah Bar David 2015-06-02 13:05:44 UTC
Ok, so it's a duplicate of bug 1113094.

Yaniv, do we want to do anything?

Check and abort if hostname is not resolvable?

Comment 7 Yaniv Lavi 2015-06-02 13:33:09 UTC
(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?

Comment 8 Yedidyah Bar David 2015-06-02 13:57:17 UTC
(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.

Comment 9 Karolína Hajná 2015-07-21 06:49:53 UTC
*** Bug 1243802 has been marked as a duplicate of this bug. ***

Comment 10 Sandro Bonazzola 2015-10-01 08:14:49 UTC
Moved to 3.6.1 since it's not a 3.6.0 blocker

Comment 11 Red Hat Bugzilla Rules Engine 2015-10-19 10:52:44 UTC
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.

Comment 12 Karolína Hajná 2015-12-01 11:31:58 UTC
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.

Comment 13 Yedidyah Bar David 2015-12-01 12:50:58 UTC
*** Bug 1287006 has been marked as a duplicate of this bug. ***

Comment 14 Yedidyah Bar David 2016-01-31 10:11:41 UTC
*** Bug 1113094 has been marked as a duplicate of this bug. ***

Comment 15 Sandro Bonazzola 2016-05-02 09:55:20 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 17 Yedidyah Bar David 2016-05-30 12:23:24 UTC
Closing for now. Please reopen if relevant.