Bug 1232569
| Summary: | [Backup]: Glusterfind list shows the session as corrupted on the peer node | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sweta Anandpara <sanandpa> | |
| Component: | glusterfind | Assignee: | Aravinda VK <avishwan> | |
| Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.1 | CC: | annair, asrivast, avishwan, divya, khiremat, mchangir, nsathyan, rhinduja, rhs-bugs, storage-qa-internal, vagarwal | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | RHGS 3.1.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.7.1-14 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the main status file related to the session was maintained in the node where the session was created. As a consequence, when "Glusterfind list" is executed on any node other than the node on which the session was created, the health of the session was shown as "corrupted." With this fix, the glusterfind does not to show "corrupted" when it does not find the status file in any other node except the node where the session is created. Now, the 'Glusterfind list' command will list the sessions only from the main node where the session is created.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1243838 (view as bug list) | Environment: | ||
| Last Closed: | 2015-10-05 07:11:54 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1216951, 1223636, 1243838, 1251815, 1257546 | |||
|
Description
Sweta Anandpara
2015-06-17 04:22:49 UTC
glusterfind commands will not work in peer nodes other than the initiated node. We need to enhance glusterfind to use Meta volume to save status files and collect pem keys from all nodes and distribute to all Nodes of cluster. With this enhancement, we can run glusterfind command from any peer node. For this bug I will send patch to prevent showing the session row in peer nodes other than initiated node. Upstream patch sent http://review.gluster.org/11699 Doc text is edited. Please sign off to be included in Known Issues. (In reply to monti lawrence from comment #6) > Doc text is edited. Please sign off to be included in Known Issues. Doc text looks good to me. Upstream patch posted. http://review.gluster.org/#/c/11699/ Downstream patch https://code.engineering.redhat.com/gerrit/#/c/56497/ Verified with build: glusterfs-3.7.1-14.el7rhgs.x86_64 Session is listed only from the main node from where it is created and from other peer it shows as "No Session" which is as per comment 4 [root@georep1 ~]# glusterfind create sessi2 master Session sessi2 created with volume master [root@georep1 ~]# [root@georep1 ~]# [root@georep1 ~]# [root@georep1 ~]# glusterfind list SESSION VOLUME SESSION TIME --------------------------------------------------------------------------- sessi2 master 2015-09-04 11:04:44 [root@georep1 ~]# [root@georep1 ~]# glusterfind create gf_session master Session gf_session created with volume master [root@georep1 ~]# glusterfind list SESSION VOLUME SESSION TIME --------------------------------------------------------------------------- gf_session master 2015-09-04 11:10:04 sessi2 master 2015-09-04 11:04:44 [root@georep1 ~]# Peer Node: ========== [root@georep2 ~]# glusterfind list No sessions found [root@georep2 ~]# [root@georep3 ~]# glusterfind list No sessions found [root@georep3 ~]# [root@georep4 ~]# glusterfind list No sessions found [root@georep4 ~]# Moving this bug to verified state and will open doc bug to make sure this is captured against "glusterfind list" in ADMIN guide. 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. https://rhn.redhat.com/errata/RHSA-2015-1845.html |