OCPBUGS-60524: podresources: list: use active pods #2413

haircommander · 2025-08-14T13:52:47Z

What type of PR is this?

What this PR does / why we need it:

backport of #2391

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

openshift-ci-robot · 2025-08-14T13:52:55Z

@haircommander: This pull request references Jira Issue OCPBUGS-60524, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.19.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

What type of PR is this?

What this PR does / why we need it:

backport of #2391

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2025-08-14T13:53:06Z

@haircommander: the contents of this pull request could not be automatically validated.

The following commits are valid:

08daca6|UPSTREAM: 126750: Add takeByTopologyUnCoreCachePacked if policy option align-cpus-by-uncorecache is enabled. Adding new function to evaluate uncore cache id. Reverse allocation logic. Implement preferAlignByUncorecache within TakeByTopologyNUMAPacked, along with new test cases.: the upstream PR kubernetes/kubernetes#126750 has merged
2fad11e|UPSTREAM: 129506: Fix status subresource ratcheting: the upstream PR kubernetes/kubernetes#129506 has merged
3986b3a|UPSTREAM: 126326: Add end-to-end tests for Volume Group Snapshot: the upstream PR kubernetes/kubernetes#126326 has merged
61e5748|UPSTREAM: 130422: Propagate error when creating CustomResourceStorage instead of panic'ing: the upstream PR kubernetes/kubernetes#130422 has merged
6e65518|UPSTREAM: 129506: Simplify status subresource ratcheting testing: the upstream PR kubernetes/kubernetes#129506 has merged
9198c4f|UPSTREAM: 128972: Add crd from external snapshotter: the upstream PR kubernetes/kubernetes#128972 has merged
9b830ef|UPSTREAM: 131236: RWX tests should create RWX volumes: the upstream PR kubernetes/kubernetes#131236 has merged
a2bc30e|UPSTREAM: 126750: update comments: the upstream PR kubernetes/kubernetes#126750 has merged
bf06ebe|UPSTREAM: 127757: scheduler Improve CSILimits plugin accuracy by using VolumeAttachments: the upstream PR kubernetes/kubernetes#127757 has merged
cae107a|UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver: the upstream PR kubernetes/kubernetes#130047 has merged
d14a81f|UPSTREAM: 129675: Fix Portworx plugin's CSI translation to copy secret name & namespace: the upstream PR kubernetes/kubernetes#129675 has merged

The following commits could not be validated and must be approved by a top-level approver:

