Merge pull request #81522 from johnwilkins/HCIDOCS-413

HCIDOCS-413: IPI install no longer requires disk reformat

Author: ShaunaDiaz

_topic_maps/_topic_map.yml

@@ -415,12 +415,12 @@ Topics:
     File: ipi-install-installation-workflow
   - Name: Installing a cluster
     File: ipi-install-installing-a-cluster
+  - Name: Troubleshooting the installation
+    File: ipi-install-troubleshooting
   - Name: Postinstallation configuration
     File: ipi-install-post-installation-configuration
   - Name: Expanding the cluster
     File: ipi-install-expanding-the-cluster
-  - Name: Troubleshooting
-    File: ipi-install-troubleshooting
 - Name: Installing IBM Cloud Bare Metal (Classic)
   Dir: installing_ibm_cloud
   Distros: openshift-origin,openshift-enterprise

installing/installing_bare_metal_ipi/ipi-install-installing-a-cluster.adoc

@@ -6,6 +6,9 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+// Cleaning up previous installations.
+include::modules/ipi-install-troubleshooting-cleaning-up-previous-installations.adoc[leveloffset=+1]
+
 // Deploying the cluster via the {product-title} installer
 include::modules/ipi-install-deploying-the-cluster-via-the-openshift-installer.adoc[leveloffset=+1]
 
@@ -15,11 +18,9 @@ include::modules/ipi-install-following-the-progress-of-the-installation.adoc[lev
 // Verifying static IP address configuration
 include::modules/ipi-install-verifying-static-ip-address-configuration.adoc[leveloffset=+1]
 
-// Preparing to reinstall a cluster on bare metal
-include::modules/ipi-preparing-reinstall-cluster-bare-metal.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 [id="additional-resources_creating_manifest_ignition"]
 == Additional resources
-* xref:../../installing/installing_bare_metal/installing-bare-metal.adoc#installation-user-infra-generate-k8s-manifest-ignition_installing-bare-metal[Creating the Kubernetes manifest and Ignition config files]
+
 * xref:../../updating/understanding_updates/understanding-update-channels-release.adoc#understanding-update-channels-releases[Understanding update channels and releases]

installing/installing_bare_metal_ipi/ipi-install-troubleshooting.adoc

@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="ipi-install-troubleshooting"]
-= Troubleshooting
+= Troubleshooting the installation
 include::_attributes/common-attributes.adoc[]
 :context: ipi-install-troubleshooting
 
@@ -9,19 +9,19 @@ toc::[]
 
 == Troubleshooting the installation program workflow
 
-Prior to troubleshooting the installation environment, it is critical to understand the overall flow of the installer-provisioned installation on bare metal. The diagrams below provide a troubleshooting flow with a step-by-step breakdown for the environment.
+Before troubleshooting the installation environment, it is critical to understand the overall flow of the installer-provisioned installation on bare metal. The following diagrams illustrate a troubleshooting flow with a step-by-step breakdown for the environment.
 
 image:flow1.png[Flow-Diagram-1]
 
-_Workflow 1 of 4_ illustrates a troubleshooting workflow when the `install-config.yaml` file has errors or the {op-system-first} images are inaccessible. Troubleshooting suggestions can be found at xref:ipi-install-troubleshooting-install-config_ipi-install-troubleshooting[Troubleshooting `install-config.yaml`].
+_Workflow 1 of 4_ illustrates a troubleshooting workflow when the `install-config.yaml` file has errors or the {op-system-first} images are inaccessible. See  xref:ipi-install-troubleshooting-install-config_ipi-install-troubleshooting[Troubleshooting `install-config.yaml`] for troubleshooting suggestions.
 
 image:flow2.png[Flow-Diagram-2]
 
 _Workflow 2 of 4_ illustrates a troubleshooting workflow for xref:ipi-install-troubleshooting-bootstrap-vm_ipi-install-troubleshooting[ bootstrap VM issues], xref:ipi-install-troubleshooting-bootstrap-vm-cannot-boot_ipi-install-troubleshooting[ bootstrap VMs that cannot boot up the cluster nodes], and  xref:ipi-install-troubleshooting-bootstrap-vm-inspecting-logs_ipi-install-troubleshooting[ inspecting logs]. When installing an {product-title} cluster without the `provisioning` network, this workflow does not apply.
 
 image:flow3.png[Flow-Diagram-3]
 
-_Workflow 3 of 4_ illustrates a troubleshooting workflow for xref:ipi-install-troubleshooting-cluster-nodes-will-not-pxe_ipi-install-troubleshooting[ cluster nodes that will not PXE boot]. If installing using RedFish Virtual Media, each node must meet minimum firmware requirements for the installation program to deploy the node. See *Firmware requirements for installing with virtual media* in the *Prerequisites* section for additional details.
+_Workflow 3 of 4_ illustrates a troubleshooting workflow for xref:ipi-install-troubleshooting-cluster-nodes-will-not-pxe_ipi-install-troubleshooting[cluster nodes that will not PXE boot]. If installing using Redfish virtual media, each node must meet minimum firmware requirements for the installation program to deploy the node. See *Firmware requirements for installing with virtual media* in the *Prerequisites* section for additional details.
 
 image:flow4.png[Flow-Diagram-4]
 

modules/ipi-install-troubleshooting-cleaning-up-previous-installations.adoc

@@ -6,20 +6,20 @@
 [id="ipi-install-troubleshooting-cleaning-up-previous-installations_{context}"]
 = Cleaning up previous installations
 
-In the event of a previous failed deployment, remove the artifacts from the failed attempt before attempting to deploy {product-title} again.
+In case of an earlier failed deployment, remove the artifacts from the failed attempt before trying to deploy {product-title} again.
 
 .Procedure
 
-. Power off all bare metal nodes prior to installing the {product-title} cluster:
+. Power off all bare-metal nodes before installing the {product-title} cluster by using the following command:
 +
 [source,terminal]
 ----
 $ ipmitool -I lanplus -U <user> -P <password> -H <management_server_ip> power off
 ----
 
-. Remove all old bootstrap resources if any are left over from a previous deployment attempt:
+. Remove all old bootstrap resources if any remain from an earlier deployment attempt by using the following script:
 +
-[source,terminal]
+[source,bash]
 ----
 for i in $(sudo virsh list | tail -n +3 | grep bootstrap | awk {'print $2'});
 do
@@ -31,3 +31,18 @@ do
   sudo virsh pool-undefine $i;
 done
 ----
+
+. Delete the artifacts that the earlier installation generated by using the following command:
++
+[source,terminal]
+----
+$ cd ; /bin/rm -rf auth/ bootstrap.ign master.ign worker.ign metadata.json \
+.openshift_install.log .openshift_install_state.json
+----
+
+. Re-create the {product-title} manifests by using the following command:
++
+[source,terminal]
+----
+$ ./openshift-baremetal-install --dir ~/clusterconfigs create manifests
+----