networking-sfc: cannot set a flow classifier on an existing port chain
Bug #1716942 reported by
Bernard Cafarelli
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-neutronclient |
Fix Released
|
Undecided
|
Bernard Cafarelli |
Bug Description
Tested on current master, but Pike probably has the bug too:
$ openstack sfc port chain set --flow-classifier FC_udp PC1
'Client' object has no attribute 'list_sfc_
"set --no-flow-
And old CLI works:
neutron port-chain-update --flow-classifier FC_http PC1
To post a comment you must log in.
All the find_resource() calls for SFC may actually have a problem, the list command is expected to be plural and with a sfc_ prefix.
Looking into it