tempest extend/shrink tests may use wrong share export location

[Tom Barron]

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.

[Goutham Pacha Ravi (gouthamr)]

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!

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/704246
Committed: https://git.openstack.org/cgit/openstack/manila-tempest-plugin/commit/?id=645e4eb092a6cd7ba946ec949cec684112629eed
Submitter: Zuul
Branch: master

commit 645e4eb092a6cd7ba946ec949cec684112629eed
Author: Tom Barron <email address hidden>
Date: Tue Oct 15 17:26:41 2019 -0400

    Fix export location used for extend/shrink tests

    Instead of using the first export location, use the first export
    location matching the address family (IPv4 or IPv6) to be used
    for the mount.

    Closes-Bug: #1848278
    Change-Id: Ia2a0fefc34085e21e521acb7ccfdeecef7fda186