Debugging host connectivity issues
You might need to log in to your host machine to debug a host issue further.
You can SSH into the host machine if you did not assign the host to a cluster, or if the assignment failed. Otherwise, Satellite disables the ability to log in to the host by using SSH for security purposes. You can remove the host and reload the operating system to restore the ability to SSH into the host machine.
Log in to your host by completing the following steps for your host type and and host assignment status.
- Enabling non-root SSH on RHCOS hosts before assignment.
- Enabling non-root SSH on RHEL hosts before assignment.
- Enabling root SSH on hosts after assignment.
First boot did not complete successfully
You receive output similar to the following messages.
export HOME=/root
HOME=/root
'[' '!' -f /var/log/firstboot.flag ']'
~
The first boot did not complete successfully. Check the /tmp/bootstrap/bootstrap_base.log file and continue looking for errors.
Host registration script fails
You receive output similar to the following messages. Note that the package name might be replaced with another package name.
No package matching '\''container-selinux'\'' found available, installed or updated
No package rh-python36 available. Error: Nothing to do
For more information about these messages, see Host registration script fails.
Host is attempting to register with the location
You receive output similar to the following message.
kubectl --kubeconfig=/tmp/bootstrap/priveledgedcertdir/privledged-kubeconfig
The host is attempting to register with the location.
-
Find the Satellite control plane endpoint.
ibmcloud sat location get --location <LOCATION_ID> -
Find the Public Service Endpoint URL field, for example,
https://c103-e.containers.cloud.ibm.com:12345. -
Confirm your connection exists by running
nc -z -v <ENDPOINT>from your host. For example,nc -z -v c103-e.containers.cloud.ibm.com 12345 -
Repeat the previous step to verify that your host can connect to each of the required outbound hostnames for your region.
RHCOS Machine cannot be reached on the network
RHCOS
You receive output similar to the following messages.
curl: (6) Could not resolve host
The machine cannot be reached on the network. Check that your machine meets the minimum requirements for network connectivity, remove the host, and try to add and assign the host again.
Alternatively, the infrastructure provider network might have issues, such as a failed connection. Consult the infrastructure provider documentation for further debugging steps.
RHEL machine cannot be reached on the network
RHEL
You receive output similar to the following messages.
curl: (6) Could not resolve host: <URL>.com; Unknown error
tar -xvf bootstrap.tar
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
[[ -n ‘’ ]]
echo ‘Failed to untar bootstrap.tar’
Failed to untar bootstrap.tar` \n `+ rm -rf /tmp/bootstrap
The machine cannot be reached on the network. Check that your machine meets the minimum requirements for network connectivity, remove the host, and try to add and assign the host again. Alternatively, the infrastructure provider network might have issues, such as a failed connection. Consult the infrastructure provider documentation for further debugging steps.