Conversation
|
@RadekManak: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: RadekManak The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@RadekManak was this cgroups import originally a carry itself? What does upstream do? |
|
This is an update to a carry patch. Both the code change and import are downstream only. Upstream uses the libcontainercgroups "github.com/opencontainers/cgroups" import which is the same but moved to new location. |
|
/retest |
|
/assign @bertinatto @p0lyn0mial @jacobsee |
|
/test k8s-e2e-gcp-ovn |
bertinatto
left a comment
There was a problem hiding this comment.
I see this patch in the 1.35 bump PR, which addresses the issue this PR is addressing:
However, master has a similar, but slightly different patch that uses cgroups sintead of libcontainerscgroups.
@haircommander @jacobsee PTAL and advise ifo you prefer to merge this PR or backport the other one.
|
hm this PR is targeting master right? the cgroups version is there also. or are we planning on pulling this further back? in which case, backporting the cgroups version (instead of runc) works for me |
|
@RadekManak: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR updates downstream patch to use libcontainercgroupmanager "github.com/opencontainers/cgroups/ instead of "github.com/opencontainers/runc/libcontainer/cgroups" that has been removed in new library version.
This is causing build failures on projects that depend both on kubernetes and openshift/api which transitively pulled incompatible filepath-securejoin v0.6.0.
Which issue(s) this PR is related to:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: