Bug 1941803 - Unnecessary and incorrect readiness probes in on-prem manifests
Summary: Unnecessary and incorrect readiness probes in on-prem manifests
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.7.0
Assignee: Ben Nemec
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks: 1940594
TreeView+ depends on / blocked
 
Reported: 2021-03-22 19:37 UTC by Ben Nemec
Modified: 2021-03-22 20:03 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-22 19:38:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.