You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This problem was seen on aws driver.
Steps to reproduce:
Go to your VDI.
Go to 'start' and shut-down your machine through windows (don't close it with close/minimize vdi).
Now your vm is in stop status on AWS.
That mean that this vm is never terminated cause she is not even running. You can't access the vdi again.
If you try to start this machine again manually on aws, the ip of this one will change, so you will need to change it on base, otherwise, you are totally blocked with this vm because she is assigned to you, and you cannot have an other one if your's is not remove from base.
The text was updated successfully, but these errors were encountered:
What happen if the user reboots the machine from the web interface ?
If the machine is shut down from the VDI, is a blank VDI displayed or at least an information message is shown ?
Does the machine keeps its green status "running" on the machine list ?
The machine is stopped, so reboot fail.
Not blank page are shown if you try to disconnect or minimize the vdi.
Yes, the machine keep its green status, but the count down of termination started.
The problem is, the machine is stopped on aws, so when this situation happen, we need to start the machine. This option is now implemented on drivers, so we should use it to solve this problem.
This problem was seen on aws driver.
Steps to reproduce:
Now your vm is in stop status on AWS.
That mean that this vm is never terminated cause she is not even running. You can't access the vdi again.
If you try to start this machine again manually on aws, the ip of this one will change, so you will need to change it on base, otherwise, you are totally blocked with this vm because she is assigned to you, and you cannot have an other one if your's is not remove from base.
The text was updated successfully, but these errors were encountered: