Skip to content

Commit 47e8338

Browse files
authored
Merge pull request #56658 from subhtk/OCP7145
OCPBUG#7145: Deleted a step in 'Restoring to a previous cluster state'
2 parents 49df53f + 4985555 commit 47e8338

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

modules/dr-restoring-cluster-state.adoc

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,6 @@ $ sudo mv /var/lib/etcd/ /tmp
101101

102102
. Access the recovery control plane host.
103103

104-
105104
. If the cluster-wide proxy is enabled, be sure that you have exported the `NO_PROXY`, `HTTP_PROXY`, and `HTTPS_PROXY` environment variables.
106105
+
107106
[TIP]
@@ -223,7 +222,7 @@ csr-zhhhp 3m8s kubernetes.io/kube-apiserver-client-kubelet system:servicea
223222
----
224223
<1> A pending kubelet service CSR (for user-provisioned installations).
225224
<2> A pending `node-bootstrapper` CSR.
226-
+
225+
227226
.. Review the details of a CSR to verify that it is valid:
228227
+
229228
[source,terminal]
@@ -246,7 +245,6 @@ $ oc adm certificate approve <csr_name>
246245
$ oc adm certificate approve <csr_name>
247246
----
248247

249-
250248
. Verify that the single member control plane has started successfully.
251249

252250
.. From the recovery host, verify that the etcd container is running.
@@ -288,13 +286,12 @@ etcd-ip-10-0-143-125.ec2.internal 1/1 Running 1
288286
+
289287
If the status is `Pending`, or the output lists more than one running etcd pod, wait a few minutes and check again.
290288

291-
.. Repeat this step for each lost control plane host that is not the recovery host.
292289
+
293290
[NOTE]
294291
====
295292
Perform the following step only if you are using `OVNKubernetes` network plugin.
296293
====
297-
+
294+
298295
. Delete the node objects that are associated with control plane hosts that are not the recovery control plane host.
299296
+
300297
[source,terminal]
@@ -319,7 +316,7 @@ Validating and mutating admission webhooks can reject pods. If you add any addit
319316

320317
Alternatively, you can temporarily set the `failurePolicy` to `Ignore` while restoring the cluster state. After the cluster state is restored successfully, you can set the `failurePolicy` to `Fail`.
321318
====
322-
+
319+
323320
.. Remove the northbound database (nbdb) and southbound database (sbdb). Access the recovery host and the remaining control plane nodes by using Secure Shell (SSH) and run the following command:
324321
+
325322
[source,terminal]

0 commit comments

Comments
 (0)