RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1802508 - "dracut -f" is used instead of "dracut -f --regenerate-all" in Clevis configuration procedure
Summary: "dracut -f" is used instead of "dracut -f --regenerate-all" in Clevis configu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Security_Guide
Version: 7.7
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Mirek Jahoda
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-13 10:28 UTC by Renaud Métrich
Modified: 2023-03-24 17:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-06 09:30:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Renaud Métrich 2020-02-13 10:28:44 UTC 
Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide

Section Number and Name: 4.10.6. Configuring Manual Enrollment of Root Volumes

Describe the issue: "dracut -f --regenerate-all" shall be specified instead of "dracut -f" (3 places in this paragraph).
Indeed, "dracut -f" only rebuilds the initramfs of the currently running kernel, which will end up to not have the other initramfs present on the system updated, causing the system to not boot using Clevis upon reboot, typically if the currently running kernel is not the latest one.

Example scenario where the issue will be hit:
1. Boot the system with current kernel "A"
2. Update the system to latest, kernel "B"
3. Configure clevis and execute "dracut -f" as part of the procedure
--> kernel "B"'s initramfs won't contain Clevis code.


Suggestions for improvement: 

Replace "dracut -f" by "dracut -f --regenerate-all" (3 occurrences)


Additional information: 

Additionally, there is a typo in the example under "Important" section, please fix this also:

ORIGINAL CODE:
~~~
~]# cat /etc/dracut.conf.d/static_ip.conf
kernel_cmdline="ip= 10.0.0.103 netmask=255.255.252.0 gateway=10.0.0.1 nameserver=10.0.0.1"
~~~

EXPECTED CODE: (no space between "ip= " and "10.0.0.103")
~~~
~]# cat /etc/dracut.conf.d/static_ip.conf
kernel_cmdline="ip=10.0.0.103 netmask=255.255.252.0 gateway=10.0.0.1 nameserver=10.0.0.1"
~~~
Comment 4 Mirek Jahoda 2020-03-06 09:30:40 UTC 
The fix is available on the Customer Portal:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/security_guide/index#sec-Configuring-Manual-Enrollment

Thank you for your contribution to the quality of the RHEL documentation.
Note You need to log in before you can comment on or make changes to this bug.