0023663|Merge pull request #130509 from cici37/automated-cherry-pick-of-#130035-upstream-release-1.31: does not specify an upstream backport in the commit message
00ba1de|Merge pull request #130166 from mimowo/automated-cherry-pick-of-#130164-upstream-release-1.31: does not specify an upstream backport in the commit message
014728e|Check for newer fields when deciding expansion recovery feature status: does not specify an upstream backport in the commit message
04f5b20|kubelet: Fix the volume manager did't check the device mount state in the actual state of the world before marking the volume as detached. It may cause a pod to be stuck in the Terminating state due to the above issue when it was deleted.: does not specify an upstream backport in the commit message
071f77e|Merge pull request #2176 from atiratree/bump-1.31.5: does not specify an upstream backport in the commit message
087e65b|Fix the flaky Job test: TestSuccessPolicy_ReEnabling: does not specify an upstream backport in the commit message
0b8a681|Merge pull request #2268 from mtulio/OCPBUGS-54807-backport-OCPBUGS-53249: does not specify an upstream backport in the commit message
0c68a45|UPSTREAM: : Don't retry storage calls with side effects.: does not specify an upstream backport in the commit message
1043bf3|Merge pull request #129494 from MadhavJivrajani/131-go124-webhook-regex-ut: does not specify an upstream backport in the commit message
11e2f11|Merge pull request #2163 from bertinatto/bump-1.31.4: does not specify an upstream backport in the commit message
11fefab|Merge pull request #130156 from AwesomePatrol/automated-cherry-pick-of-#130113-upstream-release-1.31: does not specify an upstream backport in the commit message
151e2cd|UPSTREAM: : kubelet: fix a stall on startup from waiting too long for a stat call: does not specify an upstream backport in the commit message
156c80a|pkg/kubelet: Fix userns tests on Windows: does not specify an upstream backport in the commit message
15c8eac|hack/tools: bump go-tools for go1.23.0: does not specify an upstream backport in the commit message
16dd861|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.9: does not specify an upstream backport in the commit message
19ebee9|Add tests: does not specify an upstream backport in the commit message
1c1a186|Merge pull request #130077 from cpanato/update-go-131: does not specify an upstream backport in the commit message
1c1db14|Merge pull request #128940 from jpbetz/automated-cherry-pick-of-#128737-upstream-release-1.31: does not specify an upstream backport in the commit message
1d723e3|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.6: does not specify an upstream backport in the commit message
1e53e59|Revert "Enforce the Minimum Kernel Version 6.3 for UserNamespacesSupport feature": does not specify an upstream backport in the commit message
1f83017|fetch cni plugins from GitHub releases: does not specify an upstream backport in the commit message
205ac00|Merge pull request #2144 from bertinatto/bump-v1.31.3-for-4.18: does not specify an upstream backport in the commit message
262df1a|Bump images, dependencies and versions to go 1.23.10 and distroless iptables: does not specify an upstream backport in the commit message
2a90c25|Update kubectl exec to use correct format: does not specify an upstream backport in the commit message
2e0622b|pkg/kubelet/userns: Wrap error to get mappings: does not specify an upstream backport in the commit message
2f59990|Merge pull request #2303 from openshift-cherrypick-robot/cherry-pick-2216-to-release-4.18: does not specify an upstream backport in the commit message
356ae81|Merge pull request #131537 from ameukam/update-go-1-23-8-k8s-1-31: does not specify an upstream backport in the commit message
3836d58|fix handle terminating pvc when kubelet rebuild dsw: does not specify an upstream backport in the commit message
3a67945|Merge pull request #130685 from carlory/automated-cherry-pick-of-#130335-upstream-release-1.31: does not specify an upstream backport in the commit message
3a9f05a|Bump to build with go 1.23.6: does not specify an upstream backport in the commit message
3f46d43|Release commit for Kubernetes v1.31.8: does not specify an upstream backport in the commit message
3fe9d93|Merge pull request #129675 from gohilankit/automated-cherry-pick-of-#129630-upstream-release-1.31: does not specify an upstream backport in the commit message
4272f70|Kubelet server handler cleanup: does not specify an upstream backport in the commit message
4370821|Also change final status by removing featuregate check: does not specify an upstream backport in the commit message
469d2bd|UPSTREAM: : disable etcd readiness checks by default: does not specify an upstream backport in the commit message
46a3947|Bump images, dependencies and versions: does not specify an upstream backport in the commit message
475334f|kubeadm: fix panic when no UpgradeConfiguration was found in the config file: does not specify an upstream backport in the commit message
4a4e942|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
4a69b15|Merge tag 'v1.31.6' into bump-1.31.6: does not specify an upstream backport in the commit message
4bdfede|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
4c65275|pkg/kubelet/userns: Provide stub implementation for windows: does not specify an upstream backport in the commit message
4ca059e|UPSTREAM: : make update: does not specify an upstream backport in the commit message
4d89057|Merge tag 'v1.31.9' into bump-1.31.9: does not specify an upstream backport in the commit message
4e49e90|Bump images, dependencies and versions to go 1.22.12 and distroless iptables: does not specify an upstream backport in the commit message
4f9453c|kubeadm: use the v1beta4 EtcdAPICall timeout for etcd calls: does not specify an upstream backport in the commit message
4fd0809|Fix nil pointer dereference in selectable fields check When checking specVersion.SelectableFields, if specVersion is nil, a nil pointer dereference could occur. This change updates the conditional to use || instead of &&, ensuring that the check for specVersion being nil happens first, avoiding potential runtime panics.: does not specify an upstream backport in the commit message
5024972|Merge pull request #131429 from princepereira/automated-cherry-pick-of-#131138-upstream-release-1.31: does not specify an upstream backport in the commit message
50c9c29|Merge pull request #129744 from pjsharath28/automated-cherry-pick-of-#128997-upstream-release-1.31: does not specify an upstream backport in the commit message
50d0ecb|UPSTREAM: : remove the backward compat featuregate for 132028: does not specify an upstream backport in the commit message
51a17c3|Honor KUBE_HACK_TOOLS_GOTOOLCHAIN: does not specify an upstream backport in the commit message
56652a0|Bump images, dependencies and versions to go 1.22.11 and distroless iptables: does not specify an upstream backport in the commit message
579a602|UPSTREAM: : Disable default off feature: does not specify an upstream backport in the commit message
588d9d3|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
593aaa5|Merge pull request #126710 from MadhavJivrajani/bump-go-tools-131: does not specify an upstream backport in the commit message
5a354ec|Merge tag 'v1.31.8' into bump-1.31.8: does not specify an upstream backport in the commit message
5ac4d36|Merge pull request #129285 from ameukam/automated-cherry-pick-of-#129095-upstream-release-1.31: does not specify an upstream backport in the commit message
5d18fcd|UPSTREAM: : require configuration file enablement: does not specify an upstream backport in the commit message
5d5ac16|Deflake the PodReplacementPolicyFeatureToggling Job integration test: does not specify an upstream backport in the commit message
5f71ced|Merge pull request #2195 from openshift-cherrypick-robot/cherry-pick-2113-to-release-4.18: does not specify an upstream backport in the commit message
6020cf5|Merge pull request #2208 from atiratree/bump-1.31.6: does not specify an upstream backport in the commit message
6118358|Release commit for Kubernetes v1.31.10: does not specify an upstream backport in the commit message
6342c77|Merge pull request #2300 from openshift-cherrypick-robot/cherry-pick-2279-to-release-4.18: does not specify an upstream backport in the commit message
6476cf7|Merge pull request #130194 from liggitt/go-1.23-1.31: does not specify an upstream backport in the commit message
6b35607|Release commit for Kubernetes v1.31.6: does not specify an upstream backport in the commit message
6b42606|Merge tag 'v1.31.5' into bump-1.31.5: does not specify an upstream backport in the commit message
6ed5abc|Merge pull request #131160 from wojtek-t/automated-cherry-pick-of-#131020-upstream-release-1.31: does not specify an upstream backport in the commit message
6f456a1|Merge pull request #129323 from ardaguclu/automated-cherry-pick-of-#129301-upstream-release-1.31: does not specify an upstream backport in the commit message
7164c72|Merge pull request #129062 from carlory/automated-cherry-pick-of-#128219-upstream-release-1.31: does not specify an upstream backport in the commit message
739d615|Fix the remaining flaky integration tests in Job controller: does not specify an upstream backport in the commit message
756c2db|Merge pull request #131785 from rata/automated-cherry-pick-of-#130243-upstream-release-1.31: does not specify an upstream backport in the commit message
75c83a6|Merge pull request #129599 from aravindhp/automated-cherry-pick-of-#129595-upstream-release-1.31: does not specify an upstream backport in the commit message
7665f4b|Merge pull request #2169 from jsafrane/4.18-add-groupsnapshot-real: does not specify an upstream backport in the commit message
772a0f4|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.8: does not specify an upstream backport in the commit message
774adff|webhook: alter regex to account for x509sha1 GODEBUG removal: does not specify an upstream backport in the commit message
77de0b9|fix e2e: does not specify an upstream backport in the commit message
7815f09|Merge tag 'v1.31.4' into bump-1.31.4: does not specify an upstream backport in the commit message
79b096c|UPSTREAM: : manually resolve conflicts: does not specify an upstream backport in the commit message
7ae3874|Merge pull request #132224 from cpanato/update-go-1-31: does not specify an upstream backport in the commit message
7d545b2|Merge tag 'v1.31.10' into bump-1.31.10: does not specify an upstream backport in the commit message
817e6dd|Merge pull request #2348 from atiratree/bump-1.31.10: does not specify an upstream backport in the commit message
84b31a3|Merge pull request #2332 from MaysaMacedo/backport-fs-metrics-fix: does not specify an upstream backport in the commit message
88e9d8f|Merge pull request #131439 from gnufied/automated-cherry-pick-of-#131418-upstream-release-1.31: does not specify an upstream backport in the commit message
8d8fe7b|Merge pull request #129861 from neolit123/automated-cherry-pick-of-#129859-origin-release-1.31: does not specify an upstream backport in the commit message
8f04a31|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
8f38003|Release commit for Kubernetes v1.31.9: does not specify an upstream backport in the commit message
8f8cca8|Added check for multipath device mapper: does not specify an upstream backport in the commit message
92e3993|Manually adding fix for failing pull-kubernetes-typecheck tests which had dependency with this commit: https://github.com/kubernetes/kubernetes/commit/61863035803cc105619925a0fa23a779a9578bd4: does not specify an upstream backport in the commit message
93a63da|do not install handler for /metrics/slis using sync.Once: does not specify an upstream backport in the commit message
93e4601|Merge pull request #129927 from mimowo/fix-job-int-test-1.31: does not specify an upstream backport in the commit message
94949be|Merge pull request #130174 from liggitt/go-tools-131: does not specify an upstream backport in the commit message
96b1747|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.5: does not specify an upstream backport in the commit message
97471c6|Merge pull request #2248 from atiratree/bump-1.31.7: does not specify an upstream backport in the commit message
9d10ddb|Fix Go vet errors for master golang: does not specify an upstream backport in the commit message
a119997|UPSTREAM: : Bump openshift-eng/openshift-tests-extension to main: does not specify an upstream backport in the commit message
a1bb711|Fix for HNS local endpoint was being deleted instead of the remote endpoint.: does not specify an upstream backport in the commit message
a3cd81b|UPSTREAM: : Enable format library for 4.18: does not specify an upstream backport in the commit message
a44b0a3|Merge pull request #131787 from rata/automated-cherry-pick-of-#130800-upstream-release-1.31: does not specify an upstream backport in the commit message
a8b2a44|Merge tag 'v1.31.7' into bump-1.31.7: does not specify an upstream backport in the commit message
a9964ae|Merge pull request #130071 from mimowo/automated-cherry-pick-of-#130068-upstream-release-1.31: does not specify an upstream backport in the commit message
aabc56c|kubeadm: remove misplaced error during image pull: does not specify an upstream backport in the commit message
ab4389f|add e2e test to reproduce unexpected unmount after kubelet is restarted: does not specify an upstream backport in the commit message
ac7239c|WIP: fix the flaky Job integration tests: does not specify an upstream backport in the commit message
acb9630|Merge pull request #2197 from benluddy/release-4.18-etcd-retry-write: does not specify an upstream backport in the commit message
ae08112|Fix Portworx plugin's CSI translation to copy secret name & namespace: does not specify an upstream backport in the commit message
ae9dcc0|Update status before returning err: does not specify an upstream backport in the commit message
aee841a|hack: backport apidiff.sh: does not specify an upstream backport in the commit message
af5c163|Merge pull request #2307 from atiratree/bump-1.31.9: does not specify an upstream backport in the commit message
af62fde|Merge pull request #129607 from neolit123/automated-cherry-pick-of-#129594-origin-release-1.31: does not specify an upstream backport in the commit message
af64d83|Release commit for Kubernetes v1.31.5: does not specify an upstream backport in the commit message
af98ede|Merge pull request #2278 from atiratree/bump-1.31.8: does not specify an upstream backport in the commit message
b26ab8b|Merge pull request #129454 from neolit123/automated-cherry-pick-of-#129452-origin-release-1.31-1735822759: does not specify an upstream backport in the commit message
b28f6f3|Merge pull request #2188 from jsafrane/4.18-downgrade-grpc: does not specify an upstream backport in the commit message
b555e6b|Fix volume expansion offline: does not specify an upstream backport in the commit message
b62290a|Merge pull request #131783 from rata/automated-cherry-pick-of-#131623-upstream-release-1.31: does not specify an upstream backport in the commit message
b6e875e|Merge pull request #130312 from neolit123/automated-cherry-pick-of-#130202-origin-release-1.31: does not specify an upstream backport in the commit message
b82572f|Do not attempt to truncate revision history if revisionHistoryLimit is negative: does not specify an upstream backport in the commit message
b8265e7|prevent unnecessary resolving of iscsi/fc devices to dm: does not specify an upstream backport in the commit message
b8e6734|UPSTREAM: : Disable VolumeGroupSnapshot tests: does not specify an upstream backport in the commit message
b9e1dc6|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
c0e6777|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
c0eb9e3|userns: Improve error returned if userns is not supported: does not specify an upstream backport in the commit message
c1cddd5|Limit ResourceQuota LIST requests to times when informer is not synced: does not specify an upstream backport in the commit message
c50a8a5|UPSTREAM: : podresources: list: use active pods in list: does not specify an upstream backport in the commit message
c5958ed|Fix: touch /dev/null permission denied on macos: does not specify an upstream backport in the commit message
c74754f|Merge pull request #129741 from bobsongplus/automated-cherry-pick-of-#129629-upstream-release-1.31: does not specify an upstream backport in the commit message
c831762|Merge pull request #129181 from RomanBednar/automated-cherry-pick-of-#128086-upstream-release-1.31: does not specify an upstream backport in the commit message
c88aef2|Revert "Switch hard error to a WARNING for kernel version check": does not specify an upstream backport in the commit message
c94919d|kubelet: use env vars in node log query PS command: does not specify an upstream backport in the commit message
c9d88fc|UPSTREAM: : Bump cadvisor version to fix container_fs metrics: does not specify an upstream backport in the commit message
c9dbae7|pkg/kubelet/userns: Remove skip on windows: does not specify an upstream backport in the commit message
c9ea8a4|Merge tag 'v1.31.3' into bump-v1.31.3-for-4.18: does not specify an upstream backport in the commit message
cf36527|UPSTREAM: : manually resolve conflicts: does not specify an upstream backport in the commit message
d060f96|Merge pull request #2283 from mpatlasov/OCPBUGS-55348-Improve-CSILimits-plugin-for-release-4.18: does not specify an upstream backport in the commit message
d2d1c41|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
d4eba92|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
d656a89|UPSTREAM: : OCPBUGS-54807: skip UDP LoadBalancer on external: does not specify an upstream backport in the commit message
d67d7ed|Bump images, dependencies and versions to go 1.23.9 and distroless iptables: does not specify an upstream backport in the commit message
d74c758|Merge pull request #130252 from fuweid/1.31-backport-130126: does not specify an upstream backport in the commit message
d7fc7e3|Merge pull request #129519 from kishen-v/automated-cherry-pick-of-#127422-upstream-release-1.31: does not specify an upstream backport in the commit message
d93c78a|Merge pull request #2162 from openshift-cherrypick-robot/cherry-pick-2136-to-release-4.18: does not specify an upstream backport in the commit message
da53587|Release commit for Kubernetes v1.31.7: does not specify an upstream backport in the commit message
dad2757|Merge pull request #129235 from gnufied/automated-cherry-pick-of-#129085-upstream-release-1.31: does not specify an upstream backport in the commit message
db4023c|Merge pull request #2324 from haircommander/fix-hung-fs-4.18: does not specify an upstream backport in the commit message
db71823|Merge pull request #2146 from openshift-cherrypick-robot/cherry-pick-2139-to-release-4.18: does not specify an upstream backport in the commit message
de2117a|Fix race for sending errors in watch: does not specify an upstream backport in the commit message
de93867|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.7: does not specify an upstream backport in the commit message
e18ecb4|Merge pull request #2175 from JoelSpeed/fix-status-ratcheting-4.18: does not specify an upstream backport in the commit message
e411fa8|Merge pull request #2187 from dobsonj/OCPBUGS-48819-4.18: does not specify an upstream backport in the commit message
e4e7f31|Mark NodeExpansion finsihed without featuregate check: does not specify an upstream backport in the commit message
e5a6db4|UPSTREAM: : manually resolve conflicts: does not specify an upstream backport in the commit message
e6e35d0|Merge pull request #2316 from openshift-cherrypick-robot/cherry-pick-2297-to-release-4.18: does not specify an upstream backport in the commit message
e885986|userns: Wrap more errors: does not specify an upstream backport in the commit message
e8b0252|proxy: should add PingPeriod for websocket translator: does not specify an upstream backport in the commit message
e983d3f|userns: Use len to handle empty non-nil slices: does not specify an upstream backport in the commit message
ea9a8bc|Merge pull request #130011 from tallclair/automated-cherry-pick-of-#129739-upstream-release-1.31: does not specify an upstream backport in the commit message
eb8c239|Bump images, dependencies and versions to go 1.22.10 and distroless iptables: does not specify an upstream backport in the commit message
ec0d04b|Merge pull request #129424 from cpanato/update-go1234-rel131: does not specify an upstream backport in the commit message
ec1a397|kubeadm: fix a bug where the node.skipPhases in UpgradeNodeConfiguration is not respected by 'kubeadm upgrade node': does not specify an upstream backport in the commit message
ec21688|Merge pull request #131937 from cpanato/update-go-1.31: does not specify an upstream backport in the commit message
ed53c53|Merge pull request #130426 from jsturtevant/automated-cherry-pick-of-#128097-upstream-release-1.31: does not specify an upstream backport in the commit message
f12dbc3|Add the feature gate OrderedNamespaceDeletion for apiserver.: does not specify an upstream backport in the commit message
f165a1d|Merge pull request #130084 from richabanker/automated-cherry-pick-of-#128430-upstream-release-1.31: does not specify an upstream backport in the commit message
f5fd936|Merge pull request #129965 from cpanato/update-go-rel131: does not specify an upstream backport in the commit message
f88fa0e|Merge pull request #129783 from pohly/apidiff-release-1.31: does not specify an upstream backport in the commit message
fd78b52|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.4: does not specify an upstream backport in the commit message
ff3bcb8|Merge pull request #2193 from openshift-cherrypick-robot/cherry-pick-2174-to-release-4.18: does not specify an upstream backport in the commit message
ff471cb|UPSTREAM: : log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

