qa/distros: add rocky 10.0 as supported distro/container host#66055
qa/distros: add rocky 10.0 as supported distro/container host#66055
Conversation
|
fyi @athanatos - i see you've been trying to test the same in wip-sjust-rocky-10-suite |
|
@cbodley Mine simply updated one suite to let me schedule at least some basic jobs to find the first problems. This one is vastly more thorough, I hearby defer to this one. |
batrick
left a comment
There was a problem hiding this comment.
I think this would be easier to integrate if components migrated as they became ready (by adjusting symlinks). In any case, +1 from me.
thanks @batrick, i agree that would help to minimize disruption from the change. i'm just concerned that some suites may forget about this and never add the new distros. we need some way to ensure that we can
full support for ubuntu24 is also blocking our retirement of ubuntu22 which goes eol during the T release so won't be supported for U. we can't drop ubuntu22 builds on main until all suites switch to ubuntu24. i'm keen to drop ubuntu22 so we can finally require gcc-13 or 14 for c++23 features i was advocating for a 'flag day' after tentacle ships so that this disruption would act as a forcing function at least for 1) above. that would only help with 2) if we also choose to backport the breaking changes. whatever we do here will need leadership consensus, but it's been challenging to get traction on this stuff even within the rgw team this PR and its ubuntu24 counterpart are just doing trivial stuff with yaml and symlinks that i'm happy to adjust. the hard part in my view is making each component/suite accountable for the work required to support these distros. blocking the T release was one option for that. i really don't want to end up in the same situation late in the U cycle |
|
@cbodley I pushed a commit to resolve some stragglers in the Scheduled a run based on https://shaman.ceph.com/builds/ceph/wip-rocky10-branch-of-the-day-2025-11-10-1762829866/d005727a2bd18718004e8ffd26bd5b7a9dc67345/ |
|
@SrinivasaBharath please do not merge/test this. |
|
This PR is under test in https://tracker.ceph.com/issues/73883. |
|
This PR is under test in https://tracker.ceph.com/issues/73884. |
|
This PR is under test in https://tracker.ceph.com/issues/73885. |
|
This PR is under test in https://tracker.ceph.com/issues/73888. |
|
This PR is under test in https://tracker.ceph.com/issues/73889. |
* refs/pull/66055/head: qa: update fs suite to rocky10 qa/distros: add rocky_10 as supported container host qa/distros: bump rpm_latest.yaml to rocky_10.yaml qa/distros: rename centos_latest.yaml to rpm_latest.yaml qa/distros: add rocky_9 and rocky_10
|
This PR is under test in https://tracker.ceph.com/issues/74161. |
|
This needs to be rebased. Github doesn't seem to notice, but qa/suites/rgw/upgrade/1-install/tentacle/distro and qa/suites/rgw/upgrade/1-install/squid/distro were touched by 2527e6f. |
ee7d7bd to
748bd2f
Compare
|
@cbodley this now needs to be rocky 10.1: |
748bd2f to
663d5d5
Compare
dbea306 to
d4e605c
Compare
|
This PR is under test in https://tracker.ceph.com/issues/74811. |
* refs/pull/66055/head: qa/distros: re-install nvme-cli package in rocky tests qa: allowlist bpf podman denials on Rocky 10 qa/distros: bump rocky to 10.1 qa/distros: add rocky_10 as supported container host qa/distros: bump rpm_latest.yaml to rocky_10.yaml qa/distros: rename centos_latest.yaml to rpm_latest.yaml qa/distros: add rocky_9 and rocky_10
idryomov
left a comment
There was a problem hiding this comment.
Ack from the RBD perspective
Signed-off-by: Casey Bodley <cbodley@redhat.com>
rename qa/distros/all/centos_latest.yaml to rpm_latest.yaml, along with all symlinks thereto Signed-off-by: Casey Bodley <cbodley@redhat.com>
Signed-off-by: Casey Bodley <cbodley@redhat.com>
Signed-off-by: Casey Bodley <cbodley@redhat.com>
Signed-off-by: Casey Bodley <cbodley@redhat.com>
Rocky Linux 10 logs SELinux AVCs for systemd BPF operations during container startup due to incomplete SELinux policy coverage. These AVCs occur in permissive mode, are reproducible without Ceph, and do not indicate functional failure. Tests should ignore this specific AVC class while continuing to fail on enforced denials. Signed-off-by: David Galloway <david.galloway@ibm.com>
Fixes: https://tracker.ceph.com/issues/73823 Signed-off-by: Adam King <adking@redhat.com>
d4e605c to
e3b084a
Compare
split from #63912
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job DefinitionYou must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.