<https://github.com/rancher/rancher/issues/50215> ...
# rancher-setup
b
https://github.com/rancher/rancher/issues/50215 Can anyone help with this issue ?
p
You just uninstalled the rancher helm from the cluster right? Nothing more?
b
yes just uninstalled rancher from cluster, nothing else
p
In your recovered log, this error line appears :
Copy code
May 08 19:26:30 rancher-rke2-test rke2[503636]: time="2025-05-08T19:26:30Z" level=warning msg="Failed to get apiserver addresses from supervisor: <nil>"
And afterwards, you do not get the
Copy code
May 08 18:58:26 rancher-rke2-test rke2[487685]: time="2025-05-08T18:58:26Z" level=info msg="Polling for API server readiness: GET /readyz failed: Get \"<https://127.0.0.1:6443/readyz?timeout=15s&verbose=>\": dial tcp 127.0.0.1:6443: connect: connection refused - error from a previous attempt: http2: server sent GOAWAY and closed the connection; LastStreamID=1, ErrCode=NO_ERROR, debug=\"\""
logline
I have no idea why, just trying to analyze for my own knowledge
Is your self-managed VM fast enough? I think this could happen if the cluster is slow to restart
b
Yes it is fast and there is no delay observed on that, Initial cluster creation and accessibility is quick enough. its only after the uninstallation of rancher, we have observed this connection issue to cluster
p
Is the unavailability time consistent or does it varies?
b
it varies, Initially we were able to access the cluster for around 30 seconds or so in regular 5 minute time interval but later cluster was totally not reachable.
p
Ok so basically, rke2 will fail after waiting for 15 minutes for the apiserver to boot However, in your recover log, the apiserver took a whole 13 minutes to start (which is quite long) are your vms using ssd storage?
b
yes they use ssd storage
Let us know if there is any findings or any info required for this issue.