I currently have all my clusters updating simultan...
# generalb
best-appointment-66450
08/27/2025, 7:56 PMI currently have all my clusters updating simultaneously on Rancher 2.12.0, all seemingly stuck with the message "KDM release data is empty for v1.33.3+rke2r1" (or slight variation in release), all with one controller stating "Reconciling. Waiting for plan to be applied". Should I be worried?
c
creamy-pencil-82913
08/27/2025, 8:29 PMdid you hardcode a custom KDM URL in your settings, and forget to update it when upgrading rancher to 2.12?
creamy-pencil-82913
08/27/2025, 8:30 PMimage.png
creamy-pencil-82913
08/27/2025, 8:30 PMthe message indicates that the data.json in use by your rancher instance is missing data for v1.33.3+rke2r1.
creamy-pencil-82913
08/27/2025, 8:38 PM Copy code
brandond@dev01:~$ curl -sL <https://releases.rancher.com/kontainer-driver-metadata/release-v2.12/data.json> | jq '.rke2.releases[].version' | grep v1.33
"v1.33.0+rke2r1"
"v1.33.1+rke2r1"
"v1.33.2+rke2r1"
"v1.33.3+rke2r1"b
best-appointment-66450
08/28/2025, 5:22 AMI have changed the rke-metadata-config entry from 2.11 to the one that you've shown. There were a number of other 2.11 urls too - ui-index and ui-dashboard-index. I definitely didn't deliberately hardcode anything, just tried following instructions to install, then to update. I might well have missed something. Is there a doc showing what I should be doing in these circumstances? Do I just wait until the next update to see if it clears up?
c
creamy-pencil-82913
08/28/2025, 5:28 AMthose would normally be handled automatically as part of the upgrade. if they were not, that indicates someone went in and changed them at some point so that they are not using the default that is built into the product. If that is done, you need to update them manually after upgrading
b
best-appointment-66450
08/28/2025, 6:07 AMThey definitely weren't changed manually. I must have missed something when I did the upgrade, not entered something I should have. Should I just wait for the daily update to make the warnings go away?
best-appointment-66450
08/28/2025, 10:22 AMI changed the update period and the warnings haven't gone away. More problematically, it stops installation of a new cluster as it's paused with the same warning. Even tried downloading data.json and swapping it with the one in place on the cluster server which was waiting for the change. Is there something I can run to kick-start this again?