https://bugzilla.suse.com/show_bug.cgi?id=1189879 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(lnussel@suse.com) -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c2 --- Comment #2 from Petr Vorel --- It's definitely not a problem to fix openQA test. I'm opening this bug to make sure it's wanted feature, because people for sure have in their scripts /boot/config-$(uname -r) as it has been there for years. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c4 --- Comment #4 from Ludwig Nussel --- It's %ghost so can be there or not. Rpm then makes sure it gets deleted on uninstall. Fedora's kernel-install(8) script for grub actually does link/copy the config file to /boot. The upstream kernel-install scripts do not handle that file. So I really wonder what the purpose of using the file in /boot would be. Does anyone know any script used in practice that uses it? And for what? The running kernel has it's config in /proc/config.gz. For building modules /lib/modules/$version/build/.config is the correct one to use. So if the %ghost entry is considered confusing I'd rather remove it than adding link. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c6 --- Comment #6 from Petr Vorel --- (In reply to Michal Suchanek from comment #5)

/boot/config-$(uname -r) is the place where the config is typically placed for distribution provided kernel. +1

@lnussel Although People have it in their custom scripts. And this is not only for some cross distro tools, even current SLES/Leap vs. openSUSE Tumbleweed users will be affected. Sure, solution is simple: f="/boot/config-$(uname -r)"; [ -f "$f" ] || f="/usr/lib/modules/$(uname -r)/config But users will think: why to break compatibility for no reason (again)? For cross distro tools you cannot rely on /proc/config.gz, because not all distros have CONFIG_IKCONFIG_PROC enabled.

It can be used for rebuilding the kernel with the same configuration.

It is not consumed by the bootloader or something so a symlink rather than hardlink would suffice.

+1 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1189881 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 Petr Vorel changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1190061 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c10 --- Comment #10 from Jiri Slaby --- (In reply to Martin Wilck from comment #9)

No offense, but these missing %ghost files create a lot of confusion. It's particularly confusing that some of the symlinks are created in %post, while others are not. That simply looks like an oversight on the part of the developers, even if it was done deliberately.

My intention definitely was: no undocumented changes. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c12 --- Comment #12 from Martin Wilck --- (In reply to Takashi Iwai from comment #11)

The fix is still missing?

Not sure which fix you mean, but Michal is working on a large-ish change of the kernel scriptlets in bug 1189841. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c14 --- Comment #14 from Martin Wilck --- The question is whether this bug here, and the ones Takashi mentioned, should be fixed *before* pushing the s-m-t changes as part of bug 1189841. They are arguably more urgent. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c16 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Flags|needinfo?(lnussel@suse.com) | --- Comment #16 from Ludwig Nussel --- The grub related script were fixed by Michael to read the new location. That fixes all linked bugs already. Thanks for that! It's the right solution IMO. I'll add the compat link back in addition. PR filed. Nevertheless script that rely on it should really be adjusted the new location. There is no promise how /boot will look like in the future. See also https://systemd.io/BOOT_LOADER_SPECIFICATION/ -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c19 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #19 from Ludwig Nussel --- (In reply to Martin Wilck from comment #17)

[...] I'm still waiting for a rationale why these symlinks should _not_ exist. Is it because /boot should be r/o? I suppose not, because then you couldn't create the sysctl.conf and other symlinks, either. I really see no other good reason. On the other hand, the absence of these files is likely not only to confuse users, but break scripts and software all over the place. These files have existed under /boot for as long as most of us can remember.

You mean symvers and symtypes? What tools use them? Fedora 34 also doesn't have them (only config and System.map left atm). Going forward the /boot as we know it is kind of redundant so there might be no need to even have it anymore IMO. All OS files are in /usr and boot stuff goes to the EFI boot partition that could be mounted only when writing it is needed. Anyway, pr for adding config link back was merged, thanks! -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c21 --- Comment #21 from Martin Wilck --- (In reply to Jiri Slaby from comment #20)

FTR, AFAICS, it was not (yet).

Ludwig submitted it to suse-module-tools, and I merged it yesterday. It's based on Michal's work to move all kernel scriptlets into s-m-t (boo#1189841). So this will fixed after the kernel migrates to the "external" scripting. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c23 --- Comment #23 from Martin Wilck --- There was a bug in my OBS submission (obsolete .obscpio file included) causing confusion. New sr#919089. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c26 --- Comment #26 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-ltp-commands@uefi_virtio-2G https://openqa.opensuse.org/tests/1943659 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c31 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #31 from Michal Suchanek --- Merged into Factory. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c35 --- Comment #35 from Swamp Workflow Management --- SUSE-RU-2021:3869-1: An update that has 8 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1189841,1189879,1190598,1191200,1191260,1191480,1191804,1191922 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Server for SAP 15-SP1 (src): suse-module-tools-15.1.23-3.19.1 SUSE Linux Enterprise Server 15-SP1-LTSS (src): suse-module-tools-15.1.23-3.19.1 SUSE Linux Enterprise Server 15-SP1-BCL (src): suse-module-tools-15.1.23-3.19.1 SUSE Linux Enterprise High Performance Computing 15-SP1-LTSS (src): suse-module-tools-15.1.23-3.19.1 SUSE Linux Enterprise High Performance Computing 15-SP1-ESPOS (src): suse-module-tools-15.1.23-3.19.1 SUSE Enterprise Storage 6 (src): suse-module-tools-15.1.23-3.19.1 SUSE CaaS Platform 4.0 (src): suse-module-tools-15.1.23-3.19.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189879 https://bugzilla.suse.com/show_bug.cgi?id=1189879#c37 --- Comment #37 from Swamp Workflow Management --- SUSE-RU-2021:3970-1: An update that has 8 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1189841,1189879,1190598,1191200,1191260,1191480,1191804,1191922 CVE References: JIRA References: Sources used: SUSE OpenStack Cloud Crowbar 9 (src): suse-module-tools-12.6.1-27.6.1 SUSE OpenStack Cloud Crowbar 8 (src): suse-module-tools-12.6.1-27.6.1 SUSE OpenStack Cloud 9 (src): suse-module-tools-12.6.1-27.6.1 SUSE OpenStack Cloud 8 (src): suse-module-tools-12.6.1-27.6.1 SUSE Linux Enterprise Server for SAP 12-SP4 (src): suse-module-tools-12.6.1-27.6.1 SUSE Linux Enterprise Server for SAP 12-SP3 (src): suse-module-tools-12.6.1-27.6.1 SUSE Linux Enterprise Server 12-SP4-LTSS (src): suse-module-tools-12.6.1-27.6.1 SUSE Linux Enterprise Server 12-SP3-LTSS (src): suse-module-tools-12.6.1-27.6.1 SUSE Linux Enterprise Server 12-SP3-BCL (src): suse-module-tools-12.6.1-27.6.1 SUSE Linux Enterprise Server 12-SP2-BCL (src): suse-module-tools-12.6.1-27.6.1 HPE Helion Openstack 8 (src): suse-module-tools-12.6.1-27.6.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.