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

these defaults in devstack-plugin-ceph are okay,
we expect the blocker in squid to have resolved
with the latest container image.
If we need to override jobs to test specific ceph
versions, we should do that against the manila
repo.
Change-Id: Ie9c62dc82b0a747257e4d6f395a127b6dd56341e
Closes-Bug: #2105833
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Adding barbican plugin to dhss=true dummy driver job
Depends-on: https://review.opendev.org/c/openstack/manila/+/955393
Change-Id: I10bdd54482a1c0d145f49cc3a095e880242d43f8
Signed-off-by: Saikumar Pulluri <saikumar1016@gmail.com>

The centos9 node used to test fips fails to deploy
a few openstack services as of Flamingo.
Switch it to a python3.11 environment for FIPS jobs
so that Flamingo services can run successfully there.
Change-Id: Ic60f6a833369cb326d8956da5763c51d75d3c311
Signed-off-by: Eric Harney <eharney@redhat.com>

Devstack has removed the USE_PYTHON3 variable[1][2] and now always uses
Python 3.
[1] https://review.opendev.org/c/openstack/devstack/+/920658
[2] Commit 5412dbfe7b797149f1f68100de8003b1876398fe
Change-Id: Ia42a03bd73b1b4b6e157c9ce2d7e02d1d59790ba

... because stable/2023.2 reached its EOL.
Change-Id: I934a60865a504f1a3d9af8a1f8df99bf6a7acdf5

Change-Id: I2bccc0667853c6030d9238124efd63a1dc68ab37

We duplicated the LVM driver job to have an integration
test job on Ubuntu 22.04 (Jammy Jellyfish). We don't
need to run it against master any longer, because
the runtime guidance for 2025.2 doesn't require it.
[1] https://governance.openstack.org/tc/reference/runtimes/2025.2.html
Change-Id: Iafe99618d96e28b4dcfbcf10692abd21b20ad63c
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

There's a bug in Ceph Squid that prevents
access rules from working as expected with
the Ceph Native driver
Change-Id: I11a3c8f573e5540840a23459d698197a9c3a8f4c
Related-Bug: #2105833
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Disables ingress in multinode-cephfs-nfs-cephadm job
pending nfs-ganesha bug fix for haproxy issues.
Depends-On: I425bb9eec525d82372f05edc63e4fb931e5a4887
Depends-On: I5f03698ed09ff906488711d5d5a6feb74146b6ca
Change-Id: I3dbab947bcf5a1df39ee16e308096b3ef75b6d51

Changing VIP from IPV6 to IPV4
Partial-Bug: 2082617
Change-Id: I112b4682b36fd8bfe9b0b2325578bedc1cd20dee

