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

    • Important
    • Yes
    • Installer (PB) Sprint 263, Installer (PB) Sprint 265
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Before the fix it was possible for backend service resources to not be discovered. In this case the associated forwarding rules, health checks, and firewall rules would not be deleted. The fix attempts to find the backend service by name first then it searches for forwarding rules, health checks, and firewall rules and determines if those match a backend service. The fix reverses the algorithm for associating resources and deletes the appropriate resources. After the fix, there are no leaked backend service resources.

      destroying a private cluster doesn't delete the forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator
      Show
      Before the fix it was possible for backend service resources to not be discovered. In this case the associated forwarding rules, health checks, and firewall rules would not be deleted. The fix attempts to find the backend service by name first then it searches for forwarding rules, health checks, and firewall rules and determines if those match a backend service. The fix reverses the algorithm for associating resources and deletes the appropriate resources. After the fix, there are no leaked backend service resources. destroying a private cluster doesn't delete the forwarding-rule/backend-service/health-check/firewall-rules created by ingress operator
    • Bug Fix
    • In Progress

      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
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: