Bug 1828630

Summary: [4.3 upgrade][alert]AggregatedAPIErrors
Product: OpenShift Container Platform Reporter: Hongkai Liu <hongkliu>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED DUPLICATE QA Contact: Xingxing Xia <xxia>
Severity: low Docs Contact:
Priority: medium    
Version: 4.3.0CC: alegrand, anpicker, aos-bugs, erooth, kakkoyun, lcosic, mfojtik, mloibl, pkrupa, scuppett, surbania
Target Milestone: ---Keywords: Upgrades
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-20 09:04:52 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:
Attachments:
Description Flags
prometheus.screenshot none

Description Hongkai Liu 2020-04-28 00:38:19 UTC 
During upgrade of a cluster in CI build farm, we have seen a sequence of alerts and messages of failures from clusterversion.

From: 4.3.17
To: 4.4.0-rc.12

Eventually upgrade was completed successfully (which is so nice).
But those alerts and messages are too frightening.

I would like to create a bug for each of those and feel better for the next upgrade.

https://coreos.slack.com/archives/CHY2E1BL4/p1588026231127500


[FIRING:11] AggregatedAPIErrors (default openshift-monitoring/k8s warning)
Comment 1 Hongkai Liu 2020-04-28 00:43:11 UTC 
Created attachment 1682323 [details]
prometheus.screenshot
Comment 2 Lili Cosic 2020-04-28 07:22:39 UTC 
I believe this alert was added by the apiserver team. Reassigning to them, feel free to correct me.

Note we are removing this alert in upstream repo for now in 4.6, let us know if you need it removed in sooner versions. https://github.com/kubernetes-monitoring/kubernetes-mixin/pull/401
Comment 3 Stephen Cuppett 2020-04-28 12:37:06 UTC 
Setting target release to current development version (4.5) for investigation. Where fixes (if any) are required/requested for prior versions, cloned BZs will be created when appropriate.
Comment 5 Stefan Schimanski 2020-05-20 09:04:52 UTC 

*** This bug has been marked as a duplicate of bug 1809031 ***