-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
update CI images to include pasta #16525
update CI images to include pasta #16525
Conversation
f96eef5
to
6775bc2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cevich, Luap99 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 |
@giuseppe @cdoern PTAL I see cgroup and pause/unpause issues with the new image: |
FYI these are the installed versions:
|
6775bc2
to
c8a1e38
Compare
@giuseppe reping, could please take a look at the e2e failures, they look all cgroup related. |
it looks like a regression in crun 1.7. Taking a look... |
fix here: containers/crun#1084 I'll release 1.7.2 ASAP |
Thank you. |
c8a1e38
to
43d332f
Compare
@giuseppe @adrianreber It looks like checkpoint/restore is broken on fedora 36 Error is
These are the version installed:
How to fix this? |
The |
265045c
to
94212fe
Compare
I have an older image-update PR I've been kicking around for a while now. Since this one is better, and there's no sense in two separate image-update PRs, I'll close mine in favor of this one. I'll keep subscribed here though in case my eyeballs are needed. |
For reference, test failures are caused by a bind() kernel bug: https://bugzilla.redhat.com/show_bug.cgi?id=2159066 |
94212fe
to
193bac1
Compare
2d84ce3
to
40ca64a
Compare
Ugh...this may actually be the case. Well 💩 @Luap99 let me guess, your preference is to get this PR merged before any new releases, ya? To be clear, what I'm worried about is:
That's going to end up in a release-branch. That makes me nervous. Our image timestamping automation can handle it just fine, it's the human-maintainers I'm worried about 😖 Context: It's both bad, and wrong (and often technically difficult) to update a CI VM-image set in release branches. If we merge this, it means everyone agrees to live with the de-sync, basically forever. Am I being paranoid, or is this a real problem we should consider? |
No this is a problem. I don't like it either, I don't think we have to merge it right now. The blocked PR already skipped the test anyway and was merged earlier so it should not block somebodies work, at least I am not aware of anything. My only point is that it makes sense to test on more recent images. At this point I really do not believe the current images reflect the software on actual users systems any more and therefore we might miss critical bugs because of it. I know we have gating tests in fedora but they only cover a subset compared to upstream CI. |
Okay, thanks for the sanity-check. Let's wait for @n1hility to help fix Windows (what would we do without him!) and/or merge this PR after the release is branched. Maybe the kernel bug will be resolved by then (one can wish).
I 100% agree, the current images are based on a beta-build of F37 😕 The good thing is, I think in a few weeks you've blown through image-update problems I was failing to fix for more than a month 😁 |
@cevich It's a hairy problem, although I have a solution almost ready to go, just needs polishing. It will require PRs to images and podman to address. |
40ca64a
to
4ebbd4a
Compare
@n1hility okay, thanks for the update and guesstimate. Last I looked, you're in-the-clear for an automation_images PR, there's nothing else happening over there ATM. This PR is the main one trying to update images for Podman CI, so we can update the ID here when it's ready. Thanks again. |
Images were build here: containers/automation_images#249 Signed-off-by: Paul Holzinger <[email protected]>
use this target in the CI script to make sure it uses the correct gingko Signed-off-by: Paul Holzinger <[email protected]>
It is not working in CI and locally, I filed containers#17074 to track it so we can fix it later. Signed-off-by: Paul Holzinger <[email protected]>
It is only needed for one CI task, and that task already calls `make .install.swagger` in setup_environment.sh. Signed-off-by: Paul Holzinger <[email protected]>
They should work with the new VM images. Signed-off-by: Paul Holzinger <[email protected]>
4ebbd4a
to
7be8ff5
Compare
Rebased to include the windows fix, this should turn green now unless I am the most unluckiest person ever. |
/lgtm |
Not a single flake as far as I can tell, guess I am not so unlucky after all. |
Nope, sometimes all it takes is persistence, and teamwork 👍 |
Ref: containers/automation_images#246
Does this PR introduce a user-facing change?