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

ens5 interface still appears after being excluded

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • netobserv-1.9
    • CLI
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 273, NetObserv - Sprint 274, NetObserv - Sprint 275, NetObserv - Sprint 276, NetObserv - Sprint 277
    • None
    • None
    • None

      Follow-up on NETOBSERV-2257

      See also discussion here: https://github.com/netobserv/network-observability-cli/pull/308#pullrequestreview-2921035893

      Looks like the rule "0a:58=eth0" to disambiguate conflicting interfaces with OVN isn't sufficient, need to investigate why there's still "ens5" traffic remaining (probably wrongly detected as ens5), and if it can be resolved via another similar rule.

              Unassigned Unassigned
              jtakvori Joel Takvorian
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: