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:
# /sbin/weak-modules --verbose --add-kernel 2.6.32-52.el6
Symvers dump file /boot/symvers-2.6.32-52.el6.gz not found

# ls -l /boot/symvers*gz
-rw-r--r--. 1 root root 161301 Jun 21 01:45 /boot/symvers-2.6.32-37.el6.x86_64.gz
-rw-r--r--. 1 root root 161201 Jul 21 18:27 /boot/symvers-2.6.32-52.el6.x86_64.gz


Version-Release number of selected component (if applicable):
module-init-tools 3.9-15.el6

How reproducible:
always


Steps to Reproduce:
1. install kmod
2. update kernel, or install new one
3. run weak-modules --verbose --add-kernel  

Actual results:
see above

Expected results:
weak-modules links are created, or the weak-modules says that the kernels are incompatible.

Additional info:
I am attaching a script session demonstrating the problem.
This is severe because it would prevent RHDUP from functioning properly.

opened issued tracker 1201243 for this bug.

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Martin, are you invoking weak-modules directly? It looks like you're calling it with the following value for the uname-r:

2.6.32-52.el6

Actually, in RHEL6, it should always include the architecture:

2.6.32-52.el6.x86_64

For example. Can you confirm, by looking at rpm -q --scripts kernel that your kernel is calling the correct script options? If you are doing this manually, please let me know why you need to call it without the full uname value.

Jon.

My bad, I'm sorry. User error :-/

I had been wondering why no weak-modules links had been created, and in order to find out, called weak-modules by hand - wrongly. I apologize for the noise.

Per comment #6, closing as not a bug.