Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html/provisioning_guide/index
or
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html/managing_hosts/index

's/6\.10/6.10/' for both URLs above

Section Number and Name:
n/a

Describe the issue:
BZ1931316 introduced a new host/hostgroup/global parameter `encrypt_grub`. If this parameter is defined, the host's bootloader will be encrypted.
Documentation does not mention this parameter at all. It would be good to have the parameter documented.

Also, please ensure that the `grub_pass` macro is also documented as it was modified within the fix for the BZ1931316.

Suggestions for improvement:
Document the new parameter

Additional information:

Published in 6.10
Have some champagne