-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local k3s clusters were not able to be upgraded within Rancher post upgrade from 2.5 to 2.6 #35797
Comments
Assigning myself for tracking purposes. |
verified fix in v2.6-e62e1ae34eca46bd733b7f67d1cea055395ac45d-head
RESULTS: |
Reopening for a validation from 1.20 to 1.21 k3s version upgrade |
On 2.6.3-rc4 the issue remains:
EXPECTED: ACTUAL: |
Available to test with v2.6-head after https://drone-publish.rancher.io/rancher/rancher/7030 passes. |
I just ran into this with one of my downstream cluster rather than my local cluster.
How do I recover from this now? The upgrade has been attempting for well over an hour now on my Raspberry Pi 4 4 GB. |
@Vashiru The following worked for me:
|
@dnoland1 Cheers mate, appreciated! That did the trick for me too. For anyone else running into this. It might still throw a message about that |
This seems to be fixed with the latest SUC version introduced in 2.6.3, but this is a explicit request to test this use case to check.
SURE-3539
SURE-3388
Before rancher server upgrade: Rancher version - v2.5.9, k3s v1.20.9+k3s1, SUC: 0.6.2
Post rancher server upgrade: Rancher version - v2.6.2, k3s v1.20.11+k3s2, SUC: 0.7.5
kubectl get serviceaccount -A | grep -i system-upgrade
apps & market --> installed apps --> SUC app installed
cordoned
and the local cluster is stuck inupgrading
and the service account name is system-upgrade-controllerError creating: pods "apply-k3s-master-plan-on-ip-172-31-8-247-with-57eb7803114-9fcec-" is forbidden: error looking up service account cattle-system/system-upgrade: serviceaccount "system-upgrade" not found
The text was updated successfully, but these errors were encountered: