Repository navigation
test(images): validate kernel FIPS boot options #19023
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
Merged
Tobias Brick (tobiasb-ms)
merged 2 commits into
microsoft:4.0
from
tobiasb-ms:tobiasb-ms/fips-marketplace-image-tests
Oct 8, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| # SPDX-License-Identifier: MIT | ||
| """Validate kernel FIPS boot configuration.""" | ||
|
|
||
| from __future__ import annotations | ||
|
|
||
| from typing import TYPE_CHECKING | ||
|
|
||
| import pytest | ||
| from utils.parsers import parse_boot_entry_kernel_options | ||
|
|
||
| if TYPE_CHECKING: | ||
| from pathlib import Path | ||
|
|
||
|
|
||
| @pytest.mark.require_capability("machine-bootable") | ||
| def test_kernel_fips_matches_image_variant( | ||
| boot_entry_option_lines: dict[Path, list[str]], | ||
| capabilities: set[str], | ||
| ) -> None: | ||
| expected_fips_options = ["fips=1"] if "fips-enabled" in capabilities else [] | ||
| options_by_entry = parse_boot_entry_kernel_options(boot_entry_option_lines) | ||
|
|
||
| for entry, options in options_by_entry.items(): | ||
| fips_options = [ | ||
| option for option in options if option.partition("=")[0] == "fips" | ||
| ] | ||
| assert fips_options == expected_fips_options, ( | ||
| "Kernel FIPS options do not match the image's capabilities " | ||
| f"in {entry}" | ||
| ) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion(non-blocking): I am not very comfortable with the implicit selection of whichever boot configs are found in the image. Much like image capability driving what to expect in the image can't we drive this fixture the same way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It feels like we should check everything and then caller can decide what to do. In our case, it feels very unlikely that any images will ever actually have multiple entrieson a freshly-baked image so we should be safe. But either way, in principle, I'd prefer to cover them all.
Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your argument is valid and that anticipation is why the comment is non-blocking. To illustrate what I am trying to convey if we look at the
rootfsfixture, it checks the image type and does the mounting in different ways. Similarly, since we know what kind of image we are inspecting, we can look at the deterministic loader configuration path for that image. This definitely does not break the test and it is your choice whether to make a change.