Two classifiers cannot be assigned to the same SFC chain

Bug #1719839 reported by Manuel Buil
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Dimitrios Markou

Bug Description

One of our OPNFV test requires that we classify on ports 20 and 80 for the same chain. Unfortunately, networking-sfc does not allow that ( and the solution that the colleagues in networking-sfc gave us is that we should create two different classification rules, one on port 22 and one on port 80, and assign both to the same chain. However, this functionality is not allowed in tacker, which only supports one classifier per chain. It would be very good for us if we could have that functionality

Changed in tacker:
assignee: nobody → Dimitrios Markou (mardim)
status: New → In Progress
Changed in tacker:
milestone: none → queens-2
importance: Undecided → Medium
Changed in tacker:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Submitter: Zuul
Branch: master

commit 5a888e1b1385824685171c06512646702f72a855
Author: Dimitrios Markou <email address hidden>
Date: Thu Oct 12 12:58:10 2017 +0300

    [Bug-Fix] Add support for multiple classifiers per chain

    Closes-Bug: #1719839

    Change-Id: I9884dc15584235b687c72a9f2cf9c180e9e1ce89

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tacker 0.9.0

This issue was fixed in the openstack/tacker 0.9.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers