Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-56262

Enhance OCP Installer destroy logging for vSphere

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • Proposed
    • None
    • Done
    • Bug Fix
    • Hide
      * Before this update, the lack of detailed logging in the cluster destroy logic for {vmw-full} meant it was unclear why virtual machines (VMs) were not properly removed. Additionally, missing power state information could cause the destroy operation to enter an infinite loop. With this update, logging for the destroy operation is enhanced to indicate when specific cleanup actions begin, include vCenter names, and display a warning if the operation fails to find VMs. As a result, the destroy process provides detailed, actionable logs. (link:https://issues.redhat.com/browse/OCPBUGS-56262[OCPBUGS-56262])
      Show
      * Before this update, the lack of detailed logging in the cluster destroy logic for {vmw-full} meant it was unclear why virtual machines (VMs) were not properly removed. Additionally, missing power state information could cause the destroy operation to enter an infinite loop. With this update, logging for the destroy operation is enhanced to indicate when specific cleanup actions begin, include vCenter names, and display a warning if the operation fails to find VMs. As a result, the destroy process provides detailed, actionable logs. (link: https://issues.redhat.com/browse/OCPBUGS-56262 [ OCPBUGS-56262 ])
    • None
    • None
    • None
    • None

      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

              rhn-support-ngirard Neil Girard
              rhn-support-ngirard Neil Girard
              None
              None
              Shang Gao Shang Gao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: