Red Hat Bugzilla – Bug 973091
[RHS-C] Binary hook contents are being displayed during Resolve Conflicts
Last modified: 2016-04-18 06:06:11 EDT
Created attachment 759503 [details]
screenshot of error
Description of problem:
Binary hook contents are being displayed during Resolve Conflicts
Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.0-0.bb2.el6rhs
How reproducible: Always
Steps to Reproduce:
Create a 3 server cluster.
1. Create a Text Hook (say: testhook.sh) in one of the servers and sync it across all the servers using the Resolve Conflict Missing feature.
2. Copy a Binary Hook to server1 with the same name as that of the Text Hook (testhook.sh). So currently, Server1 is having a binary hook with the name testhook.sh; server2 and server3 are having a text hook with the same name (testhook.sh)
3. A content conflict will now be determined in the UI and click on "Resolve Conflicts". The server copy will still be showing the "Text" content of the hook, whereas, server1 will be showing the "Binary" content.
Actual results: Binary contents of a hook is being displayed
Expected results: Content of the hook can be viewed ONLY if the hook content type is 'Text' as per http://www.ovirt.org/Features/Gluster_Hooks_Management#User_work-flows
Additional info: Screenshot attached.
>> 3. A content conflict will now be determined in the UI and click on "Resolve Conflicts". The server copy will still be showing the "Text" content of the hook, whereas, server1 will be showing the "Binary" content.
Now the Binary content is not getting displayed in server1, but instead it shows the text content with a different md5sum when we change the "Source" from "Engine (Master)" to "server1". May be the cleanup is not happening properly during the Source switch.
Moving back to Assigned.
verified in rhsc-cb10
Please review the edited DocText and signoff.
doc_text looks good.
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.