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

Flowcollector does not report status != Ready in OCP Console

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • netobserv-1.4
    • netobserv-1.1, netobserv-1.3, netobserv-1.2, netobserv-1.4-candidate
    • Operator
    • False
    • None
    • False
    • Hide
      Previously, FlowCollector status field may report incorrect information about the state of the deployment.

      Status field will now show the proper conditions with improved messages.
      The history of events is kept, ordered by event date.
      Show
      Previously, FlowCollector status field may report incorrect information about the state of the deployment. Status field will now show the proper conditions with improved messages. The history of events is kept, ordered by event date.
    • NetObserv - Sprint 240, NetObserv - Sprint 241
    • Important

      When Flowcollector status != Ready, it's not reported in OCP Console:

      In above screenshot, status is empty, however on CLI it showed as "DeploymentInProgress"

      $ oc get flowcollector
NAME      AGENT   SAMPLING (EBPF)   DEPLOYMENT MODEL   STATUS
cluster   EBPF    1                 DIRECT             DeploymentInProgress

      Steps to reproduce:

      • Run with downstream bundle v1.4.0-12 for OCP versions <= 4.12 where it's stuck in state DeploymentInProgress as ebpf pods are crashing.

        1. image-2023-07-31-11-41-30-994.png
          56 kB
          Mehul Modi
        2. Screen Recording 2023-08-23 at 1.01.33 PM.mov
          15.19 MB
          Amogh Rameshappa Devapura
        3. Screen Recording 2023-08-23 at 1.07.51 PM.mov
          11.36 MB
          Amogh Rameshappa Devapura

            jpinsonn@redhat.com Julien Pinsonneau
            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: