Bug 1093866

Summary:	The "admin-only-policy" slave HC config option is not implemented correctly
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brian Stansberry <brian.stansberry>
Component:	Domain Management	Assignee:	Brian Stansberry <brian.stansberry>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kremensky <pkremens>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	emuckenh, kkhan, smumford
Target Milestone:	ER5
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	In previous releases of JBoss EAP 6, a slave Host Controller started in admin-only mode would not be able to connect to the master Domain Controller to obtain the domain wide configuration. As a result, if a slave Host Controller is started with `--admin-only` and it's `host.xml` has the `admin-only-policy="fetch-from-master"` set, the slave cannot connect to the master to get the domain wide configuration. The slave will fail to start. This prevents the `--admin-only` slave using RBAC unless a copy of the domain-wide configuration file is stored locally as `domain.cached-remote.xml` and the slave is started with `--cached-dc`. In this release the slave connection logic has been corrected and the slave can connect to the master and get the domain wide configuration, allowing it to obtain the domain-wide RBAC configuration policy.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 14:40:44 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:

Description Brian Stansberry 2014-05-02 21:50:18 UTC

Description of problem:

If a slave Host Controller is started with --admin-only and it's host.xml has the admin-only-policy="fetch-from-master" set, the slave cannot connect to the master to get the domain wide configuration.

This prevents the --admin-only slave using RBAC unless a copy of the domain-wide configuration file is stored locally as domain.cached-remote.xml and the slave is started with --cached-dc.

How reproducible:

Always.

Steps to Reproduce:
1. Add the admin-only-policy="fetch-from-master" attribute to the domain-controller/remote element in a slave Host Controller's host config xml file. 
2. Start the slave with the --admin-only option.

Actual results:

The slave fails to start.

Expected results:

The slave should start, including connecting to the master to pull down the domain wide configuration.

Comment 2 Petr Kremensky 2014-07-02 08:38:20 UTC

Verified on EAP 6.3.0.ER8