Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1498031

Summary:	[RFE] [IPv6] _multi_ network tempest tests are failing
Product:	Red Hat OpenStack	Reporter:	Waldemar Znoinski <wznoinsk>
Component:	opendaylight	Assignee:	Sridhar Gaddam <sgaddam>
Status:	CLOSED DEFERRED	QA Contact:	Itzik Brown <itbrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	mkolesni, nyechiel, sgaddam, trozet
Target Milestone:	Upstream M1	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-02 12:02:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Waldemar Znoinski 2017-10-03 11:21:04 UTC

Description of problem:
tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_dhcpv6_stateless[compute,id-cf1c4425-766b-45b8-be35-e2959728eb00,network,slow]
tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_slaac[compute,id-9178ad42-10e4-47e9-8987-e02b170cc5cd,network]
tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_dhcpv6_stateless[compute,id-7ab23f41-833b-4a16-a7c9-5b42fe6d4123,network,slow]
tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac[compute,id-dec222b1-180c-4098-b8c5-cc1b8342d611,network,slow]

Version-Release number of selected component (if applicable):
opendaylight-6.2.0-0.1.20170921snap729.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. stack OSP12 with odl in container
2. run tempest test_network_v6 test suite
3. observe the failures

Actual results:
failures of _multi_ tests

Expected results:
success


Additional info:
The other (non _multi_) test_network_v6 tests are running ok

Comment 1 Sridhar Gaddam 2017-10-18 08:13:40 UTC

I had a close look at the failure and proposed the following WIP patch[1] to address this use-case.
However, when playing with multi subnets in the same network, I'm seeing many issues. 
Basically, Netvirt needs some additional changes to support multiple subnets in the same network.
So the use-case is more like an enhancement/RFE than a bug fix and will take sometime to address it properly. 

[1] https://git.opendaylight.org/gerrit/#/c/64113/

Comment 5 Nir Yechiel 2018-05-02 12:02:50 UTC

This is currently not supported in NetVirt. Multiple IPv6 subnets in a given network is not a widely used feature as far as I can tell, so I am closing this bug for now. Will open again if we have concrete customer demand.