Repository navigation
ci: run kind-e2e on ubuntu-latest by unloading the fusermount3 AppArmor profile - #6235
Merged
RongGu merged 2 commits intoNov 12, 2026
Conversation
…or profile ubuntu-latest now resolves to ubuntu-26.04, which ships AppArmor 5.0 with an /etc/apparmor.d/fusermount3 profile that only allows FUSE mounts under a few directories. The profile attaches by path to /usr/bin/fusermount3 even for privileged FUSE pods on Kind nodes, so the JindoRuntime e2e mount fails with EACCES and the job hangs until the step timeout (fluid-cloudnative#6224). Unload the profile from the ephemeral runner before creating the Kind cluster and switch runs-on back to ubuntu-latest. On runner images without the profile (ubuntu-24.04 and older) the step is a no-op; if the profile exists but cannot be unloaded, the step fails fast instead of letting the e2e hang for 30 minutes. Fixes fluid-cloudnative#6224 Signed-off-by: cheyang <cheyang@163.com>
…r on PATH Signed-off-by: cheyang <cheyang@163.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6235 +/- ##
=======================================
Coverage 65.75% 65.75%
=======================================
Files 486 486
Lines 34459 34459
=======================================
Hits 22660 22660
Misses 10044 10044
Partials 1755 1755 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
cheyang
force-pushed
the
cheyang-kind-e2e-unload-fusermount3-apparmor
branch
from
November 10, 2026 22:21
da56ff4 to
474f4e3
Compare
|
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
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.
Summary
E2E Functionality Checkhas been pinned toubuntu-24.04since #6225, becauseubuntu-lateststarted resolving toubuntu-26.04, whose host AppArmorfusermount3profile denies the JindoRuntime FUSE mounts (#6224). The charts repo'skind-e2e.ymlcarries the same pin for the same reason (fluid-cloudnative/charts#121).This PR un-pins the runner and makes the failure mode go away instead:
runs-onback toubuntu-latest/etc/apparmor.d/fusermount3from the host runner before the Kind cluster is createdThe step is a no-op on runner images that do not ship the profile (ubuntu-24.04 and older), and fails fast with a clear message if the profile exists but cannot be unloaded — instead of letting the JindoRuntime e2e hang until the 30-minute step timeout.
Why unloading is safe here: the profile only exists to confine interactive user FUSE mounts on multi-user hosts. A GitHub-hosted runner is ephemeral and single-tenant, and Kind node containers already run
--privileged --security-opt apparmor=unconfined; nothing on the runner legitimately relies on the profile.This also closes the first two follow-ups of #6224 (confirm the root cause on an ubuntu-26.04 runner — the kind-e2e run of this PR re-runs the jindo suite on ubuntu-26.04 with the profile unloaded, which is exactly the confirmation experiment proposed there — and make kind-e2e pass on ubuntu-26.04). The production-impact assessment for nodes running AppArmor ≥ 5.0 stays tracked in the issue; after this lands, the charts repo pin (fluid-cloudnative/charts#121) can be reverted the same way.
Verification
The kind-e2e matrix of this PR runs on
ubuntu-latest(26.04) across 5 Kubernetes versions and exercises the JindoRuntime FUSE path in every job; all 5 jobs passing is the proof. Before the fix, the same suites failed on all 5 versions withfusermount3: mount failed: Permission denied(run of PR #6219 on ubuntu-26.04, see #6224).