Traffic of trunk with subport is not classified correctly
Bug #1702426 reported by
Dima Kuznetsov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DragonFlow |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When a subport is added, its classification flows overwrite the flows of trunk port.
This happens because classification app receives event on both trunk and subport, and both share the same ofport.
Trunk classification flow:
cookie=0x0, duration=9614.115s, table=0, n_packets=0, n_bytes=0, idle_age=9614, priority=
Regular classification flow
cookie=0x0, duration=9565.526s, table=0, n_packets=333102, n_bytes=29460000, idle_age=0, priority=
description: | updated |
Changed in dragonflow: | |
status: | New → Confirmed |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/480197 /git.openstack. org/cgit/ openstack/ dragonflow/ commit/ ?id=d0e6cde422d 57d6c00156fbad8 2cd9372d898b2a
Committed: https:/
Submitter: Jenkins
Branch: master
commit d0e6cde422d57d6 c00156fbad82cd9 372d898b2a
Author: Omer Anson <email address hidden>
Date: Tue Jun 27 17:20:27 2017 +0300
Classifier to use OvsPort events
Partial-Bug: #1690775 2c1cd188efcf26a 48fd189dca3
Closes-Bug: #1702426
Change-Id: I56bf41b9ad5909