[neutron-tempest-plugin] test_dhcpv6_stateless_* clashing when creating a IPv6 subnet

Bug #1896592 reported by Rodolfo Alonso
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Medium
Unassigned
tempest
Expired
Undecided
Unassigned

Bug Description

The following three test cases are clashing when creating, at the same time, an IPv6 subnet with the same CIDR:
- test_dhcpv6_stateless_eui64
- test_dhcpv6_stateless_no_ra
- test_dhcpv6_stateless_no_ra_no_dhcp

Log: https://61069af11b09b96273ad-d5a2c2135ef34e5fcff72992ca5eb476.ssl.cf2.rackcdn.com/662869/6/check/neutron-tempest-with-uwsgi/9b9c086/controller/logs/tempest_log.txt

Snippet: http://paste.openstack.org/show/798195/

Error:
"Invalid input for operation: Requested subnet with cidr: 2001:db8::/64 for network: 31e04aec-34df-49dc-8a05-05813a37be98 overlaps with another subnet."

Changed in neutron:
importance: Undecided → Medium
Revision history for this message
Brian Haley (brian-haley) wrote :

This is actually a bug in the Tempest repo, we changed the code in neutron-tempest-plugin to be better at creating unique subnets in https://review.opendev.org/#/c/560465/

Wondering if we need to have a similar change in Tempest.

Should we change the component or just add it as affected? Although it is affecting the neutron gate it seems.

Revision history for this message
Martin Kopec (mkopec) wrote :

This sounds to me like neutron-tempest-plugin bug, I don't see how we could address this from tempest side. Correct me if I'm wrong, but the tests failed because they created/requested an overlapping networks/subnets, which seems to me that the class the tests belong to should be modified to avoid such situation.

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Actually reviewing again the logs, I can see the error is not due to the CIDR overlapping but because of a server 500 response: http://paste.openstack.org/show/798383/

The server raised an unknown error.

I'll leave this bug as incomplete for now. If we see more 500 responses from the server, we can change the bug description and try to fix it.

Regards.

Changed in tempest:
status: New → Incomplete
Changed in neutron:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tempest because there has been no activity for 60 days.]

Changed in tempest:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.