Bug 2103075 - Listing secrets in all namespaces with a specific labelSelector does not work properly
Summary: Listing secrets in all namespaces with a specific labelSelector does not work...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Antonio Ojea
QA Contact: Ke Wang
Depends On: 2094012
TreeView+ depends on / blocked
Reported: 2022-07-01 11:45 UTC by OpenShift BugZilla Robot
Modified: 2022-08-10 11:20 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:19:39 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift kubernetes pull 1304 0 None Merged [release-4.11] Bug 2103075: UPSTREAM: 110652: fix: --chunk-size with selector returns missing result 2022-07-01 17:25:41 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:20:05 UTC

Comment 2 Ke Wang 2022-07-04 02:57:21 UTC
I tried with 4.11 ci build(No one nightly build available). Did a quick test with attached script reproducer.sh, 

Steps as below,
$ oc version
Client Version: 4.11.0-fc.0
Kustomize Version: v4.5.4
Server Version: 4.11.0-0.ci-2022-07-03-073357
Kubernetes Version: v1.24.0-2362+2dd8bb16eb2fd8-dirty

$ bash ./reproducer.sh
namespace/foo-43 created
secret/fubar-1 created
secret/fubar-2 created
secret/fubar-1 created
secret/fubar-2 created

 $ oc get secrets -A -l foo=bar | wc -l

Listed all secrets with label, got the expected results, since the bug has label FastFix, no need wait nightly currently, so move the bug VERIFIED.Will re-test it when nightly  build is available.

Comment 4 errata-xmlrpc 2022-08-10 11:19:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.