Bug 2209032 - CDIStorageProfilesIncomplete is firing in 42% of external clusters that are reporting to Telemetry [NEEDINFO]
Summary: CDIStorageProfilesIncomplete is firing in 42% of external clusters that are r...
Keywords:
Status: ASSIGNED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 4.12.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.13.4
Assignee: Arnon Gilboa
QA Contact: Natalie Gavrielov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-22 10:59 UTC by Shirly Radco
Modified: 2023-08-09 12:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
agilboa: needinfo? (alitke)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-28958 0 None None None 2023-05-22 10:59:49 UTC

Description Shirly Radco 2023-05-22 10:59:01 UTC
Description of problem:
After the fix in https://bugzilla.redhat.com/show_bug.cgi?id=2169686 the number of CDIStorageProfilesIncomplete alerts dropped from ~76% CNV external clusters that are impacted by the alert to 42%. This is still a high number of impacted clusters.

Please check if there is a real issue that needs to be addressed or if this is an issue with the alert itself.

Version-Release number of selected component (if applicable):
4.12.2

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
High number of clusters have this alert constantly firing.

Expected results:
Alert should fire in low numbers of clusters.

Additional info:

Comment 1 Adam Litke 2023-05-31 12:35:17 UTC
Shirly, is there a way to build a query that includes the operators that are installed on the clusters which are firing this alert?  If we have either the operator list or the storage classes that are deployed we can figure out which storage provisioners are lacking StorageProfile information.


Note You need to log in before you can comment on or make changes to this bug.