Use of static and possibly invalid IP address in tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
Medium
|
Unassigned |
Bug Description
The following python modules have hardcoded addresses in the CIDR 127.0.0/24.
neutron_
neutron_
neutron_
neutron_
neutron_
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 |
Abandoned after re-enabling the Octavia launchpad.