Hide Forgot
+++ This bug was initially created as a clone of Bug #1640868 +++ Description of problem: ----------------------- With the latest fix in cockpit-ovirt, gdeployStatus file is generated on the successful gluster configuration. When the user opts for cleanup on the successfully deployed gluster configuration, this file needs to be removed Version-Release number of selected component (if applicable): -------------------------------------------------------------- cleanup playbook shipped with gluster-ansible-roles-1.0.3 How reproducible: ----------------- Always Steps to Reproduce: --------------------- 1. Successfully complete gluster configuration 2. Cleanup the gluster configuration ( removal of volumes, VGs, PVs, etc ) 3. Start installation again Actual results: --------------- 'use existing configuration' option is available Expected results: ----------------- As the existing gluster configuration is cleanedup, there should not be 'use existing gluster configuration' option available Additional info: ---------------- Remove the file ( which holds the gdeploy status configuration ), when the cleanup playbook is executed --- Additional comment from Sahina Bose on 2018-11-19 00:05:35 EST --- Gobinda, can you check this? Create a bz clone in cockpit-ovirt if needed
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Posted patch: https://github.com/gluster/gluster-ansible/pull/65
This bug is the must required for the forthcoming RHHI-V release
Moving the bug as verified since the fix works. Conmponents: =========== glusterfs-6.0-2.el7rhgs.x86_64 gluster-ansible-roles-1.0.5-1.el7rhgs.noarch gluster-ansible-infra-1.0.4-1.el7rhgs.noarch gluster-ansible-repositories-1.0.1-1.el7rhgs.noarch gluster-ansible-features-1.0.5-1.el7rhgs.noarch Steps: ===== 1. Complete gluster deployment 2. Run the gluster_cleanup.yml 3. Verified that the file 'ansibleStatus.conf' is removed and also logged into the cockpit UI and verified that 'use existing gluster configuration' was not found
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:2557