Created attachment 1997833 [details] ocs_storage_client_operator_version metric query Description of problem (please be detailed as possible and provide log snippests): Metric ocs_storage_client_operator_version is returning -1 for all clients. This could affect StorageClientIncompatibleOperatorVersion alert functionality. ocs_storage_client_platform_version and ocs_storage_client_last_heartbeat return actual values. Version of all relevant components (if applicable): Custom 'hci' ODF 4.14 build '4.14.0-160' Steps to Reproduce: 1. Deploy HCI cluster with provider and clients 2. Check ocs_storage_client_operator_version metric values Actual results: All clients have metric value set to -1. Expected results: Connected clients should report operator version correctly. Additional info:
Already fixed in build 162.
> client: > operatorVersion: N/A > platformVersion: N/A - I believe this client didn't get update to 162 build, pls cross check once. - "-1" is returned when we couldn't encode the version to a number, such as "401400", here the version is "N/A" and so the final value is "-1", we'll be skipping such values while raising alerts - I would say the bug is fixed based on "3 consumers have version 401400"
(In reply to Leela Venkaiah Gangavarapu from comment #4) > > client: > > operatorVersion: N/A > > platformVersion: N/A > - I believe this client didn't get update to 162 build, pls cross check once. > - "-1" is returned when we couldn't encode the version to a number, such as > "401400", here the version is "N/A" and so the final value is "-1", we'll be > skipping such values while raising alerts > - I would say the bug is fixed based on "3 consumers have version 401400" The problematic client was lost before the update. It is still reported as connected (https://bugzilla.redhat.com/show_bug.cgi?id=2247738) but the cluster is not reachable. Healthy clients return value 4014000. Unavailable client returns -1. --> VERIFIED Tested with: Custom 'hci' ODF 4.14 build '4.14.0-162'
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: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix 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-2024:1383