openshift-ci-robot · 2025-08-14T13:53:37Z

@haircommander: This pull request references Jira Issue OCPBUGS-60524, which is invalid:

expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.19.z" instead
expected Jira Issue OCPBUGS-60524 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

What type of PR is this?

What this PR does / why we need it:

backport of #2391

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

haircommander · 2025-08-14T15:43:54Z

/retest

haircommander · 2025-08-18T13:58:58Z

/skip
/jira refresh

openshift-ci-robot · 2025-08-18T13:59:02Z

@haircommander: This pull request references Jira Issue OCPBUGS-60524, which is invalid:

expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.19.z" instead
expected Jira Issue OCPBUGS-60524 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/skip
/jira refresh

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

rphillips · 2025-08-18T14:02:08Z

/approve
/label backport-risk-assessed

rphillips · 2025-08-18T14:03:56Z

/remove-label backports/unvalidated-commits

openshift-ci · 2025-08-18T14:04:06Z

@rphillips: Can not set label backports/unvalidated-commits: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/remove-label backports/unvalidated-commits

Instructions 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.

haircommander · 2025-08-18T14:49:04Z

/jira refresh

openshift-ci-robot · 2025-08-18T14:49:08Z

@haircommander: This pull request references Jira Issue OCPBUGS-60524, which is invalid:

