IMO the problem is in the devstack's configuration (or tempest test) as it is
using same IPv6 subnet 2001:db8::/64 for public network (devstack creates it)
and later in the tests for private networks.
Patch https://review.opendev.org/q/Id5d8ac09a38c656619f88a6f87b8f384fe4c55a8
just fixed bug in Neutron and improved checks of the subnets to prevent such
situation. I'm adding tempest as affected project as IMO bug is there, not in
the Neutron code.
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1914037
Title:
scenario tests tempest.scenario.test_network_v6.TestGettingAddress
fails
Status in neutron:
Invalid
Status in tempest:
New
Bug description:
scenario tests under group
tempest.scenario.test_network_v6.TestGettingAddress are failing
(observed on job tempest-slow on nova stable/rocky patches)
Example of failure:
https://7734cba1607fe472e545-7d211d4380eeb6317dc985091f0b7f02.ssl.cf5.rackcdn.com/761824/2/check/tempest-slow/e0359e0/testr_results.html
tempest.lib.exceptions.BadRequest: Bad request
Details: {u'message': u'Bad router request: Cidr 2001:db8::/64 of subnet
417e4c02-8b8a-4b89-bee2-32d35dc61b93 overlaps with cidr 2001:db8::/64 of subnet
56123648-b56d-486c-8919-a3e97802906f.', u'detail': u'', u'type': u'BadRequest'}
Could be because of recently merged patch
https://review.opendev.org/q/Id5d8ac09a38c656619f88a6f87b8f384fe4c55a8
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1914037/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
