[OSDOCS-20226]: Adding info about approvign CSRs

Author: lahinson

modules/graceful-restart.adoc

@@ -6,6 +6,7 @@
 [id="graceful-restart_{context}"]
 = Restarting the cluster
 
+[role="_abstract"]
 You can restart your cluster after it has been shut down gracefully.
 
 .Prerequisites
@@ -127,7 +128,7 @@ ip-10-0-182-134.ec2.internal   Ready    worker   64m   v1.35.0
 ip-10-0-250-100.ec2.internal   Ready    worker   64m   v1.35.0
 ----
 
-. If the compute nodes are _not_ ready, then check whether there are any pending certificate signing requests (CSRs) that must be approved.
+. If the compute nodes are _not_ ready, then check whether there are any pending CSRs that must be approved.
 
 .. Get the list of current CSRs:
 +
@@ -184,7 +185,7 @@ $ oc adm certificate approve <csr_name>
 $ for node in $(oc get nodes -o jsonpath='{.items[*].metadata.name}'); do echo ${node} ; oc adm uncordon ${node} ; done
 ----
 
-. Verify that the cluster started properly.
+.Verification
 
 .. Check that there are no degraded cluster Operators.
 +
@@ -229,4 +230,20 @@ ip-10-0-211-16.ec2.internal    Ready    control-plane,master   82m   v1.35.0
 ip-10-0-250-100.ec2.internal   Ready    worker                 69m   v1.35.0
 ----
 +
-If the cluster did not start properly, you might need to restore your cluster using an etcd backup. For more information, see "Restoring to a previous cluster state".
+If the cluster did not start properly, you might need to restore your cluster by using an etcd backup. For more information, see "Restoring to a previous cluster state".
+
+. If a CSR is not approved after the restart, you can investigate possible issues by checking the logs:
++
+.. Check the Machine Approver logs by entering the following command:
++
+[source,terminal]
+----
+$ oc logs -n openshift-cluster-machine-approver -l app=machine-approver
+----
++
+.. Check the Kube Controller Manager logs by entering the following command:
++
+[source,terminal]
+----
+$ oc logs -n openshift-kube-controller-manager -l app=kube-controller-manager
+----