-
Bug
-
Resolution: Done
-
Major
-
netobserv-1.3, netobserv-1.2, netobserv-1.4, netobserv-1.5, netobserv-1.6
-
4
-
False
-
None
-
False
-
-
-
-
NetObserv - Sprint 255
-
Moderate
Description of problem:
If SRIOV secondary interface is already created before agent is deployed, ebpf-agent fails to recognize it unless application pods using secondary interfaces are redeployed or some states are changed on those secondary interface. This is a day 1 issue exists in all NOO versions
Steps to Reproduce:
1. Have SRIOV set up with applications using secondary interfaces. 2. Deploy NOO and create flowcollector with sampling 1 and privileged=true 3.
Actual results:
Existing SRIOV secondary interfaces are not detected when agent is deployed.
Expected results:
All SRIOV secondary interfaces are not detected when agent is deployed.
Workaround:
After netobserv-ebpf-agent is deployed, delete/re-create application pods
must-gather and SOS report from SRIOV node:
1. When secondary interface was created after agent:
https://drive.google.com/file/d/18T3vyB2-9d7_wilkJMJ_dG9WdK0mm6xU/view?usp=drive_link
2. When secondary interface already existed (not working scenario)
https://drive.google.com/file/d/1qFPQ7C4mPYU7UgAxHDuZjZOBaUvecvwP/view?usp=drive_link
3. SOS Report:
https://drive.google.com/file/d/17-oCRVHcQ7EwiNjdOmhJmzOCIiW5nj4z/view?usp=drive_link
- blocks
-
NETOBSERV-1667 Supporting non-SRIOV secondary interfaces (for Virtualization case)
- Closed
- is related to
-
RFE-5206 Secondary networks monitored through the Observability operator
- Backlog
- links to
-
RHSA-2024:133664 Network Observability 1.6.1 for OpenShift
- mentioned on