Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-58065

APIRequestCounts for non-deprecated APIs persist after upgrade from 4.17 to 4.18

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description

      In OpenShift 4.18, the oc get apirequestcounts command is expected to report usage only for APIs that are deprecated and planned for future removal.

      However, in a customer cluster upgraded from 4.17 to 4.18.17, APIRequestCounts are still shown for non-deprecated APIs — those with no REMOVEDINRELEASE value — all showing 0 in both usage columns.

      This suggests these records were created in 4.17 and are not cleaned up after the upgrade. This behavior:

      • Does not appear in fresh 4.18 installs
      • Is visible in CI upgrade scenarios
      • Was observed in a real customer environment

      Steps to Reproduce

      1. Start with an OCP 4.17 cluster.
      2. Trigger some usage on various APIs (including non-deprecated ones).
      3. Upgrade the cluster to 4.18.
      4. Run `oc get apirequestcounts`.

      Actual Result
      Entries for active (non-deprecated) APIs still appear, with all 0 counts and no REMOVEDINRELEASE set.

      Example APIs observed:

      alertmanagers.v1.monitoring.coreos.com
      
      applications.v1alpha1.argoproj.io
      
      appprojects.v1alpha1.argoproj.io
      
      appliedclusterresourcequotas.v1.quota.openshift.io
      

      Expected Result

      Only deprecated APIs planned for removal should show up in `APIRequestCounts` on 4.18+ clusters.

      Breadcrumbs

      Slack Discussion: Internal Slack thread

              rh-ee-ehearne Evan Hearne
              rh-ee-shpaitha Shubhada Paithankar
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: