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

Enhance OCP Installer destroy logging for vSphere

XMLWordPrintable

    • Important
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when you diagnosed issues related to running the `openshift-install destroy cluster` command for {vmw-first}, the logging information provided insufficient detail. As a consequence, it was unclear why clusters were not removed from virtual machines (VMs). With this release, when you destroy a cluster, enhanced debug logging is provided and the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-56372[OCPBUGS-56372])
      Show
      * Previously, when you diagnosed issues related to running the `openshift-install destroy cluster` command for {vmw-first}, the logging information provided insufficient detail. As a consequence, it was unclear why clusters were not removed from virtual machines (VMs). With this release, when you destroy a cluster, enhanced debug logging is provided and the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-56372 [ OCPBUGS-56372 ])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-56262. The following is the description of the original issue:
      —
      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-rvanderp Richard Vanderpool
              openshift-crt-jira-prow OpenShift Prow Bot
              Shang Gao Shang Gao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: