Bugzilla – Bug 1227436
openQA did not catch regression https://github.com/openSUSE/snapper/issues/918
Last modified: 2024-07-12 12:12:55 UTC
Apparently openQA did not catch the regression caused by the latest libzypp update, see https://github.com/openSUSE/snapper/issues/918. A openQA test for this important feature (functionality of the snapper-zypp-plugin seems needed. That is also the case for all other SUSE distributions.
snapper stopped creating pre/post snapshots and dumps core: erlangen:~ # journalctl -b -p3 Jul 08 05:32:09 erlangen systemd-coredump[4538]: [🡕] Process 4536 (snapper-zypp-pl) of user 0 dumped core. Stack trace of thread 4536: #0 0x00007fc52d2949dc __pthread_kill_implementation (libc.so.6 + 0x949dc) #1 0x00007fc52d241176 raise (libc.so.6 + 0x41176) #2 0x00007fc52d228917 abort (libc.so.6 + 0x28917) #3 0x00007fc52d6adc4d n/a (libstdc++.so.6 + 0xadc4d) #4 0x00007fc52d6bf2ec n/a (libstdc++.so.6 + 0xbf2ec) #5 0x00007fc52d6ad7f5 _ZSt9terminatev (libstdc++.so.6 + 0xad7f5) #6 0x00007fc52d6bf578 __cxa_throw (libstdc++.so.6 + 0xbf578) #7 0x000055d955b6b249 n/a (snapper-zypp-plugin + 0x14249) #8 0x000055d955b69535 n/a (snapper-zypp-plugin + 0x12535) #9 0x00007fc52d22a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #10 0x00007fc52d22a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #11 0x000055d955b6b3c5 n/a (snapper-zypp-plugin + 0x143c5) ELF object binary architecture: AMD x86-64 Jul 08 05:32:09 erlangen systemd-coredump[4547]: [🡕] Process 4545 (boot-plugin) of user 0 dumped core. Stack trace of thread 4545: #0 0x00007faa94c949dc __pthread_kill_implementation (libc.so.6 + 0x949dc) #1 0x00007faa94c41176 raise (libc.so.6 + 0x41176) #2 0x00007faa94c28917 abort (libc.so.6 + 0x28917) #3 0x00007faa950adc4d n/a (libstdc++.so.6 + 0xadc4d) #4 0x00007faa950bf2ec n/a (libstdc++.so.6 + 0xbf2ec) #5 0x00007faa950ad7f5 _ZSt9terminatev (libstdc++.so.6 + 0xad7f5) #6 0x00007faa950bf578 __cxa_throw (libstdc++.so.6 + 0xbf578) #7 0x0000559a0366e697 n/a (boot-plugin + 0xc697) #8 0x0000559a0366cf67 n/a (boot-plugin + 0xaf67) #9 0x00007faa94c2a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #10 0x00007faa94c2a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #11 0x0000559a0366e725 n/a (boot-plugin + 0xc725) ELF object binary architecture: AMD x86-64 erlangen:~ #
(In reply to Arvin Schnell from comment #0) > Apparently openQA did not catch the regression caused by the latest > libzypp update, see https://github.com/openSUSE/snapper/issues/918. > > A openQA test for this important feature (functionality of the > snapper-zypp-plugin seems needed. > > That is also the case for all other SUSE distributions. Is somebody form your team going to implement the test? let me know otherwise
The bug even made it to reddit: https://old.reddit.com/r/openSUSE/comments/1dyrjms/snapper_stop_add_new_snapshot_after_install_update/
One way this could've been caught is the journal_check openQA test module. That's currently used on MicroOS, where the snapper plugin isn't used, and on JeOS images directly after boot. If it ran closer to the end of the test run, it would've complained about the crashed processes. Ideally openQA would have an explicit check that zypper in/rm/up/dup create snapshots though.