One test is failing, https://api.cirrus-ci.com/v1/artifact/task/4968184671895552/html/int-podman-fedora-38-root-host-boltdb.log.html#t--podman-checkpoint-container-with-export--migration--and-ipc-host--1

@giuseppe PTAL look like a possible crun bug in f38/rawhide, f37 and debian seems to work fine.

Also selinux tests are failing on f38: https://api.cirrus-ci.com/v1/artifact/task/4528380020785152/html/sys-podman-fedora-38-root-host-sqlite.log.html
@rhatdan PTAL

Thanks Paul for checking & pinging. I managed to completely loose track of this PR 😞

Added to #18577 to see if this fixes both problems.

force-push: Attempted rebasing ontop of Dan's #18577 since it's CI went all green.

@rhatdan FWIW: rebased with your PR, seems we get a handful of checkpoint and SELinux test failures.

I don't see how #18577 is relevant for the test failures?

I don't see how #18577 is relevant for the test failures?

Honestly I'm just throwing a bucket of golf-balls and hoping one lands in the hole. I read Dan's comment above and thought I'd give it a try. I should probably pull it out and rebase again, see if anything's changed from your assessment.

@giuseppe ping - Any feedback on Paul's observation of a possible crun bug in this podman checkpoint container with export (migration) and --ipc host failure?

are we using crun 1.8.5? There was an issue in crun 1.8.4 with CRIU on Fedora that could have caused this problem

CI logs says crun-1.8.4-1.fc38-x86_64 so no.

Thanks @giuseppe and @Luap99. Darn, so that means 1.8.5 wasn't in the updates-testing repo. at image-build time (a few weeks ago). I see the same test is failing on rawhide as well, with crun-1.8.4-1.fc39-x86_64. The bodhi pages show 1.8.5 entries from last week. So it sounds like I simply need to build newer CI VM Images then...

...opened containers/automation_images#281

Force-push: New CI VM images.

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

force-push: Rebased.

All system tests failing with:

Failed tests (3):
 - 410 podman selinux: container with label=disable
 - 411 podman selinux: privileged container
 - 416 podman selinux: pid=host

I did not look deeply, for now I'm assuming it's related to the fixes Dan's working on.

Force-push: I've reached my limit on this PR, and lack of F38 + updated rawhide testing at-large is hampering ongoing development and pending/imminent releases. Added skips for all persistently failing tests, with "TODO/FIXME" comments and references where possible.

@edsantiago IIRC, you have a preferred format for these kinds of skip messages. Please advise how you'd like them to appear. This push is to see if we can even get a clean-run at this point (w/o new images).

You also need to skip this test in rawhide, same BZ:

Force-push: 43rd time's the charm?

@containers/podman-maintainers PTAL. This isn't perfect, I've had to add some test skips and workarounds. But for months worth of trying, this is the best I can get it. The skips/workarounds can be addressed by followup PRs. Assuming it's good, let's get this in so I can backport it to the v4.6 branch (unless there's a reason not to?).

Thanks @sbrivio-rh maybe he's on vacation or something. I just was able to check, and indeed it's still installing 0.0~git20230309.7c7625d-1. I'll wait for your word.

Behold, for 'tis my word. Debian unstable (sid) package is now updated to 0.0~git20230627.289301b-1.

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cevich, edsantiago, renovate[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

/hold cancel