From 2d8b063fc8016473db6cfe1805276f004a3d4e2f Mon Sep 17 00:00:00 2001 From: Laura Hinson Date: Wed, 3 Sep 2025 11:54:27 -0400 Subject: [PATCH] Fixing incorrect command in etcd docs --- modules/restore-identify-unhealthy-etcd-member.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/restore-identify-unhealthy-etcd-member.adoc b/modules/restore-identify-unhealthy-etcd-member.adoc index 2cf7a828e0..21a40930a8 100644 --- a/modules/restore-identify-unhealthy-etcd-member.adoc +++ b/modules/restore-identify-unhealthy-etcd-member.adoc @@ -18,7 +18,7 @@ You can identify if your cluster has an unhealthy etcd member. + [source,terminal] ---- -$ oc get etcd -o=jsonpath='{range .items[0].status.conditions[?(@.type=="EtcdMembersAvailable")]}{.message}{"\n"}' +$ oc get etcd -o=jsonpath='{range .items[0].status.conditions[?(@.type=="EtcdMembersAvailable")]}{.message}{"\n"}{end}' ---- . Review the output: