[Bug 1111786] New: quit() tries to remove current snapshot
http://bugzilla.suse.com/show_bug.cgi?id=1111786 Bug ID: 1111786 Summary: quit() tries to remove current snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kubic Assignee: iforster@suse.com Reporter: kukuk@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 785936 --> http://bugzilla.suse.com/attachment.cgi?id=785936&action=edit transactional-update.log g126.suse.de is running openSUSE Kubic with nightly automatic updates and reboots via rebootmgrd. In the logs I saw know: 2018-10-13 00:36 Trying to rebuild kdump initrd 2018-10-13 00:36 transactional-update finished - rebooting machine 2018-10-13 00:36 Removing snapshot #26... Deleting snapshot failed. 2018-10-13 00:36 Removing snapshot #25... 2018-10-13 00:36 transactional-update finished That's the "quit()" routine, why does it thinks it has to remove the current snapshot? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c1 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk@suse.com Flags| |needinfo?(kukuk@suse.com) --- Comment #1 from Ignaz Forster <iforster@suse.com> --- quit() is called when prematurely exiting the application, so it will try to revert everything it has done. On successful completion the teardown() routine is used instead. Is this error happening with the upstream transactional-update, or is this a modified version? I've just verified that every time quit() is called an error message is printed, so the attached log should not be possible... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c2 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kukuk@suse.com) | --- Comment #2 from Thorsten Kukuk <kukuk@suse.com> --- g126:~ # rpm -qi transactional-update Name : transactional-update Version : 2.6 Release : 2.1 Architecture: x86_64 Install Date: Tue Oct 2 07:12:02 2018 It's what currently is in Factory, it was a plain openSUSE Kubic installation. And I agree that this log should not be possible,that's why I created the bug ... Could it be that the log file is not written in the correct order? reboot_via_systemd() { log_info "transactional-update finished - rebooting machine" sync systemctl reboot |& tee -a ${LOGFILE} exit 0 } Or is it coming from the self-update? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c3 --- Comment #3 from Thorsten Kukuk <kukuk@suse.com> --- 2018-10-13 00:36 Removing snapshot #26... Deleting snapshot failed. 2018-10-13 00:36 Removing snapshot #25... Snapshot #25 is clearly missing on the system. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c4 --- Comment #4 from Ignaz Forster <iforster@suse.com> --- That's interesting. There's exactly one condition when quit is called without a message in the log file, and this is when it receives a termination signal. It seems systemd is faster to send termination signals to all processes than the transactional-update Bash script can complete the next line where it would just exit. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c6 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Ignaz Forster <iforster@suse.com> --- Fixed by unsetting the error handling traps before initiating a reboot. Will be available in transactional-update 2.10 (https://github.com/openSUSE/transactional-update/commit/6c9359fb6841ffea835f...) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c7 --- Comment #7 from Swamp Workflow Management <swamp@suse.de> --- This is an autogenerated message for OBS integration: This bug (1111786) was mentioned in https://build.opensuse.org/request/show/651388 15.0 / transactional-update -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c8 --- Comment #8 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-RU-2018:4027-1: An update that has 6 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1088676,1097619,1105992,1111319,1111321,1111786 CVE References: Sources used: openSUSE Leap 15.0 (src): transactional-update-2.11-lp150.2.9.1 openSUSE Backports SLE-15 (src): transactional-update-2.11-bp150.2.6.1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111786 http://bugzilla.suse.com/show_bug.cgi?id=1111786#c9 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #9 from Ignaz Forster <iforster@suse.com> --- Fix released in all affected products. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com