[#ABICLOUD-69] VM status does not match with current status of the Virtual Appliance - ABIQUO

Abiquo

VM status does not match with current status of the Virtual Appliance

Created: 21/Jun/09 06:35 PM Updated: 19/Oct/09 12:32 PM Resolved: 09/Oct/09 01:57 PM

Component/s:

None

Affects Version/s:

abiCloud-0.7.0

Fix Version/s:

abicloud-1.0.0PR

Time Tracking:

Not Specified

Description

« Hide

It seems that forcing a virtual machine to stop in the 'Infrastructure View' does not affect the status of the progress stopping and undeploying a Virtual Appliance. The Virtual Appliance does not seem to recognize the changes in the VM status.

As a rule of thumb, any change in the Infrastructure View should affect the Virtual Appliance view and in the other way around.

Sort Order:

[ Permalink | « Hide ]

Xavier Fernandez added a comment - 21/Jun/09 07:49 PM

Hi Diego.

If I change the state of a Virtual Machine in the Infraestructure View, this state change on Virtual Appliance View.

We tested it and It works. Can you explain more details?

Maybe You said that if I stop a virtual Machine, The appliance will be stoped? Are you sure?

Remember that the stop on a VirtualMachine it's only a shutDown of the Virtual Machine, not the stop on the appliance (And undeploy of the different VM).

Thanks

[ Permalink | « Hide ]

Diego Parrilla added a comment - 21/Jun/09 09:25 PM

The status in the Virtual Appliance was 'stopping'. But nothing happened. No timeout, no error, just 'stopping'.

The information in the Infrastructure Management about the Virtual Machines in the Virtual Appliance was 'running'. Forcing the a VM to stop made the VM status to change to 'stopping', and later on to 'stopped'.

Returning to the Virtual Appliance view, no change in the status was visible. Obviously the information in a view an another was not coherent.