Tests for both scheduler hints e.g. same_host and different_host are
added and guarded by multiple backends check. Default version updated to
2.65.

Depends-on: Ic42d8a0c1d22e77ae64e0ca014607b28fd336467
Partially implements: bp/affinity-antiaffinity-filter

Change-Id: If9c123363d71ac6bc89e743efe4dc2a00299cf5a

The change [1] modified the share server migration complete
operation behavior in Manila.

In the previous behavior there was a chance that manila would
keep the inactive source share server after a successful
migration.

Such behavior is not possible anymore after this change was
merged, since Manila started to expect that the source share
servers were deleted within the successful completion of a share
server migration.

This change introduces a new waiter to make sure that the source
share server is actually being deleted from manila after the
migration complete phase.

[1] https://review.opendev.org/c/openstack/manila/+/803623

Change-Id: Ibb092111032241a71763da0c7fa40470a3cd95ae

Some vendors might not have enough available space for testing features
that require creating huge volumes. So, this patch adds a new tempest
CONF `capability_thin_provisioned` that could be used to create volumes
as thin provisioned during the test execution.

Change-Id: I646f782c3e2be5ac799254f08a248a22cb9e0358

This change modifies the behavior of some share server migration
tests. Since Xena release, after the share server migration is
completed, the share server will be always deleted.

Removes the code fragments that ensured that if a share server
existed, it should reach an 'inactive' state.

Signed-off-by: silvacarloss <ces.eduardo98@gmail.com>
Change-Id: I43bd3fdafea02eb8e853114a57bfb863a441f3ed

"create_share" method defines an instance variable self.share
that is not really needed which causes confusion in reading
the code.

Change-Id: Iec00424cfee7efd262989a49df1f7e7ebef83bed

We're experiencing failures to SSH into test
VMs over IPv6 IP addresses from private tenant
networks in the LVM driver job when testing
main branch code. It's possible this is a regression
in nova, neutron, neutron dynamic routing or bgp. We'll
drop this test exclusion when the bug has been
identified and fixed.

Change-Id: Ib39cb2bda862758f575262647e068dd9deaf1459
Partial-Bug: #1940324
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Some tests from share group and replication are not creating
share following the `share_size` tempest CONF. This patch
fixed them applying that configuration.

Change-Id: If525e97a5d456d6ddebb4bf9bc8ff6190c95a555

When using the shares client, since
86f24324

,
JSON objects from the response body are extracted in-place
rather than in the client methods. We didn't catch this issue
when merging [1] because these tests are skipped in the jobs
running against manila-tempest-plugin:

manila_tempest_tests.tests.api.admin.test_share_groups.ShareGroupsTest.test_default_share_group_type_applied_1_2_31 ... SKIPPED: Only if defaults are defined.
manila_tempest_tests.tests.api.admin.test_share_groups.ShareGroupsTest.test_default_share_group_type_applied_2_2_55 ... SKIPPED: Only if defaults are defined.
manila_tempest_tests.tests.api.admin.test_share_groups.ShareGroupsTest.test_default_share_group_type_applied_3_2_61 ... SKIPPED: Only if defaults are defined.

However, default share and group types are defined in the
grenade job and these tests are currently failing.

Change-Id: Ida39026d655d34af17846cd45867c2d46141f39f
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

This patch is a preparation for adding RBAC tests.
Currently, we only return the body without the response
in manila REST client. The response is necessary for
the testing, because we need to check the returned code
status and to compare it with the expected status.
This way we will check if the user has the right
permissions for the action.

Change-Id: If0e39afb635c469a25919770a869087bf5def561

Add get metadata item for share metadata testcase

Change-Id: Ib3b3148a99812c69476e51cf0609c08fc9c4a9ef

Supported stable branches in maintenance state
(ussuri, victoria, wallaby) use the Tempest and
plugin's master version for their testing.

To make sure master version (new tests or any changes)
are compatible with stable branch testing, we need to
add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the
stable branches in same way [1].

Ussuri onwards, Tempest or plugins are py3 only, so we
are running only python3 version of stable jobs

Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html

[1] https://opendev.org/openstack/tempest/src/commit/e8f1876aa6772077f85f380677b30251c2454505/.zuul.yaml#L646



Change-Id: Ib1067db3771bacb287517e370c83a13d8bea89b5
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Change of inheritance to "BaseSharesMixedTest" class since it
requires admin privileges.
This change will allow removal of duplicate code.

