My setup: CentOS 7 with Gluster 9.6 managed outside of engine, includes 3 servers plusdt the engine host. engine is a standalong but controls the 3 managed gluster volumes hosts. One of the hosts manages the gluster volume. I have used this setup for years and have never seen this on the engine host, but I have on the gluster volume servers. engine.log: 2023-05-22 15:58:33,020-04 INFO [org.ovirt.engine.core.vdsbroker.gluster.Gluste rServersListVDSCommand] (DefaultQuartzScheduler6) [235e97d6] FINISH, GlusterServ ersListVDSCommand, return: [192.168.254.252/24:CONNECTED, kvm04.digitaldatatechs .com:CONNECTED, kvm02.digitaldatatechs.com:CONNECTED], log id: 513632a0 2023-05-22 15:58:33,032-04 INFO [org.ovirt.engine.core.vdsbroker.gluster.AddGlu sterServerVDSCommand] (DefaultQuartzScheduler6) [235e97d6] START, AddGlusterServ erVDSCommand(HostName = kvm02, AddGlusterServerVDSParameters:{hostId='41b5df10-e d0a-4d6a-b375-c77ae9b681b6'}), log id: 6b6b5c97 2023-05-22 15:58:36,237-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghan dling.AuditLogDirector] (DefaultQuartzScheduler6) [235e97d6] EVENT_ID: GLUSTER_S ERVER_ADD_FAILED(4,436), Failed to add host kvm02 into Cluster ovirt_cluster. Ad d host failed: rc=107 out=() err=['Probe returned with Transport endpoint is not connected'] This shows up about eveny 90 seconds. No other issues and the host is up, volume is up. Triple checked firewalld and even disabled it as a test. SELinux is disabled. I'm not sure what I'm missing. Everything looks great in the cockpit. Any help is appreciated. Thanks in advance.