[BUG] Error writing node IP when join node, The status has been constantly in Upgrading about autok3s HOT 14 CLOSED

The workaround below may help you:

• Using kubectl get nodes to check whether the batch of nodes have joined to the cluster successfully.
• If not, use autok3s join CLI to join a node to refresh the cluster status.

autok3s join -p native --name jacie-test --ip <master-ip> --ssh-user <your-ssh-user> --ssh-key-path <your-ssh-key-path> --worker-ips <one-worker-ip>

Once the join process is complete, the cluster status will be refreshed to Running and the UI can work properly.

from autok3s.

Yes. AutoK3s can't synchronize your operation because the node was removed manually and didn't synchronize the AutoK3s database. So you can't rejoin the node by AutoK3s because the node is already in the cluster by AutoK3s side.
The workaround is to add the node back by K3s CLI manually for now.

from autok3s.

tested with v0.9.2-rc1. AutoK3s can return the correct status of the cluster if join nodes fail.
Close as complete

from autok3s.

Thanks for your feedback.

Are all cluster nodes CentOS 7.9 or only the newly added worker node is using CentOS 7.9?
It seemed that the new worker node could not fetch from the rpm mirror.
Could you please provide the join node parameters and the full log with joined the new node?

from autok3s.

vps-regtech.log
This is all the logs of this cluster.
all cluster nodes CentOS 7.9, When I added a new batch of nodes, an IP address was written incorrectly. The cluster is currently in an Upgraded state

from autok3s.

Is the joining node action stuck at the last line of the log you provide?
It seems like AutoK3s can't access the node 74.48.115.18 by SSH tunnel. Is this node IP the incorrect one?

from autok3s.

Q1: Yes
Q2: 74.48.115.18 is wrong, I made a mistake in writing. emmmmmm...

from autok3s.

Sometimes the native provider can't catch the join error correctly. When this situation happens, the cluster's status will be Upgrade forever.
I will find out if there's a workaround.

from autok3s.

Okay, I'll rebuild the cluster. Thank you for your answer.
Best wishes to you.

from autok3s.

@xuzheng0017 There's no need to rebuild the cluster. The K3s cluster won't impact by the AutoK3s cluster status.

from autok3s.

Okay, but I want to join other nodes to the page without any options.

from autok3s.

The bug is relative to the wrong catch of error in defer function. Will fix this in the next version.

from autok3s.

I have encountered another problem:
When I deleted a node in kube-explorer and then returned to the cluster page, the number of nodes did not decrease.
I added the node again with the command:

81d5d17a77de:/home/shell # autok3s join -p native --name vps-cargogo --ip xx.xx.xx.xx --ssh-user root --ssh-key-path /root/.autok3s/vps-cargogo/id_rsa --worker-ips xx.xx.xx.xx
time="2023-12-06T14:53:03+08:00" level=info msg="[native] begin to join nodes for vps-cargogo..."
time="2023-12-06T14:53:03+08:00" level=info msg="[native] executing join k3s node logic"
time="2023-12-06T14:53:03+08:00" level=info msg="[native] successfully executed join k3s node logic"
time="2023-12-06T14:53:03+08:00" level=info msg="[native] successfully executed join logic"

from autok3s.

Can only use commands on nodes to rejoin?

from autok3s.