tree 44bf37d3979f11c00deb7085ab14cb3c12445314
parent 560dd61d0aeadde7816bce8223adefeb06936377
author Yaroslav Lobankov <ylobankov@mirantis.com> 1432649080 +0300
committer Yaroslav Lobankov <ylobankov@mirantis.com> 1433329863 +0000

Fixing some tests for DHCP IPv6

The problem is that some tests in tempest/api/network/test_dhcp_ipv6.py
have wrong assumption on which exact IP a port will receive on the DHCP
enabled subnet. This is wrong because Neutron may assign ANY IP from
the subnet allocation pool based on some internal logic. So the check
should be that the port got ANY IP from the subnet allocation pool.

test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_64_subnets
test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_two_subnets
test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcp_stateful

In these tests the assumption is that the port will receive the first
or second IP address from the subnet allocation pool. But we can schedule
a network to 2 DHCP agents or more - two DHCP ports are created (while
the test expects one DHCP port) and the port created by the test may get
only the third IP address from the subnet allocation pool.

Closes-Bug: #1458878

Change-Id: I655f803aa96509e95d52e8288395714c88b9e3b4