This job is non-voting against the manila repos currently.
We've observed sporadic failures in data intensive scenario
tests. There are a number of manila tests that write a few
gigabytes of data onto mounted shares. While we've tried
to optimize test concurrency and the kind of data being written,
sometimes, things seem to fall over and a test case runs into
a generic I/O error. So maybe more work is necessary to
get this job to be stable; but that work may not be in this
devstack plugin repository.
Change-Id: Id89f161ba6dd5b5fbb5b82042a3e94c92797a881
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
download.ceph.com used to maintain named versions of ceph
releases, which were hardlinked folders corresponding
to the latest minor release from a stable branch; we've noticed
that these folders can be deleted. Let's instead look for
cephadm under the corresponding numeric release tag folder.
Change-Id: Ic39b48fb2dd48f47d5b3c6165e4f4c6b1c47cc7d
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
For releases older than reef (e.g., octopus, pacific), packages are not
always available under the el9 subdirectory.
This patch introduces a switch case to make sure we're able to match the
right version of cephadm.
Change-Id: I0ee37b832f1ea47961528f074f2d42492b0ac755
Ceph release tags adhere to a versioning scheme x.y.z [1], where:
- x = major release number (e.g.: quincy is 17, reef is 18)
- y = 1 or 2, where 1 is an release candidate, and 2 is a stable release
- z = patch/updates
We shouldn't hardcode a patch version in the default container
image we're fetching in our jobs, unless absolutely necessary
for some bugfix/feature that we rely on.
[1] https://docs.ceph.com/en/latest/releases/general/
Related-Bug: #1989273
Change-Id: Iea541d2edefc871bcac2d965997c88462fcbe521
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Reverting a bad rebase to fix cephadm binary source
Also adds catatonit to rpms file to fix CI issues
Change-Id: Ie1b1dc0ef2508eae38ae7954fb0bb62653780644
Add podman ceph-common and jq as part of preinstall dependency.
Add REMOTE_CEPH capabilities to CEPHADM deployment.
Removed set_min_client only if cinder is enabled, this should be set
in any case.
Get FSID from ceph.conf in /etc/ceph to avoid unnecessary override.
Part of an effort to test multinode deployments with cephadm.
Needed-By: I5162815b66d3f3e8cf8c1e246b61b0ea06c1a270
Change-Id: I84249ae268dfe00a112c67e5170b679acb318a25
Following up on the usage of inclusive jargon [1] and to ensure
consistency in code, there is a need to replace deprecated term
tempest_test_blacklist with a new term tempest_test_exclude_list.
[1] https://review.opendev.org/c/openstack/tempest/+/768583
Change-Id: I1692876c9d42b3ac857fdb61dcdc2caa61cd349d
We don't need to get cephadm from the source tree.
The ceph community publishes this binary on download.ceph.com [1]
[1] https://docs.ceph.com/en/latest/cephadm/install/#curl-based-installation
Change-Id: I9c1f46b15a03768aa92803e7c51522c3553b1595
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
We are about to drop Fedora support as the latest image in upstream
has been transitioned to EOL. Centos 9 Stream has evolved as replacement
platform for new features. Review which deletes nodeset from devstack:
https://review.opendev.org/c/openstack/devstack/+/885467
Change-Id: I3b1bece44b9ad2f4bf4d822f261b141ddf3031fd
Affects only the package based install script.
Pacific is going to be EOL'ed soon [1], we do not
expect folks to deploy the next version of OpenStack
(2023.2/Bobcat) with Ceph Pacific; moreover, all our
CI jobs are using Quincy by default, and the cephadm
script uses quincy by default.
[1] https://docs.ceph.com/en/latest/releases/index.html#active-releases
Change-Id: I6abdb1241e99d76bcee35b331e1059c4fe48296b
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
On the multinode job we need to enable validation like the base job
and also disable block migration for live migration that we get from
our parent job.
Change-Id: I076527536e19f7fa2c0cd177bebb1df22db51a0a
The overrides in "devstack-plugin-ceph-cephfs-nfs"
are being applied to the parent job, so they
can be removed here.
Depends-On: I6abf7a8eb275c5b29cfe29b3a0f54de76c5bb1e8
Change-Id: I35ebd069399d3a8d8e2bb56542a01993914b1d73
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This reverts commit 863a01b032.
Partial revert only for the pin to focal, leaves the broken other jobs
commented out.
Update paste-deploy workaround to be used always.
Add qemu-block-extra and podman deps to the debs list.
Running on the newer ceph and distro causes some quite different
performance characteristics that cause tests that used to pass to fail
more often. This includes some performance optimizations to help
reduce the memory footprint, as well as depends on changes to
tempest tests to improve the reliability of those tests by enabling
validation via SSH.
This also moves the cephadm job to be the voting/gating job as that
seems to be the clear consensus about "the future" of how we deploy
ceph for testing.
Depends-On: https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/881764
Co-Authored-By: Dan Smith <dms@danplanet.com>
Change-Id: I899822fec863f43cd6c58b25cf4688c6a3ac1e9b
Package based deployment of ceph isn't a Ceph-community
supported deployment strategy. We are trying to migrate
to using cephadm orchestrated ceph in the CI one job
at a time. See [1]
[1] https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/865315/11
Depends-On: I66ac85b735566f8f7dd75234eb8e0be7773fee3a
Change-Id: I21688daa7ac21eb395897daba61a5fdba2697b5f
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
The cephfs-nfs job was turned off [1] for perma-failing.
This commit adds the original non-voting job back into the
check queue and fixes some installation issues:
1) use ceph "quincy" release: Ceph Pacific's end of life
is 2023-06-01 [2]. The manila community thinks deployers
are more likely to use quincy with the 2023.2 (bobcat)
release of OpenStack.
2) run the job with centos-stream-9: There are no packages
currently available for Jammy Jellyfish on download.ceph.com [3].
The OS shouldn't really matter for this CI job that is meant to
test feature functionality provided by manila. At this time, we'd
like to stick with builds provided by the ceph community instead
of the distro since it may take a while to get bugfixes into distro
builds.
3) The install script uses "nfs-ganesha" builds for ubuntu and
centos hosted by the nfs-ganesha community [4]. We will not rely on
the ceph community to provide the latest builds for
nfs-ganesha any longer.
This commit also cleans up the unnecessary condition in the
ceph script file pertaining to configuring ceph packages for
Jammy Jellyfish. This step wasn't doing anything.
Ubuntu packages don't work at the moment and that requires some more
investigation.
[1] Id2ae61979505de5efb47ce90a2bac8aac2fc5484
[2] https://docs.ceph.com/en/latest/releases/
[3] https://www.spinics.net/lists/ceph-users/msg74312.html
[4] https://download.nfs-ganesha.org/
Change-Id: I40dfecfbbe21b2f4b3e4efd903980b5b146c4202
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
As per the community wide goal to migrate the CI/CD from
Ubuntu Focal to Ubuntu jammy, we need to merge the devstack, tox base
jobs to jammy on Nov 18. But ceph jobs are failing on Ubuntu Jammy.
To move ahead to merge the base job patches we need to pin the
ceph jobs nodeset to Focal until this is fixed for Jammy.
Since the devstack-plugin-ceph-tempest-py3 is currently permanently
failing, although this patch is a no-op, make it non-voting. Also don't
run 100% failing non-voting jobs until they are fixed.
Needed-By: https://review.opendev.org/c/openstack/devstack/+/860795
Related-bug: #1996628
Change-Id: Id2ae61979505de5efb47ce90a2bac8aac2fc5484
Ubuntu 22.04 does provide Ceph Quincy (17.2.*) out of the box, thus
there's no urgent need to have comunity repos and we can simply rely
on distro-provided ones. We can remove logic once community publish
Ceph packages for Ubuntu Jammy (22.04).
Change-Id: I169971ef77f11ceb01a5db87441051dcb33555f7
CephFS driver supports snapshots, therefore the snapshot_support
extra spec for the cephfsnfstype we create should be True.
Change-Id: I97b58697f27824a97cfd31ed21d79916b9e270cc
As part of change I1826f2970528928a31b32a664013380e38bbd7c9
we added a configuration option to the manila cephfs nfs driver
when deployed using cephadm.
We also need this option set here to get the m-shr service
to pick the right helper when deploying with DevStack
Change-Id: If99714e07f4b75c76db29a660ad8d1e93f7055e5
Latest Ceph stable version is Quincy. This patch set
sets Quincy as default for the cephadm deploy.
This change won't have an impact in the script being
currently used in our CI.
Change-Id: I2d87ec0e93853cd0852944b30a87f6127f491550
The configuration that we are using by default that
sets pg_num and pgp_num values in bootstrap_ceph
breaks devstack-plugin-ceph when using the latest Ceph version (quincy).
This patch sets removes the config for pg_num and pgp_num,
so we delegate to Ceph the pools autoscaling.
Closes-Bug: #1983107
Change-Id: Iecd949ef2258ae8a6ded596219bb993aeff20de5
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I71bfcf0576eda9f72d963c4f5d92464c5a04734e
It's not a required configuration item; and its not required
with cephadm deployed NFS-Ganesha daemon/s.
Change-Id: I54380f1cb905dfa5ab287ba423561aa75bc1d2f4
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Add the option to deploy the Ceph cluster
with the cephadm tool.
Depends-On: I799521f008123b8e42b2021c1c11d374b834bec3
Co-Authored-By: Francesco Pantano <fpantano@redhat.com>
Change-Id: Id2a704b136b9e47b7b88ef586282cb5d0f754cf1
This patch adds a new VAR for when the user wants to set the minimum
client version used in a Manila/Glance/Nova/Cinder test job in addition
to using devstack.
A new configuration option, CEPH_MIN_ CLIENT _VERSION, has been
introduced to specify a Ceph-minium client version that allows proper
handling when deleting images and snapshots with dependencies, etc. The
default value is null.
Co-Author-By: Sofia Enriquez <lsofia.enriquez@gmail.com>
Change-Id: Id8e581893ee4b373b268acc7c59b670985cedc2f
The parent jobs of the basic tempest jobs defined here enabled
horizon since the merge of tempest-horizon into tempest (see
Id2ced856a41548a0b49e594ee5fed6ed28785f24).
But horizon is not really needed here, as the default list of
tests does not incldue any horizon test. Disabling it helps
freeing up a bit of resources for the job and also helps
the ongoing effort of testing FIPS, which would otherwise
require a patched django at this point.
Change-Id: I05ea7f675aafb85eb54427ca95167b4c8f0eabdf
Recently cinder has utilized clone v2 support of Ceph for its
RBD backend, since then if you attempt to delete an image from
glance that has a dependent volume, all future uses of that
image will fail in error state. Despite the fact that image
itself is still inside of Ceph/Glance. This issue is reproducible
if you are using ceph client version greater than 'luminous'
To resolve this issue glance RBD driver now checks whether original
image has any dependency before deleting/removing it's snapshot and
returns 409 response if it has any dependency. To check this
dependency glance osd needs 'read' access to cinder and nova
side RBD pool.
This change allows glance keyring/osd a read access on cinder and nova
side RBD pool.
Related-Bug: #1954883
Change-Id: I2e6221e6de23920998bb5f32b2323704b3c89f74
this change ensure that python3-logutils is removed so that
that it can be installed by pip later.
Before today in passing build, there were no python3-logutils pulled by neutron deps so
it was not installed or tried to uninstall so all good
- https://zuul.openstack.org/build/590c5996ca1b402486bfe1c7e1d08535/log/job-output.txt
But from today (10th Dec), python3-logutils pulled by neutron deps and failure started
- https://zuul.opendev.org/t/openstack/build/722c6caf8e454849b897a43bcf617dd2/log/job-output.txt#9419
The root cause of why this issue started happening today is not known. May be its
pecan===1.4.1 ? I8ee467bbb363f428a005f92554812bfdae95881a making it install but there
is no change for logutils as deps in pecan previous version 1.3.3 also[1]). Or it may
be cpeh/ubuntu packaging.
But it is clear that python3-logutils is coming from somewhere and causing gate blocker
in Nova gate, let's remove it and later we can find the root cause if anyone need this
package for their ceph job.
[1] https://github.com/pecan/pecan/blob/1.3.3/requirements.txt#L5
Closes-bug: #1954427
Change-Id: Icb63649b252fd6eb229adeae454b5ec3c6b79cad
Few URLs from some ganesha repositories were not corresponding
to actual valid URLs, where packages could be searched in
the repository.
These broken URLs have now been fixed.
Change-Id: If27b488cfec29731b74e7db774c4811b0e34c14e