-
Bug
-
Resolution: Done
-
Major
-
netobserv-1.6-candidate
-
None
-
False
-
None
-
False
-
-
-
NetObserv - Sprint 250, NetObserv - Sprint 251
While testing the merge deduper, it seemed to not always report all the involved interfaces in flows. Here's my reproducing steps:
- I'm running with a 6-nodes cluster, ocp-4.15-rc5
- Deploy netobserv with sampling 1 and other default settings (merge deduper DISABLED)
- Deploy mesh-arena: `kubectl create namespace mesh-arena ; kubectl apply -f https://raw.githubusercontent.com/jotak/demo-mesh-arena/main/quickstart-naked.yml -n mesh-arena`
- Open netobserv console, in Flows table tab, set filter Destination Owner Name = "ui-base".
- You should see a bunch of flows, focus on one that has Node Direction "Ingress" or "Egress" (not Inner) and add a filter to its source
- If you query last 5 minutes, you should get around ~60 flows
- Now in Query options, click "Show duplicates": the number of flows doubles/triples, and we can see that 2 interfaces are involved
- Then enable merge deduper in Flowcollector:
- advanced:
env:
DEDUPER_JUST_MARK: "false"
DEDUPER_MERGE: "true" - Back to the console, refresh (perhaps clear cache), wait a little bit for new flows to come. There's only one visible interface. The other has disappeared, and it's not in the Interfaces list. It should be there.
- links to
- mentioned on