Open github-actions[bot] opened 2 months ago
@torchiaf based on this comment https://github.com/rancher/dashboard/pull/11017#issuecomment-2202667245 - I assume the same is true here - and that we should push this to 2.8.next2 - can you confirm?
@torchiaf based on this comment https://github.com/rancher/dashboard/pull/11017#issuecomment-2202667245 - I assume the same is true here - and that we should push this to 2.8.next2 - can you confirm?
@nwmac confirmed.
FYI @gaktive
This is a backport issue for #10989, automatically created via GitHub Actions workflow initiated by @gaktive
Original issue body:
Setup Rancher version:v2.8-head Browser type & version: Chrome Version 124.0.6367.78 Harvester Version: v1.3.0
To Reproduce
Result Once the harvester cluster is redeployed for any reason (the user edits the config, the nodes go into an error state, etc), the new VMs spin up before the old ones are completely shut down, which causes the "un-schedulable" error as the vGPUs won't be available yet.
Expected Result We could add a warning banner in the UI to recommend that the user should provision N+1 allocatable vgpu, where N is number of nodes.