As per 2025.1 testing runtime[1], we need to test on Ubuntu
Noble (which will be taken care by depends-on tempest and devstack
patches to move base jobs to Noble) and at least single job to run on
Ubuntu Jammy (for smooth upgrade from previous releases).
This commit adds a new job to run on Jammy which can be removed
in future cycle when testing runtime test next version of Ubuntu
as default.
Depends-On: https://review.opendev.org/c/openstack/tempest/+/932156
[1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html
Change-Id: Id7ddf6e39ae8c0de72b2d48d6beed718fcd760ce

stable/2023.1 is planned to be in unmaintained state[1]
and with python 3.8 drop from Tempest[2], we have to pin the
Tempest for stable/2023.1 testing[3]. This means Tempest and
its plugin master does not need to support stable/2023.1.
With that we can remove the stable/2023.1 jobs from tempest
plugin master jobs.
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/UDQAC7SR5JAQJE5WBAG54A2MTBVBTJ44/
[2] https://review.opendev.org/c/openstack/tempest/+/933398
[3] https://review.opendev.org/c/openstack/devstack/+/933704
Change-Id: I906357495c50173c578cb54dc60fb4bc98620a4b

These jobs were removed from manila[1], because the drivers were
deprecated.
The job definitions are still kept to be used in stable branches.
[1] a50f699d449ac286c9ea4a9617abf8fc60845f2e
Change-Id: I5a1126f1c0a9c0f0d83569b5c4de37e1ecdbfca4

This file is used only in code style checks.
Change-Id: Iabd59b683ac998a784eccc7fbc634ad1eb20e889

stable/2024.2 was released, so should be tested now.
Also replace codenames by official release names.
Change-Id: Ib861e1a707109daecb2cdd189de40da24bb829cb

Now that manila-tempest-plugin-cephfs-nfs is a cephadm
based job, and it is using Reef, we must add
CEPH_INGRESS_IP to job declaration.
Change-Id: Ib4a4479d5214f6c3a01ca1bd6301e44658bfec50

The ENABLE_CEPH_NOVA variable needs to be set
to False in the compute node because its disabled
in the controller.
Depends-On: I5f75cb829383d7acd536e24c70cc4418d93c13bc
Change-Id: I5c73ef42d8f01560ea85bffc2283ffaee001f48f

There's a regression in Ceph tracked by
https://tracker.ceph.com/issues/67323
So we'll skip the test for now while the
issue is resolved in Ceph.
Change-Id: I030fe57608f4082a84ff60c31132c9bc7cbd1b1e
Partial-Bug: #2075981
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Recently [1], we turned off a bunch of tests since we
were building out a way to run nfs-ganesha
standalone with a cephadm based ceph cluster [2].
Running API tests will increase the coverage. We
can retain the "backend" filter in our test regex
since we still don't want to run any API only tests
in this job.
[1] I5b7fd5b2b557203189c25fa2a988d790e7fda3eb
[2] If983bb5d5a5fc0c16c1cead84b5fa30ea961d21b
Change-Id: I2198eee3892b2bb0eb835ec66e21b708152b33a9
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

As per Ia1671de5c770d1cf5a3cd58e05fe5204f5bbc3c6,
fixed some ingress mode issues by identifying a
virtual ip as "CEPH_INGRESS_IP".
Bumping that variable to the parent job as well.
Change-Id: I8e04b866e2ebce291dfeb21dadda78ac2ecb8983

Reduce test concurrency to 1, and limit the tests to only those
tagged with 'backend' to hopefully reduce the resouce consumption
causing timeouts and flakiness in cephfs-nfs standalone jobs.
Change-Id: I777e8137c5a2b8f2a03667faf413ae65b1170d48

Neutron dynamic routing can be temporarily disabled, as it is not
being used until a known issue gets fixed [1].
[1] https://bugs.launchpad.net/manila/+bug/1940324
Related-Bug: #1940324
Change-Id: Iceeb41ff8c34fe86f2825089140801f983a96a85
Signed-off-by: Carlos Eduardo <ces.eduardo98@gmail.com>

cephfs-nfs job running on Reef, adding ingress ip
Change-Id: I5b7fd5b2b557203189c25fa2a988d790e7fda3eb

I28e6159944746abe2d320369249b87f1c4b9e24e introduced
OSCaaS and enabling it offers a good amount of speedup
in our test jobs. So lets enable it in the base jobs.
Change-Id: I4a1c8d75faa8151fb94cd227e24967a06d02ff4b
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

As 2024.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible to
stable branch.
At the same time, we're dropping the zed job
since the zed branch of openstack/manila has now
transitioned to "unmaintained". manila-tempest-plugin
may no longer support running against the zed branch.
Please use the "zed-last" tag instead [1]
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
[1] https://review.opendev.org/c/openstack/releases/+/918346
Change-Id: I0625576d14d9e084aa65beed5d0c988dcebd85dc
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

This is an effort to remove package based deployment
of Ceph from devstack-plugin-ceph in favor of ceph
orchestrator (cephadm) deployed ceph.
Change-Id: I0c35ef0eb4293aae37cd597d78d7aed0100e8ec7
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Share backup tests i.e. create/delete/get share_backups.
Change-Id: I366221702b3aa2e78bff82e6b2a543b6f6784f77

Xena and Yoga are past the stable maintenance
cycles. We're soon going to tag these release
branches as "unmaintained" branches [1]. We don't
expect the trunk version of manila-tempest-plugin
to work against these older branches any more.
Instead, we have tagged a "xena-last" and will
soon [2] tag a "yoga-last" branch that will be more
appropriate.
Going forward we must be testing the "maintained"
stable branches, which are zed, antelope, bobcat
as of this commit.
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://review.opendev.org/c/openstack/releases/+/908381
Change-Id: Ib0e984a4acdc2f82f5e3a75e34c7ec922674b0a5
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Pop off ceph release pin in cephfs-native-cephadm job
Change-Id: Idf15ccf996eb6cdc05a960bdc6411f6fdb9e5fea

The scenario test
`test_write_data_to_share_created_from_snapshot`
was being skipped because of a bug in ceph's MDS
service. It has now been addressed [1]
[1] https://tracker.ceph.com/issues/57210
Closes-Bug: #1989273
Change-Id: I967479458038b67c7892a71ac881491e1f8c87f7
Depends-On: Iea541d2edefc871bcac2d965997c88462fcbe521
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Use if=/dev/zero: Instead of reading from /dev/urandom,
which is slow for generating random data, use /dev/zero
to write zeros to the disk. Zeros are generated much faster.
Omit conv=fsync: The conv=fsync option forces dd to
synchronize the data after each write, which can be slow for
large writes.
Change-Id: Id845c60c39072a03171fa5906461eb254c2736a7

We had disabled scenario tests on the IPv6
test job manila-tempest-plugin-lvm [1] to prevent
gate failures at feature freeze. We can partially
re-enable these tests; while still working to
get IPv6 testing as well soon.
[1] https://review.opendev.org/c/openstack/manila-tempest-plugin/+/893651/
Related-bug: #1998489
Change-Id: Ie6599bc3533a002fa118ebe8b9243d677bdb410e
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

A multinode job creates a controller node
that runs manila with other OpenStack components;
and an additional compute node to spread the
compute VM workload around.
`manila-tempest-plugin-multinode-cephfs-nfs-cephadm`
replaces the existing `manila-tempest-plugin-cephfs-nfs`
in the check queue for this repository. These jobs
are different. `manila-tempest-plugin-cephfs-nfs`
uses devstack-plugin-ceph to install ceph and nfs-ganesha
as standalone components on the devstack host, whereas
`manila-tempest-plugin-multinode-cephfs-nfs-cephadm` uses
cephadm to deploy ceph, and it includes the deployment
of an nfs service. Manila's ceph driver communicates with
cephadm deployed nfs via ceph-mgr APIs, and with standalone
nfs-ganesha service via DBUS APIs. Ideally we'd run
both jobs all the time, however, since these jobs will
run individually against the manila repository, we'll just
pick the newer one here.
Depends-On: I84249ae268dfe00a112c67e5170b679acb318a25
Change-Id: I5162815b66d3f3e8cf8c1e246b61b0ea06c1a270
Co-Authored-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Zuul has deprecated Perl-style syntax; and we're
getting warnings posted against the manifests:
 The RE2 syntax error is: invalid perl operator: (?!
Change-Id: I498573532fd701b47684a54bda9b54b86836afdc
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

A couple of issues happening at the moment:
- Nova recently merged a change that bumps the libvirt version in
the Bobcat release [1]. The new libvirt version is not available
in Ubuntu Focal. In order to get the new libvirt version, our jobs
that were using Ubuntu Focal, are now forced to use Jammy, so we
bump it to the new version in this patch.
- The support for Ubuntu Focal has also been dropped in this
release [2]. Making it one more reason to get the new jammy
images.
While upgrading the image, some other issues surfaced:
- Some CI jobs are doing IPv6 testing, which use quagga. Quagga
does not have a candidate for installation in Jammy and must be
replaced. This issue is already documented [3].
- The inability to set up IPv6, combined with the scenario tests
being enabled in the LVM and CEPH drivers brought up another known
issue: when doing IPv6 setup, we don't set up only IPv6 networking
and we also end up setting crucial information for the scenario
tests to run in the function that does IPv6 setup. So in case the
job is only using IPv4 in scenario testing, we currently don't set
some key configuration to let the shares be created/mounted [4].
- Due to the reasons above, the scenario tests will never pass, as
we can't use Focal images, and when using Jammy, we can't do
scenario testing.
This is blocking the Manila gate and all other changes in the CI.
As we are forced to use the Jammy image and the scenario tests
won't pass, we disable them in this change, do some refactoring
in Manila [5], and re-enable them again for IPv4, until we have
figured out the quagga replacement.
[1] https://review.opendev.org/c/openstack/nova/+/887255
[2] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034968.html
[3] https://bugs.launchpad.net/manila/+bug/1998489
[4] https://github.com/openstack/manila/blob/master/devstack/plugin.sh#L1104-L1116
[5] https://review.opendev.org/c/openstack/manila/+/893804
Change-Id: Ia45a8e7f7c9cf9959bcc9b9a7243cccbbd1f4916