You must be logged in to the server (Unauthorized) or the server is currently unable to handle the request

[Akarsha-rai]

Once the node is reboot/shut down we see the following errors frequently, my initial guess even the node reaches Ready state some other networks/connection are down so we hit the error Unauthorized or server is currently unable to handle the request.

If it is due to hardware issue then we are good to close the issue.

19:38:17 - MainThread - ocs_ci.utility.baremetal - INFO - Baremetal Machine dell-r730-004.dsal.lab.eng.bos.redhat.com reached poweredOn status
19:38:17 - MainThread - ocs_ci.ocs.ocp - INFO - Waiting for cluster connectivity
19:38:17 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig get Service  -o yaml
19:38:18 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig get Node  --selector=node-role.kubernetes.io/master -o yaml
19:38:28 - MainThread - ocs_ci.utility.utils - WARNING - Command stderr: error: You must be logged in to the server (Unauthorized)

19:38:28 - MainThread - ocs_ci.ocs.ocp - WARNING - Failed to get resource:  of kind: Node, selector: node-role.kubernetes.io/master, Error: Error during execution of command: oc --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig get Node  --selector=node-role.kubernetes.io/master -o yaml.
Error is error: You must be logged in to the server (Unauthorized)```

[fbalak]

It seems that this is not a hardware issue as it is seen also on production AWS configuration.

[Akarsha-rai]

Haven't seen the issue in recently runs, so closing for now.