-
Notifications
You must be signed in to change notification settings - Fork 3.4k
v1.9 backports 2021-07-15 (2) #16910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.9 backports 2021-07-15 (2) #16910
Conversation
Lgtm, thanks! Let's include this in the upcoming 1.9 release. |
test-me-please |
4a541de
to
6ccf6c1
Compare
test-backport-1.9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My PR looks good 👍
CI triage:
These do not represent regressions so fine to merge. |
Oh, it could be that this directory is only accessed in the k8s-upstream test. We've had some changes in VM image permissions recently... |
@pchaigno I don't think we need to block 1.9.9 with this PR, what do you think? |
The Union for v1.9.9 political party agrees. There's only CI and misc changes here. |
[ upstream commit e3f9c61 ] [ Backporter's notes: handle rename pkg/cgroups/cgroups{,_linux}.go ] If cgroupv2 is not mounted, a logical mistake returns a error even after a successful mount, which is silently ignored by the caller function. This commit fixes the logical mistake and takes care of print a warning message if the cgroupv2 could not be mounted. Fixes: cilium#15997 Signed-off-by: Joao Victorino <joao@accuknox.com> Signed-off-by: Joe Stringer <joe@cilium.io>
6ccf6c1
to
3ee7661
Compare
test-backport-1.9 |
CI triage:
|
vagrant: Bump all Vagrant box versions #16589 -- vagrant: Bump all Vagrant box versions (@pchaigno)contrib: Explicitly set remote for backport branches #16804 -- contrib: Explicitly set remote for backport branches (@twpayne)Once this PR is merged, you can update the PR labels via:
EDIT: Dropped first two PRs to ship the fix with the next release. Will follow up on CI to check whether the vagrant change impacts branch stability.