I think this is the issue. When HCI deployed nodes. and consumed the drives and setup "engine" "data" and "vmstore" The GUI was set for "storage" network via hostsnames correctly. And I think, based on watching replication traffic it is using 10Gb "storage" network. CLI shows peers on that LAN also. BUT.. oVirt keeps refering to nodes as the "hostname" EX: thor.penguinpages.local (ovirtmanagment lan 1Gb 172.16.100.0/24) vs thorst.penguinpages.local (storage lan 10Gb 172.16.101.0/24) We see this error when I notice a brick having replication issue. Which the CLI does not show..... but that is a different topic :) # node "medusa" showing three unsynced files. Select brick ->reset But when I say "reset brick" to restart its replication I get error #### Error while executing action Start Gluster Volume Reset Brick: Volume reset brick start failed: rc=-1 out=() err=['brick: medusa_penguinpages_local:/gluster_bricks/vmstore/vmstore does not exist in volume: vmstore'] ## the real brick name is [root@odin ~]# gluster volume status vmstore Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick thorst.penguinpages.local:/gluster_br icks/vmstore/vmstore 49155 0 Y 14179 Brick odinst.penguinpages.local:/gluster_br icks/vmstore/vmstore 49156 0 Y 8776 Brick medusast.penguinpages.local:/gluster_ bricks/vmstore/vmstore 49156 0 Y 11985 Self-heal Daemon on localhost N/A N/A Y 2698 Self-heal Daemon on thorst.penguinpages.loc al N/A N/A Y 14256 Self-heal Daemon on medusast.penguinpages.l ocal N/A N/A Y 12363 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks