Description of problem: When a host OS is reinstalled, and a new IP address/FQDN is assigned to the interface associated with gluster network, the gluster server UUID is also different from the previous associated one. Reinstalling the host from UI does not reflect the new gluster server UUID, and the host is stuck at "Non-Operational" state Error message on host: "Gluster command [gluster peer status fisher.lab.eng.blr.redhat.com] failed on server pinstripe.lab.eng.blr.redhat.com" - which is thrown when trying to match the gluster server UUID known to engine with list of peer UUIDs from any one host Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Move a host(host3) to maintenance 2. Reinstall host3 OS, and assign a new IP address to interface associated with gluster network. The host FQDN associated with ovirtmgmt remains unchanged. 3. Peer probe the new IP address from one of the peers in cluster 4. Reinstall host from UI. Actual results: Host does not move to active state. Expected results:
Verified with RHV 4.1.3-5 With the re-installation of the host from RHV UI, the older gluster UUID is replaced with the new gluster UUID , and the host becomes operational