1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00
Files
openshift-docs/modules/installation-rhv-creating-bootstrap-machine.adoc
2020-12-04 16:40:59 -05:00

39 lines
1.5 KiB
Plaintext

// Module included in the following assemblies:
//
// * installing/installing_rhv/installing-rhv-user-infra.adoc
[id="installation-rhv-creating-bootstrap-machine_{context}"]
= Creating the bootstrap machine
You create a bootstrap machine by running the `bootstrap.yml` playbook. This playbook starts the bootstrap virtual machine, and passes it the `bootstrap.ign` Ignition file from the assets directory. The bootstrap node configures itself so it can serve Ignition files to the control plane nodes.
To monitor the bootstrap process, you use the console in the {rh-virtualization} Administration Portal or connect to the virtual machine by using SSH.
.Procedure
. Create the bootstrap machine:
+
[source,terminal]
----
$ ansible-playbook -i inventory.yml bootstrap.yml
----
. Connect to the bootstrap machine using a console in the Administration Portal or SSH. Replace `<bootstrap_ip>` with the bootstrap node IP address. To use SSH, enter:
+
[source,terminal]
----
$ ssh core@<boostrap.ip>
----
. Collect `bootkube.service` journald unit logs for the release image service from the bootstrap node:
+
[source,terminal]
----
[core@ocp4-lk6b4-bootstrap ~]$ journalctl -b -f -u release-image.service -u bootkube.service
----
+
[NOTE]
====
The `bootkube.service` log on the bootstrap node outputs etcd `connection refused` errors, indicating that the bootstrap server is unable to connect to etcd on master nodes. After etcd has started on each master node and the nodes have joined the cluster, the errors should stop.
====