Drop miscellanea/secure_boot_mode_{gadget} for platforms that don't support it

[amalinowski75]

Enhancement Proposal

Pn RPis there is no secure boot but it is still tested.

Error message is:
ERROR: Unexpected bootloader name piboot

Example test run: http://10.102.156.15:8080/job/cert-cm4l-arm64-pi-kernel-24-beta/7/testReport/com.canonical/certification__miscellanea_secure_boot_mode_pi/com_canonical_certification__miscellanea_secure_boot_mode_pi/

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-1571.

This message was autogenerated

[omar-selo]

For reference here are other non RPI machines that don't have secure boot:

aaeon-lookout-canyon-ehl
aaeon-lookout-canyon-tgl
dawson-j-uc24

[pieqq]

Solution to implement:

1. create a has_secure_boot manifest to know whether or not Checkbox should test for Secure Boot on a given device
2. use this manifest in the miscellanea/secure_boot_mode_{gadget}
3. Investigate the RPi-related failures (confirm with Pi team what devices, if any, should have Secure Boot working)
4. Investigate other devices failures (confirm with people in the lab whether or not these should have Secure Boot capabilities)
5. Add manifest in the devices in the lab following results from investigation (to either set it to true or false)

[pieqq]

For reference here are other non RPI machines that don't have secure boot:

aaeon-lookout-canyon-ehl
aaeon-lookout-canyon-tgl
dawson-j-uc24

The aaeon-lookout machines both have Secure Boot functionality (I've checked with QA, and there is some information in their associated QA readme docs — here and there), so that should be enabled in the lab.

For dawson, although there's also a QA readme, it doesn't mention anything about secure boot. However, the device being a 7th gen Intel CPU, it should probably support it already. We need someone in the lab to check.

[pieqq]

For RPis, I got the confirmation from @waveform80 that all the RPis currently in the lab could be set to skip Secure Boot related tests, as there is no official support in Ubuntu at the moment.