Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1293

flowcollector status oscillates between DeploymentInProgress and Ready

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      Previously, the FlowCollector status could sometimes oscillate between "DeploymentInProgress" and "Ready" states during reconciliation.
      Now, actual readiness is correctly detected, and the status only becomes "Ready" when all underlying components are fully ready.


      (old - RN 1.4: known issue)
      Currently, when the processor metric server is configured to use a provided certificate (`processor.metrics.server.tls.type` is `PROVIDED`), the operator enters in an unsteady state that might affect its performances and resource consumption. It is recommended to not use a provided certificate until this issue is resolved, and prefer using an auto-generated certificate (set `processor.metrics.server.tls.type` to `AUTO`).
      Show
      Previously, the FlowCollector status could sometimes oscillate between "DeploymentInProgress" and "Ready" states during reconciliation. Now, actual readiness is correctly detected, and the status only becomes "Ready" when all underlying components are fully ready. (old - RN 1.4: known issue) Currently, when the processor metric server is configured to use a provided certificate (`processor.metrics.server.tls.type` is `PROVIDED`), the operator enters in an unsteady state that might affect its performances and resource consumption. It is recommended to not use a provided certificate until this issue is resolved, and prefer using an auto-generated certificate (set `processor.metrics.server.tls.type` to `AUTO`).
    • NetObserv - Sprint 242, NetObserv - Sprint 243

      This was found while testing NETOBSERV-1087 when transitioned from DISABLED to PROVIDED mode and new FLP containers are being created, flowcollectors status oscillated between DeploymentInProgress and Ready until it became fully Ready:

      oc get flowcollector -w
cluster   EBPF    1                 DIRECT             DeploymentInProgress
cluster   EBPF    1                 DIRECT             Ready
cluster   EBPF    1                 DIRECT             DeploymentInProgress
cluster   EBPF    1                 DIRECT             Ready
cluster   EBPF    1                 DIRECT             DeploymentInProgress
cluster   EBPF    1                 DIRECT             Ready
cluster   EBPF    1                 DIRECT             DeploymentInProgress
cluster   EBPF    1                 DIRECT             Ready
cluster   EBPF    1                 DIRECT             DeploymentInProgress
cluster   EBPF    1                 DIRECT             Ready
cluster   EBPF    1                 DIRECT             DeploymentInProgress
cluster   EBPF    1                 DIRECT             Ready

      Expected results

      It should stick to DeploymentInProgress until rollout is complete before marking it Ready and should not oscillate

              ocazade@redhat.com Olivier Cazade
              rhn-support-memodi Mehul Modi
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: