Description of problem: No 1.25 shown in REMOVEDINRELEASE for apis audited with 1.25. Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-05-08-025039 How reproducible: Always Steps to Reproduce: 1. Install fresh env. Then try below. $ MASTERS=$(oc get no -l node-role.kubernetes.io/master --no-headers | awk '{print $1}') $ oc adm node-logs $MASTERS --path=kube-apiserver/audit.log --raw | grep -E '"k8s.io/removed-release":"[^"]+"' > all.log 2. $ grep -v '"k8s.io/removed-release":"1.22"' all.log > non-1.22.log $ grep -o '"k8s.io/removed-release":"[^"]*"' non-1.22.log | grep -o '"[^"]*"$' | sort | uniq -c 60 "1.25" $ oc get apirequestcount | grep "1\.25" # none 3. $ jq -r '.user.username+": "+.requestURI' non-1.22.log | grep -o '/[^?]*' | sort | uniq -c | sort -n 2 /apis/batch/v1beta1/namespaces/openshift-image-registry/cronjobs 2 /apis/policy/v1beta1/namespaces/openshift-image-registry/poddisruptionbudgets 5 /apis/policy/v1beta1/poddisruptionbudgets 5 /apis/policy/v1beta1/podsecuritypolicies 6 /apis/batch/v1beta1/cronjobs 15 /apis/policy/v1beta1/namespaces/openshift-etcd/poddisruptionbudgets/etcd-quorum-guard 25 /apis/discovery.k8s.io/v1beta1/endpointslices 4. No 1.25 shown in REMOVEDINRELEASE for them: $ oc get apirequestcount | grep -E '(NAME|cronjob|etcd-quorum-guard|poddisruptionbudget|podsecuritypolicies|endpointslices)' | grep -v '\.v1\.' NAME REMOVEDINRELEASE REQUESTSINCURRENTHOUR REQUESTSINLAST24H cronjobs.v1beta1.batch 22 140 endpointslices.v1beta1.discovery.k8s.io 55 258 poddisruptionbudgets.v1beta1.policy 99 719 podsecuritypolicies.v1beta1.policy 7 42 Actual results: Audit logs showed "k8s.io/deprecated":"true","k8s.io/removed-release":"1.25". But oc get apirequestcount does not show 1.25 in REMOVEDINRELEASE column. Expected results: Should show 1.25 in REMOVEDINRELEASE column. $ oc explain apirequestcount.status.removedInRelease # shows: DESCRIPTION: removedInRelease is when the API will be removed. Per this DESCRIPTION, 1.25 should be shown in the oc output column for above. Additional info:
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
This should be fixed and possibly backported to a z-stream, but I don't see it as a blocker to 4.8.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Tested with latest 4.11 oc and 4.11 env, the issue seems fixed, now REMOVEDINRELEASE columns shows "1.26" instead of blank. $ oc version Client Version: 4.11.0-202204141741.p0.g1b0e16c.assembly.stream-1b0e16c Server Version: 4.11.0-0.nightly-2022-04-20-002931 Kubernetes Version: v1.23.3+e7218b0 $ oc get apirequestcounts -o json | jq -r '.items[] | select(.status.removedInRelease) | .metadata.name' flowschemas.v1beta1.flowcontrol.apiserver.k8s.io horizontalpodautoscalers.v2beta2.autoscaling podsecuritypolicies.v1beta1.policy prioritylevelconfigurations.v1beta1.flowcontrol.apiserver.k8s.io $ oc get apirequestcounts `oc get apirequestcounts -o json | jq -r '.items[] | select(.status.removedInRelease) | .metadata.name'` NAME REMOVEDINRELEASE REQUESTSINCURRENTHOUR REQUESTSINLAST24H flowschemas.v1beta1.flowcontrol.apiserver.k8s.io 1.26 146 387 horizontalpodautoscalers.v2beta2.autoscaling 1.26 5 18 podsecuritypolicies.v1beta1.policy 1.25 5 21 prioritylevelconfigurations.v1beta1.flowcontrol.apiserver.k8s.io 1.26 12 38
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. https://access.redhat.com/errata/RHSA-2022:5069