Bug 2008207

Summary: vsphere CSI driver doesn't set resource limits
Product: OpenShift Container Platform Reporter: Stephen Benjamin <stbenjam>
Component: StorageAssignee: Hemant Kumar <hekumar>
Storage sub component: Storage QA Contact: Wei Duan <wduan>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs, hekumar
Version: 4.9   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
job=periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere=all job=periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-ovn=all job=periodic-ci-openshift-release-master-ci-4.10-upgrade-from-stable-4.9-e2e-vsphere-upgrade=all job=periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-upi=all job=periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-techpreview=all
Last Closed: 2022-03-12 04:38:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stephen Benjamin 2021-09-27 15:18:38 UTC 
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.
Comment 3 Wei Duan 2021-10-01 03:16:43 UTC 
Verified pass on 4.10.0-0.nightly-2021-09-30-154054

    name: vsphere-syncer
    resources:
      requests:
        cpu: 10m
        memory: 50Mi
Comment 6 errata-xmlrpc 2022-03-12 04:38:40 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 (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