Bug 2055197

Summary: Increased etcd alert test failures after latest static pod fix
Product: OpenShift Container Platform Reporter: Devan Goodwin <dgoodwin>
Component: Test FrameworkAssignee: Devan Goodwin <dgoodwin>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.10CC: wking
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2055196 Environment:
Last Closed: 2022-02-28 18:22:37 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: 2055196    
Bug Blocks: 2049750    

Description Devan Goodwin 2022-02-16 13:11:41 UTC 
+++ This bug was initially created as a clone of Bug #2055196 +++

Test has begun failing more often:

[bz-etcd][invariant] alert/etcdHighNumberOfLeaderChanges should not be at or above info

This is because the latest round of static pod fix included some increased delays, and now things can take longer.

TRT needs to update the alerting data json in origin based on latest data from bigquery to allow the test to not fail as often.

--- Additional comment from Devan Goodwin on 2022-02-16 13:10:26 UTC ---

https://sippy.ci.openshift.org/sippy-ng/tests/4.11/analysis?test=openshift-tests-upgrade.[bz-etcd][invariant]%20alert/etcdHighNumberOfLeaderChanges%20should%20not%20be%20at%20or%20above%20info indicates that test results are improving as of today.