expected Jira Issue OCPBUGS-60524 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

haircommander · 2025-08-18T14:49:44Z

/jira refresh

openshift-ci-robot · 2025-08-21T16:07:05Z

@haircommander: the contents of this pull request could not be automatically validated.

The following commits are valid:

4795ccd|UPSTREAM: 132028: podresources: list: use active pods in list: the upstream PR kubernetes/kubernetes#132028 has merged

The following commits could not be validated and must be approved by a top-level approver:

2bb7140|UPSTREAM: : remove the backward compat featuregate for 132028: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

haircommander · 2025-08-21T16:07:15Z

@bertinatto I've updated!

haircommander · 2025-08-21T19:28:37Z

/retest

bertinatto

/remove-label backports/unvalidated-commits
/lgtm

bertinatto · 2025-08-25T12:05:15Z

/retest

In order to facilitate backports (see OCPBUGS-56785) we prefer to remove the feature gate added as safety measure upstream and disable this escape hatch upstream added. This commit must be dropped once we rebase on top of 1.34. Signed-off-by: Francesco Romani <[email protected]>

openshift-ci-robot · 2025-08-25T14:43:13Z

@haircommander: the contents of this pull request could not be automatically validated.

The following commits are valid:

4795ccd|UPSTREAM: 132028: podresources: list: use active pods in list: the upstream PR kubernetes/kubernetes#132028 has merged

