vsphere jobs that run e2e tests are failing with the following messsage: fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Sep 26 20:45:06.367: Pods in platform namespaces are not following resource request/limit rules or do not have an exception granted: apps/v1/Deployment/openshift-cluster-csi-drivers/vmware-vsphere-csi-driver-controller/container/vsphere-syncer does not have a cpu request (rule: "apps/v1/Deployment/openshift-cluster-csi-drivers/vmware-vsphere-csi-driver-controller/container/vsphere-syncer/request[cpu]") apps/v1/Deployment/openshift-cluster-csi-drivers/vmware-vsphere-csi-driver-controller/container/vsphere-syncer does not have a memory request (rule: "apps/v1/Deployment/openshift-cluster-csi-drivers/vmware-vsphere-csi-driver-controller/container/vsphere-syncer/request[memory]") Example job: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-ovn/1442212891288670208 See https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#resources-and-limits for more information about the conventions used to set memory and cpu requests.
Verified pass on 4.10.0-0.nightly-2021-09-30-154054 name: vsphere-syncer resources: requests: cpu: 10m memory: 50Mi
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 (Moderate: OpenShift Container Platform 4.10.3 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:0056