tempest does not fully support ipv6

Bug #1450820 reported by David Kranz on 2015-05-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

There is currently no way to run tempest with tenant isolation in an environment that only uses ipv6. There should be an option to control whether the isolated tenant code creates subnets with ipv4, ipv6, or both.

In addition, there are places in the code that do get_server(id)['addresses'][some-network-name][0] and then do something with the subnet descriptor. There was only one place in the code that was failing (due to the need to use 'ip6' instead of 'ip' for list server filter), but because the subnet list seems to be non-deterministic in terms of ordering, there may be subtle bugs in the other usages that can be found by searching for "'addresses'".

Changed in tempest:
importance: Undecided → Medium
assignee: nobody → Matthew Treinish (treinish)
status: New → Incomplete
status: Incomplete → Confirmed

This is still partially true. Pre-provisioed credentials provide a way to avoid going through the dynamic provisioning of network resources. Because of this I'm reducing this to wish list.
Matt are you still planning to work on this?

Changed in tempest:
importance: Medium → Wishlist
Changed in tempest:
assignee: Matthew Treinish (treinish) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers