mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
100 lines
3.5 KiB
Plaintext
100 lines
3.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_{context}"]
|
|
|
|
= Troubleshooting bootstrap VM issues
|
|
|
|
The {product-title} installation program spawns a bootstrap node virtual machine, which handles provisioning the {product-title} cluster nodes.
|
|
|
|
.Procedure
|
|
|
|
. About 10 to 15 minutes after triggering the installation program, check to ensure the bootstrap VM is operational using the `virsh` command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ sudo virsh list
|
|
----
|
|
+
|
|
[source,terminal]
|
|
----
|
|
Id Name State
|
|
--------------------------------------------
|
|
12 openshift-xf6fq-bootstrap running
|
|
----
|
|
+
|
|
[NOTE]
|
|
====
|
|
The name of the bootstrap VM is always the cluster name followed by a random set of characters and ending in the word "bootstrap."
|
|
====
|
|
|
|
. If the bootstrap VM is not running after 10-15 minutes, verify `libvirtd` is running on the system by executing the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ systemctl status libvirtd
|
|
----
|
|
+
|
|
[source,terminal]
|
|
----
|
|
● libvirtd.service - Virtualization daemon
|
|
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
|
|
Active: active (running) since Tue 2020-03-03 21:21:07 UTC; 3 weeks 5 days ago
|
|
Docs: man:libvirtd(8)
|
|
https://libvirt.org
|
|
Main PID: 9850 (libvirtd)
|
|
Tasks: 20 (limit: 32768)
|
|
Memory: 74.8M
|
|
CGroup: /system.slice/libvirtd.service
|
|
├─ 9850 /usr/sbin/libvirtd
|
|
----
|
|
+
|
|
If the bootstrap VM is operational, log in to it.
|
|
|
|
. Use the `virsh console` command to find the IP address of the bootstrap VM:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ sudo virsh console example.com
|
|
----
|
|
+
|
|
[source,terminal]
|
|
----
|
|
Connected to domain example.com
|
|
Escape character is ^]
|
|
Red Hat Enterprise Linux CoreOS 43.81.202001142154.0 (Ootpa) 4.3
|
|
SSH host key: SHA256:BRWJktXZgQQRY5zjuAV0IKZ4WM7i4TiUyMVanqu9Pqg (ED25519)
|
|
SSH host key: SHA256:7+iKGA7VtG5szmk2jB5gl/5EZ+SNcJ3a2g23o0lnIio (ECDSA)
|
|
SSH host key: SHA256:DH5VWhvhvagOTaLsYiVNse9ca+ZSW/30OOMed8rIGOc (RSA)
|
|
ens3: fd35:919d:4042:2:c7ed:9a9f:a9ec:7
|
|
ens4: 172.22.0.2 fe80::1d05:e52e:be5d:263f
|
|
localhost login:
|
|
----
|
|
+
|
|
[IMPORTANT]
|
|
====
|
|
When deploying an {product-title} cluster without the `provisioning` network, you must use a public IP address and not a private IP address like `172.22.0.2`.
|
|
====
|
|
|
|
. After you obtain the IP address, log in to the bootstrap VM using the `ssh` command:
|
|
+
|
|
[NOTE]
|
|
====
|
|
In the console output of the previous step, you can use the IPv6 IP address provided by `ens3` or the IPv4 IP provided by `ens4`.
|
|
====
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ ssh core@172.22.0.2
|
|
----
|
|
|
|
If you are not successful logging in to the bootstrap VM, you have likely encountered one of the following scenarios:
|
|
|
|
* You cannot reach the `172.22.0.0/24` network. Verify the network connectivity between the provisioner and the `provisioning` network bridge. This issue might occur if you are using a `provisioning` network.
|
|
|
|
* You cannot reach the bootstrap VM through the public network. When attempting to SSH via `baremetal` network, verify connectivity on the
|
|
`provisioner` host specifically around the `baremetal` network bridge.
|
|
|
|
* You encountered `Permission denied (publickey,password,keyboard-interactive)`. When attempting to access the bootstrap VM, a `Permission denied` error might occur. Verify that the SSH key for the user attempting to log in to the VM is set within the `install-config.yaml` file. |