Merge pull request #45677 from rohennes/BZ2084113

Updates for 2084113

Author: bergerhoffer

installing/index.adoc

@@ -10,6 +10,17 @@ include::modules/installation-overview.adoc[leveloffset=+1]
 
 include::modules/installation-process.adoc[leveloffset=+2]
 
+include::modules/ipi-verifying-nodes-after-installation.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../post_installation_configuration/bare-metal-configuration.adoc#getting-the-baremetalhost-resource_post-install-bare-metal-configuration[Getting the BareMetalHost resource]
+
+* xref:../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#ipi-install-troubleshooting-following-the-installation_ipi-install-installation-workflow[Following the installation]
+
+* xref:../installing/validating-an-installation.adoc#validating-an-installation[Validating an installation]
+
 [discrete]
 === Installation scope
 

modules/installation-process.adoc

@@ -101,4 +101,7 @@ Bootstrapping a cluster involves the following steps:
 . The control plane sets up the compute nodes.
 . The control plane installs additional services in the form of a set of Operators.
 
-The result of this bootstrapping process is a fully running {product-title} cluster. The cluster then downloads and configures remaining components needed for the day-to-day operation, including the creation of compute machines in supported environments.
+The result of this bootstrapping process is a running {product-title} cluster. The cluster then downloads and configures remaining components needed for the day-to-day operation, including the creation of compute machines in supported environments.
+
+
+

modules/ipi-verifying-nodes-after-installation.adoc

@@ -0,0 +1,70 @@
+// Module included in the following assemblies:
+//
+// * installing/index.adoc
+
+:_module-type: PROCEDURE
+[id="ipi-verifying-nodes-after-installation_{context}"]
+= Verifying node state after installation
+
+[role="_abstract"]
+The {product-title} installation completes when the following installation health checks are successful:
+
+* The provisioning host can access the {product-title} web console.
+
+* All control plane nodes are ready.
+
+* All cluster Operators are available.
+
+[NOTE]
+====
+After the installation completes, the specific cluster Operators responsible for the worker nodes continuously attempt to provision all worker nodes. It can take some time before all worker nodes report as `READY`. For installations on bare metal, wait a minimum of 60 minutes before troubleshooting a worker node. For installations on all other platforms, wait a minimum of 40 minutes before troubleshooting a worker node. A `DEGRADED` state for the cluster Operators responsible for the worker nodes depends on the Operators' own resources and not on the state of the nodes.
+==== 
+
+After your installation completes, you can continue to monitor the condition of the nodes in your cluster using the following steps. 
+
+.Prerequisites
+* The installation program resolves successfully in the terminal.
+
+.Procedure
+. Show the status of all worker nodes:
+
++
+[source,terminal]
+----
+$ oc get nodes
+----
+
++
+.Example output
+[source,terminal]
+----
+NAME                           STATUS   ROLES    AGE   VERSION
+example-compute1.example.com   Ready    worker   13m   v1.21.6+bb8d50a
+example-compute2.example.com   Ready    worker   13m   v1.21.6+bb8d50a
+example-compute4.example.com   Ready    worker   14m   v1.21.6+bb8d50a
+example-control1.example.com   Ready    master   52m   v1.21.6+bb8d50a
+example-control2.example.com   Ready    master   55m   v1.21.6+bb8d50a
+example-control3.example.com   Ready    master   55m   v1.21.6+bb8d50a
+----
+
+. Show the phase of all worker machine nodes:
+
++
+[source,terminal]
+----
+$ oc get machines -A
+----
+
++
+.Example output
+[source,terminal]
+----
+NAMESPACE               NAME                           PHASE         TYPE   REGION   ZONE   AGE
+openshift-machine-api   example-zbbt6-master-0         Running                              95m
+openshift-machine-api   example-zbbt6-master-1         Running                              95m
+openshift-machine-api   example-zbbt6-master-2         Running                              95m
+openshift-machine-api   example-zbbt6-worker-0-25bhp   Running                              49m
+openshift-machine-api   example-zbbt6-worker-0-8b4c2   Running                              49m
+openshift-machine-api   example-zbbt6-worker-0-jkbqt   Running                              49m
+openshift-machine-api   example-zbbt6-worker-0-qrl5b   Running                              49m
+----