Bootstrap VM is not pingable

A temporary bootstrap VM is created on provisioner node (also known as RU7 or compute-1-ru7) to create Red Hat OpenShift Container Platform control plane.

Message: Either bootstrap VM is not created or did not receive hostname and IP from DHCP.

Diagnostics

Note: Run all commands from the provisioner node (also known as RU7 or compute-1-ru7) as a kni user.

Run the following command on the provisioner node (also known as RU7 or compute-1-ru7) as a kni user to check whether the bootstarp VM is created:
```
sudo virsh list
```
Empty output of previous command indicates that bootstrap VM is not created. To debug further, check the log file /home/kni/clusterconfigs/.openshift_install.log for errors.
```
sudo virsh list
setlocale: No such file or directory
Id   Name   State
--------------------
```

If output from first command is not empty. Example when bootstrap VM is created.

sudo virsh list

setlocale: No such file or directory
Id   Name                          State
---------------------------------------------
1    isf-rackae4-2bztv-bootstrap   running

If VM is listed in step 3, then run the following command to connect to it and check whether it has a valid hostname assigned.
```
ping bootstrap.<subdomain>
```
Here, subdomain is your <cluster name>.<basedomain name>.
- If bootstrap is not pinging, then verify your DHCP and DNS setting for bootstrap VM.
- An IP reservation in DHCP server must be made for bootstrap VM with correct MAC address as received in TDA sheet.
- Lookup and reverse lookup records in DNS server for bootstrap VM.
- Rectify the identified problems.

Next actions

In the installation user interface, click Retry to restart the installation.