Bug 1905324 - ingress-operator is not requesting required memory resource
Summary: ingress-operator is not requesting required memory resource
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Ryan Fredette
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-08 03:25 UTC by W. Trevor King
Modified: 2022-08-04 22:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The ingress-operator container definition did not include a memory request Consequence: It was possible that the ingress-operator pod could be scheduled on a node without enough memory available Fix: An appropriate memory request was added to the ingress-operator container definition Result: ingress-operator will not be scheduled on nodes without enough available memory
Clone Of:
Environment:
Last Closed: 2021-02-24 15:40:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 515 0 None closed Bug 1905324: Request appropriate memory for ingress-operator container 2021-02-03 15:26:23 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:40:50 UTC

Description W. Trevor King 2020-12-08 03:25:17 UTC
This bug was initially created as a copy of Bug #1905298, but for the ingress operator.  Containers must set both of these going forward [1], while [2] is showing:

openshift-ingress-operator/ingress-operator-5855ff78d5-46l5c container containers[0] (ingress-operator) is not requesting required resources: memory

as part of failing:

  [sig-arch] Managed cluster should ensure control plane containers have requests set for cpu and memory [Suite:openshift/conformance/parallel]

origin/25747 is in flight to transition an existing, but overly relaxed, test-case to explicitly require both requests on all containers.  Any components which have not been fixed after an initial pass will have temporary exceptions linked to their tracking bugs when the stricter test lands.

[1]: https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#resources-and-limits
[2]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25747/pull-ci-openshift-origin-master-e2e-gcp/1336048716389289984

Comment 2 Hongan Li 2021-01-11 09:37:54 UTC
verified with 4.7.0-0.nightly-2021-01-10-070949 and passed

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-01-10-070949   True        False         60m     Cluster version is 4.7.0-0.nightly-2021-01-10-070949


$ oc -n openshift-ingress-operator get deployment/ingress-operator -oyaml
<---snip--->
        name: ingress-operator
        resources:
          requests:
            cpu: 10m
            memory: 56Mi

Comment 5 errata-xmlrpc 2021-02-24 15:40:33 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.7.0 security, bug fix, and enhancement 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-2020:5633


Note You need to log in before you can comment on or make changes to this bug.