This message was deleted.
# harvester
a
This message was deleted.
r
Though I haven’t tried it before, I wouldn’t recommend that. From Harvester upgrade’s perspective, there are basically three parts to upgrade: the system services (essential Pods for Harvester to operate), the RKE2, and the operating system of the nodes. The Harvester upgrade process will handle all of these in order. Joining an older node does not trigger the Harvester upgrade process. The OS part will remain as is, but I think some of the system services and the RKE2 could be upgraded by some mechanisms from the Rancher Manager. The result will be a mess 🤯 What’s the bug you’re facing when installing Harvester on bare-metals?
e
https://github.com/harvester/harvester/issues/4510 Thanks for reply! I actually had issues during the upgrade, and I probably made things worse to the point beyond repair 🙂 Gave up around 0230 this morning. I should of stopped hours earlier and not kept 'trying stuff' 😄 Pretty sure I cancelled the upgrade beyond the point of 'that is a bad idea' 😄 Then today thought i'd just do a fresh v1.2.0 install and move things over -- so install fresh 1-2 nodes and migrate over workloads to a new RKE2 cluster. But now the bare metal bug 😄 I want to keep some of my nodes running in the 'broken' cluster so I can get a new cluster up, and move services over, then reprovision those last nodes. So I can't reinstall a full v1.1.2 then upgrade, since I need to keep those mixed state nodes running with the current cluster. I also don't want to install rancher-in-a-vm to migrate the broken clsuter to a v1.1.2 cluster then do another upgrade attempt.
👀 1
I've spent a few hours now trying all I can think of to get v1.2.0 working on the mini PC, from bios reset/upgrade, disabling drives, etc. I am not smart enough to know why the v.1.2.0 iso is failing, unforutnately. It does seem like harvester changed some stuff atleast when comparing the grub configuration of v1.1.2 iso and v1.2.0 iso.
r
Thanks for trying and for your feedback to us. We’re looking into this 🧐
❤️ 1
e
I think I will aim to install 2x nodes with r1.1.2, then upgrade them together. That should give me enough capacity to migrate from my broken cluster, and I can wait until a work around/fix for the baremetal to reprovision them to v1.2.0 and add to the new cluster... Or atleast that is the current goal, I suspect another late night ahead 🙂 Thanks for all the effort, have really enjoyed this bit of kit and eagerly been watching for this release. MCM will be super super nice.
🙌 1