Description of problem: ------------------------ Post the single node RHHI-V deployment from the cockpit, the host is added to the host twice, one with front-end FQDN, and other time with backend FQDN. Expected is that the host should be UP with front-end FQDN only. But in actual, the host with front-end FQDN is up while the the same host with backend FQDN is in 'Install Failed' state Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHHI-V 1.6 RHV 4.3.3 How reproducible: ------------------ Always Steps to Reproduce: --------------------- 1. Deploy RHHI-V on the single host 2. Post deployment check the hosts in the cluster Actual results: --------------- The same host is added twice one with front-end FQDN and other with back-end FQDN. The host entry with front-end FQDN is up while the host entry with back-end FQDN is in 'Install Failed' state Expected results: ----------------- Only one host in the cluster, added using front-end FQDN Additional info:
There exists the simple workaround of removing the host with 'Install Failed' status from the cluster
Created attachment 1611476 [details] Screenshot for verification
Tested with the following:- 1. rhvh-4.3.6.2-0.20190821 2.gluster-ansible-repositories-1.0.1-1.el7rhgs.noarch glusterfs-cli-3.12.2-47.4.el7rhgs.x86_64 glusterfs-rdma-3.12.2-47.4.el7rhgs.x86_64 glusterfs-3.12.2-47.4.el7rhgs.x86_64 glusterfs-api-3.12.2-47.4.el7rhgs.x86_64 python2-gluster-3.12.2-47.4.el7rhgs.x86_64 gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch glusterfs-events-3.12.2-47.4.el7rhgs.x86_64 vdsm-gluster-4.30.29-2.el7ev.x86_64 glusterfs-libs-3.12.2-47.4.el7rhgs.x86_64 gluster-ansible-cluster-1.0-1.el7rhgs.noarch gluster-ansible-infra-1.0.4-3.el7rhgs.noarch gluster-ansible-roles-1.0.5-4.el7rhgs.noarch glusterfs-fuse-3.12.2-47.4.el7rhgs.x86_64 glusterfs-geo-replication-3.12.2-47.4.el7rhgs.x86_64 gluster-ansible-features-1.0.5-3.el7rhgs.noarch glusterfs-client-xlators-3.12.2-47.4.el7rhgs.x86_64 3.cockpit-ovirt-dashboard-0.13.6-1.el7ev After the successful single node deployment, when logged into RHVM could find one host in the cluster, added using front-end FQDN. Hence ,moving the bug to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2963