Bug 1985022

Summary: NBDE client system role does not support servers with static IP addresses
Product: Red Hat Enterprise Linux 8 Reporter: Brian Smith <briasmit>
Component: rhel-system-rolesAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Martin Zelený <mzeleny>
Severity: high Docs Contact: Jan Fiala <jafiala>
Priority: high    
Version: 8.4CC: djez, gfialova, jafiala, lmiksik, mzeleny, nhosoi, pkettman, rmeggins, scorreia, spetrosi
Target Milestone: betaKeywords: Triaged
Target Release: 8.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: role:nbde_client
Fixed In Version: rhel-system-roles-1.16.2-1.el8 Doc Type: Enhancement
Doc Text:
.The NBDE client System Role supports systems with static IP addresses Previously, restarting a system with a static IP address and configured with the NBDE client System Role would change the system’s IP address. With this change, systems with static IP addresses are supported by the NBDE client System Role, and their IP addresses do not change after a reboot.
Story Points: ---
Clone Of:
: 2031555 2071011 (view as bug list) Environment:
Last Closed: 2022-05-10 14:12:08 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: 2031555, 2071011    

Description Brian Smith 2021-07-22 16:38:47 UTC
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

Comment 1 Sergio Correia 2021-07-22 17:01:04 UTC
(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

Comment 2 Rich Megginson 2021-07-29 21:23:39 UTC
@scorreia does https://github.com/linux-system-roles/nbde_client/pull/49 fix this bz?

Comment 3 Sergio Correia 2021-07-29 22:10:16 UTC
(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`.

Comment 4 Peter Kettmann 2021-09-17 13:51:53 UTC
Priority and severity set to High based on a discussion with Brian Smith (System roles PM).

Comment 6 Peter Kettmann 2021-11-04 14:47:02 UTC
Sergio, as this is planned for 8.6 can you please provide dev ack and ask qa to provide qa ack? Thanks.

Comment 40 errata-xmlrpc 2022-05-10 14:12:08 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 (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