Chapter 16. Troubleshooting

Procedure

1. Verify that your host machine is powered on.
2. If you selected DHCP networking, check that the DHCP server is enabled.
3. If you selected Static IP, bridges and bonds networking, check that your configurations are correct.

4. Verify that you can access your host machine using SSH, a console such as the BMC, or a virtual machine console:

   $ ssh core@<host_ip_address>

   You can specify private key file using the -i parameter if it isn’t stored in the default directory.

   $ ssh -i <ssh_private_key_file> core@<host_ip_address>

   If you fail to ssh to the host, the host failed during boot or it failed to configure the network.

   Upon login you should see this message:

   Example login

   If you are not seeing this message it means that the host didn’t boot with the assisted-installer ISO. Make sure you configured the boot order properly (The host should boot once from the live-ISO).

5. Check the agent service logs:

   $ sudo journalctl -u agent.service

   In the following example, the errors indicate there is a network issue:

   Example agent service log screenshot of agent service log

   

   If there is an error pulling the agent image, check the proxy settings. Verify that the host is connected to the network. You can use nmcli to get additional information about your network configuration.

Procedure

1. Add the .spec.kernelArguments stanza to the infraEnv object of the cluster you are deploying:

   Note

   For details on modifying an infrastructure environment, see Additional Resources.

   # ...
   spec:
     clusterRef:
       name: sno1
       namespace: sno1
     cpuArchitecture: x86_64
     ipxeScriptType: DiscoveryImageAlways
     kernelArguments:
     - operation: append
       value: rd.break=initqueue 1
     nmStateConfigLabelSelector:
       matchLabels:
         nmstate-label: sno1
     pullSecretRef:
       name: assisted-deployment-pull-secret

   1

   rd.break=initqueue interrupts the boot at the dracut main loop. See rd.break options for debugging kernel boot for details.

2. Wait for the related nodes to reboot automatically and for the boot to abort at the iniqueue stage, before rootfs is downloaded. You will be redirected to the root console.

3. Identify and change the incorrect network configurations. Here are some useful diagnostic commands:

   1. View system logs by using journalctl, for example:

      # journalctl -p err //Sorts logs by errors
      # journalctl -p crit //Sorts logs by critical errors
      # journalctl -p warning //Sorts logs by warnings

   2. View network connection information by using nmcli, as follows:

      # nmcli conn show

   3. Check the configuration files for incorrect network connections, for example:

      # cat /etc/assisted/network/host0/eno3.nmconnection

4. Press control+d to resume the bootstrap process. The server downloads rootfs and completes the process.
5. Reopen the infraEnv object and remove the .spec.kernelArguments stanza.