-
Bug
-
Resolution: Done
-
Major
-
netobserv-1.1, netobserv-1.3, netobserv-1.2, netobserv-1.4-candidate
-
False
-
None
-
False
-
-
-
-
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.
- relates to
-
NETOBSERV-1234 Updating flowcollector CRD YAML from console shows error
- Closed
-
NETOBSERV-610 Condition status issues
- Closed
- links to
-
RHSA-2023:116729 Network Observability 1.4.0 for OpenShift
- mentioned on
(1 mentioned on)