The following commits could not be validated and must be approved by a top-level approver:

f50d9d5|UPSTREAM: : remove the backward compat featuregate for 132028: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

bertinatto · 2025-08-25T15:19:12Z

/remove-label backports/unvalidated-commits
/lgtm

openshift-ci · 2025-08-25T15:19:46Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, haircommander, rphillips, tkashem

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

The pull request process is described here

Needs approval from an approver in each of these files:

~~pkg/kubelet/DOWNSTREAM_OWNERS~~ [bertinatto,tkashem]

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

openshift-ci-robot · 2025-08-25T17:27:36Z

/retest-required

Remaining retests: 0 against base HEAD 971b931 and 2 for PR HEAD f50d9d5 in total

openshift-ci · 2025-08-25T19:50:57Z

@haircommander: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-techpreview-serial	`50d0ecb`	link	false	`/test e2e-aws-ovn-techpreview-serial`
ci/prow/e2e-aws-ovn-downgrade	`50d0ecb`	link	true	`/test e2e-aws-ovn-downgrade`
ci/prow/e2e-aws-ovn-hypershift	`50d0ecb`	link	true	`/test e2e-aws-ovn-hypershift`
ci/prow/e2e-aws-ovn-techpreview	`50d0ecb`	link	false	`/test e2e-aws-ovn-techpreview`
ci/prow/artifacts	`50d0ecb`	link	true	`/test artifacts`

