Bug 879040 - Initialization of HostControllerComponent results in ERRORs in agent log due to assuming host controller's host is named "master"
Summary: Initialization of HostControllerComponent results in ERRORs in agent log due ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 6
Version: JON 3.1.1
Hardware: All
OS: All
unspecified
low
Target Milestone: ER01
: JON 3.2.0
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 879041
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-21 21:58 UTC by Larry O'Leary
Modified: 2018-11-29 19:24 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 879041 (view as bug list)
Environment:
Last Closed: 2014-01-02 20:33:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Excerpt from agent debug log (4.39 KB, text/x-log)
2012-11-21 22:19 UTC, Larry O'Leary
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 267443 0 None None None Never

Description Larry O'Leary 2012-11-21 21:58:06 UTC
Description of problem:
When a HostControllerComponent resource is initialized by the plug-in container, the follow error is seen in the agent's log:

ERROR [ResourceContainer.invoker.daemon-1] (rhq.modules.plugins.jbossas7.BaseServerComponent)- Failed to validate base dir for {JBossAS7}JBossAS7 Host Controller [/home/loleary/workspace/Cases/00744811/test-env/jboss-eap-6.0.0.GA/domain].
java.lang.Exception: Failed to read attribute [domain-base-dir] of address [] - response: Result{outcome='failed', failureDescription=JBAS010850: No handler for operation read-attribute at address [
    ("host" => "master"),
    ("core-service" => "host-environment")
], rolledBack=true}

Version-Release number of selected component (if applicable):
4.4.0.JON311GA

How reproducible:
Always

Steps to Reproduce:
1.  Install EAP 6
2.  Change the master host name from `master` to `mymain`

        cd "${JBOSS_HOME}"
        sed -i 's/<host name="master" xmlns="urn:jboss:domain:1\.3">/<host name="mymain" xmlns="urn:jboss:domain:1.3">/' "domain/configuration/host.xml"
    
3.  Start EAP server in domain mode

        cd "${JBOSS_HOME}/bin"
        ./domain.sh
        
4.  Start ON system
5.  Import EAP host controller into ON inventory
  
Actual results:
Agent log contains the error mentioned above

Expected results:
No error in the agent log

Additional info:
This is because we assume that the EAP host controller is named "master." Not sure why we are doing this as the host controller's name is determined by the user at configuration time.

Specifically, we are using hard coded values ENVIRONMENT_ADDRESS and HOST_ADDRESS in HostControllerComponent[1] which are used in validateServerAttributes[2]


[1]: http://git.fedorahosted.org/cgit/rhq/rhq.git/tree/modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/HostControllerComponent.java#n51
[2]: http://git.fedorahosted.org/cgit/rhq/rhq.git/tree/modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/BaseServerComponent.java#n131

Comment 1 Larry O'Leary 2012-11-21 22:19:50 UTC
Created attachment 649443 [details]
Excerpt from agent debug log

Attachment contains the complete stack and error as seen from the agent during initialization of the resource component.

Comment 3 Thomas Segismont 2013-08-06 16:24:36 UTC
Fixed in master

commit 74bbb4e2d9da88afb6b529517795451635dba0e1
Author: Thomas Segismont <tsegismo>
Date:   Tue Aug 6 17:51:05 2013 +0200

Comment 4 Jakub Cechacek 2013-11-19 12:55:10 UTC
Verified 3.2.ER5


Note You need to log in before you can comment on or make changes to this bug.