Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1981055[details]
Log created by weak-modules script
Description of problem:
Marvell Netxtreme2 RPM has 5 modules bnx2, cnic, bnx2x, bnx2i, bnx2fc
During kernel upgrade the weak links are created for modules that are compatible (or don't have KABI breakage)
When KABI breakage is detected, that module is skipped. But other modules from same RPM are processed and weak-links are created for them.
These modules are interdependent. And they should be either processed or rejected as a set.
As a result of above behavior of weak-modules script, OS ends up have a set of non-compatible set modules (In this case, bnx2x and bnx2i are Inbox and rest of them are OOB)
The OS fails to boot and goes into dracut shell.
Version-Release number of selected component (if applicable):
netxtreme2-7.15.17-1
How reproducible:
Always
Steps to Reproduce:
1. Install RHEL8.7 OS
2. Install attached RPM which is built against RHEL8.7 GA kernel.
3. Update the system kernel to RHEL8.8 GA
4. Observe the issue.
Actual results:
System fails to boot and goes in dracut shell.
Expected results:
System should come up with Inbox modules.
Additional info:
Log created by weak-modules script attached.
Hello @esyr - do you have any update on this issue?
Comment 8Eugene Syromiatnikov
2023-08-22 09:13:42 UTC
(In reply to Sarang Radke from comment #7)
> Hello @esyr - do you have any update on this issue?
My apologies for the late reply. Currently, this logic is intentional, as there are scenarios where this behaviour is expected/desired, but if it is the case that the kmods are part of a single RPM, the situation might be improved.
Hello Eugene,
Yes, the modules in discussion here are part of single KMOD RPM.
Due to the current processing logic, we end up with few modules as inbox and few as OOB. Which are incompatible as a set and system fails to boot.
Please suggest how to go about this.
Comment 10Nilesh Javali (Marvell)
2023-09-11 15:11:27 UTC
Comment 12RHEL Program Management
2023-09-25 21:19:43 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 13RHEL Program Management
2023-09-25 21:58:52 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 14Red Hat Bugzilla
2024-01-24 04:25:37 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Created attachment 1981055 [details] Log created by weak-modules script Description of problem: Marvell Netxtreme2 RPM has 5 modules bnx2, cnic, bnx2x, bnx2i, bnx2fc During kernel upgrade the weak links are created for modules that are compatible (or don't have KABI breakage) When KABI breakage is detected, that module is skipped. But other modules from same RPM are processed and weak-links are created for them. These modules are interdependent. And they should be either processed or rejected as a set. As a result of above behavior of weak-modules script, OS ends up have a set of non-compatible set modules (In this case, bnx2x and bnx2i are Inbox and rest of them are OOB) The OS fails to boot and goes into dracut shell. Version-Release number of selected component (if applicable): netxtreme2-7.15.17-1 How reproducible: Always Steps to Reproduce: 1. Install RHEL8.7 OS 2. Install attached RPM which is built against RHEL8.7 GA kernel. 3. Update the system kernel to RHEL8.8 GA 4. Observe the issue. Actual results: System fails to boot and goes in dracut shell. Expected results: System should come up with Inbox modules. Additional info: Log created by weak-modules script attached.