Full PR test history. Your PR dashboard.

Instructions 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.

openshift-ci-robot · 2025-08-26T11:13:13Z

/retest-required

Remaining retests: 0 against base HEAD 971b931 and 2 for PR HEAD f50d9d5 in total

openshift-ci-robot · 2025-08-26T15:29:09Z

@haircommander: Jira Issue OCPBUGS-60524: All pull requests linked via external trackers have merged:

openshift/kubernetes#2413

Jira Issue OCPBUGS-60524 has been moved to the MODIFIED state.

In response to this:

What type of PR is this?

What this PR does / why we need it:

backport of #2391

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

openshift-bot · 2025-08-26T17:17:08Z

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.18.0-202508261703.p0.g3c7968e.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-08-26T17:44:09Z

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.18.0-202508261703.p0.g3c7968e.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-08-26T17:47:10Z

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.18.0-202508261703.p0.g3c7968e.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-08-26T17:53:12Z

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-kube-apiserver-artifacts
This PR has been included in build ose-installer-kube-apiserver-artifacts-container-v4.18.0-202508261703.p0.g3c7968e.assembly.stream.el9.
All builds following this will include this PR.

openshift-merge-robot · 2025-08-27T18:11:16Z

Fix included in accepted release 4.18.0-0.nightly-2025-08-27-065249

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 14, 2025

openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Aug 14, 2025

haircommander changed the base branch from master to release-4.18 August 14, 2025 13:53

openshift-ci bot requested review from rphillips and sjenning August 14, 2025 13:54

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 14, 2025

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 18, 2025

openshift-ci bot assigned duanwei33, gangwgr, kasturinarra, lyman9966, wangke19, xingxingxia and zhouying7780 Aug 18, 2025

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 18, 2025

openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Aug 21, 2025

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 21, 2025

bertinatto reviewed Aug 25, 2025

View reviewed changes

openshift-ci bot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Aug 25, 2025

openshift-ci bot assigned bertinatto Aug 25, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2025

haircommander force-pushed the podresources-list-active-pods-backport-4.18 branch from 2bb7140 to f50d9d5 Compare August 25, 2025 14:43

openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Aug 25, 2025

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2025

openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Aug 25, 2025

haircommander mentioned this pull request Aug 26, 2025

OCPBUGS-60552: [4.17] podresources: list: use active pods #2426

Open

openshift-merge-bot bot merged commit 3c7968e into openshift:release-4.18 Aug 26, 2025
22 checks passed

OCPBUGS-60524: podresources: list: use active pods #2413

OCPBUGS-60524: podresources: list: use active pods #2413

Uh oh!

Conversation

haircommander commented Aug 14, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Uh oh!

openshift-ci-robot commented Aug 14, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Uh oh!

openshift-ci-robot commented Aug 14, 2025

Uh oh!

openshift-ci-robot commented Aug 14, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Uh oh!

haircommander commented Aug 14, 2025

Uh oh!

haircommander commented Aug 18, 2025

Uh oh!

openshift-ci-robot commented Aug 18, 2025

Uh oh!

rphillips commented Aug 18, 2025

Uh oh!

rphillips commented Aug 18, 2025

Uh oh!

openshift-ci bot commented Aug 18, 2025

Uh oh!

haircommander commented Aug 18, 2025

Uh oh!

openshift-ci-robot commented Aug 18, 2025

Uh oh!

haircommander commented Aug 18, 2025

Uh oh!

openshift-ci-robot commented Aug 21, 2025

Uh oh!

haircommander commented Aug 21, 2025

Uh oh!

haircommander commented Aug 21, 2025

Uh oh!

bertinatto left a comment

Choose a reason for hiding this comment

Uh oh!

bertinatto commented Aug 25, 2025

Uh oh!

openshift-ci-robot commented Aug 25, 2025

Uh oh!

bertinatto commented Aug 25, 2025

Uh oh!

openshift-ci bot commented Aug 25, 2025

Uh oh!

openshift-ci-robot commented Aug 25, 2025

Uh oh!

openshift-ci bot commented Aug 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 26, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 26, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

openshift-ci bot commented Aug 25, 2025 •

edited

Loading