[Bugs] [Bug 1322145] Glusterd fails to restart after replacing a failed GlusterFS node and a volume has a snapshot

bugzilla at redhat.com bugzilla at redhat.com
Tue Jun 21 13:59:00 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1322145

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |NOTABUG
        Last Closed|                            |2016-06-21 09:59:00



--- Comment #7 from Atin Mukherjee <amukherj at redhat.com> ---
So this means that an IP change had happened? If so GlusterD is not capable of
handling this scenario until and unless some manual intervention is done (the
workaround you had executed). If you'd have used hostname while probing the
nodes, this situation could have been avoided.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=MT7OcJUSxg&a=cc_unsubscribe


More information about the Bugs mailing list