ip6tables rules for PD subnets not fully recreated at l3-agent restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Brian Haley |
Bug Description
currently ip6tables in the qrouter namespace has the following rule. This causes unmarked packets to drop.
-A neutron-
In a related bug (1570122) there was a problem that prefix-delegated sub-nets did not get a rule setting this mark on traffic incoming on the gateway port, and this traffic was thus dropped. Now, this seems to work correctly when a user creates a subnet with IPv6 from PD. The problem arises when the l3-agent restarts, or the router moves to another l3-agent, as the rule marking the traffic is not recreated in these cases. The result is the same symptoms as the bug #1570122
Adding the rule manually makes traffic flowing again, for instance with the line:
$ip6tables -t mangle -A neutron-
We are running at the Queens release at the moment:
- neutron-l3-agent 2:12.0.
This bugs are a major obstacle for IPv6 in our clouds, as we cannot deliver reliable transport of ipv6 packets when this rule suddenly are missing.
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in neutron: | |
status: | Confirmed → In Progress |
tags: | added: rocky-backport-potential |
Can you test a patch if I post one? I think there's one line of code missing.
https:/ /review. openstack. org/597710