Chapter 4. Installing a cluster
4.1. Cleaning up previous installations Copy linkLink copied to clipboard!
In case of an earlier failed deployment, remove the artifacts from the failed attempt before trying to deploy OpenShift Container Platform again.
Procedure
Power off all bare-metal nodes before installing the OpenShift Container Platform cluster by using the following command:
$ ipmitool -I lanplus -U <user> -P <password> -H <management_server_ip> power offRemove all old bootstrap resources if any remain from an earlier deployment attempt by using the following script:
for i in $(sudo virsh list | tail -n +3 | grep bootstrap | awk {'print $2'}); do sudo virsh destroy $i; sudo virsh undefine $i; sudo virsh vol-delete $i --pool $i; sudo virsh vol-delete $i.ign --pool $i; sudo virsh pool-destroy $i; sudo virsh pool-undefine $i; doneDelete the artifacts that the earlier installation generated by using the following command:
$ cd ; /bin/rm -rf auth/ bootstrap.ign master.ign worker.ign metadata.json \ .openshift_install.log .openshift_install_state.jsonRe-create the OpenShift Container Platform manifests by using the following command:
$ ./openshift-baremetal-install --dir ~/clusterconfigs create manifests
4.2. Deploying the cluster via the OpenShift Container Platform installer Copy linkLink copied to clipboard!
Run the OpenShift Container Platform installer:
$ ./openshift-baremetal-install --dir ~/clusterconfigs --log-level debug create cluster
4.3. Following the progress of the installation Copy linkLink copied to clipboard!
During the deployment process, you can check the installation’s overall status by issuing the tail command to the .openshift_install.log log file in the install directory folder:
$ tail -f /path/to/install-dir/.openshift_install.log
4.4. Verifying static IP address configuration Copy linkLink copied to clipboard!
If the DHCP reservation for a cluster node specifies an infinite lease, after the installer successfully provisions the node, the dispatcher script checks the node’s network configuration. If the script determines that the network configuration contains an infinite DHCP lease, it creates a new connection using the IP address of the DHCP lease as a static IP address.
The dispatcher script might run on successfully provisioned nodes while the provisioning of other nodes in the cluster is ongoing.
Verify the network configuration is working properly.
Procedure
- Check the network interface configuration on the node.
- Turn off the DHCP server and reboot the OpenShift Container Platform node and ensure that the network configuration works properly.