Use the following guidelines and suggested steps to help resolve remote gateway upgrade issues.
- Condition:
- Upgrading remote gateway to 9.6 fails if it is configured with FQDN.
- What it Means:
- Upgrading remote gateway from 9.4 to 9.5, and then from 9.5 to 9.6 fails.
- Corrective Action:
-
- Revert to the remote gateway 9.5 snapshot.
- Using SSH, log on to the remote gateway as a ucpadmin user.
- Run the following commands:
[ucpadmin@ucpadvisormasterhost105 ~] kubectl get nodes -n ucp # NAME STATUS ROLES AGE VERSION # ucpadvisormasterhost105 Ready control-plane,master 83s v1.32.6+k3s1 # ucpadvisormasterhost105.ucpa-sc-hv.com NotReady control-plane,master 12h v1.32.6+k3s1 #if there are two nodes as in example, one with fqdn and one without fqdn, execute the following commands to reset the k3s cluster: #note: this procedure is to be followed only when the remotegateway vm is created with fqdn hostname initially NON_FQDN_HOSTNAME=ucpadvisormasterhost105 FQDN_HOSTNAME=ucpadvisormasterhost105.ucpa-sc-hv.com kubectl cordon $NON_FQDN_HOSTNAME kubectl delete pods --all -n ucp --force kubectl delete pods --all -n kube-system --force kubectl drain $NON_FQDN_HOSTNAME --ignore-daemonsets --delete-emptydir-data kubectl delete node $NON_FQDN_HOSTNAME sudo hostnamectl set-hostname $FQDN_HOSTNAME reboot
- Retry upgrading the remote gateway.