Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1545222

Summary:	Project stuck in Terminating state after deletion
Product:	OpenShift Container Platform	Reporter:	Gajanan <gchakkar>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED DUPLICATE	QA Contact:	DeShuai Ma <dma>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-14 22:10:04 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:

Description Gajanan 2018-02-14 12:26:15 UTC

Description of problem:

Project stuck in Terminating state after deletion for long period of time

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

$ less installed-rpms | egrep "atomic|docker|kernel" 
abrt-addon-kerneloops-2.1.11-48.el7.x86_64                  Tue Sep 26 14:54:00 2017
atomic-openshift-3.7.23-1.git.0.8edc154.el7.x86_64          Sat Feb 10 16:12:40 2018
atomic-openshift-clients-3.7.23-1.git.0.8edc154.el7.x86_64  Sat Feb 10 16:11:34 2018
atomic-openshift-docker-excluder-3.7.23-1.git.0.8edc154.el7.noarch Sat Feb 10 16:13:48 2018
atomic-openshift-excluder-3.7.23-1.git.0.8edc154.el7.noarch Sat Feb 10 16:14:25 2018
atomic-openshift-master-3.7.23-1.git.0.8edc154.el7.x86_64   Sat Feb 10 16:27:57 2018
atomic-openshift-node-3.7.23-1.git.0.8edc154.el7.x86_64     Sat Feb 10 16:40:14 2018
atomic-openshift-sdn-ovs-3.7.23-1.git.0.8edc154.el7.x86_64  Sat Feb 10 16:41:34 2018
atomic-openshift-utils-3.7.23-1.git.0.bc406aa.el7.noarch    Thu Feb  1 11:28:03 2018
atomic-registries-1.20.1-9.git436cf5d.el7.x86_64            Thu Feb  1 11:28:31 2018
cockpit-docker-157-1.el7.x86_64                             Sat Feb 10 16:34:14 2018
docker-1.12.6-71.git3e8e77d.el7.x86_64                      Thu Feb  1 11:29:09 2018
docker-client-1.12.6-71.git3e8e77d.el7.x86_64               Thu Feb  1 11:29:06 2018
docker-common-1.12.6-71.git3e8e77d.el7.x86_64               Thu Feb  1 11:29:05 2018
docker-rhel-push-plugin-1.12.6-71.git3e8e77d.el7.x86_64     Thu Feb  1 11:29:05 2018
kernel-3.10.0-693.17.1.el7.x86_64                           Thu Feb  1 11:21:25 2018
kernel-3.10.0-693.el7.x86_64                                Tue Sep 26 14:53:45 2017
kernel-devel-3.10.0-693.17.1.el7.x86_64                     Thu Feb  1 11:21:05 2018
kernel-devel-3.10.0-693.el7.x86_64                          Tue Sep 26 14:52:20 2017
kernel-headers-3.10.0-693.17.1.el7.x86_64                   Thu Feb  1 11:19:17 2018
kernel-tools-3.10.0-693.17.1.el7.x86_64                     Thu Feb  1 11:21:40 2018
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64                Thu Feb  1 11:20:30 2018
python-docker-2.4.2-1.3.el7.noarch                          Sat Feb 10 16:01:39 2018
python-docker-pycreds-1.10.6-3.el7.noarch                   Sat Feb 10 16:01:39 2018
tuned-profiles-atomic-openshift-node-3.7.23-1.git.0.8edc154.el7.x86_64 Sat Feb 10 16:40:12 2018



How reproducible: everytime, similar issue reproduced in my test environment as well. 


Steps to Reproduce:

1. Create a new project.
2. Add mysql service with "mysql persistent" template.
3. wait for pods to run.
4. Delete project.
5. Project stuck in Terminating status.

Actual results: Project stuck in Terminating status.

Expected results: Project should get deleted and should not get stuck in Terminating Status. 

Additional info: Customers pod is also seen stuck in terminating state. But when I tried to reproduce it, my pod was deleted successfully but project is still in terminating state

Comment 1 Seth Jennings 2018-02-14 22:10:04 UTC

Had to dig through the logs to get the important information; what is fulfilling the PVs.  The answer is gluster/CNS.

The logs show me that this is an occurrence of this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1489082

*** This bug has been marked as a duplicate of bug 1489082 ***