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

Flowcollector does not report status != Ready in OCP Console

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • 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

    Description

      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.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. NETOBSERV-1234 Updating flowcollector CRD YAML from console shows error

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. NETOBSERV-610 Condition status issues

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub netobserv/network-observability-operator#403: NETOBSERV-1224 Flowcollector does not report status != Ready in OCP Console

          GitHub openshift/openshift-docs#63934: Network Observability 1.4 Release Notes

          Web Link RHSA-2023:116729 Network Observability 1.4.0 for OpenShift

          mentioned on

          GitLab Merge request - Updated 3 upstream sources

          Activity

            People

              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

              Dates

                Created:
                Updated:
                Resolved: