Bug 1516288

Summary: [GSS] heketi doesn't remove old pods
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Damian Wojsław <dwojslaw>
Component: heketiAssignee: Michael Adam <madam>
Status: CLOSED ERRATA QA Contact: Rachael <rgeorge>
Severity: high Docs Contact:
Priority: urgent    
Version: rhgs-3.3CC: dwojslaw, hchiramm, jcall, madam, pprakash, rcyriac, rekhan, rhs-bugs, storage-qa-internal, vinug
Target Milestone: ---   
Target Release: CNS 3.9   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: heketi-6.0.0-2.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-05 03:08:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1526414    

Description Damian Wojsław 2017-11-22 12:20:25 UTC
Description of problem:
After some time of operating openshift the internal database of storage differs from actual list of deployed storage. This sometimes leads to a situation where new deployments fail or get stuck, because the pvr can't be satisfied.

Version-Release number of selected component (if applicable):


How reproducible:
Run oc with gluster as backing storage for pods. Create and delete projects. After some time you should see difference between what's on storage and what heketi thinks is there. 

Steps to Reproduce:
1. install Openshift cluster with gluster as CRS
2. Run some project creations, deletions
3. Check volumes in OpenShift and in heketi

Actual results:
The number of volumes present in heketi and not in OpenShift is different.

Expected results:
The number should be the same, 

Additional info:
In next comments

Comment 14 errata-xmlrpc 2018-04-05 03:08:10 UTC
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:0638