Use of static and possibly invalid IP address in tests

Bug #1675785 reported by John Gruber on 2017-03-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
New
Medium
Unassigned

Bug Description

The following python modules have hardcoded addresses in the CIDR 127.0.0/24.

neutron_lbaas/tests/tempest/v2/ddt/base_ddt.py
neutron_lbaas/tests/tempest/v2/api/test_members_admin.py
neutron_lbaas/tests/tempest/v2/api/test_members_non_admin.py
neutron_lbaas/tests/unit/services/loadbalancer/test_loadbalancer_plugin.py
neutron_lbaas/tests/unit/db/loadbalancer/test_db_loadbalancerv2.py

These addresses are reserved, according to rfc5735, for loopback, meaning used inside the host. When used in regard to LBaaS, if the provider technology is implemented as a proxy gateway and not a proxy host, these addresses are invalid as pool members or loadbalancer.

I assume it would be better if the tempest client was used to create a Neutron network, subnet, and allocate IP addresses from that subnet as a dynamic test resource.

Changed in octavia:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers