Bug 1853651

Summary: Rebase clevis for better support of generic initrds and network-less machines
Product: Red Hat Enterprise Linux 8 Reporter: Jonathan Lebon <jlebon>
Component: clevisAssignee: Sergio Correia <scorreia>
Status: CLOSED ERRATA QA Contact: Martin Zelený <mzeleny>
Severity: unspecified Docs Contact: Mirek Jahoda <mjahoda>
Priority: medium    
Version: 8.3CC: dapospis, miabbott, mjahoda, mzeleny, rsroka
Target Milestone: rcKeywords: Triaged
Target Release: 8.3Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: clevis-15-1.el8 Doc Type: Enhancement
Doc Text:
.Clevis no longer automatically adds `rd.neednet=1` Clevis now correctly produces a generic `initrd` (initial ramdisk) without host-specific configuration options by default. As a result, Clevis no longer automatically adds the `rd.neednet=1` parameter to the kernel command line. If your configuration uses the previous functionality, you can either enter the `dracut` command with the `--hostonly-cmdline` argument or create the `clevis.conf` file in the `/etc/dracut.conf.d` and add the `hostonly_cmdline=yes` option to the file. A Tang binding must be present during the `initrd` build process.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 15:41:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1887836    

Description Jonathan Lebon 2020-07-03 13:19:04 UTC
For RHCOS support of LUKS-on-root, we would like to use Clevis with the upstream patches from https://github.com/latchset/clevis/pull/211 so that by default networking not always turned on in the initramfs.

Comment 1 Jonathan Lebon 2020-07-03 13:43:21 UTC
Hmm, I guess this is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1818780, though that one has already progressed with v13. I suppose we could do with just a backport of the upstream patches from that PR if you'd prefer that. In that case, we can reuse this RHBZ to track the backport. Or if you'd rather do another full rebase, you can reuse this ticket or the other one as is easier for you!

Comment 14 errata-xmlrpc 2021-05-18 15:41:00 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 (clevis bug fix and enhancement update), 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-2021:1808