This message was deleted.
# harvestera
adamant-kite-43734
05/07/2025, 12:59 PMThis message was deleted.
a
alert-london-41705
05/07/2025, 3:15 PMOut of curiosity do any of the nodes that are stuck have cpu manager enabled on them? I had a similar issue recently going to 1.4 and I had to turn that off.
b
bland-article-62755
05/07/2025, 5:39 PMI feel like this symptom happens to me frequently but the cause is always different.
bland-article-62755
05/07/2025, 5:40 PMNormally launching the built in rancherUI and checking the events (or using kubectl to) gives some sort of indication on what's stuck.
bland-article-62755
05/07/2025, 5:41 PMSometimes it's a system pod(s) that are blocking the upgrade from progressing because the node doesn't enter a ready state.
s
salmon-city-57654
05/08/2025, 4:02 AMHi @gray-room-77418,
I thought you also created the issue here [BUG] Failed upgrade from 1.4.2 to 1.5.0.
I tried to investigate the issue with your support bundle, but it lacks the
yamlg
gray-room-77418
05/08/2025, 7:47 AMJust uploaded a new support bundle to that ticket @salmon-city-57654. With that said: it doesn't look like the yamls directory is in the new bundle, either, so maybe we have something more going on here.
gray-room-77418
05/08/2025, 8:08 AMok, found the cause of that nugget (cluster cert expired), so now I have a complete support bundle, and am wondering if that's the cause of the other issues
👍 1
s
salmon-city-57654
05/08/2025, 8:10 AMThe cert expired sometime, causing the upgrade issue, but anyway, you could upload the latest SB. We would like to check.
g
gray-room-77418
05/08/2025, 8:10 AMI'm just uploading to the Github ticket now - thanks @salmon-city-57654!
🙌 1
3 Views