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 1975929 - Network configuration from CMS config file is not applied
Summary: Network configuration from CMS config file is not applied
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: dracut
Version: 9.0
Hardware: s390x
OS: Linux
unspecified
high
Target Milestone: beta
: ---
Assignee: Lukáš Nykrýn
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks: 1942219 1971841 2027125
TreeView+ depends on / blocked
 
Reported: 2021-06-24 18:42 UTC by Jan Stodola
Modified: 2022-02-28 19:15 UTC (History)
11 users (show)

Fixed In Version: dracut-055-9.git20210812.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 21:57:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
[PATCH-dracut] cms: reload NetworkManager connections (1.44 KB, patch)
2021-08-04 07:41 UTC, Beniamino Galvani 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Github dracutdevs dracut pull 1582 0 None None None 2021-08-09 07:46:31 UTC

Description Jan Stodola 2021-06-24 18:42:44 UTC 
Description of problem:
When running installation on a z/VM s390x guests and the VM configuration is provided via a CMS config file, dracut doesn't configure networking properly. It looks like dracut/NM is trying to use dhcp, although static IPv4 configuration from the CMS config file should be used instead.

Version-Release number of selected component (if applicable):
RHEL-9.0.0-20210623.3
dracut-055-1.el9
NetworkManager-1.32.0-1.el9

How reproducible:
Always

Steps to Reproduce:
1. Have a z/VM s390x guest. Create a CMS configuration file.
2. Start the installation using the CMS config file by adding "CMSDASD=191 CMSCONFFILE=default.conf" to the kernel command line.

Actual results:
Network configuration from the CMS config file is not applied.

Expected results:
Network configuration from the CMS config file is applied, it is possible to start the installation.
Comment 3 Andrew Price 2021-07-23 11:00:31 UTC 
This is blocking GFS2/HA testing on s390x RHEL9. Is there a workaround?
Comment 4 David Tardon 2021-07-23 11:56:29 UTC 
Could you boot with rd.debug and attach boot log here?
Comment 5 Jan Stodola 2021-07-23 12:00:36 UTC 
(In reply to David Tardon from comment #4)
> Could you boot with rd.debug and attach boot log here?

See comment 1
(I will be on PTO next week, so I can do any additional testing when I'm back)
Comment 6 David Tardon 2021-07-27 12:40:17 UTC 
It's clear from the rdsosreport that the cms dracut module parses the config correctly. It produces /etc/cmdline.d/80-cms.conf with the following content:

ip=10.16.105.197::10.16.111.254:255.255.248.0:rtt6.s390.bos.redhat.com:enc900:none::
nameserver=10.11.5.19

that is then processed by NM.
Comment 7 Beniamino Galvani 2021-07-28 09:28:06 UTC 
Jan, the rdsosreport contains journal log only starting from second 9
after boot. Do you know why? Would it be possible to capture the full
boot log?

It seems to me that the issue is that "/sbin/cmsifup enc900", which
generates the NM connection, is called during the initqueue only after
NM has started and so the new generated connection does not have
effect.

The fix would be probably to explicitly call "nmcli connection up" on
the new connection, or "nmcli connection reload". I will try to
prepare a patch for that.

Is there a way I can easily test this scenario?
Comment 8 Beniamino Galvani 2021-08-04 07:41:36 UTC 
Created attachment 1810748 [details]
[PATCH-dracut] cms: reload NetworkManager connections

This (untested) dracut patch should help.
Comment 9 David Tardon 2021-08-05 11:45:52 UTC 
(In reply to Beniamino Galvani from comment #7)
> It seems to me that the issue is that "/sbin/cmsifup enc900", which
> generates the NM connection, is called during the initqueue only after
> NM has started and so the new generated connection does not have
> effect.

I think you're right. cmsifup is called from a udev rule, which means it must handle being run at any time. Moving back to dracut.
Comment 19 Jan Stodola 2021-08-19 17:28:39 UTC 
I can confirm this bug is fixed in dracut-055-9.git20210812.el9, compose RHEL-9.0.0-20210818.6, network configuration from CMS config file is successfully applied.
Comment 25 David Tardon 2022-02-28 19:15:34 UTC 
*** Bug 2052591 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.