[Bug 1191945] New: [Build 20211020] t-u 3.5.7 - results in emergency console
http://bugzilla.opensuse.org/show_bug.cgi?id=1191945 Bug ID: 1191945 Summary: [Build 20211020] t-u 3.5.7 - results in emergency console Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1983403/modules/disk _boot/steps/5 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-ContainerHost-x86_64-container-host@64bit fails in [disk_boot](https://openqa.opensuse.org/tests/1983403/modules/disk_boot/steps/5) From the journal: Oct 22 07:26:34.116234 localhost combustion[634]: transactional-update 3.5.7 started Oct 22 07:26:34.118437 localhost combustion[634]: Options: shell Oct 22 07:26:34.183109 localhost combustion[634]: Separate /var detected. Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 tukit 3.5.7 started Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 Options: -c1 open Oct 22 07:26:34.682648 localhost combustion[634]: Failure (dbus fatal exception). Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 Using snapshot 1 as base for new snapshot 2. Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 No previous snapshot to sync with - skipping Oct 22 07:26:34.682648 localhost combustion[634]: ID: 2 Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/log] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/zypp] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/ca-certificates] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/alternatives] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/selinux] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/cache] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/tmp] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 Transaction completed. ��� Oct 22 07:26:35.114100 localhost combustion[634]: transactional-update finished Oct 22 07:26:35.134257 localhost combustion[931]: umount: /sysroot/var: target is busy. Oct 22 07:26:35.135028 localhost systemd[1]: combustion.service: Main process exited, code=exited, status=32/n/a Oct 22 07:26:35.142244 localhost systemd[1]: combustion.service: Failed with result 'exit-code'. Oct 22 07:26:35.142512 localhost systemd[1]: Failed to start Combustion. ## Test suite description ## Reproducible Fails since (at least) Build [20211020](https://openqa.opensuse.org/tests/1982883) ## Expected result Last good: [20211019](https://openqa.opensuse.org/tests/1980808) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos&flavor=MicroOS-Image-ContainerHost&machine=64bit&test=container-host&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191945 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs@opensuse.org |iforster@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191945 http://bugzilla.opensuse.org/show_bug.cgi?id=1191945#c1 --- Comment #1 from Ignaz Forster <iforster@suse.com> --- If I understood Fabian correctly this doesn't happen every time? That's interesting, because I didn't change the mount behavior of *those* directories in the latest updates (though I did some mount optimizations in other areas). Let's try with a different approach then, which was originally supposed to go into the 4.0 release, but I may also pull this into the 3.x series: Instead of mounting everything twice (once into /.snapshots and then bind mounting everything into a temporary directory) just use the temporary mount point. I will do a new transactional-update release in a few minutes. If that also doesn't work I will set up a private mount for separate mount namespaces. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191945 http://bugzilla.opensuse.org/show_bug.cgi?id=1191945#c2 --- Comment #2 from OBSbugzilla Bot <bwiedemann+obsbugzillabot@suse.com> --- This is an autogenerated message for OBS integration: This bug (1191945) was mentioned in https://build.opensuse.org/request/show/927034 Factory / transactional-update -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191945 http://bugzilla.opensuse.org/show_bug.cgi?id=1191945#c3 --- Comment #3 from Ignaz Forster <iforster@suse.com> --- It's been some time since the update with the potential fix was released. Have you seen this problem again or can I assume that the new handling fixed it? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191945 http://bugzilla.opensuse.org/show_bug.cgi?id=1191945#c4 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Ignaz Forster from comment #3)
It's been some time since the update with the potential fix was released. Have you seen this problem again or can I assume that the new handling fixed it?
Issue has not shown up since then. Let's assume fixed -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com