Skip to content

[cherry-pick: release-v0.43.x] ci(e2e): raise inotify limits for ubuntu-26.04 runners - #3397

Merged
tekton-robot merged 1 commit into
release-v0.43.xfrom
cherry-pick-3393-to-release-v0.43.x
Oct 29, 2026
Merged

tekton-robot merged 1 commit into
release-v0.43.xfrom
cherry-pick-3393-to-release-v0.43.x

Conversation

@tekton-robot

Copy link
Copy Markdown
Contributor

This is a cherry-pick of #3393


Changes

The ubuntu-latest runner image rolled over to ubuntu-26.04, where
/etc/sysctl.conf is no longer applied at boot, dropping
fs.inotify.max_user_instances from the image's intended 1280 to the kernel
default of 128 (and max_user_watches from 655360 to 64097). inotify
limits are not namespaced, so the 3-node kind cluster used by the e2e tests
exhausts them and Tekton entrypoint pods fail with failed to create fsnotify watcher: too many open files, breaking the pipelinerun/taskrun log assertions
(TestPipelineRunLogE2E, TestClusterResolverPipelineRunLogE2E,
TestPipelineInteractiveStartE2E).

This adds a step that restores the intended inotify limits on the runner host
before the kind cluster is created.

References

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Run the code checkers with make check
  • Regenerate the manpages, docs and go formatting with make generated
  • Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

NONE

The ubuntu-latest runner image rolled over to ubuntu-26.04, where
/etc/sysctl.conf is no longer applied at boot (actions/runner-images#15108).
This drops fs.inotify.max_user_instances from the image's intended 1280 to
the kernel default of 128. inotify limits are not namespaced, so the 3-node
kind cluster used by the e2e tests exhausts them and Tekton entrypoint pods
fail with "failed to create fsnotify watcher: too many open files", making
the pipelinerun/taskrun log assertions fail.

Restore the intended limits on the runner host before creating the kind
cluster.

Assisted-by: Claude Opus 4.8 (via GitHub Copilot CLI)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: divyansh42 <diagrawa@redhat.com>
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Oct 29, 2026
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 29, 2026

@divyansh42 divyansh42 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 29, 2026
@tekton-robot

Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: divyansh42

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 29, 2026
@divyansh42

Copy link
Copy Markdown
Member

/retest

1 similar comment
@divyansh42

Copy link
Copy Markdown
Member

/retest

@tekton-robot
tekton-robot merged commit c489755 into release-v0.43.x Oct 29, 2026
22 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants