-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.10
-
Moderate
-
No
-
Rejected
-
False
-
Description of problem:
OpenShift 4 cluster becomes inaccessible intermittently with following errors when we try to do oc login. oc login --server-https://api.cluster.example.com:6443 - -username=k0cbwUnable to connect to the server: read tp 10.x.x.x:49243->10.21.x.x:443: Ware: A connection attempt failed bec Sause the connected party did not properly respond after a period of time, or established connection failed because conne cted host has failed to respond. oc login --server-https://api.cluster.example.com:6443 --username-k0cbwRUnable to connect to the server: read tc 10.x.x.x:49334->10.21.x.x:443: ware: An established connection was a borted by the software in your host machine. oc login --server-https://api.cluster.example.com:6443 --username=k0cbwUnable to connect to the server: read tp 10.x.x.x:48656->10.21.x.x:443: ware: A connection attempt failed bec ause the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. oc login - -server=https: //api.cluster.example.com: 6443 - -username=kecbwUnable to connect to the server: read tp 10.x.x.x:37022->10.21.x.x:443: ware: A connection attempt failed because the connected party did not properly respond after a period of time, on established connection failed because connected host has failed to respond As per the customer the ingress VIP remains attached to the same node during and after the issue. The issue get resolved by itself automatically.
Need the engineering team's help in troubleshooting the issue further. I will be uploading the cluster must-gather.