Description of problem: If a containers provider has some archived entities and then its deleted, the archived entities will remain forever in the DB Version-Release number of selected component (if applicable): 5.7.0 How reproducible: Always Steps to Reproduce: 1. add an openshift provider and refresh 2. remove either a pod or a project from the openshift environment 3. refresh again and delete provider Actual results: the entity removed from the environment is still in the DB Expected results: the entity should not be in the DB Additional info:
PR: https://github.com/ManageIQ/manageiq/pull/14359
I can still see the deleted project although with deleted_on status: vmdb_production=# SELECT * FROM container_projects; 16 | 5bd75afc-c937-11e7-bc5a-001a4a16984a | bz-stuff | 2017-11-14 12:28:45 | 7245448 | Verifying | 2 | 2017-11-14 12:29:38.348377 | 2017-11-14 12:31:39.573588 |
Pavel, I cant manage to reproduce this. Are you sure the provider was already deleted when you checked the db? Lately destroying providers takes a while because we wait for associated workers to be destroyed.
Ari, I'll try to recreate this issue with you later this week.
Per comments 6 & 7 moving this bug back to ON_QA, Pavel if you reproduce it (pay attention the provider was actually deleted) , please reopen
My bad, forgot to delete the provider..