[Bugs] [Bug 1756704] New: Peer Rejected (Connected) after instance recreation
bugzilla at redhat.com
bugzilla at redhat.com
Sun Sep 29 08:28:00 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1756704
Bug ID: 1756704
Summary: Peer Rejected (Connected) after instance recreation
Product: GlusterFS
Version: 6
Hardware: x86_64
OS: Linux
Status: NEW
Component: glusterd
Severity: medium
Assignee: bugs at gluster.org
Reporter: alexettelis at gmail.com
CC: bugs at gluster.org
Target Milestone: ---
Classification: Community
Description of problem:
When an instance dies in GCP, it is recreated with the same, but different boot
disk and different data drive. The other node see that node as Peer Rejected
(Connected)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create 3 node cluster
2. Recreate one of the instance (new boot and data disk) with the same name, IP
3. Run gluster peer status
Actual results:
On old nodes: Peer Rejected (Connected)
On new node: no peers
Expected results:
Every peer should be connected
Additional info:
The UUID of the new node is changed.
I tried editing glusterd.info with the new node UUID.
I tried restarting all of the nodes, deleting data on the broken node.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list