Chapter 1. Gathering installation logs

Procedure

1. Generate the commands that are required to obtain the installation logs from the bootstrap and control plane machines:

   • If you used installer-provisioned infrastructure, run the following command:

     $ ./openshift-install gather bootstrap --dir=<directory> 1

     1

     installation_directory is the directory you stored the OpenShift Container Platform definition files that the installation program creates.

     For installer-provisioned infrastructure, the installation program stores information about the cluster, so you do not specify the host names or IP addresses

   • If you used infrastructure that you provisioned yourself, run the following command:

     $ ./openshift-install gather bootstrap --dir=<directory> \ 1
         --bootstrap <bootstrap_address> \ 2
         --master <master_1_address> \ 3
         --master <master_2_address> \ 4
         --master <master_3_address>" 5

     1

     installation_directory is the directory you stored the OpenShift Container Platform definition files that the installation program creates.

     2

     <bootstrap_address> is the fully-qualified domain name or IP address of the cluster’s bootstrap machine.

     3 4 5

     For each control plane, or master, machine in your cluster, replace <master_*_address> with its fully-qualified domain name or IP address.

     Note

     A default cluster contains three control plane machines. List all of your control plane machines as shown, no matter how many your cluster uses.

   The command output resembles the following example:

   INFO Pulling debug logs from the bootstrap machine
   INFO Bootstrap gather logs captured here "<directory>/log-bundle-<timestamp>.tar.gz"

   If you open a Red Hat support case about your installation failure, include the compressed logs in the case.

Procedure

1. Collect the bootkube.service service logs from the bootstrap host using the journalctl command by running:

   $ journalctl -b -f -u bootkube.service

2. Collect the bootstrap host’s container logs using the Podman logs. This is shown as a loop to get all of the container logs from the host:

   $ for pod in $(sudo podman ps -a -q); do sudo podman logs $pod; done

3. Alternatively, collect the host’s container logs using the tail command by running:

   # tail -f /var/lib/containers/storage/overlay-containers/*/userdata/ctr.log

4. Collect the kubelet.service and crio.service service logs from the master and worker hosts using the journalctl command by running:

   $ journalctl -b -f -u kubelet.service -u crio.service

5. Collect the master and worker host container logs using the tail command by running:

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

Procedure

1. Access journald unit logs under /var/log by running:

   $ oc adm node-logs --role=master -u kubelet

2. Access host file paths under /var/log by running:

   $ oc adm node-logs --role=master --path=openshift-apiserver