glusterfs Host is not in 'Peer in Cluster' state"

Version: 4.5.1 Configure the HCI mode on the cockpit web interface, and the message "glusterfs Host is not in 'Peer in Cluster' state" is displayed. node1 gluster peer status normally shows three storage nodes #gluster peer status Number of Peers: 2 Hostname: 10.10.1.6 Uuid: 7973fa76-092e-4102-be43-d69ce2e1202f State: Accepted peer request (Connected) Hostname: 110.10.1.7 Uuid: c65ca1f1-8b0c-4424-80cd-d4606a6bed9e State: Accepted peer request (Connected) node2 # gluster peer status Number of Peers: 1 Hostname: localhost Uuid: 2fd3c233-6457-4d3e-9646-c1d6ed0c27aa State: Accepted peer request (Disconnected) node3 # gluster peer status Number of Peers: 1 Hostname: localhost Uuid: 2fd3c233-6457-4d3e-9646-c1d6ed0c27aa State: Accepted peer request (Disconnected) TASK [gluster.features/roles/gluster_hci : Create the GlusterFS volumes] ******* failed: [10.10.1.5] (item={'volname': 'tj-data1', 'brick': '/gluster_bricks/tj-data1/tj-data1', 'arbiter': 1}) => {"ansible_loop_var ": "item", "changed": true, "cmd": "gluster volume create tj-data1 replica 3 arbiter 1 transport tcp 10.10.1.5:/gluster_bricks/tj-data1/tj-data1 10.10.1.6:/gluster_bricks/ tj-data1/tj-data1 10.10.1.7:/gluster_bricks/tj-data1/tj-data1 force\n", "delta": "0:00:00.091228", "end": "2022-11-08 22: 37:07.609311", "item": {"arbiter": 1, "brick": "/gluster_bricks/tj-data1/tj-data1", "volname": "tj-data1"}, "msg": "non -zero return code", "rc": 1, "start": "2022-11-08 22:37:07.518083", "stderr": "volume create: tj-data1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state", "stderr_lines": ["volume create: tj-data1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state"], "stdout": "", "stdout_lines": []} failed: [10.10.1.5] (item={'volname': 'tj-vmstore1', 'brick': '/gluster_bricks/tj-vmstore1/tj-vmstore1', 'arbiter': 1}) => {"ansible_loop_var ": "item", "changed": true, "cmd": "gluster volume create tj-vmstore1 replica 3 arbiter 1 transport tcp 10.10.1.5:/gluster_bricks/tj-vmstore1/tj-vmstore1 10.10.1.6:/gluster_bricks/ tj-vmstore1/tj-vmstore1 10.10.1.7:/gluster_bricks/tj-vmstore1/tj-vmstore1 force\n", "delta": "0:00:00.092017", "end": "2022-11-08 22: 37:08.076088", "item": {"arbiter": 1, "brick": "/gluster_bricks/tj-vmstore1/tj-vmstore1", "volname": "tj-vmstore1"}, "msg": "non -zero return code", "rc": 1, "start": "2022-11-08 22:37:07.984071", "stderr": "volume create: tj-vmstore1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state", "stderr_lines": ["volume create: tj-vmstore1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state"], "stdout": "", "stdout_lines": []}

I already know why peering fails. GlusterFS needs to use fqdn, through DNS or hosts file to achieve When I deployed the first few machines, I used the IP without reporting an error, and I continued to deploy other machines and reported an error.
participants (1)
-
ziyi Liu