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
Gobinda, can you check this? Create a bz clone in cockpit-ovirt if needed
Calling this issue as the known_issue for RHHI-V 1.6. After cleaning the setup, and starting the fresh deployment, would still show up a opion - 'Use existing configuration' Once the gluster cleanup is done, always, do not use the option - "use existing configuration"
Update on the bug based on the base bug: --------------------------------------- The bug is fixed in the latest bits 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
The dependent bug is already in VERIFIED state, moving this bug to ON_QA
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:2963