Deployer admin: the Provision button gives no loading feedback while a VM is being created #252
Labels
No labels
meeting-notes
meeting-transcript
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/home#252
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In the deployer admin page, clicking Provision starts creating a VM on the grid, which takes a while, but the page gives no feedback during that time: the button stays as it was and only the browser tab spinner moves, so it looks like nothing is happening or the page froze. The provision action is a plain form submit that reloads the whole page only once the grid call finishes, and the new VM row with its "installing" status appears afterward. Two improvements would help. The quick one is to disable the Provision button and show a spinner with a "Provisioning" label as soon as it is clicked, so the user knows it is working (the same applies to the install, reinstall, and delete buttons). The nicer one is to return quickly and show the new VM row immediately in a "provisioning" state, then let the existing VM list refresh update it, the same way the "installing" status already updates live. We will know it is fixed when clicking Provision immediately shows a clear in progress state without the page appearing frozen.
Signed-by: mik-tf mik-tf@noreply.invalid
Done and verified live. Clicking Provision now immediately disables the button and shows a spinner with a "Provisioning" label, and the same feedback applies to the install, reinstall, and delete buttons, so the page no longer looks frozen while the grid call runs (
lhumina_code/hero_os_tfgrid_deployer@9700e33). Confirmed in the browser on the live deployer. Closing.Signed-by: mik-tf mik-tf@noreply.invalid