This message was deleted.
# generala
adamant-kite-43734
05/08/2024, 7:40 AMThis message was deleted.
a
abundant-napkin-79526
05/08/2024, 8:45 AMIm assuming you're using the system-upgrade-controller - the labels and server/agent plans will remain until deleted. There's no harm in letting them be AFAIK.
h
high-mouse-79037
05/08/2024, 8:47 AMThanks for reply.
The label backs immediately after removing.
Removing plans or adding them back does not affect on nothing visible.
a
abundant-napkin-79526
05/08/2024, 8:55 AMIf you dont update the plans version parameter I don't think the controller has anything to act on 🙂
abundant-napkin-79526
05/08/2024, 8:57 AMI don't know about those cattle.io labels, I'd imagine the controller would be the one to label them up so unless you'd want to remove that completely then I wouldnt worry about them.
abundant-napkin-79526
05/08/2024, 8:58 AMIf you don't want a particular node to be upgraded at all you can control that with the
rke2-upgrade=h
high-mouse-79037
05/08/2024, 8:59 AMYes, the upgrade itself seems finished, everything running, but the whole cluster status still "upgrading". Something still not finished yet. And I cannot find where is the state of upgrade process.
a
abundant-napkin-79526
05/08/2024, 9:00 AMWhat is the status of the plan? It should say on what nodes it's still applying?
abundant-napkin-79526
05/08/2024, 9:01 AMI've had issues with the upgrading status on Linux/Windows mixed clusters - since versioning was different on Windows IIRC.
h
high-mouse-79037
05/08/2024, 9:01 AMstatus:
conditions:
- lastUpdateTime: "2024-05-08T090014Z"
reason: PlanIsValid
status: "True"
type: Validated
- lastUpdateTime: "2024-05-08T090014Z"
reason: Version
status: "True"
type: LatestResolved
latestHash: 6de058e9c48bb0568a151e795d143ad09327d44aa09f8585de3f6ed3
latestVersion: v1.28.8-rke2r1
a
abundant-napkin-79526
05/08/2024, 9:02 AMAnd all nodes have been upgraded to the correct version?
h
high-mouse-79037
05/08/2024, 9:05 AMyep
The only things to worry:
kubectl -n cattle-system describe pod/system-upgrade-controller-77b8db4449-62r4h
Containers:
system-upgrade-controller:
Container ID: containerd://5138d2048a12e4154f89066b33fa0c2db7f99095d1735c018a43d0595c54494c
Image: nexus.2cloud4.com/rancher/system-upgrade-controller:v0.13.1
Image ID: nexus.2cloud4.com/rancher/system-upgrade-controller@sha256:c730c4ec8dc914b94be13df77d9b58444277330a2bdf39fe667beb5af2b38c0b
Port: <none>
Host Port: <none>
State: Running
Started: Tue, 07 May 2024 164648 +0300
Last State: Terminated
Reason: Error
Exit Code: 2
Started: Tue, 07 May 2024 162623 +0300
Finished: Tue, 07 May 2024 164648 +0300
Ready: True
Restart Count: 1
is mention about Error above.
a
abundant-napkin-79526
05/08/2024, 9:07 AMWell perhaps that'll be something to look at - I don't think the "Upgrading" label is dangerous but maybe head over to #rke2 and ask. The system-upgrade-controller has a more recent release so you might wanna upgrade the controller too
h
high-mouse-79037
05/08/2024, 9:11 AM👍
4 Views