-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: Add bootc image #21559
Merged
Merged
test: Add bootc image #21559
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
74eb063
to
824fd7f
Compare
2 tasks
824fd7f
to
a711734
Compare
837aaf1
to
6be0410
Compare
6be0410
to
045df1e
Compare
On RHEL 9 (although only on bootc, curiously), systemd sometimes has trouble with cleaning up beiboot's temp files: > avc: denied { remove_name } for pid=1 comm="systemd" name="user-known-hosts" dev="tmpfs" ino=77 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:cockpit_tmp_t:s0 tclass=dir permissive=0 Allow this, this is harmless enough.
Whether pam_ssh_add is available or not depends on whether we use cockpit-ws.rpm or the ws container; not if the image is OSTree or not. The difference matters on centos-9-bootc.
They are in /var/home/.
MD5 keys haven't been a thing any more for many years.
045df1e
to
6432297
Compare
We want to test deploying cockpit rpms in bootc images. This will prevent hiccups like cockpit-project#21201 in the future and also test a lot of OS subsystems. The centos-9-bootc bots image includes its own deployment container image, so we can easily derive an image with our locally built RPMs included. https://issues.redhat.com/browse/COCKPIT-1237
6432297
to
6a17410
Compare
jelly
approved these changes
Jan 31, 2025
martinpitt
added a commit
to martinpitt/bots
that referenced
this pull request
Jan 31, 2025
mvollmer
pushed a commit
to cockpit-project/bots
that referenced
this pull request
Jan 31, 2025
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.
We want to test deploying cockpit rpms in bootc images. This will prevent hiccups like #21201 in the future and also test a lot of OS subsystems.
The centos-9-bootc bots image includes its own deployment container image, so we can easily derive an image with our locally built RPMs included.
https://issues.redhat.com/browse/COCKPIT-1237
Note that I only cover/trigger
centos-9-bootc/{networking,other,expensive}
here. /storage requires adding cockpit-storaged, udisks, etc., which we skip on fedora-coreos as well. Managing storage isn't the most important thing on a bootc system, so I'll left that for a follow-up.Prerequisites/split out work:
dnf install
→rpm -i
)TestMultiMachineKeyAuth.testBasic
failure