Bug 1188886
| Summary: | volume extended attributes remain on failed volume creation | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> |
| Component: | glusterd | Assignee: | bugs <bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.1 | CC: | bugs, sasundar |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-01 04:42:37 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: | |||
This is not a security bug, not going to fix this in 3.6.x because of http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html If the issue persists in the latest releases, please feel free to clone them |
Description of problem: When a volume creation fails, extended attributes are left behind on any bricks that were not part of that failure. Version-Release number of selected component (if applicable): 3.6.2 How reproducible: Always Steps to Reproduce: 1. Pick a brick and do something to ensure it fails, make the filesystem read only, use selinux to block access, whatever. Call this server3:/brick1 2. Create a volume: gluster volume create fubar server{1,2,3}:/brick1 3. When volume creation fails on server[12], getfattr -n trusted.glusterfs.volume-id -e hex /brick1 Actual results: volume-id exists preventing additional attempts at creating a volume with those server/brick combinations. Expected results: A failed volume creation should return the potential brick to pre-attempt state. Additional info: This is a common problem seen in #gluster. Users do not understand, based on the error message, what the cause of the problem is nor how to fix it.