Description of problem: Heartbeat job running in hcp based cluster is not sending the cluster name # k get storageconsumer -ojsonpath='{.items[*].status.client}' | jq { "clusterId": "727c7233-a0ee-4790-815d-6efa3578ebb6", "clusterName": "ibm-baremetal1", "name": "ocs-storagecluster", "operatorVersion": "4.16.0-89.stable", "platformVersion": "4.16.0-ec.5" } { "clusterId": "fcdf9cac-a123-4566-beb0-3d9d5e51f2d6", "clusterName": "", "name": "storage-client", "operatorVersion": "4.16.0-86.stable", "platformVersion": "4.16.0-ec.5" } Version-Release number of selected component (if applicable): Provider - OCP 4.16.0-ec.5, ODF 4.16.0-86 Client - OCP 4.16.0-ec.5, ODF 4.16.0-89 How reproducible: oc -n -n openshift-storage get storageconsumer -ojsonpath='{.items[*].status.client}' | jq The native Client populates clusterName and Hosted client is not Steps to Reproduce: 1. oc -n -n openshift-storage get storageconsumer -ojsonpath='{.items[*].status.client}' | jq 2. 3. Actual results: "clusterName": "" Expected results: "clusterName": "ibm-baremetal1" Additional info: Management cluster MG - https://drive.google.com/drive/folders/10tPMdkjpft6SVsqyxlPb8TCVqzN75-CQ?usp=drive_link
Tested in version: OCP 4.16.0-110 Cluster version is 4.16.0-ec.6 ClusterName is missing in storageconsumer of a client in hosted cluster. % oc get storageconsumer storageconsumer-077361a6-259a-48ef-8fe9-f7ccd957a406 -n openshift-storage -ojsonpath='{.status}' | jq { "cephResources": [ { "kind": "CephClient", "name": "d580c1393ec50f784baa789d258564d8", "status": "Ready" } ], "client": { "clusterId": "077361a6-259a-48ef-8fe9-f7ccd957a406", "clusterName": "", "name": "ocs-storagecluster", "operatorVersion": "4.16.0-101.stable", "platformVersion": "4.16.0-ec.6" }, "lastHeartbeat": "2024-05-30T13:39:00Z", "state": "Ready" }
ODF 4.16.0-118 fixed oc -n openshift-storage get storageconsumer -ojsonpath='{.items[*].status.client}' | jq { "clusterId": "853b3ca7-378a-4fc0-8f20-4d770483d30b", "clusterName": "hcp415-bm2-b.apps.ibm-baremetal2.qe.rh-ocs.com", "name": "storage-client", "operatorVersion": "4.16.0-120.stable", "platformVersion": "4.15.16" } { "clusterId": "b61413fc-d665-4891-baf0-f57f71c41374", "clusterName": "ibm-baremetal2.qe.rh-ocs.com", "name": "ocs-storagecluster", "operatorVersion": "4.16.0-118.stable", "platformVersion": "4.16.0-rc.3" } { "clusterId": "d922ca9d-7ca6-40ea-8b41-5851fd525574", "clusterName": "hcp415-bm2-a.apps.ibm-baremetal2.qe.rh-ocs.com", "name": "storage-client", "operatorVersion": "4.16.0-120.stable", "platformVersion": "4.15.15" }
Please update the RDT flag/text appropriately.
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.16.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:4591