floating ips not reachable with linuxbridge agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Stefan Nica |
Bug Description
The floating IPs of instances are not reachable when linuxbridge is used as the ML2 mechanism driver. The vlan subinterfaces on compute nodes are DOWN and the linuxbridge-agent logs exhibit errors such as:
2017-09-05 13:58:56.625 30355 ERROR neutron.
-------
Unserializable message: Traceback (most recent call last):
File "/usr/lib64/
send(msg)
File "/usr/lib/
s = self.dumps(obj)
File "/usr/lib/
return json.dumps(obj, cls=RpcJSONEnco
File "/usr/lib64/
sort_
File "/usr/lib64/
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib64/
return _iterencode(o, 0)
File "/usr/lib/
return super(RpcJSONEn
File "/usr/lib64/
raise TypeError(repr(o) + " is not JSON serializable")
TypeError: ValueError('I/O operation on closed file',) is not JSON serializable
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
Additional info: this issue started manifesting in Pike because sysctl is missing from the linuxbridge- plugin. filters rootwrap configuration file. Note that sysctl was covered by the iptables- firewall. filters rootwrap configuration file until it was recently removed from there as well (see https:/ /review. openstack. org/#/c/ 436315/).