Replace debian-bookworm with debian-trixie for the base job in order
to use a newer version of qemu that has patch [0] that addresses an
issue where test_boot_cloned_encrypted_volume fails when run on a
fast machine.
The default python in debain-trixie is Python 3.13, which is a supported
python version for the Gazpacho development cycle [1].
Also, updated the package prereq file for some necessary packages that
aren't included by default in trixie.
[0] https://lists.gnu.org/archive/html/qemu-devel/2025-01/msg01071.html
[1] https://governance.openstack.org/tc/reference/runtimes/2026.1.html
Related-bug: #2121941
Change-Id: I0db46ae97e61186f7bc2e0c940cf27278d742146
Signed-off-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>
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
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
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>
