-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.17.0
-
None
-
False
-
4.17.0-0.nightly-2024-08-05-063006 failed in part due to aws-ovn-upgrade-4.17-micro aggregation failures
Caused by
{Zero successful runs, we require at least one success to pass (P70=3.00s failures=[1820347983690993664=56s 1820348008856817664=80s 1820347977814773760=46s 1820347658217197568=52s 1820347967748444160=70s 1820347998836625408=52s 1820347972789997568=38s 1820347993786683392=52s 1820347988728352768=72s 1820347962715279360=80s 1820348003832041472=76s]) name: kube-api-http1-localhost-new-connections disruption P70 should not be worse
Failed: Mean disruption of openshift-api-http2-localhost-new-connections is 70.20 seconds is more than the failureThreshold of the weekly historical mean from 10 days ago: historicalMean=0.00s standardDeviation=0.00s failureThreshold=1.00s historicalP95=0.00s successes=[] failures=[1820347983690993664=68s 1820348008856817664=96s 1820347972789997568=48s 1820347658217197568=62s 1820348003832041472=88s 1820347962715279360=94s 1820347998836625408=62s 1820347993786683392=60s 1820347988728352768=86s 1820347977814773760=54s 1820347967748444160=80s] name: openshift-api-http2-localhost-new-connections mean disruption should be less than historical plus five standard deviations testsuitename: aggregated-disruption
Additionally we are seeing failures on azure upgrades that show large disruption during etcd-operator updating
Opening this bug to investigate and run payload tests against to rule it out.