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

whereabouts container defines limits where it's not allowed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 4.20.0
    • 4.19
    • Networking / multus
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • In Progress
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-59134. The following is the description of the original issue:
      —
      Description of problem:

         ShiftOnStack conformance tests fails """
fail [github.com/openshift/origin/test/extended/operators/resources.go:244]: Pods in platform namespaces are not following resource request/limit rules or do not have an exception granted:
  apps/v1/Deployment/openshift-multus/whereabouts-controller/container/whereabouts defines a limit on cpu of 100m which is not allowed (rule: "apps/v1/Deployment/openshift-multus/whereabouts-controller/container/whereabouts/limit[cpu]")
  apps/v1/Deployment/openshift-multus/whereabouts-controller/container/whereabouts defines a limit on memory of 200Mi which is not allowed (rule: "apps/v1/Deployment/openshift-multus/whereabouts-controller/container/whereabouts/limit[memory]")
Ginkgo exit error 1: exit with code 1"""

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

              pliurh Peng Liu
              ekuvaja Erno Kuvaja
              None
              None
              Weibin Liang Weibin Liang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: