[skip-ci] TMT: run system tests on Fedora #24369
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
release-note-none
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
lsm5
force-pushed
the
tmt-fedora-centos
branch
from
af89e2d to
fbd02d2
Compare
|
A friendly reminder that this PR had no activity for 30 days. |
lsm5
force-pushed
the
tmt-fedora-centos
branch
from
fbd02d2 to
ab31b4b
Compare
lsm5
force-pushed
the
tmt-fedora-centos
branch
12 times, most recently
from
1276d46 to
002ca1c
Compare
|
Ephemeral COPR build failed. @containers/packit-build please check. |
lsm5
force-pushed
the
tmt-fedora-centos
branch
4 times, most recently
from
5df7e93 to
a2a9383
Compare
openshift-merge-robot
added
the
needs-rebase
lsm5
force-pushed
the
tmt-fedora-centos
branch
from
a2a9383 to
ff774a1
Compare
openshift-merge-robot
removed
the
needs-rebase
lsm5
force-pushed
the
tmt-fedora-centos
branch
from
ff774a1 to
c92c69f
Compare
martinpitt
reviewed
Dec 13, 2024
| @@ -187,7 +191,9 @@ when `%{_bindir}/%{name}sh` is set as a login shell or set as os.Args[0]. | |||
| Summary: Metapackage for setting up %{name} machine | |||
| Requires: %{name} = %{epoch}:%{version}-%{release} | |||
| Requires: gvisor-tap-vsock | |||
| %if %{defined qemu} | |||
There was a problem hiding this comment.
Perhaps you want qemu-kvm? Publishing podman-machine in RHEL without QEMU otherwise feels rather moot?
martinpitt
reviewed
Dec 13, 2024
lsm5
force-pushed
the
tmt-fedora-centos
branch
from
2137e28 to
5322e01
Compare
martinpitt
reviewed
Dec 13, 2024
| @@ -187,7 +191,11 @@ when `%{_bindir}/%{name}sh` is set as a login shell or set as os.Args[0]. | |||
| Summary: Metapackage for setting up %{name} machine | |||
| Requires: %{name} = %{epoch}:%{version}-%{release} | |||
| Requires: gvisor-tap-vsock | |||
| %if %{defined qemu} | |||
| Requires: qemu | |||
There was a problem hiding this comment.
Note that "qemu" is a really awkward dependency - it pulls in tons of emulators, spice-server, GTK, vte291 etc. -- all stuff that you really don't want on servers. qemu-system-x86-core or qemu-kvm-core exist everywhere and aren't so heavyweight.
There was a problem hiding this comment.
We do not use emulation, AFAICT we call qemu-system-x86_64 on x86_64 and qemu-system-aarch64 on aarch64.
Then we also need qemu-img to resize the disk so whatever proves what we need should be fine.
$ rpm -q --whatprovides /usr/bin/qemu-img
qemu-img-8.2.8-2.fc40.x86_64
$ rpm -q --whatprovides /usr/bin/qemu-system-x86_64
qemu-system-x86-core-8.2.8-2.fc40.x86_64
$ rpm -q --whatprovides /usr/bin/qemu-system-aarch64
qemu-system-aarch64-core-8.2.8-2.fc40.x86_64
586f5bc to
d669b9f
Compare
lsm5
force-pushed
the
tmt-fedora-centos
branch
5 times, most recently
from
c60c626 to
30faf43
Compare
The default `gobuild` macro on CentOS Stream 9 now includes support for `BUILDTAGS`. CentOS Stream envs now also define `_user_tmpfilesdir` macro by default. Both these definitions are no longer needed here. Signed-off-by: Lokesh Mandvekar <[email protected]>
QEMU is available only on Fedora. RHEL and CentOS Stream can use qemu-kvm instead. Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
force-pushed
the
tmt-fedora-centos
branch
2 times, most recently
from
88703ed to
4ca7502
Compare
|
/packit test |
lsm5
force-pushed
the
tmt-fedora-centos
branch
2 times, most recently
from
b3dfdaf to
6924c8a
Compare
This commit introduces TMT test jobs triggered via packit to run system tests on testing-farm infrastructure. Tests are run for all active Fedora and CentOS Stream environments for aarch64 and x86_64. The same test plan will be reused by Fedora for bodhi, zuul and fedora-ci gating tests. Packit will handle syncing of test plan and sources from upstream to downstream. Jobs will be selectively triggered for `main` v/s release branches based on the `release` PR label. The GHA for labeling PRs has also been updated in this commit. Test jobs on the main branch will include builds from the `rhcontainerbot/podman-next` copr while tests on release branches will only include official distro packages. Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
force-pushed
the
tmt-fedora-centos
branch
from
6924c8a to
a4e73e7
Compare
|
/packit test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces TMT test jobs triggered via packit to run system
tests on testing-farm infrastructure. Tests are run for all active
Fedora environments for aarch64 and x86_64. The same
test plan will be reused by Fedora for bodhi, zuul and fedora-ci gating
tests. Packit will handle syncing of test plan and sources from upstream
to downstream.
Jobs will be selectively triggered for
mainv/s release branches basedon the
releasePR label. The GHA for labeling PRs has also beenupdated in this commit.
Test jobs on the main branch will include builds from the
rhcontainerbot/podman-nextcopr while tests on release branches willonly include official distro packages.
Does this PR introduce a user-facing change?