When starting/stopping instance, the PVE task status returns that the start/stop task has completed before the instance's power status is changed. This results in a desynchronization between user input and the instance's true status as it transitions between states.
Recreating:
Start or stop a VM instance
Observe that the status GET returns complete
The following GET instances does not fetch an updated instance status, eventually causing a refresh
Only then will the user get non-stale status information
This issue is observed on instances without HA.
When starting/stopping instance, the PVE task status returns that the start/stop task has completed before the instance's power status is changed. This results in a desynchronization between user input and the instance's true status as it transitions between states.
Recreating:
- Start or stop a VM instance
- Observe that the status GET returns complete
- The following GET instances does not fetch an updated instance status, eventually causing a refresh
- Only then will the user get non-stale status information
This issue is observed on instances without HA.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When starting/stopping instance, the PVE task status returns that the start/stop task has completed before the instance's power status is changed. This results in a desynchronization between user input and the instance's true status as it transitions between states.
Recreating:
This issue is observed on instances without HA.