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 1467907 - Clevis does not document its LUKS unlockers in the man pages
Summary: Clevis does not document its LUKS unlockers in the man pages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: clevis
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nathaniel McCallum
QA Contact: Jiri Jaburek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-05 13:32 UTC by Nathaniel McCallum
Modified: 2018-04-10 18:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 18:27:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0985 0 None None None 2018-04-10 18:27:44 UTC

Description Nathaniel McCallum 2017-07-05 13:32:02 UTC 
It would be helpful, for example, to know that for unlocking you need to install clevis-dracut or clevis-udisks2. Further, it would be helpful to know that after installing clevis-dracut on a preexisting system, you'll need to run dracut -f.
Comment 4 Nathaniel McCallum 2017-11-27 16:06:08 UTC 
The man page section is already fixed upstream. Here is the full text of the paragraph in question:


"After a reboot, Clevis will attempt to unlock all _netdev devices listed in /etc/crypttab when systemd prompts for their passwords. This implies that systemd support for _netdev is required."

What do you think is unclear in the phrase "_netdev devices listed in /etc/crypttab"?
Comment 5 Jiri Jaburek 2017-11-27 20:17:07 UTC 
(In reply to Nathaniel McCallum from comment #4)
> The man page section is already fixed upstream. Here is the full text of the
> paragraph in question:
> 
> 
> "After a reboot, Clevis will attempt to unlock all _netdev devices listed in
> /etc/crypttab when systemd prompts for their passwords. This implies that
> systemd support for _netdev is required."
> 
> What do you think is unclear in the phrase "_netdev devices listed in
> /etc/crypttab"?

A system administrator is likely to know the "_netdev" feature of fstab, but not the (new) "_netdev" feature of crypttab. This can lead to misunderstanding of "_netdev devices" as "devices mounted with _netdev in fstab", whereas the proper meaning is "devices with _netdev in crypttab".

This is not a major request or anything (which is why I didn't make a bug out of it), but IMO better wording would be;
"Clevis will attempt to unlock all devices listed in /etc/crypttab with the _netdev option specified, see crypttab(5), when systemd prompts for their passwords."

It is nitpicking a bit, but I've been in those situations several times.

Thanks.
Comment 8 errata-xmlrpc 2018-04-10 18:27:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0985
Note You need to log in before you can comment on or make changes to this bug.