Bug 973091
Summary: | [RHS-C] Binary hook contents are being displayed during Resolve Conflicts | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Prasanth <pprakash> | ||||
Component: | rhsc | Assignee: | Kanagaraj <kmayilsa> | ||||
Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 2.1 | CC: | dpati, dtsang, kmayilsa, knarra, mmahoney, pprakash, rhs-bugs, sabose, sankarshan, sdharane, sharne, ssampat | ||||
Target Milestone: | --- | Keywords: | ZStream | ||||
Target Release: | RHGS 2.1.2 | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | CB10 | Doc Type: | Bug Fix | ||||
Doc Text: |
Previously, binary hook contents were displayed during Resolve Conflicts. Now, with this update, the binary hook content is not displayed in the 'Resolve Conflicts' window.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-02-25 07:30:39 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: | |||||||
Attachments: |
|
Description
Prasanth
2013-06-11 09:27:39 UTC
>> 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. http://rhn.redhat.com/errata/RHEA-2014-0208.html |