While running 4.12.44 pipeline testing overnight, the api server became unavailable and the error condition could not clear next day. 


[jenchen@ericsson-ocp-4 ~]$ oc get nodes
The connection to the server api.cloudransno-site5.slcm3.bos2.lab:6443 was refused - did you specify the right host or port?
[jenchen@ericsson-ocp-4 ~]$ ping api.cloudransno-site5.slcm3.bos2.lab
PING api.cloudransno-site5.slcm3.bos2.lab(cloudransno-site5.slcm3.bos2.lab (fd12:3456:789a:45::95)) 56 data bytes
64 bytes from cloudransno-site5.slcm3.bos2.lab (fd12:3456:789a:45::95): icmp_seq=1 ttl=64 time=0.066 ms
64 bytes from cloudransno-site5.slcm3.bos2.lab (fd12:3456:789a:45::95): icmp_seq=2 ttl=64 time=0.315 ms
^C
--- api.cloudransno-site5.slcm3.bos2.lab ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1045ms
rtt min/avg/max/mdev = 0.066/0.190/0.315/0.125 ms
[jenchen@ericsson-ocp-4 ~]$ date
Fri Nov 17 15:54:04 EST 2023
[jenchen@ericsson-ocp-4 ~]$ oc get nodes
The connection to the server api.cloudransno-site5.slcm3.bos2.lab:6443 was refused - did you specify the right host or port?

From hub cluster, it was marked as status unknown.

As api is not available, no mustgathering. But the SNO at error status is kept for debug purpose for 3 days. Please access it ASAP. 




Dci pipeline: https://www.distributed-ci.io/jobs?page=1&perPage=20&where=tags:gitlab-146852

4.12.44

Not sure if it's reproducible. the SNO at error status is kept for debug purpose for 3 days. Please access it ASAP.

1.Deploy SNO with midband policies
2. Run E/// pipeline tests.
3.

API is not reachable and pipeline stopped at middle. 

API unavailable is not noticeable 

the SNO at error status is kept for debug purpose for 3 days. Please access it ASAP.