-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18, 4.19, 4.20
Description of problem:
When diagnosing issue with cluster destroy for vSphere, we are not able to better pinpoint why VMs are not getting cleaned up. It would be nice to add debug logging that says when we are starting to attempt an action in addition to some new logging that shows what we are receiving from vSphere when listing items by tags. Tags are not to be problematic when querying vCenter so any clues would be helpful.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
Always
Steps to Reproduce:
Simply install a cluster and then uninstall. The logging we show in debug mode is insufficient. As for creating the issue where VMs are not cleaned up, this is hard to recreate.
Actual results:
Not enough info on where destroy logic is failing
Expected results:
More logging that gives us a better idea of where the issues are occurring.
Additional info:
This new logging is being added to help aid with a customer case. The Jira is https://issues.redhat.com/browse/OCPBUGS-55379 and the case number is 04119877
- blocks
-
OCPBUGS-56372 Enhance OCP Installer destroy logging for vSphere
-
- Closed
-
- is cloned by
-
OCPBUGS-56372 Enhance OCP Installer destroy logging for vSphere
-
- Closed
-
- links to