Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2164

[m5] After deleting orchestrator CR, DI pod isn't removed after OSL and serverless operators are deleted

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:

      After deleting a deployed Orchestrator CR, it removes the serverless and serverless-logic operators as designed. However, the DI pod keeps running:

      oc get pods -n sonataflow-infra 
NAME                                                      READY   STATUS    RESTARTS      AGE
sonataflow-platform-data-index-service-778f9566f5-qqsrk   1/1     Running   0             22m
sonataflow-psql-postgresql-679fc6b785-pkpsx               1/1     Running   1 (25m ago)   26m

      How reproducible: 100%

      Steps to reproduce:

      1. Deploy m5 usiong operator image 1.5.0-2025-03-11

      2. Deploy orchestrator CR with OSL and SL operators enabled

      3. After everything is done deploying, delete the orchestrator resource.

      Actual results:
      The OSL and SL operators are removed but the Data Index pod continues running. The deployment is also still there:

      oc get deploy -n sonataflow-infra 
NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
sonataflow-platform-data-index-service   1/1     1            1           26m
sonataflow-platform-jobs-service         0/0     0            0           23m
sonataflow-psql-postgresql               1/1     1            1           29m

      Expected results: DI pod should be removed with other resources.

              jubah@redhat.com Jennifer Ubah
              yfirst Yona First
              Yona First Yona First
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: