Print StorageCluster CR health table from odf get health by AnikaYadav1 · Pull Request #429 · red-hat-storage/odf-cli

AnikaYadav1 · 2026-10-21T18:15:18Z

Add CR health table to odf get health

Add PrintCRHealth, which reports the status of each StorageCluster
and the custom resources it manages, and wire it into
odf get health so the table is printed by default.

Each StorageCluster gets a header with its basic details, followed
by a table showing the state of its managed resources.

The header shows:

StorageCluster: name of the StorageCluster
Namespace: namespace it runs in
Phase: current phase from its status
Mode: internal or external

The table has these columns:

COMPONENT: kind of managed resource (for example
CephCluster, Block pool, NooBaa)
NAME: name of the resource
OBSERVED: current state reported by the resource
STATUS MESSAGE: message explaining that state, if any
Fields that are missing or empty are shown as "-".

Changes to odf get health:

odf get health prints the CR health table, then the cluster health
report.
odf get health --verbose prints the same output with more details.
-n limits the table to that namespace.
Without it, all namespaces are searched.

AnikaYadav1 · 2026-10-21T18:29:43Z

@parth-gr @subhamkrai @travisn
please take a look

travisn · 2026-10-21T19:57:33Z

 	Example: "odf get health",
 	PreRun: func(cmd *cobra.Command, args []string) {
-		// verify operator pod is running
+		if !healthVerbose {


Some basic useful info will come from the operator pod, so it seems valid to wait for it even if not verbose

now it waits in both cases, with and without --verbose.

travisn · 2026-10-21T19:58:47Z

 - `odf get`:
  - `recovery-profile`: Get the recovery profile value.
-  - `health`: Check health of the cluster and common configuration issues.
+  - `health`: Print StorageCluster-managed CR status. Use `--verbose` for checking health of the cluster and common configuration issues.


I would recommend the odf get health command print as much status as useful, as long as it is quick to gather. There is more useful info by default than only the CR status.

After discussing with the team and Eran we had decided that odf get health should be a quick look at StorageCluster CR status only. odf get health --verbose includes everything else. The original odf get health output was already a subset of --verbose, so everything that used to be in odf get health is still in odf get health --verbose.

Let's get a written agreement on the epic, just to confirm everyone is on the same page. On the epic, could you show the following info?

Example output for the proposed get health output

Example output for the full verbose get health output

Point out which verbose status takes longer to detect, and which verbose status is quick to collect. Then we can finalize if any quick info would be helpful in the main output instead.

Confirm what we will collect with the must-gather. (IIRC we discussed the mg will not gather the verbose info)

Started a slack thread for this:
https://ibm-systems-storage.slack.com/archives/C0C3WJBCUMP/p1793095017298569

AnikaYadav1 · 2026-10-22T13:50:00Z

Here are the screenshots testing it on a cluster
https://docs.google.com/document/d/1CIohaA1w7uHO5YxDGqFbISjwH60p_krfYkdteBaR7pw/edit?tab=t.0
ptal @parth-gr @travisn @subhamkrai

subhamkrai

I'll review in details tomorrow. Also, please share the new output in github comments, and also, update the CI tests.

subhamkrai · 2026-10-26T11:46:46Z

 var clusterHealth = &cobra.Command{
 	Use:     "health",
-	Short:   "check health of the cluster and common configuration issues",
+	Short:   "print StorageCluster-managed CR status, or detailed pod checks with --verbose",


Suggested change

Short: "print StorageCluster-managed CR status, or detailed pod checks with --verbose",

Short: "print ODF CR status, or detailed status with --verbose flag",

Let's add Long as well, if needed, to describe the default command and the --verbose command

subhamkrai · 2026-10-26T11:47:52Z

-			},
+		namespace := ""
+		namespaceSet := false
+		if f := cmd.Flag("namespace"); f != nil && f.Changed {


Suggested change

if f := cmd.Flag("namespace"); f != nil && f.Changed {

if flagNamespace := cmd.Flag("namespace"); f != nil && f.Changed {

Please use meaningful variable names

AnikaYadav1 · 2026-10-27T04:52:03Z

Output screenshots :

odf get health

odf get health --verbose

subhamkrai · 2026-10-28T10:15:40Z

+	{component: "Consumer", group: "ocs.openshift.io", version: "v1alpha1", kind: "StorageConsumer", namespaced: true, observedPath: []string{"status", "state"}},
+	{component: "SVG", group: "ceph.rook.io", version: "v1", kind: "CephFilesystemSubVolumeGroup", namespaced: true, observedPath: []string{"status", "phase"}},
+	{component: "RNS", group: "ceph.rook.io", version: "v1", kind: "CephBlockPoolRadosNamespace", namespaced: true, observedPath: []string{"status", "phase"}},


Suggested change

{component: "Consumer", group: "ocs.openshift.io", version: "v1alpha1", kind: "StorageConsumer", namespaced: true, observedPath: []string{"status", "state"}},

{component: "SVG", group: "ceph.rook.io", version: "v1", kind: "CephFilesystemSubVolumeGroup", namespaced: true, observedPath: []string{"status", "phase"}},

{component: "RNS", group: "ceph.rook.io", version: "v1", kind: "CephBlockPoolRadosNamespace", namespaced: true, observedPath: []string{"status", "phase"}},

{component: "StorageConsumer", group: "ocs.openshift.io", version: "v1alpha1", kind: "StorageConsumer", namespaced: true, observedPath: []string{"status", "state"}},

{component: "SubVolumeGroup", group: "ceph.rook.io", version: "v1", kind: "CephFilesystemSubVolumeGroup", namespaced: true, observedPath: []string{"status", "phase"}},

{component: "RadosNamespace", group: "ceph.rook.io", version: "v1", kind: "CephBlockPoolRadosNamespace", namespaced: true, observedPath: []string{"status", "phase"}},

Those abbreviations are not always known to customers reading this command

made the changes

AnikaYadav1 · 2026-10-28T15:38:36Z

This is what the output looks like after adding the Ceph status section

odf get health

odf get health --verbose

travisn · 2026-10-28T17:54:01Z

I would recommend refining the verbose option further. How about this?

odf get health shows all sections
odf get health does not show any details for any section for "Details" or "Items"
odf get health --verbose: Shows all sections and all "Details" and "Items"

This would really provide the most useful approach to showing overall status, and include verbose details when needed.

parth-gr · 2026-10-29T08:12:19Z

I would recommend refining the verbose option further. How about this?

odf get health shows all sections

odf get health does not show any details for any section for "Details" or "Items"

odf get health --verbose: Shows all sections and all "Details" and "Items"

This would really provide the most useful approach to showing overall status, and include verbose details when needed.

Wont we still show the ceph -s which the live and more accurate status with odf get health?

My future plans for this were as a follow-up:
We can combine all same-type resources.

For ex: 
If there are 10 blockpools, we have to indivdualy show each one of them, 

Instead, we can show,
> 8 blockpools ready, 2 in failed/not-ready state
And just display the failed ones message and status

travisn · 2026-10-29T13:55:49Z

Wont we still show the ceph -s which the live and more accurate status with odf get health?

Yes, I would expect the ceph status to be shown always with odf get health. The ceph status is not verbose.

My future plans for this were as a follow-up: We can combine all same-type resources.

For ex: 
If there are 10 blockpools, we have to indivdualy show each one of them, 

Instead, we can show,
> 8 blockpools ready, 2 in failed/not-ready state
And just display the failed ones message and status

Yes, that's a nice simplification to show only a summary for the healthy resources.

subhamkrai · 2026-10-30T06:58:14Z

@AnikaYadav1 @parth-gr
In this output, it lists components multiple times that have more than 1 resource

What about this,

Component                    Resource   
BlockPool                    pool1         
                             pool2          
                             pool3         

RadosNamespace               RNS1
                             RNS2
                             RNS3

SubVolumeGroup               SVG1
                             SVG2
                             SVG3

Let me know if the above is not clear.

openshift-ci · 2026-10-30T08:14:48Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AnikaYadav1
Once this PR has been reviewed and has the lgtm label, please ask for approval from subhamkrai. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

travisn

Per the discussion today, we will plan on printing all status info with the main odf get health command. If not verbose, we will just hide the details and items sections. After these updates, I'll plan on reviewing in more detail. Thanks!

travisn · 2026-10-30T17:33:21Z

        shell: bash
        run: |
          ./bin/odf --help
+          # CI deploys Rook only. Install a dummy StorageCluster API so


How about move this to the github-action-helper.sh? It helps keep this github action simpler to read.

made the change

AnikaYadav1 · 2026-11-03T15:07:46Z

Updated output after discussion:

odf get health:

odf get health --verbose:

Detailed testing results : https://docs.google.com/document/d/1CIohaA1w7uHO5YxDGqFbISjwH60p_krfYkdteBaR7pw/edit?tab=t.wdon487g3fct

travisn

The new output looks good to me, where the verbose only adds the details and items, thanks!

travisn · 2026-11-03T17:04:24Z

+Object store  ocs-storagecluster-cephobjectstore                Ready     Object store created successfully
+Consumer      internal                                          Ready     Last heartbeat from the client was 20s ago
+SubVolumeGroup csi                                               Ready     Subvolume group created successfully
+RadosNamespace ocs-storagecluster-cephblockpool-builtin-implicit Ready     Rados namespace created successfully


Does the tool output have this alignment issue too? It appears we just need one more space for alignment.

The tool output does not have the alignment issue (as we can see in the output screenshots).
It was misaligned in the docs/get.md file . I have corrected it .

AnikaYadav1 · 2026-11-04T15:21:14Z

The new output looks good to me, where the verbose only adds the details and items, thanks!

Pinned kubectl-rook-ceph in go.mod to b2e68a2 (rook/kubectl-rook-ceph#483).

odf get health now includes that change, so Details and Items print only with --verbose.

ptal @travisn

travisn

LGTM, just a few nits to simplify the output.
@subhamkrai PTAL

travisn · 2026-11-04T19:35:43Z

 - `odf get`:
  - `recovery-profile`: Get the recovery profile value.
-  - `health`: Check health of the cluster and common configuration issues.
+  - `health`: Print StorageCluster-managed CR status, then the cluster health report. Use `--verbose` to include Details and Items.


Suggested change

- `health`: Print StorageCluster-managed CR status, then the cluster health report. Use `--verbose` to include Details and Items.

- `health`: Print StorageCluster-managed CR status, then the cluster health report. Use `--verbose` for more details.

travisn · 2026-11-04T19:36:09Z

 var clusterHealth = &cobra.Command{
 	Use:     "health",
-	Short:   "check health of the cluster and common configuration issues",
+	Short:   "print ODF CR status and cluster health, or include Details and Items with --verbose",


No need tell them the implementation about where the report comes from

Suggested change

Short: "print ODF CR status and cluster health, or include Details and Items with --verbose",

Short: "print cluster health, and include more details with --verbose",

travisn · 2026-11-04T19:38:14Z

+
 func init() {
-	clusterHealth.Flags().BoolVar(&healthVerbose, "verbose", false, "shows detailed check for pods")
+	clusterHealth.Flags().BoolVar(&healthVerbose, "verbose", false, "include Details and Items in the cluster health report")


Suggested change

clusterHealth.Flags().BoolVar(&healthVerbose, "verbose", false, "include Details and Items in the cluster health report")

clusterHealth.Flags().BoolVar(&healthVerbose, "verbose", false, "include more details in the cluster health report")

travisn · 2026-11-04T19:38:45Z

 ## health

-The health command checks the health of the Ceph cluster and common configuration issues. The health command validates these configurations:
+`odf get health` prints the status of each StorageCluster and the CRs it manages, then the cluster health report. `odf get health --verbose` prints the same sections and includes Details and Items for each check.


Suggested change

`odf get health` prints the status of each StorageCluster and the CRs it manages, then the cluster health report. `odf get health --verbose` prints the same sections and includes Details and Items for each check.

`odf get health` prints the status of each StorageCluster and the CRs it manages, then the cluster health report. `odf get health --verbose` prints more details for each check.

travisn · 2026-11-04T19:39:41Z

-Info: Checking if at least one mgr pod is running
-rook-ceph-mgr-a-54f7dbddcd-h7j7m        Running openshift-storage       ip-10-0-64-239.us-west-1.compute.internal
-```
+Both commands print the CR status table first, then the cluster health report. `--verbose` adds Details and Items.


No need for this line

Suggested change

Both commands print the CR status table first, then the cluster health report. `--verbose` adds Details and Items.

subhamkrai · 2026-11-06T06:51:08Z

+		namespace := ""
+		namespaceSet := false
+		if flagNamespace := cmd.Flag("namespace"); flagNamespace != nil && flagNamespace.Changed {
+			namespace = flagNamespace.Value.String()
+			namespaceSet = true
+		}


What are we trying to do here?

-n always has a default (openshift-storage), so the flag value alone cannot tell us whether the user passed it. This block checks Flag.Changed and then uses that to decide how we list StorageClusters.

namespace starts empty and namespaceSet starts false (user did not pass -n).

We look up the global --namespace flag.

If that flag exists and Changed is true, the user typed -n / --namespace. We store the value in namespace and set namespaceSet to true.

If Changed is false (odf get health with no -n), we skip the block. PrintCRHealth then lists StorageClusters in all namespaces, for example both openshift-storage and openshift-storage-extended.
-If the user passes -n openshift-storage or -n openshift-storage-extended, namespaceSet is true.

PrintCRHealth lists only that namespace, and health.Health() uses it as the cluster namespace for the Ceph report.
can refer to output screenshots when -n flag is used

https://docs.google.com/document/d/1CIohaA1w7uHO5YxDGqFbISjwH60p_krfYkdteBaR7pw/edit?tab=t.wdon487g3fct

If Changed is false (odf get health with no -n), we skip the block. PrintCRHealth then lists StorageClusters in all namespaces.

I was thinking to let's by default print for openshfit-storage namespace and if users passes other namespace or more than one than we can search all.

@parth-gr @travisn thoughts?

Instead of the namespaceSet variable, could you just set namespace="" to indicate that the namespace is not set? Then you wouldn't need to pass around two variables everywhere for the namespace.

Another thought is that everything about the cluster health seems related to a single namespace. So perhaps we need a iterate through each namespace and print health reports separately. Then we just need to pass the specific namespace everywhere since the top-level entry method would decide which namespace is being analyzed.

Dropped namespaceSet, an empty namespace means -n was not set and StorageClusters are listed in all namespaces.

odf get health now iterates through the namespaces and prints the health report separately. In case we specify a particular namespace ( e.g. odf get health -n openshift-storage) , only that cluster health report is printed .

testing screenshots -
https://docs.google.com/document/d/1CIohaA1w7uHO5YxDGqFbISjwH60p_krfYkdteBaR7pw/edit?tab=t.iadch5j96qay

Pinned kubectl-rook-ceph to the v0.10.0 release as well

@travisn @subhamkrai pal

subhamkrai · 2026-11-06T07:00:19Z

+}
+
+// listStorageClusters lists all StorageClusters present on the cluster.
+// If namespaceSet is true, the list is limited to that namespace.


What is the default behaviour, are we searching all the namespace to find storageCluster or by default we are looking for openshift-storage namespace only?

By default we search all namespaces, not only openshift-storage. odf get health with no -n lists every StorageCluster (for example both openshift-storage and openshift-storage-extended). If the user passes -n openshift-storage or -n openshift-storage-extended, we list only that namespace.

updated the comment as well

pls see the output screenshots

subhamkrai · 2026-11-06T07:05:43Z

+		if !spec.namespaced {
+			items = matchingStorageClients(items, sc.Name)


I'm not sure I understand this. Could you explain the goal here?

StorageClient is cluster-scoped, unlike the other kinds, so we cannot list it by StorageCluster namespace. listKind returns every StorageClient on the cluster (usually only the internal one anyway) . Through this check we are just ensuring that we are keeping only the local Storage Client (the one whose name matches this StorageCluster)

subhamkrai · 2026-11-06T07:24:22Z

+// nestedStringOrDash reads a nested string field (for example status.phase).
+// If the field is missing, is not a string, or is empty, it returns "-".
+func nestedStringOrDash(obj map[string]interface{}, fields ...string) string {
+	s, found, err := unstructured.NestedString(obj, fields...)


Suggested change

s, found, err := unstructured.NestedString(obj, fields...)

<meaningfull small name>, found, err := unstructured.NestedString(obj, fields...)

instead of s, can we have a more meaningful var name

Renamed s to fieldValue.
This helper reads a nested string from the CR at whatever path the caller passes, so it is used for both table columns. OBSERVED calls it with spec.observedPath. STATUS MESSAGE calls it with status.message.

subhamkrai · 2026-11-06T07:25:11Z

+// "Last heartbeat from the client was 20s ago".
+// Missing, empty, or unparsable timestamps return "-".
+func lastHeartbeatMessage(obj map[string]interface{}, now time.Time) string {
+	s, found, err := unstructured.NestedString(obj, "status", "lastHeartbeat")


same here

Suggested change

s, found, err := unstructured.NestedString(obj, "status", "lastHeartbeat")

<meaningful name>, found, err := unstructured.NestedString(obj, "status", "lastHeartbeat")

Renamed s to lastHeartbeat. This is status.lastHeartbeat from the StorageConsumer

travisn

@AnikaYadav1 For final review, could you share the output again? Or is it about the same since posted last week?

travisn · 2026-11-13T22:06:36Z

 	Use:     "health",
-	Short:   "check health of the cluster and common configuration issues",
+	Short:   "print cluster health, and include more details with --verbose",
+	Long:    `Print the status of each StorageCluster and the CRs it manages, then the cluster health report (Ceph MON, MGR, and OSD checks, pod status, placement groups, and object storage). --verbose includes Details and Items for each check.`,


--verbose is obvious, let's simplify this a bit:

Suggested change

Long: `Print the status of each StorageCluster and the CRs it manages, then the cluster health report (Ceph MON, MGR, and OSD checks, pod status, placement groups, and object storage). --verbose includes Details and Items for each check.`,

Long: `Print the status of each StorageCluster and the CRs it manages, then the cluster health report (Ceph MON, MGR, and OSD checks, pod status, placement groups, and object storage).`,

made the change

AnikaYadav1 · 2026-11-14T05:33:07Z

@AnikaYadav1 For final review, could you share the output again? Or is it about the same since posted last week?

The output screenshots are here
https://docs.google.com/document/d/1CIohaA1w7uHO5YxDGqFbISjwH60p_krfYkdteBaR7pw/edit?tab=t.iadch5j96qay

Add PrintCRHealth, which reports the status of each StorageCluster and the custom resources it manages. Each StorageCluster gets a header with its basic details, followed by a table showing the state of its managed resources. Signed-off-by: AnikaYadav1 <Anika.Yadav1@ibm.com>

odf get health prints the CR status table, then the cluster health report.odf get health --verbose prints the same output with more details. Passing -n limits the table to that namespace. Without -n the command searches all namespaces. Signed-off-by: AnikaYadav1 <Anika.Yadav1@ibm.com>

The Go Test workflow deploys Rook only, so listing StorageClusters fails without the CRD. Apply a minimal StorageCluster CRD and CR before odf get health. Other smoke tests are unchanged. Signed-off-by: AnikaYadav1 <Anika.Yadav1@ibm.com>

Bump github.com/rook/kubectl-rook-ceph to v0.10.0. odf get health then prints Details and Items only with --verbose. Signed-off-by: AnikaYadav1 <Anika.Yadav1@ibm.com>

travisn reviewed Oct 21, 2026

View reviewed changes

AnikaYadav1 force-pushed the get-health-cr-status branch 2 times, most recently from 17b67d4 to 954299b Compare October 22, 2026 13:35

subhamkrai reviewed Oct 26, 2026

View reviewed changes

AnikaYadav1 force-pushed the get-health-cr-status branch from 954299b to e92db75 Compare October 27, 2026 04:37

subhamkrai requested changes Oct 28, 2026

View reviewed changes

openshift-ci Bot assigned subhamkrai Oct 28, 2026

travisn mentioned this pull request Oct 28, 2026

Hide Details in kubectl rook-ceph health command rook/kubectl-rook-ceph#483

Merged

AnikaYadav1 force-pushed the get-health-cr-status branch from e92db75 to 8633c86 Compare October 30, 2026 08:14

AnikaYadav1 force-pushed the get-health-cr-status branch from 8633c86 to 1a3e2ad Compare October 30, 2026 08:21

travisn requested changes Oct 30, 2026

View reviewed changes

openshift-ci Bot assigned travisn Oct 30, 2026

AnikaYadav1 force-pushed the get-health-cr-status branch 2 times, most recently from 6e374a6 to 9203eab Compare November 3, 2026 15:24

travisn reviewed Nov 3, 2026

View reviewed changes

AnikaYadav1 force-pushed the get-health-cr-status branch from 9203eab to 2a4276c Compare November 4, 2026 15:17

openshift-ci Bot added the needs-rebase label Nov 4, 2026

AnikaYadav1 force-pushed the get-health-cr-status branch from 2a4276c to 949aba1 Compare November 4, 2026 15:19

AnikaYadav1 force-pushed the get-health-cr-status branch from 949aba1 to f1c32ce Compare November 4, 2026 15:31

openshift-ci Bot removed the needs-rebase label Nov 4, 2026

travisn reviewed Nov 4, 2026

View reviewed changes

travisn requested a review from subhamkrai November 4, 2026 19:45

AnikaYadav1 force-pushed the get-health-cr-status branch 2 times, most recently from ef388a9 to a86dcf8 Compare November 5, 2026 06:11

subhamkrai requested changes Nov 6, 2026

View reviewed changes

AnikaYadav1 force-pushed the get-health-cr-status branch from a86dcf8 to 80f435e Compare November 6, 2026 08:58

openshift-ci Bot added the needs-rebase label Nov 6, 2026

AnikaYadav1 force-pushed the get-health-cr-status branch from 80f435e to 715344c Compare November 6, 2026 09:06

openshift-ci Bot removed the needs-rebase label Nov 6, 2026

AnikaYadav1 force-pushed the get-health-cr-status branch from 715344c to 11b1122 Compare November 11, 2026 10:49

subhamkrai reviewed Nov 13, 2026

View reviewed changes

Comment thread pkg/health/cr_status.go Resolved

subhamkrai reviewed Nov 13, 2026

View reviewed changes

Comment thread cmd/odf/get/health.go Resolved

travisn requested changes Nov 13, 2026

View reviewed changes

openshift-ci Bot added the needs-rebase label Nov 14, 2026

AnikaYadav1 force-pushed the get-health-cr-status branch 2 times, most recently from d014ede to e685b0a Compare November 14, 2026 05:41

AnikaYadav1 added 4 commits November 14, 2026 11:15

Bump kubectl-rook-ceph

dee9fda

Bump github.com/rook/kubectl-rook-ceph to v0.10.0. odf get health then prints Details and Items only with --verbose. Signed-off-by: AnikaYadav1 <Anika.Yadav1@ibm.com>

AnikaYadav1 force-pushed the get-health-cr-status branch from e685b0a to dee9fda Compare November 14, 2026 05:47

openshift-ci Bot removed the needs-rebase label Nov 14, 2026

	Short: "print StorageCluster-managed CR status, or detailed pod checks with --verbose",
	Short: "print ODF CR status, or detailed status with --verbose flag",

	if f := cmd.Flag("namespace"); f != nil && f.Changed {
	if flagNamespace := cmd.Flag("namespace"); f != nil && f.Changed {

	- `health`: Print StorageCluster-managed CR status, then the cluster health report. Use `--verbose` to include Details and Items.
	- `health`: Print StorageCluster-managed CR status, then the cluster health report. Use `--verbose` for more details.

	Short: "print ODF CR status and cluster health, or include Details and Items with --verbose",
	Short: "print cluster health, and include more details with --verbose",

	clusterHealth.Flags().BoolVar(&healthVerbose, "verbose", false, "include Details and Items in the cluster health report")
	clusterHealth.Flags().BoolVar(&healthVerbose, "verbose", false, "include more details in the cluster health report")

	`odf get health` prints the status of each StorageCluster and the CRs it manages, then the cluster health report. `odf get health --verbose` prints the same sections and includes Details and Items for each check.
	`odf get health` prints the status of each StorageCluster and the CRs it manages, then the cluster health report. `odf get health --verbose` prints more details for each check.

		if !spec.namespaced {
		items = matchingStorageClients(items, sc.Name)

	s, found, err := unstructured.NestedString(obj, fields...)
	<meaningfull small name>, found, err := unstructured.NestedString(obj, fields...)

	s, found, err := unstructured.NestedString(obj, "status", "lastHeartbeat")
	<meaningful name>, found, err := unstructured.NestedString(obj, "status", "lastHeartbeat")

	Long: `Print the status of each StorageCluster and the CRs it manages, then the cluster health report (Ceph MON, MGR, and OSD checks, pod status, placement groups, and object storage). --verbose includes Details and Items for each check.`,
	Long: `Print the status of each StorageCluster and the CRs it manages, then the cluster health report (Ceph MON, MGR, and OSD checks, pod status, placement groups, and object storage).`,

Conversation

AnikaYadav1 commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AnikaYadav1 commented Oct 21, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

AnikaYadav1 commented Oct 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

subhamkrai left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AnikaYadav1 commented Oct 27, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AnikaYadav1 commented Oct 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

travisn commented Oct 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

parth-gr commented Oct 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

travisn commented Oct 29, 2026

Uh oh!

subhamkrai commented Oct 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci Bot commented Oct 30, 2026

Uh oh!

travisn left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AnikaYadav1 commented Nov 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

travisn left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AnikaYadav1 Nov 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AnikaYadav1 commented Nov 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

travisn left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AnikaYadav1 commented Oct 21, 2026 •

edited

Loading

AnikaYadav1 commented Oct 22, 2026 •

edited

Loading

AnikaYadav1 commented Oct 28, 2026 •

edited

Loading

travisn commented Oct 28, 2026 •

edited

Loading

parth-gr commented Oct 29, 2026 •

edited

Loading

subhamkrai commented Oct 30, 2026 •

edited

Loading

AnikaYadav1 commented Nov 3, 2026 •

edited

Loading

AnikaYadav1 Nov 4, 2026 •

edited

Loading

AnikaYadav1 commented Nov 4, 2026 •

edited

Loading

AnikaYadav1 Nov 6, 2026 •

edited

Loading

AnikaYadav1 Nov 6, 2026 •

edited

Loading