Bug 765437 (GLUSTER-3705)
Summary: | [FEAT] Use uuid in volume info file for servers instead of hostname or ip address | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> |
Component: | glusterd | Assignee: | bugs <bugs> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | mainline | CC: | amukherj, bugs, chrisw, ian.conrad, jdarcy, joe, me, rwheeler, smohan, stefano.stagnaro |
Target Milestone: | --- | Keywords: | FutureFeature, Reopened, Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-15 16:37:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joe Julian
2011-10-05 18:39:50 UTC
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it. I myself encountered a situation where this feature would have prevented a disruption in my gluster volumes' availability after a hostname-change. Although detaching and re-attaching the peer was successful against the new hostname, at some point it reverted to the old hostname (which was to a different IP address), and my brick-hosts became detached as a result. This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release. We are thinking of addressing it in GD2, github reference https://github.com/gluster/glusterd2/issues/356 . Joe - since we don't have plan to fix this in current form of glusterd, do you have any objection if we close this bug and track it through the github reference mentioned? Closing in favor of the github issue. |