Updates for ironic-api and ironic-conductor

Author: abhatt-rh

modules/ipi-install-troubleshooting-bootstrap-vm-cannot-boot.adoc

@@ -12,8 +12,7 @@ During the deployment, it is possible for the bootstrap VM to fail to boot the c
 
 To verify the issue, there are three containers related to `ironic`:
 
-* `ironic-api`
-* `ironic-conductor`
+* `ironic`
 * `ironic-inspector`
 
 .Procedure
@@ -32,7 +31,7 @@ $ ssh [email protected]
 [core@localhost ~]$ sudo podman logs -f <container-name>
 ----
 +
-Replace `<container-name>` with one of `ironic-api`, `ironic-conductor`, or `ironic-inspector`. If you encounter an issue where the control plane nodes are not booting up via PXE, check the `ironic-conductor` pod. The `ironic-conductor` pod contains the most detail about the attempt to boot the cluster nodes, because it attempts to log in to the node over IPMI.
+Replace `<container-name>` with one of `ironic` or `ironic-inspector`. If you encounter an issue where the control plane nodes are not booting up from PXE, check the `ironic` pod. The `ironic` pod contains information about the attempt to boot the cluster nodes, because it attempts to log in to the node over IPMI.
 
 .Potential reason
 The cluster nodes might be in the `ON` state when deployment started.

modules/ipi-install-troubleshooting-bootstrap-vm-inspecting-logs.adoc

@@ -54,9 +54,9 @@ If the bootstrap VM cannot access the URL to the images, use the `curl` command
 [core@localhost ~]$ sudo podman ps
 ----
 
-. If there are issues with the pods, check the logs of the containers with issues. To check the log of the `ironic-api`, execute the following:
+. If there are issues with the pods, check the logs of the containers with issues. To check the logs of the `ironic` service, run the following command:
 +
 [source,terminal]
 ----
-[core@localhost ~]$ sudo podman logs <ironic-api>
+[core@localhost ~]$ sudo podman logs ironic
 ----