CS 4.20.1 - possible bug (or I don't know what I am doing)

[rongage2]

On CS 4.20.1 with KVM hosts.

If an instance is in an error state, you cannot edit the settings of the instance.

Example: set up an instance with a UEFI. Launch that instance on a host without UEFI being available. Error state. Click on instance, then click on the settings tab. You cannot edit any settings (i.e.: to set the instance to BIOS mode) because CS doesn't apparently recognize the instance state of "error" as the instance not running. Note the message on the settings page: Please stop the Instance to access settings.

Seeking verification before I open up an Issue.

Ron Gage

[rajujith]

@rongage2 An instance in 'Error' state can't be edited; this is expected. You can select the UEFI boot type while deploying an instance. Make sure that you have hosts configured correctly.

[weizhouapache]

correct

or uncheck "Start Instance", add VM settings, then start the instance

[rongage2]

Wei:
I have already "finished" the deploy screen - there is no "Start Instance" to uncheck anymore. It seems that the only solution to this is to delete the VM, and try again since settings cannot be edited on a machine in error state.

Ron

[weizhouapache]

@rongage2
yes, if the vm is in Error state, there is no way to recover . you can not do anything except deleting it

[DaanHoogland]

@rongage2 , the reason for this is that an instance in error state may be able to write to its disk and you wouldn’t want to corrupt it. I think there are some improvements possible. This is the simple crude interpretation of the state of the VM.

I am not sure if the VM can be safely stopped or if this even automatically happens. I’ve seen VMs in error state being destroyed automatically even. Some improvement requests around this can be made, no doubt.

[weizhouapache]

@rongage2 , the reason for this is that an instance in error state may be able to write to its disk and you wouldn’t want to corrupt it. I think there are some improvements possible. This is the simple crude interpretation of the state of the VM.

I am not sure if the VM can be safely stopped or if this even automatically happens. I’ve seen VMs in error state being destroyed automatically even. Some improvement requests around this can be made, no doubt.

the error only happens during vm deployment. If VM is Error state, I think it is not ready for use, no user data.

[DaanHoogland]

isn’t it also possible during a (re)start , @weizhouapache ?

[weizhouapache]

isn’t it also possible during a (re)start , @weizhouapache ?

@DaanHoogland
not 100% sure, I only faced the issue when deploy a new vm