workflows/e2e: Revert bpf/bpf-next image updates#37485
Merged
Conversation
Member
|
Could it be cilium/little-vm-helper-images#850 😬 |
Member
Author
|
@jschwinger233 The symptoms look different. We have pods restarting during the upgrade in my case. |
This was referenced Feb 10, 2025
b62a752 to
b2918f4
Compare
This partially reverts commit 86639d0 ("chore(deps): update all lvh-images main"). That commit introduced a fairly frequent flake on bpf-next and bpf kernels in our end-to-end suite, with connectivity being interrupted during upgrades from v1.17. IPsec end-to-end tests were not impacted because they were not updated. The present commit reverts the change and blocks future updates of the bpf and bpf-next images for the time being. Signed-off-by: Paul Chaignon <paul.chaignon@gmail.com>
b2918f4 to
f08ae87
Compare
Member
Author
|
/test |
julianwiedmann
approved these changes
Feb 10, 2025
Member
julianwiedmann
left a comment
There was a problem hiding this comment.
Thank you!
Needed to remind myself that the ginkgo upgrade test is gone, and that's why we don't need to touch the ginkgo dependency.
brlbil
approved these changes
Feb 10, 2025
This was referenced Feb 12, 2025
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
4 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.
This partially reverts pull request #37406.
That commit introduced a fairly frequent flake on bpf-next and bpf kernels in our end-to-end suite, with connectivity being interrupted during upgrades from v1.17. IPsec end-to-end tests were not impacted because they were not updated. The present commit reverts the change and blocks future updates of the bpf and bpf-next images for the time being.
I ran the workflow 10 times at https://github.com/cilium/cilium/actions/runs/13204674613 and couldn't reproduce the issue.
Updates: #37520.