[WIP] Fixed youki molecule test#13102
Open
tico88612 wants to merge 3 commits intokubernetes-sigs:masterfrom
Open
[WIP] Fixed youki molecule test#13102tico88612 wants to merge 3 commits intokubernetes-sigs:masterfrom
tico88612 wants to merge 3 commits intokubernetes-sigs:masterfrom
Conversation
k8s-ci-robot
added
release-note-none
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tico88612 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
size/M
Member
Author
|
Only molecule /label ci-short |
tico88612
force-pushed
the
fix/youki-molecule-seccomp
branch
2 times, most recently
from
071f59e to
9e7ed30
Compare
k8s-ci-robot
added
size/L
The youki molecule test fails because youki's libseccomp binding treats duplicate seccomp rules as fatal (EEXIST), unlike crun/runc which silently ignore them. CRI-O's default seccomp profile contains duplicate rules for the socket syscall (AF_NETLINK), triggering this failure. Work around this by setting seccomp profile_type to Unconfined (1) in the shared sandbox.json.j2 template when youki_enabled is true, so CRI-O skips applying its default seccomp profile for youki test runs. Signed-off-by: ChengHao Yang <17496418+tico88612@users.noreply.github.com>
Signed-off-by: ChengHao Yang <17496418+tico88612@users.noreply.github.com>
tico88612
force-pushed
the
fix/youki-molecule-seccomp
branch
from
9e7ed30 to
91c9b58
Compare
Member
Author
|
/remove-label ci-short |
Member
Author
|
/retest |
tico88612
changed the title
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
Member
Author
|
/cc @VannTen |
Contributor
|
Can we fill an issue on CRI-O side and reference it ? This looks like something which would also cause problem in real clusters. |
Member
Author
|
I'm not sure if this is a youki or a CRI-O issue, so I'll check with youki first. |
k8s-ci-robot
added
do-not-merge/work-in-progress
Contributor
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
The youki molecule test fails because youki's libseccomp binding treats
duplicate seccomp rules as fatal (EEXIST), unlike crun/runc which
silently ignore them. CRI-O's default seccomp profile contains duplicate
rules for the socket syscall (AF_NETLINK), triggering this failure.
Work around this by setting seccomp profile_type to Unconfined (1) in
the shared sandbox.json.j2 template when youki_enabled is true, so
CRI-O skips applying its default seccomp profile for youki test runs.
Special notes for your reviewer:
#13076 failing at youki molecule, I'm not sure which layer is causing the issue yet; I don't see any obvious commits in CRI-O.
Does this PR introduce a user-facing change?: