mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
46 lines
1.5 KiB
Plaintext
46 lines
1.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
//installing/installing_bare_metal/ipi/ipi-install-troubleshooting.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="ipi-install-troubleshooting-bootstrap-vm-cannot-boot_{context}"]
|
|
= Bootstrap VM cannot boot up the cluster nodes
|
|
|
|
During the deployment, it is possible for the bootstrap VM to fail to boot the cluster nodes, which prevents the VM from provisioning the nodes with the {op-system} image. This scenario can arise due to:
|
|
|
|
* A problem with the `install-config.yaml` file.
|
|
* Issues with out-of-band network access when using the baremetal network.
|
|
|
|
To verify the issue, there are three containers related to `ironic`:
|
|
|
|
* `ironic`
|
|
* `ironic-inspector`
|
|
|
|
.Procedure
|
|
|
|
. Log in to the bootstrap VM:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ ssh core@172.22.0.2
|
|
----
|
|
|
|
. To check the container logs, execute the following:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
[core@localhost ~]$ sudo podman logs -f <container_name>
|
|
----
|
|
+
|
|
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.
|
|
|
|
.Solution
|
|
Power off the {product-title} cluster nodes before you begin the
|
|
installation over IPMI:
|
|
|
|
[source,terminal]
|
|
----
|
|
$ ipmitool -I lanplus -U root -P <password> -H <out_of_band_ip> power off
|
|
---- |