Merge pull request #74785 from dfitzmau/OCPBUGS-30076-av

skrthomas · web-flow · commit 1ffa2bd0173e · 2024-04-18T09:09:46.000-04:00
OCPBUGS-30076-av
diff --git a/installing/installing_oci/installing-oci-assisted-installer.adoc b/installing/installing_oci/installing-oci-assisted-installer.adoc
@@ -14,7 +14,7 @@ include::modules/installing-oci-about-assisted-installer.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform/2024[{ai-full} for {product-title}]
+* link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform/[{ai-full} for {product-title}]
 * xref:../../installing/installing_platform_agnostic/installing-platform-agnostic.adoc#cluster-entitlements_installing-platform-agnostic[Internet access for {product-title}]
 * link:https://docs.oracle.com/en-us/iaas/Content/Block/Concepts/blockvolumeperformance.htm#vpus[Volume Performance Units (Oracle documentation)]
 
@@ -52,6 +52,6 @@ include::modules/installing-troubleshooting-assisted-installer-oci.adoc[leveloff
 .Additional resources
 
 * xref:../../installing/installing_on_prem_assisted/installing-on-prem-assisted.adoc#using-the-assisted-installer_installing-on-prem-assisted[Installing an on-premise cluster using the {ai-full}]
-* link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform/2022/html-single/assisted_installer_for_openshift_container_platform/index[{ai-full} for {product-title}]
+* link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform/[{ai-full} for {product-title}]
 * link:https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Concepts/resourcemanager.htm#ways[Ways to access Resource Manager (Oracle documentation)]
 * link:https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Tasks/create-stack.htm#top[Creating a stack (Oracle documentation)]
diff --git a/modules/complete-assisted-installer-oci.adoc b/modules/complete-assisted-installer-oci.adoc
@@ -16,14 +16,14 @@ After you provision {oci-first} resources and upload {product-title} custom mani
 
 . From the link:https://console.redhat.com/[Red Hat Hybrid Cloud Console] web console, go to the *Host discovery* page.
 
-.Under the *Role* column, select either `Control plane node` or `Worker` for each targeted hostname.
+. Under the *Role* column, select either `Control plane node` or `Worker` for each targeted hostname.
 +
 [IMPORTANT]
 ====
 Before, you can continue to the next steps, wait for each node to reach the `Ready` status.
 ====
 
-. Accept the default settings for the *Storage* and *Networking* steps, and then Click *Next*.
+. Accept the default settings for the *Storage* and *Networking* steps, and then click *Next*.
 
 . On the *Custom manifests* page, in the *Folder* field, select `manifest`. This is the {ai-full} folder where you want to save the custom manifest file.
 .. In the *File name* field, enter a value such as `oci-ccm.yml`.
diff --git a/modules/creating-config-files-cluster-install-oci.adoc b/modules/creating-config-files-cluster-install-oci.adoc
@@ -103,7 +103,7 @@ The {oci-ccm} manifest are required for deploying the {oci-ccm} during cluster i
 You must change the secret `oci-cloud-controller-manager` defined in the link:https://github.com/oracle-quickstart/oci-openshift/blob/main/custom_manifests/manifests/oci-ccm.yml[`oci-ccm.yml`] configuration file to match your organization's region, compartment {ocid}, VCN {ocid}, and the subnet {ocid} from the load balancer.
 ====
 
-. Use the Agent-based Installer to generate a minimal ISO image, which excludes the `rootfs` image, by entering the following command in your {product-title} CLI. You can use this image later in the process to boot all your cluster’s nodes.
+. Use the Agent-based Installer to generate a minimal ISO image, which excludes the rootfs image, by entering the following command in your {product-title} CLI. You can use this image later in the process to boot all your cluster’s nodes.
 +
 [source,terminal]
 ----
@@ -118,7 +118,7 @@ The command also completes the following actions:
 +
 [IMPORTANT]
 ====
-The Agent-based Installer uses {op-system-first}. The `rootfs` image, which is mentioned in a later listed item,  is required for booting, recovering, and repairing your operating system.
+The Agent-based Installer uses {op-system-first}. The rootfs image, which is mentioned in a later listed item,  is required for booting, recovering, and repairing your operating system.
 ====
 
 . Configure the `agent-config.yaml` configuration file to meet your organization’s requirements.
@@ -137,22 +137,22 @@ bootArtifactsBaseURL: <server_URL> <4>
 <1> The cluster name that you specified in your DNS record.
 <2> The namespace of your cluster on {product-title}.
 <3> If you use IPv4 as the network IP address format, ensure that you set the `rendezvousIP` parameter to an IPv4 address that the VCN’s Classless Inter-Domain Routing (CIDR) method allocates on your network. Also ensure that at least one instance from the pool of instances that you booted with the ISO matches the IP address value you set for `rendezvousIP`.
-<4> The URL of the server where you want to upload the `rootfs` image.
+<4> The URL of the server where you want to upload the rootfs image.
 
 . Apply one of the following two updates to your `agent-config.yaml` configuration file:
 +
-* For a disconnected network:  After you run the command to generate a minimal ISO Image, the Agent-based installer saves the `rootfs` image into the `./<installation_directory>/boot-artifacts` directory on your local system. Use your preferred web server, such as any Hypertext Transfer Protocol daemon (`httpd`), to upload `rootfs` to the location stated in the `bootArtifactsBaseURL` parameter in the `agent-config.yaml` configuration file.
+* For a disconnected network:  After you run the command to generate a minimal ISO Image, the Agent-based installer saves the rootfs image into the `./<installation_directory>/boot-artifacts` directory on your local system. Use your preferred web server, such as any Hypertext Transfer Protocol daemon (`httpd`), to upload rootfs to the location stated in the `bootArtifactsBaseURL` parameter in the `agent-config.yaml` configuration file.
 +
-For example, if the `bootArtifactsBaseURL` parameter states \http://192.168.122.20, you would upload the generated `rootfs` image to this location, so that the Agent-based installer can access the image from \http://192.168.122.20/agent.x86_64-rootfs.img. After the Agent-based installer boots the minimal ISO for the external platform, the Agent-based Installer downloads the `rootfs` image from the \http://192.168.122.20/agent.x86_64-rootfs.img location into the system memory.
+For example, if the `bootArtifactsBaseURL` parameter states `\http://192.168.122.20`, you would upload the generated rootfs image to this location, so that the Agent-based installer can access the image from `\http://192.168.122.20/agent.x86_64-rootfs.img`. After the Agent-based installer boots the minimal ISO for the external platform, the Agent-based Installer downloads the rootfs image from the `\http://192.168.122.20/agent.x86_64-rootfs.img` location into the system memory.
 +
 [NOTE]
 ====
-The Agent-based Installer also adds the value of the `bootArtifactsBaseURL` to the minimal ISO Image’s configuration, so that when the Operator boots a cluster’s node, the Agent-based Installer  downloads the `rootfs` image into system memory.
+The Agent-based Installer also adds the value of the `bootArtifactsBaseURL` to the minimal ISO Image’s configuration, so that when the Operator boots a cluster’s node, the Agent-based Installer downloads the rootfs image into system memory.
 ====
 +
-* For a connected network: You do not need to specify the `bootArtifactsBaseURL` parameter in the `agent-config.yaml` configuration file, because the Agent-based Installer, by default, reads the a `rootfs` URL location from \https://rhcos.mirror.openshift.com. After the Agent-based Installer  boots the minimal ISO for the external platform, the Agent-based Installer then downloads the `rootfs` file into your system’s memory from the default {op-system} URL.
+* For a connected network: You do not need to specify the `bootArtifactsBaseURL` parameter in the `agent-config.yaml` configuration file. The default behavior of the Agent-based Installer reads the rootfs URL location from `\https://rhcos.mirror.openshift.com`. After the Agent-based Installer boots the minimal ISO for the external platform, the Agent-based Installer then downloads the rootfs file into your system’s memory from the default {op-system} URL.
 +
 [IMPORTANT]
 ====
-Consider that the full ISO image, which is in excess of `1` GB, includes the `rootfs` image and the image is considerably larger than the minimal ISO Image, which is typical less than `150` MB.
+Consider that the full ISO image, which is in excess of `1` GB, includes the rootfs image. The image is larger than the minimal ISO Image, which is typically less than `150` MB.
 ====
