Bug 1975929
| Summary: | Network configuration from CMS config file is not applied | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jan Stodola <jstodola> | ||||
| Component: | dracut | Assignee: | Lukáš Nykrýn <lnykryn> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Frantisek Sumsal <fsumsal> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 9.0 | CC: | anprice, atragler, bgalvani, cmackows, dracut-maint-list, dtardon, fsumsal, lrintel, rkhan, sukulkar, till | ||||
| Target Milestone: | beta | Keywords: | Bugfix, Patch, Triaged | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | s390x | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | dracut-055-9.git20210812.el9 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-12-07 21:57:54 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: | 1942219, 1971841, 2027125 | ||||||
| Attachments: |
|
||||||
|
Description
Jan Stodola
2021-06-24 18:42:44 UTC
This is blocking GFS2/HA testing on s390x RHEL9. Is there a workaround? Could you boot with rd.debug and attach boot log here? (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) 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. 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? Created attachment 1810748 [details]
[PATCH-dracut] cms: reload NetworkManager connections
This (untested) dracut patch should help.
(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. 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. *** Bug 2052591 has been marked as a duplicate of this bug. *** |