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

ibm-powervs-block-csi-driver-controller does not set resource requests

    XMLWordPrintable

Details

    • Bug
    • Status: Verified
    • Major
    • Resolution: Unresolved
    • 4.12.0
    • None
    • Storage
    • Rejected
    • Hide

      None

      Show
      None

    Description

      [sig-arch] Managed cluster should set requests but not limits [Suite:openshift/conformance/parallel]

      This test is failing on e2e-ppc64le-powervs. See resource requests https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#resources-and-limits for more information about how to add these.

      {  fail [github.com/onsi/ginkgo@v4.7.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Sep 28 08:25:05.277: 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/ibm-powervs-block-csi-driver-controller/container/node-update-controller does not have a cpu request (rule: "apps/v1/Deployment/openshift-cluster-csi-drivers/ibm-powervs-block-csi-driver-controller/container/node-update-controller/request[cpu]")
        apps/v1/Deployment/openshift-cluster-csi-drivers/ibm-powervs-block-csi-driver-controller/container/node-update-controller does not have a memory request (rule: "apps/v1/Deployment/openshift-cluster-csi-drivers/ibm-powervs-block-csi-driver-controller/container/node-update-controller/request[memory]")
      Ginkgo exit error 1: exit with code 1}
      

      Attachments

        Activity

          People

            jdobson@redhat.com Jonathan Dobson
            stbenjam Stephen Benjamin
            Julie Mathew Julie Mathew
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: