# Upgrade worker nodes after master nodes

**URL:** <https://forums.suse.com/t/upgrade-worker-nodes-after-master-nodes/45366>\
**Category:** General\
**Created:** [April 7, 2025, 7:50am UTC](https://forums.suse.com/t/upgrade-worker-nodes-after-master-nodes/45366 "2025-04-07T07:50:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PioterW](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@PioterW](https://forums.suse.com/u/PioterW)\
**Post date:** [April 7, 2025, 7:50am UTC](https://forums.suse.com/t/upgrade-worker-nodes-after-master-nodes/45366/1 "2025-04-07T07:50:12Z")

</div>

Dear All,  
We faced an issue durning the upgrade process.  
Using Rancher v1.30.2+k3s2 - in docker we did upgrade for installed and hosted in Rancher Cluster ( in GUI ) from 1.29.6 to 1.29.15 to fix security issue with last Ngnix CVE. The process failed because of the allready knowed bug: [https://www.suse.com/support/kb/doc/?id=000021371](https://www.suse.com/support/kb/doc/?id=000021371) and the upgrade process goes only with master nodes. Currently all three Master nodes are in 1.29.15 Version but the four of worker nodes are in 1.29.6. How can we “force/restart” the upgrade process only on the worker nodes ?  
Should it be done manualy by downloading the softwere ( from where ) ?  
Regards

---

<div class="post-metadata">

**Author:** ![PioterW](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@PioterW](https://forums.suse.com/u/PioterW)\
**Post date:** [April 8, 2025, 7:10am UTC](https://forums.suse.com/t/upgrade-worker-nodes-after-master-nodes/45366/2 "2025-04-08T07:10:10Z")

</div>

Manuall update of the rest of the cluster nodes has been succeeded by following this steps [https://docs.rke2.io/upgrades/manual\_upgrade:](https://docs.rke2.io/upgrades/manual_upgrade:)