Incorrect tag in other-config for openvsiwtch agent after upgrade to mitaka
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Undecided
|
Unassigned |
Bug Description
We've performed upgrade juno->kilo-
After mitaka upgrage we found that some of tenant networks are not functional. Deeper debug shows that in openvswitch tag value in 'other-config' field in ovs port description does not match actual tag on the port. (tag field).
This cause openvswitch-agent to set wrong segmentation_id on irrelevant host-local tags.
Visual symptom: after restarting neutron-
There are two ways to fix this:
1. reboot host
2. write tag field to the tag value of the port and restart neutron-
Example of the incorrectly filled port (ovs-vsctl port list):
_uuid : a5bfb91f-
bond_active_slave : []
bond_downdelay : 0
bond_fake_iface : false
bond_mode : []
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [7fb9c7a6-
lacp : []
mac : []
name : "tap20802dee-34"
other_config : {net_uuid=
qos : []
statistics : {}
status : {}
tag : 302
trunks : []
vlan_mode : []
This problems repeated in the few installations of openstack, therefore is not a random fluke.
This script [1] fixes bad tags, but I believe this is a rather serious issue with openvswitch-agent persistency.
[1] https:/
Affected version: mitaka, but I believe it related to previous versions, which was: juno, upgraded to kilo, upgraded to liberty, upgraded to mitaka.
Changed in neutron: | |
status: | New → Invalid |
Fixed in master, Newton and Mitaka (https:/ /review. openstack. org/#/c/ 422026/)
This bug is solved.