Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add /hardening/*/uefi tests #276

Merged
merged 2 commits into from
Oct 24, 2024
Merged

Add /hardening/*/uefi tests #276

merged 2 commits into from
Oct 24, 2024

Conversation

comps
Copy link
Contributor

@comps comps commented Oct 18, 2024

This fixes #19 .

These tests are especially important for RHEL-10 (which might be UEFI-by-default), but they seem to work well on others, so I left them without a distro limitation. ComplianceAsCode/content#12510 and ComplianceAsCode/content#12508 were already found using them (on non-RHEL-10).

Yes, they increase the testing matrix a bit, but I would argue these are just as useful as with-gui variants, if not more.

Regarding missing /hardening/anaconda, the commit message explains it:

    /hardening/anaconda is not included because the upstream kickstarts
    are not UEFI compatible, ie.

        Failed to find a suitable stage1 device: EFI System Partition
        cannot be of type xfs.; EFI System Partition must be mounted on
        one of /boot/efi.; EFI System Partition cannot be of type lvmpv.

I'd like to merge these as broken for now (not run in any automation), because while they do work, it's usually only on the 3rd retry on RHEL-9.5, something is causing the VM to fail to start and/or get DHCP, with about 70% reproducibility rate.

Having these tests merged would help long-term debugging of the issue (so I didn't want to just delete my work), and I'll create a GH issue to make sure we don't forget, but I also feel uncomfortable adding more broken-ish tests to our regular pipelines, we already have image-builder for that .. 😁

Comment on lines 139 to 141
# https://github.com/ComplianceAsCode/content/issues/12508
/hardening/ansible/uefi/anssi_bp28_(enhanced|high)
status == 'error'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not relevant anymore? ComplianceAsCode/content#12514

Copy link
Contributor

@mildas mildas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To keep anaconda tc consistent with others, what about adding uefi.fmf there as well but disabled with reasoning pointing to Content issue regarding kickstart not compatible with uefi?

@comps
Copy link
Contributor Author

comps commented Oct 22, 2024

To keep anaconda tc consistent with others, what about adding uefi.fmf there as well but disabled with reasoning pointing to Content issue regarding kickstart not compatible with uefi?

I think that would make sense on the profile level, but probably not on the test type / variant level. Ie. we already do not have disabled with-gui tests for image-builder, because it's not meant to be used with GUI, apparently.

/hardening/anaconda is not included because the upstream kickstarts
are not UEFI compatible, ie.

    Failed to find a suitable stage1 device: EFI System Partition
    cannot be of type xfs.; EFI System Partition must be mounted on
    one of /boot/efi.; EFI System Partition cannot be of type lvmpv.

Signed-off-by: Jiri Jaburek <[email protected]>
@comps
Copy link
Contributor Author

comps commented Oct 22, 2024

I'll launch a full daily run on this, to make sure it didn't break anything.

edit: all green

@mildas mildas merged commit c670509 into main Oct 24, 2024
3 checks passed
@mildas mildas deleted the add_uefi_tests branch October 24, 2024 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Test on UEFI/non-UEFI
2 participants