Email this issue
Send issue summary in email
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
If you start up a virtual appliance with two images, m0n0wall and debian linux, abicloud does not know when both images have been deployed and started succesfully in the hypervisor. If you click on 'force refresh' button, then you get the event status and everything is refreshed, and the status information updated.
If you stop a virtual machine in a running virtual appliance with more than one virtual machine, the status is not refreshed and any change performed in the hypervisor is not detected. A local 'force refresh' button is needed for every virtual machine deployed.
|
|
Description
|
If you start up a virtual appliance with two images, m0n0wall and debian linux, abicloud does not know when both images have been deployed and started succesfully in the hypervisor. If you click on 'force refresh' button, then you get the event status and everything is refreshed, and the status information updated.
If you stop a virtual machine in a running virtual appliance with more than one virtual machine, the status is not refreshed and any change performed in the hypervisor is not detected. A local 'force refresh' button is needed for every virtual machine deployed. |
Show » |
Sort Order:
|
Bug
Closed
Critical
Power Up and Power Down events lost
ABICLOUD-339. When the CPu is at 100% the system drops events ( and connections?).