This message was deleted.

if you want to kick start the update you can

kubectl apply -f <https://releases.rancher.com/harvester/v1.7.1/version.yaml>

I'd rather wait or understand why its not showing - I suspect as we use LVM volumes it might not be "supported" and maybe a manual only thing, wanted to make sure that I'm not jumping the gun too... Our stack uses MinIO VM's with dedicated LVM - and we can afford one to be down at a time (its a cluster of 4 VM's one on each host), may I need to do each node in sequence, possibly manual update anyway - just wasn't sure if this was meant to be advertised to 1.6.1 clusters as available yet?

LVM has nothing to do with it. Harvester looks for an update server to have it listed. In many cases they delay it or it is blocked on your network. I run the kubectl apply for every upgrade.

OK - cool, I cant see anything that would explain it being blocked by network. So this is meant to be live then?

1.7.1 has a bug where rke2 will peg 100% of 1 cpu btw, I would stick w/ 1.7.0 atm

Usually it advertises in harvester at least - it isn't currently so I'll wait then... quite happy to wait until it starts advertising in the UI.... just wanted to check I hadn't missed the wave.... Its all running quite nicely at present too 🙂

We have had nothing but issues upgrading to the 1.7.x from 1.6.x and paused until issue are resolved around the pre-drain freezing and freezing after the repo is created due to longhorn replicas and pod disruption budgets. Ball ache to upgrade.

I noticed this is now showing available - will hold off for a short while - @acceptable-analyst-61974 did you raise an issue on the Github account?

I didn't need too, multiple issues regarding upgrades already present @worried-state-78253. Looks like similar problems back in 1.5.1 resurfaced in 1.7.x

I'm planning to upgrade over the weekend, will let you know how it goes....