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

CCM not able to remove a LB in ERROR state

XMLWordPrintable

    • ?
    • Important
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-3827. The following is the description of the original issue:
      —
      Description of problem:

      If the Openstack Loadbalancer is moved to error status, CCM is not able to remove it:

E1117 11:25:09.920626       1 controller.go:320] error processing service e2e-test-openstack-crkht/udp-lb-etplocal-svc (will retry): failed to delete load balancer: load balancer 9f555a63-a166-4f80-82fa-f38cf2b96db2 is not ACTIVE, current provisioning status: ERROR

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

      4.12.0-0.nightly-2022-11-07-181244
RHOS-16.2-RHEL-8-20220804.n.1

      How reproducible:

      Always

      Steps to Reproduce:

      1. Apply  [^default-manifests.yaml] 
2. Modify on the OSP database the LB status to ERROR:

$ ssh heat-admin@192.168.24.40
$ sudo podman exec -it galera-bundle-podman-0 mysql
MariaDB [(none)]> use octavia;
MariaDB [octavia]> update load_balancer set provisioning_status='ERROR' where id='9f555a63-a166-4f80-82fa-f38cf2b96db2';

3. Destroy the project:

$ oc delete project e2e-test-openstack-crkht
project.project.openshift.io "e2e-test-openstack-crkht" deleted

      Actual results:

      The project deletion is stuck and the logs are reported on openshift-cloud-controller-manager pod

      Expected results:

      The LB is removed

              mdulko Michał Dulko (Inactive)
              openshift-crt-jira-prow OpenShift Prow Bot
              Ramón Lobillo Ramón Lobillo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: