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.

Description of problem:
The NBDE client system role does not work properly with RHEL 8 and RHEL 7 servers using static IP addresses

Version-Release number of selected component (if applicable):
rhel-system-roles-1.0.1-1.el8.noarch

How reproducible:
Every time


Steps to Reproduce:
1. Run NBDE client role against RHEL 8 and RHEL 7 systems which have a static IP address configured


Actual results:
- The dracut configuration doesn't get updated with static IP address info
- When rebooting the systems, if DHCP is available, a DHCP address is assigned and the NBDE unlocking works properly
- However, the systems are then booted up with the DHCP address rather than their static IP address previously configured
- Result is systems unexpectedly have their IP address change when rebooted. 

Expected results:
- NBDE system role works with systems with static IP addresses
- When systems with static IP addresses are rebooted, they retain their static IP address


Additional info:
Related, however this does not appear to solve this issue:  https://github.com/linux-system-roles/nbde_client/pull/49

(In reply to Brian Smith from comment #0)

[...]

> 
> Additional info:
> Related, however this does not appear to solve this issue: 
> https://github.com/linux-system-roles/nbde_client/pull/49

Right, this is required to have network at all, but it won't resolve this particular issue.
We will have to configure networking similar to what is being requested in https://github.com/linux-system-roles/nbde_client/issues/22

@scorreia does https://github.com/linux-system-roles/nbde_client/pull/49 fix this bz?

(In reply to Rich Megginson from comment #2)
> @scorreia does
> https://github.com/linux-system-roles/nbde_client/pull/49 fix this bz?

No, it does not. What that issue will do is enable networking in the initramfs -- this is a step required since clevis 15 --, but for people using static IP, this needs to be setup somehow, e.g. using an `ip="..." parameter`.

Priority and severity set to High based on a discussion with Brian Smith (System roles PM).

Sergio, as this is planned for 8.6 can you please provide dev ack and ask qa to provide qa ack? Thanks.

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 (rhel-system-roles 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-2022:1896