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

Bug 1941803

Summary:	Unnecessary and incorrect readiness probes in on-prem manifests
Product:	OpenShift Container Platform	Reporter:	Ben Nemec <bnemec>
Component:	Machine Config Operator	Assignee:	Ben Nemec <bnemec>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Nguyen <mnguyen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.7
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-22 19:38:13 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:
Bug Depends On:
Bug Blocks:	1940594

Description Ben Nemec 2021-03-22 19:37:06 UTC

Description of problem: In 4.6 we somehow ended up with some readiness probes on the on-prem static pods. This makes no sense because the ready status of those containers is irrelevant (Kubernetes never routes traffic to them), but it can cause some confusion when a container shows as not ready in the API. It also triggers unnecessary warnings in the UI.

For 4.7 we actually cleaned these up without a bug because they didn't cause any functional problems, but due to the cosmetic issues we've now had a bug opened against 4.6 for it. I'm opening and closing this one to indicate that we fixed the problem in 4.7 so we can backport the removal to 4.6.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1940594
https://github.com/openshift/machine-config-operator/pull/2073