Bug 1888206 - MAO alert timing too aggressive
Summary: MAO alert timing too aggressive
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.z
Assignee: Michael Gugino
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On: 1878204
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-14 11:38 UTC by OpenShift BugZilla Robot
Modified: 2021-03-02 15:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-02 15:45:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-api-operator pull 729 0 None open [release-4.5] Bug 1888206: Adjust alert timing and severity 2021-02-16 16:35:00 UTC

Comment 1 Michael Gugino 2020-10-26 20:31:59 UTC 
Merging into older releases is not a priority for this bug.  Fixed in 4.6 and newer.  Closing.
Comment 2 Rick Rackow 2021-02-09 21:27:28 UTC 
Service Delivery has a major need for this, as we can't tolerate the noise but also won't and can't force customers into upgrading
Comment 4 W. Trevor King 2021-02-09 22:03:10 UTC 
The critical alerts are noisy, but we've had them throughout 4.5.z, so the PR not having landed should not block further 4.5.z.
Comment 5 Joel Speed 2021-02-25 14:11:59 UTC 
4.5 will shortly move into CVE only patches, I don't think this is going to get backported to 4.5 at this stage in the lifecycle. Will leave open until we have confirmed that this is correct
Comment 7 Joel Speed 2021-03-02 15:45:20 UTC 
Discussed within the team, we are going to close this out now as we don't deem this high enough priority to backport to an N-2 release
Note You need to log in before you can comment on or make changes to this bug.