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):
Steps to Reproduce:
1. install kmod
2. update kernel, or install new one
3. run weak-modules --verbose --add-kernel
weak-modules links are created, or the weak-modules says that the kernels are incompatible.
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:
Actually, in RHEL6, it should always include the architecture:
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.
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.