tempest extend/shrink tests may use wrong share export location

Bug #1848278 reported by Tom Barron on 2019-10-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tom Barron

Bug Description

Manila shares may have multiple export locations in multiple address families -- IPv4 and IPv6 -- but the scenario tests that extend and shrink shares mount the shares using the first export location regardless of whether its address family is appropriate for the test. Consequently, one can have e.g. a compute instance attached only to an IPv4 network attempting a mount using an unreachable IPv6 export location so the mount attempt fails and the test case fails as well due to its own problems rather than to any problem with the code under test.

Tom Barron (tpb) on 2019-12-19
Changed in manila:
assignee: nobody → Tom Barron (tpb)
importance: Undecided → Medium
milestone: none → ussuri-2
Goutham Pacha Ravi (gouthamr) wrote :

The failures are sporadic on the CI because of the behavior of picking up these exports at random. It'd be nice to get the fix in at our convenience. Thanks, Tom!

Changed in manila:
importance: Medium → Low

Fix proposed to branch: master
Review: https://review.opendev.org/704246

Changed in manila:
status: New → In Progress
Changed in manila:
milestone: ussuri-2 → ussuri-3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers