Open github-actions[bot] opened 1 month ago
This might be unblocked soon as Harvester QA works on this. @ibrokethecloud can provide an environment upon request to help out so someone please check ASAP.
We got word from Harvester that this is OK to push to the next release. @rebeccazzzz will keep UI posted on when Harvester will do their part to unblock us.
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.