How do I see what is happening with my UPI install.

Environment

• Red Hat OpenShift Container Platform 4.x

Issue

• When doing a UBI install the 'openshift-installer' binary tells me INFO Waiting up to 30m0s for the Kubernetes API at https://api.cluster_name.sub_domain.domain:6443... but I can't tell what if anything is happening.

Root Cause

As the install is happening on remote systems, some form of SSH access will be needed (to these systems) in order to watch what progress is being made.

You need to ensure that ssh_key access (defined by ignition or ignition config) works prior to trying any diagnostics steps.

Using the journal_shim to monitor a UPI install is not possible (like it is with IPI), because local tls certificates are not created (by the openshift-install binary) so that you can talk, directly to the api endpoints.

Diagnostic Steps

You can watch the install progress in 3 ways:

1. Review the local, .openshift_install.log for any messages or information.

   tail -f .openshift_install.log
   

2. Monitory the bootstrap system.

   ssh core@bootstrap.cluster_name.sub_domain.domain journalctl -b -f -u bootkube.service
   

3. Monitor one or all of your masters with the following:

   ssh core@master-N.cluster_name.sub_domain.domain journalctl -b -f -u kubelet -u crio
   

   • You might also need to look at the logs from key containers. You can list these key containers with: sudo crictl ps -a. You can then watch or get the logs for each container with sudo crictl logs -f CONTAINER-ID

     • For bulk collection run the following:

     $ sudo tail -f /var/log/containers/*
     

Additional details on troubleshooting 4.x UPI Installs can be found in the 4.x UPI Troubleshooting Guide

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.