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 1762028 - clevis-dracut sets rd.neednet=1 without obvious reason
Summary: clevis-dracut sets rd.neednet=1 without obvious reason
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: clevis
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Sergio Correia
QA Contact: Martin Zelený
URL:
Whiteboard:
: 1784079 (view as bug list)
Depends On:
Blocks: 1760262
TreeView+ depends on / blocked
 
Reported: 2019-10-15 21:34 UTC by Dominik Holler
Modified: 2023-03-24 15:41 UTC (History)
5 users (show)

Fixed In Version: clevis-11-7.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:37:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
terminal log of reproducer (13.92 KB, text/plain)
2019-10-15 21:34 UTC, Dominik Holler
no flags Details
Proposed patch to make clevis-dracut add rd.neednet=1 only when there are tang devices bound (1.54 KB, patch)
2019-12-01 13:40 UTC, Sergio Correia
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-30368 0 None None None 2021-08-30 11:57:09 UTC
Red Hat Knowledge Base (Solution) 3017441 0 None None None 2019-10-25 12:59:53 UTC
Red Hat Product Errata RHEA-2020:1595 0 None None None 2020-04-28 15:37:22 UTC

Description Dominik Holler 2019-10-15 21:34:42 UTC
Created attachment 1626194 [details]
terminal log of reproducer

Description of problem:
Looks like clevis-dracut sets rd.neednet=1 always. This might trigger problems like bug 1760262

Version-Release number of selected component (if applicable):
clevis-dracut-11-2.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Ensure that "dracut --print-cmdline" does not contain rd.neednet=1
2. dnf install clevis-dracut
3. "dracut --print-cmdline" contains rd.neednet=1

Actual results:
"dracut --print-cmdline" contains rd.neednet=1

Expected results:
"dracut --print-cmdline" does not contain rd.neednet=1

Additional info:

Comment 1 Dominik Holler 2019-11-04 14:41:14 UTC
Please note that RHEL 7.7 is affected, too.

Comment 2 Martin Zelený 2019-11-22 14:05:58 UTC
Simple test will need to be created.

Comment 3 Martin Zelený 2019-11-22 14:52:13 UTC
AC:

Installation of clevis-dracut package does not automatically add rd.neednet=1 to the dracut cmdline.

Comment 4 Sergio Correia 2019-12-01 13:40:06 UTC
Created attachment 1641038 [details]
Proposed patch to make clevis-dracut add rd.neednet=1 only when there are tang devices bound

Comment 6 Barry 2019-12-05 12:17:07 UTC
I think I am being affected by this bug on RHEL 8.0 

One caveat though is I am bound to both tang server and have a password bound as well. (The desired configuration is to boot automatically if tang is present, otherwise use password to boot). However we have noticed that if network is not present then boot hangs after accepting password. Eventually it drops us into dracut shell where we only need to exit the dracut shell to continue to boot normally - but it is annoying. 

So my question is: In this configuration with both tang + password, what will the effects be of removing "rd.neednet=1"? Will the desired configuration above still work?

Comment 7 Sergio Correia 2019-12-07 13:46:41 UTC
(In reply to Barry from comment #6)
> I think I am being affected by this bug on RHEL 8.0 
> 
> One caveat though is I am bound to both tang server and have a password
> bound as well. (The desired configuration is to boot automatically if tang
> is present, otherwise use password to boot). However we have noticed that if
> network is not present then boot hangs after accepting password. Eventually
> it drops us into dracut shell where we only need to exit the dracut shell to
> continue to boot normally - but it is annoying. 
> 
> So my question is: In this configuration with both tang + password, what
> will the effects be of removing "rd.neednet=1"? Will the desired
> configuration above still work?

Hi Barry. We will not be removing rd.neednet=1. What happens is right now it's added unconditionally: if we have the clevis-dracut package installed and generate a new initramfs, dracut cmdline will contain rd.neednet=1, always.
This may cause confusion in situations where people would not be expecting any such changes, considering they had not added any tang bindings, for instance. 

With the change available in clevis-11-7.el8, when generating the initramfs, we will check whether any of the devices is bound to tang; if we have any such devices, we will then add rd.neednet=1 as we did before. If no devices are bound to tang, we will not add rd.neednet to dracut cmdline. So your use case of having tang + a password will not see any changes. You may want to open a separate bug to track the issue you describe with the boot hanging after accepting the password.

Comment 8 Barry 2019-12-07 13:56:20 UTC
Many thanks for the clear explanation. I will open new issue for my specific case.

Comment 12 Renaud Métrich 2019-12-17 07:22:02 UTC
*** Bug 1784079 has been marked as a duplicate of this bug. ***

Comment 14 errata-xmlrpc 2020-04-28 15:37:11 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/RHEA-2020:1595


Note You need to log in before you can comment on or make changes to this bug.