openstack/manila-tempest-plugin - manila-tempest-plugin - OpenDev: Free Software Needs Free Tools

Fixed SharesActionsTest cases for API version >= 2.73
since a metadata field was added in that version.
Closes-bug: #1993283
Signed-off-by: Alexander Deiter <adeiter@infinidat.com>
Change-Id: Ib285d9c740558d1ff3e24acb1ccc3de7e1ad562f

Change-Id: Ibbc849f59a71c3368bd997e93cf4fe09151add4d

The tempest tests `test_promote_out_of_sync_share_replica` and
`test_resync_share_replica` are concurrency-prone.
Theses tests are trying to determine something that shouldn't really
be a problem and may require to over-engineer the APIs to solve it.
Closes-Bug: #1631314
Change-Id: I4519147f2c1e7f4ea060d83b1a34d0a85dca9687

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

When I ran manila scenario tests, some tests failed due to
ssh key authentication. I noticed that tests with single
instance pass, however, tests with more than one instance
(e.g. "test_read_write_two_vms" test) fail.
I figured out that every instance initialization creates a
unique keypair.
An unnecessary resource duplication, when a single user boots
more than one instance. Depending on test flow this may also
cause keypair mismatch.
Change-Id: Ic685d1b9574daf7e6c9b90d5636f1b614a70b0da
Related-bug: #1858024 

This tempest plugin is being split out of the main manila project in
accordance with Queens goal "Split Tempest Plugins into Separate
Repos/Projects"[1]. This patch applies the standard boilerplate files
for OpenStack projects so that it can stand on its own.
[1] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html