Bug 2012010 - APIRemovedInNextReleaseInUse: give exact command in description
Summary: APIRemovedInNextReleaseInUse: give exact command in description
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.z
Assignee: Stefan Schimanski
QA Contact: Ke Wang
Depends On: 2012008
TreeView+ depends on / blocked
Reported: 2021-10-07 23:37 UTC by W. Trevor King
Modified: 2021-10-27 08:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2012008
Last Closed: 2021-10-27 08:15:28 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 1241 0 None open Bug 2012010: alerts: give exact oc get apirequestcounts command in APIRemovedInNextReleaseInUse alert 2021-10-07 23:39:07 UTC
Red Hat Product Errata RHBA-2021:3927 0 None None None 2021-10-27 08:15:49 UTC

Description W. Trevor King 2021-10-07 23:37:19 UTC
+++ This bug was initially created as a clone of Bug #2012008 +++

The current:

  Refer to the apirequestcount.apiserver.openshift.io resources to identify the workload.

is not particularly specific, and folks might not think to look at the '-o yaml' or similar detailed view to see consumer information.  We now have a kbase solution [1] walking folks through the analysis in more detail.  We should link to it from the alert description.

[1]: https://access.redhat.com/articles/6329921

--- Additional comment from W. Trevor King on 2021-10-07 23:35:10 UTC ---

Already fixed via an explicit '-o yaml' in 4.9+.  Moving this straight to MODIFIED to hang a 4.8.z backport on.

Comment 5 errata-xmlrpc 2021-10-27 08:15:28 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 (OpenShift Container Platform 4.8.17 bug fix 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.