The port-chain-update API functionality fails to reverse order to PPGs

Bug #1746686 reported by Dimitrios Markou
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
networking-sfc
New
Undecided
Unassigned

Bug Description

I am using the networking-sfc API through Tacker to update the PPGs which are used in an existing chain.

When I am trying to reverse the order of the PPGs that are used in an existing chain through the update_port_chain API functionality the result is that the order is not updated but remains the same as before. The follwing example describes exactly that:

Let's say that the current chain connects the PPGs [red,blue]. If I try to update the chain through n-sfc API and pass to the update function the reverse order of the PPGs like [blue,red] the n-sfc will still give the result [red,blue]

summary: - The port-chain-update API functionality fials to reverse order to PPGs
+ The port-chain-update API functionality fails to reverse order to PPGs
Revision history for this message
Cong Phuoc Hoang (hoangphuoc) wrote :

I met this error too. Even with [blue, red] --> [red] --> [red, blue] but the result still [blue, red]

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.