Concern about VM deletion

Hello,

On OpenNebula 5.0, an advanced user created a wrong VM template which resulted in a BOOT_FAILURE state.

This user found the issue but only the admin can delete the VM with the recoverDELETE operation.

This could burden the admin quite a lot.

How could I alleviate the burden on my shoulders, without downgrading advanced user to simple cloud consumer.

Regards.

Hi Daniel,

We may have overlooked at it. The assumption is that a BOOT_FAILURE issue
is related to a misconfigured hypervisor, thus something that requires
admin intervention. What was the problem?

Cheers

“Ruben S. Montero” forum@opennebula.org writes:

Hi Daniel,

Hello,

We may have overlooked at it. The assumption is that a BOOT_FAILURE issue
is related to a misconfigured hypervisor, thus something that requires
admin intervention. What was the problem?

We used to generate some template automatically with jenkins, and the
boot order configuration changed from

HD,CDROM

to

disk0,disk1

Fixing it only requires to modify the template.

Regards.

Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF

So, I think that should be addressed as a bug, OpenNebula should complain
about a wrong syntax in the VM Template and not let the user to create such
VM. Any template error should be catched early in the VM life-cycle, and
not go through the cloning process of disk images and so on…

http://dev.opennebula.org/issues/4610