Description of problem: Unable to resolve gluster hook conflicts when there are 3 conflicts - Content + Status + Missing Version-Release number of selected component (if applicable): rhsc-3.1.0-0.62.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create a cluster and add 3 servers to it, say: server1, server2, server3 2. Make sure that some hooks are existing in all the servers. If not, try creating some manually. 3. Create Content Conflict by changing the content of a hook (say: Hook1) in one of the servers (say: server1) in the cluster by manually modifying it from the back-end 4. Create Status Conflict by changing the status of a hook (say: Hook1) in the second server (say: server2) in the cluster by manually renaming the hook from the back-end: To Disable: Rename a hook with prefix "K" To Enable: Rename a hook with prefix "S" 5. Create Missing Conflict by removing a hook (say: Hook1) from the third server (say: server3) 6. Click on "Resolve Conflicts" 7. Select the appropriate Resolve Actions for all 3 types of conflicts and click on OK Actual results: "Error while executing action Enable Gluster Hook: Internal Engine Error" is seen. Expected results: All the conflicts shoiuld be successfully resolved Additional info: Screenshot Attached
Created attachment 1052352 [details] screenshot for gluster hook resolve error
sosreport logs can be located at - http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1243443/
Logs are not accessible. Arthy, could you check?
http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1243443/sosreport-LogCollector-20150717155811.tar.xz
The issue seems to be as the Status conflict is being resolved before the missing/ content conflict - and the file is not found to set this. Treating this as low priority, as this is not an often recurring case, and there's a possible workaround.
Doc text is edited. Please sign off to be included in Known Issues.
Looks good to me
This is a corner case, and documented workaround available to get this to work. Closing this as wont fix