Describe the bug
Calm DSL is not creating a usable blueprint which requires UEFI and Secure Boot in Self-Service. Calm DSL compiles the blueprint correctly and creates it in Self-Service in an Active state. If you look at the UI of the blueprint which was created via Calm DSL, the UI shows UEFI and Secure Boot set, but when you go to launch the blueprint, it fails trying to create the VM due to the machine type not being set to Q35 in the payload sent to PC.
Branch/Container
4.2
To Reproduce
Create blueprint DSL code with boot_type = "SECURE_BOOT". Compile and create the blueprint in Self-Service. Validate the blueprint has UEFI and Secure Boot enabled. Launch the blueprint. When the blueprint gets to the step of sending the payload to PC it will fail due to the machine type of Q35 not being set. Now inside the UI go to the blueprint and disable Secure Boot and save. Then enable Secure Boot and save again. Now try to launch the blueprint again and this time it will succeed as the payload now contains the correct machine type.
Available Logs/Data
Audit Log
ERROR: VM Creation failed at the AHV due to the following reasons:
ERROR MESSAGE: Machine type must be set to Q35 for secure boot.
REASON: ACTION_NOT_SUPPORTED
ERROR DETAILS:
ERROR: No ergon task created for VM Create operation
Describe the bug
Calm DSL is not creating a usable blueprint which requires UEFI and Secure Boot in Self-Service. Calm DSL compiles the blueprint correctly and creates it in Self-Service in an Active state. If you look at the UI of the blueprint which was created via Calm DSL, the UI shows UEFI and Secure Boot set, but when you go to launch the blueprint, it fails trying to create the VM due to the machine type not being set to Q35 in the payload sent to PC.
Branch/Container
4.2
To Reproduce
Create blueprint DSL code with
boot_type = "SECURE_BOOT". Compile and create the blueprint in Self-Service. Validate the blueprint has UEFI and Secure Boot enabled. Launch the blueprint. When the blueprint gets to the step of sending the payload to PC it will fail due to the machine type of Q35 not being set. Now inside the UI go to the blueprint and disable Secure Boot and save. Then enable Secure Boot and save again. Now try to launch the blueprint again and this time it will succeed as the payload now contains the correct machine type.Available Logs/Data
Audit Log
ERROR: VM Creation failed at the AHV due to the following reasons:
ERROR MESSAGE: Machine type must be set to Q35 for secure boot.
REASON: ACTION_NOT_SUPPORTED
ERROR DETAILS:
ERROR: No ergon task created for VM Create operation