Hide Forgot
Description of problem: unable to resolve a hook's content conflict by copying from another host. When copying from another host,instead of copying the host version to all other hosts, rhsc actually copies the engine version to all hosts. This is using the transaction to resolve hook content conflict: POST /api/clusters/:clusterid/glusterhooks/:hookid/resolve <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <action> <resolution_type>COPY</resolution_type> <host.id>${id}</host.id> </action> Version-Release number of selected component (if applicable): rhsc-cb8 How reproducible: 100% Steps to Reproduce: 0. 2 node cluster created 1. create an hook script on each host with the content "engine copy" 2. sync the hook with engine via gui 3. change the contents of hook on each node, so that the contents of each hook script is distinct from the engine and the other node. 4. sync the scripts => content conflict for script flagged by engine 5. resolve by copying from one of the nodes Actual results: The hook script has been replaced with the contents from step 1, "engine copy". Expected results: the hooks content for each node should be the same the hooks content should not be the contents from step 1. the hooks content for each node should have the contents of the node selected in step 5, before executing step 5. Additional info:
Use the following parameters for resolving by copying from host: <action> <resolution_type>COPY</resolution_type> <host id="<Host-Id>"/> </action> or <action> <resolution_type>COPY</resolution_type> <host> <name>Host-Name</name> </host> </action>
verified fix in rhsc-cb11
Please review the edited DocText and signoff.
The correct comment would be - "Previously, resolving hook content conflict by copying hook content from another host was not working properly and always engine copy was getting copied. Now, the correct hook content from the selected host is copied and resolving hook content conflict is successful."
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html