Bug 916089
| Summary: | 'gluster peer detach' of a server with bricks on it succeeded | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> | ||||||
| Component: | glusterfs | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> | ||||||
| Status: | CLOSED EOL | QA Contact: | Shruti Sampat <ssampat> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 2.1 | CC: | kaushal, knarra, mmahoney, mmccune, nsathyan, poelstra, rhs-bugs, sdharane, vagarwal, vbellur | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-12-03 17:17:11 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: |
|
||||||||
Created attachment 703338 [details]
gluster logs from server 2
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/ If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release. |
Created attachment 703337 [details] gluster logs from server 1 Description of problem: --------------------------------------- 'gluster peer detach' of a server, that had bricks on it, succeeded. Version-Release number of selected component (if applicable): glusterfs 3.4.0qa8 How reproducible: Saw this happen only once. Steps to Reproduce: 1. Create a volume on a two-node cluster such that there are bricks on both nodes and start the volume. 2. On one of the nodes, run 'gluster peer detach <IP-of-the-other-node>' Actual results: Peer detach succeeded. Expected results: Peer detach should fail. Additional info: Attaching glusterfs logs from both the servers.