sparse-dusk-81900
11/18/2022, 9:31 AMv2.6.9
and the custom
RKE2 clusters to v1.24.7
. However, both clusters are now in “Updating” state as both have a single node/machine with status waiting for plan to be applied
. What’s the best way to troubleshoot this? I’ve already checked the rancher-system-agent.service
on the regarding VMs but didn’t find anything suspicious. Also, cluster operations like a manually triggered cert rotation after the upgrade to v1.24.7
run successfully - even on the affected nodes/machines. Because of that it just looks like an old status from a previous sync which keeps the whole clusters in “updating” state.