Bug 1102752

Summary: deployed applications are not distributed to host controller(s)
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tom Fonteyne <tfonteyn>
Component: Domain ManagementAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: high Docs Contact: Russell Dickenson <rdickens>
Priority: high    
Version: 6.3.0CC: emuckenh, jdoyle, kkhan
Target Milestone: ER6   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1102753 (view as bug list) Environment:
Last Closed: 2014-06-28 15:24:48 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:
Bug Depends On:    
Bug Blocks: 1102753    

Description Tom Fonteyne 2014-05-29 13:39:21 UTC 
https://issues.jboss.org/browse/WFLY-3418

I realize this is likely to late for inclusion in 6.3 but would like to ask anyhow. Otherwise, we kindly request this for a CP.


    Install node 1
    remove all local servers
    start it in domain mode, so it runs as the DC
    use the CLI to deploy an application

=> the application will end up in the domain/data/content folder as expected.

    Install node 2 on another machine
    remove all local servers
    point it to the DC on node 1
    start in domain mode, so it runs as a HC
    wait a little...
    stop the node 2, and inspect the local domain/data/content
    => empty

    start node 2 again
    on node 1, with the CLI, deploy a second application
    inspect node 2 local domain/data/content
    => the new / 2nd application will have been copied but the original first is still not copied.

Whether you start node 2 with or without "--backup" makes no difference.

Problem:
due to the HC not receiving a full copy of the "content" folder, it is not possible to promote the HC to a DC (when the original DC is down)
Comment 1 Tom Fonteyne 2014-05-29 13:53:31 UTC 
workaround:
Do not promote an HC. Instead have a backup of the DC and restore when needed.
Comment 2 Tom Fonteyne 2014-05-29 15:18:07 UTC 
workaround2:
use rsync or similar to keep the "content" directory of an HC synced with the DC
Comment 4 Petr Kremensky 2014-06-17 10:17:00 UTC 
Verified on EAP 6.3.0.ER7.

Starting a node 2 with the "--backup" force synchronization of domain/data/content folder with node 1.