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

[GCP] "destroy cluster" doesn't delete the PVC disks which have the label "kubernetes-io-cluster-<infra-id>: owned"

XMLWordPrintable

    • Moderate
    • None
    • Installer (PB) Sprint 263, Installer (PB) Sprint 265
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Before the fix we were only searching for resources with the name filter. The fix allows the cluster destruction to find GCP disk resources using the labels filter too. Any disk resource with the label kubernets-io-cluster-<cluster-d>: "owned" will be deleted.
      Show
      Before the fix we were only searching for resources with the name filter. The fix allows the cluster destruction to find GCP disk resources using the labels filter too. Any disk resource with the label kubernets-io-cluster-<cluster-d>: "owned" will be deleted.
    • Bug Fix
    • In Progress

      Description of problem:

          "destroy cluster" doesn't delete the PVC disks which have the label "kubernetes-io-cluster-<infra-id>: owned"

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

          4.18.0-0.nightly-multi-2024-11-27-162629

      How reproducible:

          Always

      Steps to Reproduce:

      1. include the step which sets the cluster default storageclass to the hyperdisk one before ipi-install (see my debug PR https://github.com/openshift/release/pull/59306)
2. "create cluster", and make sure it succeeds
3. "destroy cluster"

Note: although we confirmed with issue with disk type "hyperdisk-balanced", we believe other disk types have the same issue.

      Actual results:

          The 2 PVC disks of hyperdisk-balanced type are not deleted during "destroy cluster", although the disks have the label "kubernetes-io-cluster-<infra-id>: owned".

      Expected results:

          The 2 PVC disks should be deleted during "destroy cluster", because they have the correct/expected labels according to which the uninstaller should be able to detect them.

      Additional info:

          FYI the PROW CI debug job: https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/pr-logs/pull/openshift_release/59306/rehearse-59306-periodic-ci-openshift-verification-tests-master-installer-rehearse-4.18-installer-rehearse-debug/1861958752689721344

              rh-ee-bbarbach Brent Barbachem
              rhn-support-jiwei Jianli Wei
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: