This bug was initially created as a copy of Bug #1964691
I am copying this bug because: Bug #1964691 related only to RHVH. While working on that bug we realized that it might be possible to concisely document how to enable RHEL hosts based on the .yaml file that is used to enable the DISA STIG profile during the self-hosted engine deployment.
---- Description of Bug #1964691 ----
In RHV 4.3 we have announced the support of DISA-STIG profile availability for RHV Deployments:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/installing_red_hat_virtualization_as_a_standalone_manager_with_local_databases/index#disa-stig-for-red-hat-linux-7-assembly-securing-rhv
With the migration to RHEL8, this does not work anymore on RHV 4.4 and that's why it is a regression for the customers that used this functionality or plan to use it on RHV 4.4.
This might be a test only bz + documentation to follow, maybe more then just test only.
I see today these 2 related BZs that may mean this is a test only BZ:
Bug#1930550 - RHVH upgrade failed via engine with STIG profile selected
Bug#1950239 - Failed to authenticate ssh session with host during hosted engine deployment with STIG profile
After opening this, Asaf found that the DISA STIG policy is already part of the normal RHEL Anaconda installer.
So I just added a link to the relevant RHEL doc and merged this.