This message was deleted.
# harvestera
adamant-kite-43734
05/23/2025, 10:34 PMThis message was deleted.
w
worried-state-78253
05/23/2025, 10:55 PMBasically - it doesn't look like changing the "node schedule" is possible despite the fact that there is available capacity and there are healthy replicas, other than restoring manually I cant see an easy way to sort this out.
worried-state-78253
05/24/2025, 11:36 AMI'll raise as a bug as it should be possible to change the node scheduling, currently cloning the disk to start a new VM based on the clone as a workaround.
worried-state-78253
05/24/2025, 1:01 PMOK - workaround was to edit the YAML directly and change the scheduled node to a healthy one - this got me running again.
👀 1
worried-state-78253
05/24/2025, 1:11 PMIssue is on GH - https://github.com/harvester/harvester/issues/8351 I'll be updating to 1.4.2 soon so will re-test this when its updated
r
red-king-19196
05/26/2025, 3:25 AMHi Craig, I have some updates on the GH ticket. Please take a look.
BTW, did you tried editing the node selectors using the Harvester UI?
✅ 1
6 Views