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

[GCP] destroying a private cluster doesn't delete the forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • Yes
    • None
    • Rejected
    • Installer (PB) Sprint 263, Installer (PB) Sprint 265
    • 2
    • Done
    • Bug Fix
    • Hide
      * Previously, when destroying a cluster that was installing on {gcp-short}, forwarding rules, health checks and firewall rules were not deleted, leading to errors. With this update, all resources are deleted when the cluster is destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-43779[OCPBUGS-43779])
      Show
      * Previously, when destroying a cluster that was installing on {gcp-short}, forwarding rules, health checks and firewall rules were not deleted, leading to errors. With this update, all resources are deleted when the cluster is destroyed. (link: https://issues.redhat.com/browse/OCPBUGS-43779 [ OCPBUGS-43779 ])
    • None
    • None
    • None
    • None

      Description of problem:

          Destroying a private cluster doesn't delete the forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator.

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

          4.18.0-0.nightly-multi-2024-10-23-202329

      How reproducible:

          Always

      Steps to Reproduce:

      1. pre-create vpc network/subnets/router and a bastion host
      2. "create install-config", and then insert the network settings under platform.gcp, along with "publish: Internal" (see [1])
      3. "create cluster" (use the above bastion host as http proxy)
      4. "destroy cluster" (see [2])
      

      Actual results:

          Although "destroy cluster" completes successfully, the forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator are not deleted (see [3]), which leads to deleting the vpc network/subnets failure.

      Expected results:

          The forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator should also be deleted during "destroy cluster".

      Additional info:

      FYI one history bug https://issues.redhat.com/browse/OCPBUGS-37683    

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

                Created:
                Updated:
                Resolved: