Skip to content

Commit 70f7982

Browse files
authored
Merge pull request #43025 from JoeAldinger/BZ-2013110
BZ-2013110:removes hostname from command copy button
2 parents 9a12c39 + 16986c8 commit 70f7982

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

modules/dr-restoring-cluster-state.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -57,14 +57,14 @@ It is not required to manually stop the pods on the recovery host. The recovery
5757
+
5858
[source,terminal]
5959
----
60-
[core@ip-10-0-154-194 ~]$ sudo mv /etc/kubernetes/manifests/etcd-pod.yaml /tmp
60+
$ sudo mv /etc/kubernetes/manifests/etcd-pod.yaml /tmp
6161
----
6262

6363
.. Verify that the etcd pods are stopped.
6464
+
6565
[source,terminal]
6666
----
67-
[core@ip-10-0-154-194 ~]$ sudo crictl ps | grep etcd | grep -v operator
67+
$ sudo crictl ps | grep etcd | grep -v operator
6868
----
6969
+
7070
The output of this command should be empty. If it is not empty, wait a few minutes and check again.
@@ -73,14 +73,14 @@ The output of this command should be empty. If it is not empty, wait a few minut
7373
+
7474
[source,terminal]
7575
----
76-
[core@ip-10-0-154-194 ~]$ sudo mv /etc/kubernetes/manifests/kube-apiserver-pod.yaml /tmp
76+
$ sudo mv /etc/kubernetes/manifests/kube-apiserver-pod.yaml /tmp
7777
----
7878

7979
.. Verify that the Kubernetes API server pods are stopped.
8080
+
8181
[source,terminal]
8282
----
83-
[core@ip-10-0-154-194 ~]$ sudo crictl ps | grep kube-apiserver | grep -v operator
83+
$ sudo crictl ps | grep kube-apiserver | grep -v operator
8484
----
8585
+
8686
The output of this command should be empty. If it is not empty, wait a few minutes and check again.
@@ -89,7 +89,7 @@ The output of this command should be empty. If it is not empty, wait a few minut
8989
+
9090
[source,terminal]
9191
----
92-
[core@ip-10-0-154-194 ~]$ sudo mv /var/lib/etcd/ /tmp
92+
$ sudo mv /var/lib/etcd/ /tmp
9393
----
9494

9595
.. Repeat this step on each of the other control plane hosts that is not the recovery host.
@@ -108,7 +108,7 @@ You can check whether the proxy is enabled by reviewing the output of `oc get pr
108108
+
109109
[source,terminal]
110110
----
111-
[core@ip-10-0-143-125 ~]$ sudo -E /usr/local/bin/cluster-restore.sh /home/core/backup
111+
$ sudo -E /usr/local/bin/cluster-restore.sh /home/core/backup
112112
----
113113
+
114114
.Example script output
@@ -146,7 +146,7 @@ static-pod-resources/kube-scheduler-pod-8/kube-scheduler-pod.yaml
146146
+
147147
[source,terminal]
148148
----
149-
[core@ip-10-0-143-125 ~]$ sudo systemctl restart kubelet.service
149+
$ sudo systemctl restart kubelet.service
150150
----
151151

152152
.. Repeat this step on all other control plane hosts.
@@ -201,7 +201,7 @@ $ oc adm certificate approve <csr_name>
201201
+
202202
[source,terminal]
203203
----
204-
[core@ip-10-0-143-125 ~]$ sudo crictl ps | grep etcd | grep -v operator
204+
$ sudo crictl ps | grep etcd | grep -v operator
205205
----
206206
+
207207
.Example output
@@ -214,7 +214,7 @@ $ oc adm certificate approve <csr_name>
214214
+
215215
[source,terminal]
216216
----
217-
[core@ip-10-0-143-125 ~]$ oc get pods -n openshift-etcd | grep -v etcd-quorum-guard | grep etcd
217+
$ oc get pods -n openshift-etcd | grep -v etcd-quorum-guard | grep etcd
218218
----
219219
+
220220
[NOTE]

0 commit comments

Comments
 (0)