Beyond that, "create_share_type" method is under "BaseSharesTest",
which is incorrect since it requires admin privileges.

Change-Id: Idd2c2285e266f0b733301ccfae5c423340de2511

This patch validates that share has been deleted after
deletion of share instance.

Change-Id: I14db6e04d9635229e4554582268ba8c5f745b57a

For legacy reasons we always included snapshot_support
and create_share_from_snapshot_support in all the
share types the tests created. These extra-specs are
no different from any other optional extra-specs in
manila, atleast since API version 2.24 (snapshot_support
was "implied"/"required" until API version 2.23). 2.24
is a really old version to support for tempest testing.

Since we always use the latest API version to create the
share types necessary, we only ever need 1 required
extra spec (driver_handles_share_servers) - lets supply
the rest only within tests that need to test snapshots
and shares from snapshots.

This patch also adds missing skip decorators for share
group tests that were testing snapshots.

Change-Id: Ifaceab574e3242e44a9cf1bea77a4be9e505d8b8
Related-Bug: #1922784
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

API tests must be evaluated by min and max
versions, however, we've multiple places
where we don't seem to evaluate the min_version;
this leads to incorrect behavior when test
runners set a different min_version in their
test configuration.

We can also consolidate the decorators and
callables that we have. We attempted this in
the recent past [1], however, we replaced the
callables with calling a decorator method, which
resulted in many tests not being skipped.

This bugfix is currently necessary to get
tests working against stable/ussuri and
stable/train branches.

[1] I0c35aff993e67c1ef44c27580f8c2c829a6275f7
Change-Id: I2eceb1d5fe42b1b779e115a0144a5d9639d3753f
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

System-wide installation via the tempest plugin's
devstack-plugin is unnecessary since we set the
"TEMPEST_PLUGINS" devstack localrc variable with
manila-tempest-plugin, and that should handle installing
the plugin alongside other tempest requirements within
a test virtual environment.

Change-Id: Id312005dc0cc9e039a9c6a8a58476965e8d6954d
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:

  UserWarning: Usage of dash-separated 'description-file' will not be
  supported in future versions. Please use the underscore name
  'description_file' instead

[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb

Change-Id: I6e9d570f6d2ddbe0c09cd84784808708e503dd74

When unmounting a share with the kernel
client, the target directory must be what
we used during the mount operation.

This patch adds a create-share-from-snapshot
scenario test for the ceph-fuse client, and
drops the redundant 'ip_version' attribute
to test classes that was added in the
test reorganization patch earlier [1]

[1] I7e63434e745cc1c2a5e8aaccc20f7c31404742d9
Change-Id: I9e373c658bf8aefa5763b7bb58637969e5253312
Closes-Bug: #1921369
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Create protocol specific manager classes
where we can abstract away common code
to handle access rules and mount operations
and re-use these in the tests to get adequate
coverage to the three protocols we support
in these tests currently.

Change-Id: I7e63434e745cc1c2a5e8aaccc20f7c31404742d9
Closes-Bug: #1921369
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Remove capability_create_share_from_snapshot_support = False
from tempest config for both CephFS Native and CephFS NFS

Partially-Implements: blueprint create-share-from-snapshot-cephfs
Change-Id: Ifb984a3cee219fa97a9768495f80ff0c8349830b

This test case validates the fix to CVE-2020-27781.

The test will create a share and allow access to "admin" user.
This step should return success, but the access rule for
"admin" will be set to "error".

Related-Bug: #1904015
Depends-On: I1edd5a50079f325fa143a7e0d51b3aa3bb5ed45d
Change-Id: I01157147e749ae6068e9878bffe322cb3993fb60

We attempt to manage a share with a fake/invalid
path in some tests and expect asynchronous
failures. So as long as there's only one of these
fake/invalid exports known to manila at a time,
there's no issue. However, when tests are run in
parallel, we see failures because manila validates
that the export path provided isn't known so far.

Change-Id: Ic1ed8c559221417347eeb71441ed8e941d70b8f1
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Depends-on: I5ce0fabf59bfca5ebaf0be5ffe9986e2b0480295
Partially implements: blueprint share-size-limited-by-share-type

Change-Id: I14e71ccb5f8f4f1851bc023586d6c96841ad68f9

Getting "share_server_id" parameter requires an admin client.
Therefore it should be placed whithin the admin test suite.

Change-Id: I17c64b8ffe0538309bdd823c723dbf1176a92754