We hardcode p99 values for alert-seconds . burn budget was recently fixed, so we need to update the values for 4.10 to prevent regressions in z-streams.
https://github.com/openshift/origin/pull/26815 fixes this
@David As discussed with David this is not functional change only file change. https://amd64.ocp.releases.ci.openshift.org/releasestream/4.10.0-0.ci/release/4.10.0-0.ci-2022-02-04-082923 lists the PR in the change history but in bug target release 4.11. Can you please confirm on this?
git log -4
commit 287faac66f56c565280d5fec947082c1fd413399 (HEAD -> master, origin/release-4.11, origin/master, origin/HEAD)
Merge: 4b7fedba31 88866b022f
Author: David Eads <deads2k.github.com>
Date: Thu Feb 3 14:50:03 2022 -0500
Merge pull request #26815 from deads2k/times
bug 2050345: update p99 values for disruption and alerts
oc adm release info --commits registry.ci.openshift.org/ocp/release:4.11.0-0.nightly-2022-02-04-104502 | grep origin
tests https://github.com/openshift/origin 287faac66f56c565280d5fec947082c1fd413399
As discussed with David this is not functional change only file change, PR changes present in build, moving this bug to verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.