[Bug 1189881] New: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available
https://bugzilla.suse.com/show_bug.cgi?id=1189881 Bug ID: 1189881 Summary: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-defaul t not available Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: gp@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Running zypper dup on my Tumbleweed machine, I noticed the following in the logs: (121/203) Installing: kernel-default-5.13.12-2.1.x86_64 ....[done] Additional rpm output: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available It is probably benign, but still a bit confusing/worrisome. What do we want to tell users here (that would be actionable)? And/or is this indicative of some problem with the upgrade as such? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c1 Martin Wilck <martin.wilck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gp@suse.com Flags| |needinfo?(gp@suse.com) --- Comment #1 from Martin Wilck <martin.wilck@suse.com> --- This warning is emitted because there is no file /boot/symvers-5.13.12-2-default.gz, but a KMP is installed, and without the symvers weak-module2 can't check reliably for unresolved symbols. This file has indeed been moved to /usr/lib/modules/5.13.12-2-default/symvers.gz. However, the kernel-default package claims to contain a symlink
/boot/symvers-5.13.12-2-default.gz -> ../usr/lib/modules/5.13.12-2-default/symvers.gz
This symlink is missing after installation. It seems that it's just packaged as a ghost file, but the link is never created. The %post scripts actually only create links for vmlinuz, sysctl.conf, and System.map. Anyway I need to support this in weak-modules2. Please try again with s-m-t from OBS home:mwilck:suse-module-tools/suse-module-tools. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c2 --- Comment #2 from Martin Wilck <martin.wilck@suse.com> --- @Michal, it seems strange that these files show up in the file listing of kernel-default but not in the file system. You see the missing files only with "rpm -Vv kernel-default"; "rpm -V" alone shows no error. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c3 --- Comment #3 from Martin Wilck <martin.wilck@suse.com> --- @Gerald, that updated suse-module-tools package from my home project contains a new debug feature I created just recently. Please set the environment variable WM2_VERBOSE=2 before installing the kernel with zypper. The warning should be gone. In any case, please attach the output here.
WM2_VERBOSE=2 zypper in --force kernel-default-5.13.12-2.1
-- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c4 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1189879 --- Comment #4 from Michal Suchanek <msuchanek@suse.com> --- (In reply to Martin Wilck from comment #2)
@Michal, it seems strange that these files show up in the file listing of kernel-default but not in the file system. You see the missing files only with "rpm -Vv kernel-default"; "rpm -V" alone shows no error.
Yes, this is a problem for a number of files after usrmerge -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c5 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(gp@suse.com) | --- Comment #5 from Gerald Pfeifer <gp@suse.com> --- Unfortunately the issue no longer reproduces if I force reinstallation with `zypper in -f kernel-default-5.13.12-2.1.x86_64`. Here is what's installed currently: % rpm -qa | grep kernel-default | sort kernel-default-5.13.12-2.1.x86_64 kernel-default-5.13.8-1.1.x86_64 kernel-default-devel-5.13.12-2.1.x86_64 Since I have not rebooted into that new kernel yet I removed it via `zypper rm kernel-default-5.13.12-2.1.x86_64` and then installed it again. That reproduces the issue. Good. Next I installed the version of suse-module-tools from home:mwilck. The original problem went away, alas I now got a different one: Additional rpm output: warning: %post(kernel-default-5.13.12-2.1.x86_64) scriptlet failed, exit status 1 Repeating again, removing the kernel package and then running WM2_VERBOSE=2 zypper in kernel-default-5.13.12-2.1 either warning is gone. Here is the output: === snip ==== Additional rpm output: DEPMOD=/usr/sbin/depmod LSINITRD=/usr/lib/module-init-tools/lsinitrd-quick find_kmps: looking at v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 check_kmp: v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 contains modules for 5.13.8-1-default check_kmp: v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 contains: v4l2loopback.ko find_kmps: kmps found: v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 kernel_changed: checking v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 for 5.13.12-2-default kmp_is_present: kmp=v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 krel=5.13.12-2-default => 1 previous_version_of_kmp: kmp=v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 krel=5.13.12-2-default => basenames_are_unique: v4l2loopback-kmp-default-0.12.5_k5.13.8_1-5.29 is unique in /var/tmp/weak-modules2.Eg6Kgd/5.13.12-2-default add_kmp_modules: added /lib/modules/5.13.8-1-default/updates/v4l2loopback.ko to 5.13.12-2-default has_unresolved_symbols: found /usr/lib/modules/5.13.12-2-default/symvers.gz ==== snap ==== -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c6 --- Comment #6 from Martin Wilck <martin.wilck@suse.com> --- (In reply to Michal Suchanek from comment #4)
Yes, this is a problem for a number of files after usrmerge
Is anyone working on fixing it? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c7 --- Comment #7 from Martin Wilck <martin.wilck@suse.com> --- (In reply to Gerald Pfeifer from comment #5)
Next I installed the version of suse-module-tools from home:mwilck. The original problem went away, alas I now got a different one:
Additional rpm output: warning: %post(kernel-default-5.13.12-2.1.x86_64) scriptlet failed, exit status 1
Repeating again, removing the kernel package and then running WM2_VERBOSE=2 zypper in kernel-default-5.13.12-2.1 either warning is gone.
I've observed this, too. Scriptlet fails for unknown reason, only the first time around. Very confusing. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c8 --- Comment #8 from Martin Wilck <martin.wilck@suse.com> --- (In reply to Martin Wilck from comment #7)
I've observed this, too. Scriptlet fails for unknown reason, only the first time around. Very confusing.
Ludwig fixed it in https://github.com/openSUSE/suse-module-tools/pull/30 Thanks! -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c9 --- Comment #9 from Martin Wilck <martin.wilck@suse.com> --- Factory request sr#915041 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c10 --- Comment #10 from Martin Wilck <martin.wilck@suse.com> --- The error message warning: %post(kernel-default-5.13.12-2.1.x86_64) scriptlet failed, exit status 1 May actually indicate that no initrd has been built for the kernel just installed. This is of course potentially fatal. I'll post a warning on the factory ML. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881 https://bugzilla.suse.com/show_bug.cgi?id=1189881#c12 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby@suse.com Resolution|--- |FIXED --- Comment #12 from Jiri Slaby <jslaby@suse.com> --- SO I assume this is fixed. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com