Arun, is this expected or this is a bug? If it is expected then what is the impact (on QE, Doc, customer etc.)
(In reply to Mudit Agarwal from comment #5) > Arun, is this expected or this is a bug? > If it is expected then what is the impact (on QE, Doc, customer etc.) Yes Mudit. This is a bug, we should be showing all the Storage Systems available (Ceph or IBM or MCG etc). @Sanjal, you have mentioned that `UI cannot use a different query`. Is it possible for us to use multiple queries (in the UI) and get all the results (instead of a single query)? If that is not possible then we have to device a single query or change the existing `odf_system_health_status` query to support all the Storage Systems.
(In reply to arun kumar mohan from comment #9) > (In reply to Mudit Agarwal from comment #5) > > Arun, is this expected or this is a bug? > > If it is expected then what is the impact (on QE, Doc, customer etc.) > > Yes Mudit. This is a bug, we should be showing all the Storage Systems > available (Ceph or IBM or MCG etc). > > @Sanjal, you have mentioned that `UI cannot use a different query`. Is it > possible for us to use multiple queries (in the UI) and get all the results > (instead of a single query)? > > If that is not possible then we have to device a single query or change the > existing `odf_system_health_status` query to support all the Storage Systems. Hi Arun, UI uses generic metric/query which will work for all type of StorageSystems (internal/external/mcg-standalone/ibm-flashsystem/<any_new_maybe_in_future>). Ideally we shouldn't be making any UI change as we are using same metric/query since beginning unless it is not a monitoring/backend bug and are deliberate changes (if these are intentional changes from the backend it sounds strange that these changes were made without prior info that too after feature freeze:/ ) In case it is something that can not be fixed from backend then we need to make sure (we can discuss offline in a call as well): 1) Whatever metric we use is generic as well (for example: we can't use ceph_health_status as it will not work for mcg-standalone storagesystem). 2) We might have to backport the changes to earlier releases as well, depending upon upto which versions are affect. But that is just my take, tagging @badhikar as well to keep him in loop and in case I missed anything.
We cannot change queries in the dashboard to accommodate any storage system. Storage Systems must report metrics as per the agreed upon convention.
Closing this issue as 'WORKS-FOR-ME'.
from conversation with @skatiyar and @muagarwa appears that the bug fix for 4.10 depends on https://bugzilla.redhat.com/show_bug.cgi?id=2142787 which on 23/11/22 is being under development. Even though bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=2142763 is on verification we still need to wait pr merged for 2142787, in order to verify and close this issue
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days