Created attachment 1436752 [details] screenshot of peer getting attached Description of problem: The expand cluster parameter in day 2 operations is hung after the peers are attached. No further processes are being performed. Version-Release number of selected component (if applicable): cockpit-ovirt-dashboard-0.11.24-1.el7ev.noarch How reproducible: Everytime Steps to Reproduce: 1.Successfully deploy the gluster and hosted engine. 2.Go to the 'HOSTED ENGINE' tab in cockpit UI and the click on 'Manage Cluster' tab. 3.Fill the all required parameters for expand cluster and deploy. 4.Go to the terminal and issue the command "gluster peer status". Actual results: The cockpit UI is hung and even when investigated the conf file the gdeploy process is terminating after peer probe. Expected results: The process should not stop after the peer probe and the volumes should be added and further procedures should proceed. Additional info:
Tested with the following: (i)redhat-release-virtualization-host-4.2-3.0.el7.x86_64 (ii)gdeploy-2.0.2-27.el7rhgs.noarch (iii)cockpit-ovirt-dashboard-0.11.999-0.0.master.el7.noarch.rpm Following are the steps performed for testing: (i) Successfully deployed gluster and hosted engine. (ii)Reached out to the gluster management wizard via hosted engine. (iii)Clicked on the expand cluster button and proceeded with configuring the tabs required for expanding the cluster . (iv) The expand cluster was not hung after the peers were probed.
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/RHEA-2018:3523