Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-20512

[2118823] Deprecated API 1.25 call: virt-cdi-controller/v0.0.0 (linux/amd64) kubernetes/$Format

XMLWordPrintable

    • Important
    • None

      Description of problem:
      On an upgraded cluster found the following deprecated api 1.25 call for virt-cdi-controller/v0.0.0 (linux/amd64) kubernetes/$Format:
      =============
      {'kind': 'Event', 'apiVersion': 'audit.k8s.io/v1', 'level': 'Metadata', 'auditID': '728c199f-df42-4a91-b737-3087e5e904f5', 'stage': 'ResponseComplete', 'requestURI': '/apis/batch/v1beta1/cronjobs?allowWatchBookmarks=true&resourceVersion=2850743&timeoutSeconds=423&watch=true', 'verb': 'watch', 'user': {'username': 'system:serviceaccount:openshift-cnv:cdi-sa', 'uid': '1afaedfa-cfd5-4713-8ec0-020ba0e4f05b', 'groups': ['system:serviceaccounts', 'system:serviceaccounts:openshift-cnv', 'system:authenticated'], 'extra': {'authentication.kubernetes.io/pod-name': ['cdi-deployment-6cdb55fbf7-l6xlp'], 'authentication.kubernetes.io/pod-uid': ['5d9a30a6-d0a9-45a5-9677-c47ba28b8a8a']}}, 'sourceIPs': ['10.1.156.7'], 'userAgent': 'virt-cdi-controller/v0.0.0 (linux/amd64) kubernetes/$Format', 'objectRef':

      {'resource': 'cronjobs', 'apiGroup': 'batch', 'apiVersion': 'v1beta1'}

      , 'responseStatus': {'metadata': {}, 'code': 200}, 'requestReceivedTimestamp': '2022-08-10T13:48:36.234802Z', 'stageTimestamp': '2022-08-10T13:49:00.776506Z', 'annotations': {'authorization.k8s.io/decision': 'allow', 'authorization.k8s.io/reason': 'RBAC: allowed by ClusterRoleBinding "cdi-sa" of ClusterRole "cdi" to ServiceAccount "cdi-sa/openshift-cnv"', 'k8s.io/deprecated': 'true', 'k8s.io/removed-release': '1.25'}}
      =============
      This cluster went through the following upgrade path:
      4.9.44(OCP)/4.9.5(CNV) → 4.10.25(OCP)/4.10.3-22(CNV) → 4.11.0-rc.5(OCP)/4.11.0-587(CNV)
      Version-Release number of selected component (if applicable):
      4.11.0-rc.5(OCP)
      4.11.0-587(CNV)

      How reproducible:
      Seen against 1 run.

      Steps to Reproduce:
      1. Upgrade a cluster from 4.9.z->4.10.z->4.11.0 and check for deprecated API log messages in audit.log
      2.
      3.

      Actual results:
      Deprecated 1.25 API call

      Expected results:
      No Deprecated 1.25 API call

      Additional info:

              akalenyu Alex Kalenyuk
              rhn-support-dbasunag Debarati Basu-Nag
              Natalie Gavrielov Natalie Gavrielov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: