Bug 1322601

Summary:	Container Overview does not get cleaned up when deleting and adding a new provder
Product:	Red Hat CloudForms Management Engine	Reporter:	ldomb
Component:	Providers	Assignee:	Ari Zellner <azellner>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Aziza Karol <akarol>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.5.0	CC:	akarol, dajohnso, fsimonce, jfrey, jhardy, kmorey, ldomb, nstephan, obarenbo
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	container:retest
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-03 12:31:30 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:

Description ldomb 2016-03-30 21:03:03 UTC

Description of problem:
It seems that if an OpenShift 3.11 provider gets deleted and a new OpenShift  provider gets added with the same name as the old provider the Container Overview is not getting deleted correctly. This has the effect that the overview shows nodes from the old OpenShift provider as well as the new provider. 

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


5.5.2.4.20160127105142_395c086


How reproducible:
You will need 2 ose installations to do that. 

Steps to Reproduce:
1.Create a OpenShift provider with the name bob
2.Wait until it populates in the overview
3.Delete the OpenShift provider
4.The overview still shows the nodes even if the provider was deleted (Bug number one)
5. create a new OpenShift provider named bob pointing to another ose installation
6. Check the container overview. It will now show the old and new nodes from provider bob even if its a different ose installation. 

Actual results:
Container overview shows wrong data for example wrong nodes.  

Expected results:
The container overview should be correct when a OpenShift provider is deleted and readded. 

Additional info:

Comment 2 Dave Johnson 2016-04-11 21:52:29 UTC

Aziza, can you try and reproduce this with VMware and ec2 please.

Comment 3 Aziza Karol 2016-04-12 10:56:25 UTC

This issue is not reproducible on VMware and ec2.

Comment 4 Ari Zellner 2016-04-26 11:06:06 UTC

I havent been able to reproduce this.
Notice that the delete might take some time both for the entities and their metrics on the dashboard. If this takes more than a reasonable amount time then its a problem. 
Can you say how much time has passed?

Comment 5 Federico Simoncelli 2016-04-29 12:18:13 UTC

ldomb can you reproduce and attach the screenshots of the steps and unexpected result. Thanks.

Comment 6 ldomb 2016-05-03 11:58:12 UTC

I don't have 2 environments right now as I have to rebuild the one in the salab.

Comment 7 ldomb 2016-05-03 12:14:44 UTC

This seems to be fixed now. Just tested in my environment

Comment 8 Federico Simoncelli 2016-05-03 12:31:30 UTC

Not reproducible or fixed. ldomb please reopen this with more information in case you encounter it again. Thanks.