Bug 1700662 - Mismatch of heketi-cli and gluster volume list. after re installation of ocs . gluster has volumes which were there before uninstall.
Summary: Mismatch of heketi-cli and gluster volume list. after re installation of ocs ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cns-ansible
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: John Mulligan
QA Contact: Prasanth
URL:
Whiteboard:
: 1718789 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-17 06:25 UTC by Pulkit Kundra
Modified: 2020-02-28 14:17 UTC (History)
8 users (show)

Fixed In Version: openshift-ansible-3.11.119-1
Doc Type: Known Issue
Doc Text:
Cause: When the OCS uninstall playbook is run, it fails to clean the /var/lib/glusterd directory on the nodes where glusterfs pods were deployed. Consequence: If a new OCS is deployed with *at least* one glusterfs pod on the old nodes then the volumes created in the previous deployment are seen in the Gluster command outputs. These volumes are seen neither in OpenShift nor in Heketi thereby causing confusion. This has no impact on dynamic provisioning of the PVCs and usage of PVs created in new deployment. However device/node replace operations of Heketi might fail. Workaround (if any): Identify the list of volumes that were created in the previous deployment and delete the relevant directories and files from /var/lib/glusterd/ and /var/lib/heketi/fstab. Result:
Clone Of:
Environment:
Last Closed: 2020-02-28 14:17:40 UTC
Embargoed:

Attachments (Terms of Use)

Comment 5 Raghavendra Talur 2019-06-12 05:05:58 UTC 
*** Bug 1718789 has been marked as a duplicate of this bug. ***
Comment 6 Raghavendra Talur 2019-06-12 05:36:57 UTC 
Patch posted at https://github.com/openshift/openshift-ansible/pull/11683
Comment 7 Raghavendra Talur 2019-06-12 05:56:59 UTC 
Root cause:
When the OCS uninstall playbook is run, it fails to clean the /var/lib/glusterd directory on the nodes where glusterfs pods were deployed. If a new OCS is deployed with *at least* one glusterfs pod on the old nodes then the volumes created in the previous deployment are seen in the Gluster command outputs. These volumes are seen neither in OpenShift nor in Heketi thereby causing confusion.

Impact:
This has no impact on dynamic provisioning of the PVCs and usage of PVs created in new deployment. However device/node replace operations of Heketi might fail.

Workaround:
Identify the list of volumes that were created in the previous deployment and delete the relevant directories and files from /var/lib/glusterd/ and /var/lib/heketi/fstab.
Note You need to log in before you can comment on or make changes to this bug.