
Email this issue
Send issue summary in email
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
When deploying a new virtual appliance and an error occurs in the cluster node, or some manual actions are performed on the cluster node, the information is managed in a different way in:
- Infraestructure Management
- Virtual Appliances
The status in Infraestructure Management seems to be updated with the information retrieved from the node, but the information in the Virtual Appliances seems to be updated with the information stored in the internal database. As result, the information is not coherent, and some actions cannot be performed due to this inconsistency.
As a rule of thumb, same status information should be retrieved and updated from the same source, same strategy.
|
|
Description
|
When deploying a new virtual appliance and an error occurs in the cluster node, or some manual actions are performed on the cluster node, the information is managed in a different way in:
- Infraestructure Management
- Virtual Appliances
The status in Infraestructure Management seems to be updated with the information retrieved from the node, but the information in the Virtual Appliances seems to be updated with the information stored in the internal database. As result, the information is not coherent, and some actions cannot be performed due to this inconsistency.
As a rule of thumb, same status information should be retrieved and updated from the same source, same strategy. |
Show » |
Sort Order:
|
1) Deploy a Virtual Appliance with a single virtual image
2) rimp copy from /mountedRepositories to /localRepository the image
3) virtualbox copy from /localRepository to $VIRTUALBOX_HOME/HardDisks/ the image
4) virtualbox starts the vm
5) The VM cannot start succesfully (whatever reason: network, not enough space, not enough ram...)
6) The VM fails to start, but in the Virtual Appliance it appears as 'Running'
It's not possible to stop the VM because there is nothing to stop...