Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1986167

Summary:	kube-apiserver initContainer setup is not requesting required resources: cpu, memory
Product:	OpenShift Container Platform	Reporter:	Luis Sanchez <sanchezl>
Component:	kube-apiserver	Assignee:	Luis Sanchez <sanchezl>
Status:	CLOSED WONTFIX	QA Contact:	Rahul Gangwar <rgangwar>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.7	CC:	aos-bugs, kewang, mfojtik, sttts, wking, xxia
Target Milestone:	---
Target Release:	4.7.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	LifecycleReset
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1986166	Environment:
Last Closed:	2021-10-21 11:59:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1986166
Bug Blocks:

Description Luis Sanchez 2021-07-26 20:01:10 UTC

+++ This bug was initially created as a clone of Bug #1986166 +++

+++ This bug was initially created as a clone of Bug #1905326 +++

This bug was initially created as a copy of Bug #1905298, but for kube-apiserver. 
 Per Clayton, initContainers must set both of these going forward [1], while [2] is showing:

openshift-kube-apiserver/kube-apiserver-ci-op-sdpv1krm-2a78c-r94vn-master-0 container initContainers[0] (setup) is not requesting required resources: cpu, memory
openshift-kube-apiserver/kube-apiserver-ci-op-sdpv1krm-2a78c-r94vn-master-1 container initContainers[0] (setup) is not requesting required resources: cpu, memory
openshift-kube-apiserver/kube-apiserver-ci-op-sdpv1krm-2a78c-r94vn-master-2 container initContainers[0] (setup) is not requesting required resources: cpu, 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

--- Additional comment from Michal Fojtik on 2021-01-07 04:24:36 UTC ---

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 1 Michal Fojtik 2021-07-26 20:09:04 UTC

The LifecycleStale keyword was removed because the needinfo? flag was reset and the bug got commented on recently.
The bug assignee was notified.