In case when such subnet is added directly to the router, there was
validation and subnet which is expected to get RA messages from the
external router couldn't be added to the Neutron router.
But in case when port was first created manually and then plugged to the
router, there wasn't such validation. This patch fixes it by adding same
validation to adding router interface by port.
Conflicts: neutron/db/l3_db.py
Change-Id: I054296c790b697198550acbeae29546758b422c2
Closes-Bug: #1889619
(cherry picked from commit 38c7fd7cef42e8c1e6430feb5ac01396c65560c2)
Reviewed: https:/ /review. opendev. org/744834 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=77ce09bcef8 26f81f1bd1ae0c8 b55b4ea36e3ec3
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 77ce09bcef826f8 1f1bd1ae0c8b55b 4ea36e3ec3
Author: Slawek Kaplonski <email address hidden>
Date: Fri Jul 31 12:50:16 2020 +0200
Fix validation of IPv6 subnets with external RAs
In case when such subnet is added directly to the router, there was
validation and subnet which is expected to get RA messages from the
external router couldn't be added to the Neutron router.
But in case when port was first created manually and then plugged to the
router, there wasn't such validation. This patch fixes it by adding same
validation to adding router interface by port.
Conflicts:
neutron/ db/l3_db. py
Change-Id: I054296c790b697 198550acbeae295 46758b422c2 1e6430feb5ac013 96c65560c2)
Closes-Bug: #1889619
(cherry picked from commit 38c7fd7cef42e8c