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

Observe > Network Traffic does not show up after installing NOO in some setups

    • False
    • None
    • False
    • Previously, the Network Observability plugin would not show up in the Console. When this happens, console pods are stuck in a pending state. The current workaround is to restart the console pods, which should return all pods to a running state.
    • Known Issue
    • NetObserv - Sprint 227, NetObserv - Sprint 228, NetObserv - Sprint 229

      Setup: 1 master node, 3 worker nodes; AWS cluster; OCP 4.11

      This is a basic install. Install Loki, Grafana, NetObserv Operator 0.1.4 (standard one on Community). Create FlowCollector with eBPF and no Kafka.

      The menu item, Observe > Network Traffic, never appears. Yet I can see the flow data in Grafana! Everything looks good except the Network Observability Plug-in is missing the Version and Description information which is normally there (see attachment).

      There are no errors in the logs. If I run the patch command to notify CNO of the plug-in (i.e. oc patch console.operator.openshift.io cluster --type='json' -p '[

      {"op": "add", "path": "/spec/plugins", "value": ["network-observability-plugin"]}

      ]', it says there are no changes, which aligns with the UI that says this plug-in is enabled.

      With 3 master nodes, 3 worker nodes or 1 master node, 1 worker node, there are no issues. I tried this setup twice and got the same results.

              ocazade@redhat.com Olivier Cazade
              stlee@redhat.com Steven Lee
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: