Bugzilla – Bug 1227457
Snapper error message after choosing System's Log in Yast via the shell
Last modified: 2024-07-08 12:02:04 UTC
Created attachment 875913 [details] y2logs I wanted to test/use Yast via the commandline/shell (in openSUSE Tumbleweed) since a longer time. I have done the following steps: 1) Open the terminal 2) Enter yast 3) Choose "Miscellaneous" 4) Choose "System's log" Yast has been closed shortly with the message: Server-side plugin '/usr/lib/snapper/plugins/10-sdbootutil.snapper' failed. Yast will be reopened with the log file /var/log messages. The error is appearing after every call of this Yast module. The yast log is attached.
Created attachment 875914 [details] messages
Whatever happened here, I am very sure it's not the fault of that YaST journal module. Rather, it's probably something that happened just before that, and calling any YaST module just made the problem visible: As you know, we are creating a pre-snapshot when starting any of them, and a post-snapshot when they are finished. This is done in the YaST startup script: https://github.com/yast/yast-yast2/blob/master/scripts/yast2#L187-L205
On my TW VM: >> [sh @ balrog-tw-dev] ~ 1 % ls -l /usr/lib/snapper/plugins >> >> total 8 >> -rwxr-xr-x 1 root root 7614 Jun 7 04:13 grub >> >> >> [sh @ balrog-tw-dev] ~ 2 % rpm -qf /usr/lib/snapper/plugins/grub >> >> grub2-snapper-plugin-2.12-20.1.noarch >> >> >> [sh @ balrog-tw-dev] ~ 3 % sudo zypper search "*snapper*" | grep plug >> >> i | grub2-snapper-plugin | Grub2's snapper plugin | package >> | python3-dnf-plugin-snapper | Snapper Plugin for DNF | package >> | sdbootutil-snapper | plugin script for snapper | package >> i | snapper-zypp-plugin | A zypp commit plugin for calling snapper | package >> >> >> [sh @ balrog-tw-dev] ~ 4 % osc maintainer -e sdbootutil-snapper >> >> Defined in project: devel:microos >> bugowner of sdbootutil-snapper : >> rbrown@suse.com >> >> maintainer of sdbootutil-snapper : >> lnussel@suse.com, kukuk@suse.com, rbrown@suse.com, fvogt@suse.com, dcermak@suse.com, -
As usual, please ALWAYS attach y2logs generated with the supplied 'save_y2logs' script. I am not going to reverse-engineer all that stuff that would be helpful here from just a lone y2logs file. It frustrates me to no end that I have to keep telling this even to people who have been working with the system for so many years. https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_attached_/var/log/YaST2/y2log_to_a_YaST2_bug,_and_still_I_am_asked_to_attach_y2logs._Why? In this case, I would have looked at the zypper history, the rpm-qa file and the storage setup in storage/ and storage-inst/. One suspicious thing here, though: >> y2-01-partitioner.log: 2022-04-09 17:18:11 <1> linux.fritz.box(3760) [Ruby] >> y2storage/storage_manager.rb(configure_snapper?):513 >> Not a fresh installation. Don't configure Snapper. >> >> y2-06-partitioner.log: 2022-06-09 13:57:16 <1> linux.fritz.box(11117) [Ruby] >> y2storage/storage_manager.rb(configure_snapper?):513 >> Not a fresh installation. Don't configure Snapper.
-> sdbootutil-snapper maintainer.
sdbootutil actual maintainer
Hi Sarah, what bootloader are you using? Is this a fresh install?
That is no fresh installation. I have got this system based on openSUSE Tumbleweed since 1.5 years. Yesterday I did my last Tumbleweed upgrade and it is continuously reproducible. Bootloader: > rpm -qa grub2 grub2-2.12-20.1.x86_64
(In reply to Stefan Hundhammer from comment #2) > Whatever happened here, I am very sure it's not the fault of that YaST > journal module. Rather, it's probably something that happened just before > that, and calling any YaST module just made the problem visible: As you > know, we are creating a pre-snapshot when starting any of them, and a > post-snapshot when they are finished. > > This is done in the YaST startup script: > > https://github.com/yast/yast-yast2/blob/master/scripts/yast2#L187-L205 You are right. I have checked it now with the "Time" module. That is happening there also.
Created attachment 875938 [details] latest y2logs > sudo zypper search "*snapper*" | grep plug i | grub2-snapper-plugin | Grub2's snapper plugin | Paket | python3-dnf-plugin-snapper | Snapper Plugin for DNF | Paket i | sdbootutil-snapper | plugin script for snapper | Paket i | snapper-zypp-plugin | Ein Modul das es zypp ermöglicht Installationsinformationen an Snapper zu senden | Paket | snapper-zypp-plugin-debuginfo | Debug information for package snapper-zypp-plugin | Paket Now I have created y2logs with save_y2logs
Perhaps I should add the hint, that I have used mostly zypper for installations in the past on this system and I have used snapper also manually (outside of the yast universum) for saving my own config changes.
(In reply to Sarah Kriesch from comment #8) > That is no fresh installation. I have got this system based on openSUSE > Tumbleweed since 1.5 years. > Yesterday I did my last Tumbleweed upgrade and it is continuously > reproducible. > > Bootloader: > > rpm -qa grub2 > grub2-2.12-20.1.x86_64 In that case, to resolve your issue, remove the sdbootutil. It should not be installed. Be careful to not remove grub2 by accident. It should not appear as a candidate to removal, but double check that "zypper rm sdbootutil" will remove stuff like some sdbootutil subpackages or "dracut-pcr-signature".
(In reply to Richard Brown from comment #6) > sdbootutil actual maintainer Please update the package metadata in OBS / IBS accordingly; see comment #3.
> sudo zypper rm sdbootutil Installierte Pakete werden gelesen... Paketabhängigkeiten werden aufgelöst... Die folgenden 2 Pakete werden GELÖSCHT: sdbootutil sdbootutil-snapper 2 zu entfernende Pakete. Package install size change: | 0 B required by to be installed packages -52,2 KiB | - 52,2 KiB released by to be removed packages Backend: classic_rpmtrans Fortfahren? [j/n/v/...? zeigt alle Optionen] (j): j (1/2) sdbootutil-1+git20240514.56dc89c-1.1.x86_64 wird entfernt ....................................[fertig] (2/2) sdbootutil-snapper-1+git20240514.56dc89c-1.1.x86_64 wird entfernt ............................[fertig] Nach-Transaktions-Skripte werden ausgeführt ........................................................[fertig]
The error message has been disappeared. Thank you!
I will close it, but to double check: you are using btrfs right?
Yes. I am using btrfs. That has been chosen as a default setting during the first installation.