Bug 1888206

Summary: MAO alert timing too aggressive
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Cloud ComputeAssignee: Michael Gugino <mgugino>
Cloud Compute sub component: Other Providers QA Contact: sunzhaohua <zhsun>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: unspecified CC: efried, mimccune, rrackow, wking
Version: 4.6Keywords: Reopened, ServiceDeliveryImpact
Target Milestone: ---   
Target Release: 4.5.z   
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: 2021-03-02 15:45:20 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: 1878204    
Bug Blocks:    

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