From c45fe6be9825c3d59613691e7ddfb911b8c57782 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Tue, 19 May 2026 19:50:21 +0200 Subject: [PATCH] docs: fix kubectl exec commands in the DR troubleshooting guide kubectl exec requires a double dash ('--') between the pod name and the command to be executed. The disaster recovery troubleshooting guide missed those characters in two places. This change fixes the guide by adding the missing double dashes Signed-off-by: Michael Adam (cherry picked from commit ef7e80bedcd08719b94bff198c51bf06c72ec31d) --- Documentation/Troubleshooting/disaster-recovery.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/Troubleshooting/disaster-recovery.md b/Documentation/Troubleshooting/disaster-recovery.md index eefc08532..971ed8421 100644 --- a/Documentation/Troubleshooting/disaster-recovery.md +++ b/Documentation/Troubleshooting/disaster-recovery.md @@ -180,7 +180,7 @@ Assuming `dataHostPathData` is `/var/lib/rook`, and the `CephCluster` trying to 7. Install Rook Ceph in the new Kubernetes cluster. 8. Watch the operator logs with `kubectl -n rook-ceph logs -f rook-ceph-operator-xxxxxxx`, and wait until the orchestration has settled. 9. **STATE**: Now the cluster will have `rook-ceph-mon-a`, `rook-ceph-mgr-a`, and all the auxiliary pods up and running, and zero (hopefully) `rook-ceph-osd-ID-xxxxxx` running. `ceph -s` output should report 1 mon, 1 mgr running, and all of the OSDs down, all PGs are in `unknown` state. Rook should not start any OSD daemon since all devices belongs to the old cluster (which have a different `fsid`). -10. Run `kubectl -n rook-ceph exec -it rook-ceph-mon-a-xxxxxxxx bash` to enter the `rook-ceph-mon-a` pod, +10. Run `kubectl -n rook-ceph exec -it rook-ceph-mon-a-xxxxxxxx -- bash` to enter the `rook-ceph-mon-a` pod, ```console mon-a# cat /etc/ceph/keyring-store/keyring # save this keyring content for later use @@ -233,7 +233,7 @@ Assuming `dataHostPathData` is `/var/lib/rook`, and the `CephCluster` trying to 17. Bring the Rook Ceph operator back online by running `kubectl -n rook-ceph edit deploy/rook-ceph-operator` and set `replicas` to `1`. 18. Watch the operator logs with `kubectl -n rook-ceph logs -f rook-ceph-operator-xxxxxxx`, and wait until the orchestration has settled. 19. **STATE**: Now the new cluster should be up and running with authentication disabled. `ceph -s` should report 1 mon & 1 mgr & all of the OSDs up and running, and all PGs in either `active` or `degraded` state. -20. Run `kubectl -n rook-ceph exec -it rook-ceph-tools-XXXXXXX bash` to enter tools pod: +20. Run `kubectl -n rook-ceph exec -it rook-ceph-tools-XXXXXXX -- bash` to enter tools pod: ```console vi key