Fix missing OVAL in some of RHEL 8 rules #4927
Merged
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.
Description:
Some of the rules in RHEL 8 becnhmark which aren't part of any RHEL 8 profile don't contain OVALs. This usually happens when OVAL hasn't been written yet. That's fine, but sometimes it's because of wrong prodtype elements or platform elements in OVAL or their mismatch. In this PR we don't add new OVALs but we try to address the second problem for some of the rules.
Read commit messages of each commit for specific details.
Rationale:
Users can add the rules to their profiles by tailoring, but if the rule is missing OVAL it has limited usability for them.