Bug 961523

Summary: Add testing for slave Host Controller join to domain testsuite DefaultConfigSmokeTestCase
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brian Stansberry <brian.stansberry>
Component: Domain Management, TestsuiteAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: cdewolf, pjelinek, rsvoboda
Target Milestone: ER2   
Target Release: EAP 6.1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-16 20:20:02 UTC Type: Task
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 2013-05-09 19:52:23 UTC 
In the managed domain test suite, there is no testing of a slave HC joining a domain using our *standard config files*. There is, of course, already testing of slaves joining a domain, but those tests use custom testsuite-specific configurations. DefaultConfigSmokeTestCase tests the "domain.xml + host.xml" config set, so a master running servers is tested. But "domain.xml + host-master.xml" is not tested nor is "host-slave.xml". These latter two can be tested in combination, and that closes the hole.

This additional testing would have caught the https://bugzilla.redhat.com/show_bug.cgi?id=961273 regression.
Comment 4 Rostislav Svoboda 2013-06-07 10:18:59 UTC 
QA_ACK granted, AS TS enrichment.