Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1243443 - Unable to resolve gluster hook conflicts when there are 3 conflicts - Content + Status + Missing
Unable to resolve gluster hook conflicts when there are 3 conflicts - Content...
Status: CLOSED WONTFIX
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
3.1
Unspecified Unspecified
low Severity unspecified
: ---
: ---
Assigned To: Sahina Bose
RHS-C QE
: ZStream
Depends On:
Blocks: 1216951
  Show dependency treegraph
 
Reported: 2015-07-15 08:51 EDT by Arthy Loganathan
Modified: 2016-04-06 02:45 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
Unable to resolve Gluster hook conflicts when there are three conflicts: Content + Status + Missing Workaround: Resolve the Content + Missing hook conflict before resolving the Status conflict.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-06 02:45:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screenshot for gluster hook resolve error (244.12 KB, image/png)
2015-07-15 08:52 EDT, Arthy Loganathan
no flags Details

  None (edit)
Description Arthy Loganathan 2015-07-15 08:51:14 EDT
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
Comment 1 Arthy Loganathan 2015-07-15 08:52:54 EDT
Created attachment 1052352 [details]
screenshot for gluster hook resolve error
Comment 3 Arthy Loganathan 2015-07-15 09:00:28 EDT
sosreport logs can be located at - http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1243443/
Comment 7 Sahina Bose 2015-07-17 05:18:30 EDT
Logs are not accessible. Arthy, could you check?
Comment 9 Sahina Bose 2015-07-17 08:30:25 EDT
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.
Comment 10 monti lawrence 2015-07-22 16:10:31 EDT
Doc text is edited. Please sign off to be included in Known Issues.
Comment 11 Sahina Bose 2015-07-23 02:14:43 EDT
Looks good to me
Comment 13 Sahina Bose 2016-04-06 02:45:55 EDT
This is a corner case, and documented workaround available to get this to work.

Closing this as wont fix

Note You need to log in before you can comment on or make changes to this bug.