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

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: abiCloud-0.7.0
  • Fix Version/s: abicloud-1.0.0PR
  • Component/s: None
  • Labels:
    None

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Xavier Fernandez added a comment -
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
Show
Xavier Fernandez added a comment - 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
Hide
Permalink
Diego Parrilla added a comment -
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.
Show
Diego Parrilla added a comment - 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.

People

  • Assignee:
    Pedro Navarro Pérez
    Reporter:
    Diego Parrilla
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: