Bug 2079197

Summary:	[RFE] alert when more than one default storage class is detected
Product:	OpenShift Container Platform	Reporter:	Roman Bednář <rbednar>
Component:	Storage	Assignee:	Roman Bednář <rbednar>
Storage sub component:	Storage	QA Contact:	Rohit Patil <ropatil>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	aos-bugs, ropatil, wduan
Version:	4.11
Target Milestone:	---
Target Release:	4.11.0
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:	2022-08-10 11:08:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roman Bednář 2022-04-27 07:47:18 UTC

CSI migration enhancement states that we should create alerts when there is more than one default storage class configured:

https://github.com/openshift/enhancements/pull/1062/files#diff-8a4ef7567cf090023cac730c09b94e71e4dfa18d439c05b9fd07ac058b5d4320R163

Initially this was intended to be implemented in storage class controller:

https://github.com/openshift/library-go/pull/1345

However, if more than one operator that uses this controller is deployed, it would result in creating the same alert from each operator making it difficult for users to troubleshoot.

Comment 3 Rohit Patil 2022-05-30 11:03:10 UTC

Verification Status: PASS 
Payload: 4.11.0-0.nightly-2022-05-25-193227
Platform: AWS 

Steps Tested. 
1) Check for the default sc alerting state: Pending  and metrics count: 1
2) Modify existing or create new sc as default and check for alerting: firing + metrics counts: 2 
3) Modify the cluster default sc gp2 to non default, check the alerting: Pending + metrics count: 1
4) Remove the sc gp2, which in turn creates new sc gp2 as default, check metrics: 2 + alerting: firing 
5) Check logs

Comment 5 errata-xmlrpc 2022-08-10 11:08:39 UTC

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.

https://access.redhat.com/errata/RHSA-2022:5069