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

Bug 1817774

Summary: Alert if any node has: kubernetes.io/hostname: localhost
Product: OpenShift Container Platform Reporter: W. Trevor King <wking>
Component: NodeAssignee: Ryan Phillips <rphillips>
Status: CLOSED DEFERRED QA Contact: Sunil Choudhary <schoudha>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.3.zCC: aos-bugs, jokerman, sdodson
Target Milestone: ---   
Target Release: 4.5.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: 2020-05-18 14:58:47 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:

Description W. Trevor King 2020-03-26 23:45:48 UTC
This can break common anti-affinity patterns as described in bug 1817769.  We should alert on this condition so the cluster admin can easily discover the problem and fix it (and also so that we hear about this issue in Telemetry/Insights), without having to do a bunch of debugging and wondering about scheduler bugs.

Comment 1 Ryan Phillips 2020-03-31 20:07:12 UTC
I'm not a huge fan of creating alarms for bugs. Typically these metrics are wasteful.

Comment 2 W. Trevor King 2020-04-01 04:16:08 UTC
Alerting on this costs CPU.  Having devs/admins hunt for this costs salary.  People are more expensive than computers.  I'm open to alternatives to alerts for raising the visibility of this troubling condition, but lots of smart people looked at the must-gather for this cluster before Miciah noticed the localhost issue.  I'd like to have the machines chip in in a way that cuts that time down for admins on the next cluster that hits this.  Do you have alternative ideas?

Comment 3 Ryan Phillips 2020-05-18 14:58:47 UTC
Created a JIRA to track the feature request: https://issues.redhat.com/browse/OCPNODE-344