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

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

XMLWordPrintable

    • Important
    • Yes
    • Installer (PB) Sprint 265
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when you deleted backend service resources on {gcp-first}, some resources to be deleted were not found. For example, the associated forwarding rules, health checks, and firewall rules were not deleted. With this release, the installer tries to find the backend service by name first, then searches for forwarding rules, health checks, and firewall rules before it determines if those results match a backend service. The algorithm for associating resources is reversed and the appropriate resources are deleted. There are no leaked backend service resources and the issue is resolved. When you destroy a private cluster, the forwarding rules, backend services, health checks, and firewall rules created by the Ingress Operator are not deleted. (link https://issues.redhat.com/browse/OCPBUGS-48611[*OCPBUGS-48611*])
      Show
      * Previously, when you deleted backend service resources on {gcp-first}, some resources to be deleted were not found. For example, the associated forwarding rules, health checks, and firewall rules were not deleted. With this release, the installer tries to find the backend service by name first, then searches for forwarding rules, health checks, and firewall rules before it determines if those results match a backend service. The algorithm for associating resources is reversed and the appropriate resources are deleted. There are no leaked backend service resources and the issue is resolved. When you destroy a private cluster, the forwarding rules, backend services, health checks, and firewall rules created by the Ingress Operator are not deleted. (link https://issues.redhat.com/browse/OCPBUGS-48611 [* OCPBUGS-48611 *])
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-43779. The following is the description of the original issue:
      —
      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
              openshift-crt-jira-prow OpenShift Prow Bot
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: