Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 880827

Summary: server won't boot if hostname is not resolveable
Product: [JBoss] JBoss Operations Network Reporter: Viet Nguyen <vnguyen>
Component: InstallerAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.1.2CC: mazz, myarboro
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-22 16:11:36 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:
Attachments:
Description Flags
boot.log none

Description Viet Nguyen 2012-11-27 20:43:41 UTC
Created attachment 653106 [details]
boot.log

Description of problem:

A server in JON blade center does not have DNS set up properly so pinging the host locally you will see
"ping: unknown host qe1.jonqe.lab.eng.bos.redhat.com"

rhq-server.sh won't boot unless the hostname is added to /etc/hosts

See attached boot.log

Version-Release number of selected component (if applicable):
3.1.2.ER2

How reproducible:
100% 

Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 John Mazzitelli 2013-04-22 16:11:36 UTC
Well, the "Expected results:" part of the template is empty, so I have to ask - what did you expect? :)

The server's own hostname cannot resolve to an IP address - so how is the server supposed to boot itself? For example, what IP address does it bind its server sockets to?

In other words, I think this BZ is documenting the behavior we should expect 
if the server's own hostname is not resolveable to an IP address.

Note that it appears the error occurs inside the internals of JBossAS itself (so this would happen for any JBossAS application server you start up - it isn't isolated to just a JON Server).

I am closing this as "not a bug". Re-open with more details if I am misunderstanding what the problem is.