November 2020 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 19 Nov '20

19 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1175850 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |systemd-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1175850 https://bugzilla.suse.com/show_bug.cgi?id=1175850#c12 --- Comment #12 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- (In reply to Fabian Vogt from comment #11) > Not great. The issue is that udev needs /etc > (https://github.com/openSUSE/read-only-root-fs/commit/ > 21c36fb3bfa66dc2bf331738f9492eda3d8f5581) and /etc needs /var (due to > /var/lib/overlay/etc/*). > So if unmounting /var needs udev, there's a cycle... Indeed. With my hack var.mount: Found ordering cycle on etc.mount/stop var.mount: Found dependency on systemd-udevd.service/stop var.mount: Found dependency on systemd-cryptsetup(a)cr_var.service/stop var.mount: Found dependency on blockdev(a)dev-mapper-cr_var.target/stop var.mount: Found dependency on var.mount/stop var.mount: Job etc.mount/stop deleted to break ordering cycle starting with var.mount/stop var.mount: Deleting job var.mount/stop as dependency of job etc.mount/stop dev-mapper-cr_var.device: Deleting job dev-mapper-cr_var.device/stop as dependency of job var.mount/stop systemd-cryptsetup(a)cr_var.service: Deleting job systemd-cryptsetup(a)cr_var.service/stop as dependency of job dev-mapper-cr_var.device/stop -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1175850 https://bugzilla.suse.com/show_bug.cgi?id=1175850#c11 --- Comment #11 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Andrei Borzenkov from comment #8) > (In reply to Fabian Vogt from comment #7) > > So it seems like systemd-journald.service doesn't reach stopped for some > > reason. > > We do not really know it if journald stopped writing into /var. To capture > what happens after that serial or net console is needed together with > systemd.log_target=console. I assumed the output was acquired by doing it like that (judging by the manual naming of files), but apparently not. (In reply to Andrei Borzenkov from comment #9) > Created attachment 843606 [details] > Hung systemd-cryptsetup stack strace > > (In reply to Fabian Vogt from comment #7) > > > > So it seems like systemd-journald.service doesn't reach stopped for some > > reason. > > nope. I can reproduce it using TW in QEMU installed with transnational > desktop and separate /var partition. For some reasons it happens only with > Plymouth disabled. I checked that systemd-journald correctly relinquishes > /var and /var is unmounted. But systemd-cryptsetup hangs. Not great. The issue is that udev needs /etc (https://github.com/openSUSE/read-only-root-fs/commit/21c36fb3bfa66dc2bf3317…) and /etc needs /var (due to /var/lib/overlay/etc/*). So if unmounting /var needs udev, there's a cycle... Apparently cryptsetup@ units don't set a dependency on udev, so that's why it fails that way. On boot there's no cycle, because /var and /etc are mounted from the initrd using the initrd's udev. Somehow making systemd-cryptsetup work without udev on shutdown is probably the best option here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 15 Nov '20

15 Nov '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 Installing kubeadm<next> shouldn't require installing kubelet<next> -> http://bugzilla.suse.com/show_bug.cgi?id=1175523 Installing kubeadm<next> shouldn't care about cri-tools -> http://bugzilla.suse.com/show_bug.cgi?id=1175524 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 k8s missing apimachinery version data -> http://bugzilla.suse.com/show_bug.cgi?id=1177289 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 14 Nov '20

14 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c10 --- Comment #10 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- Workaround is mkdir -p /etc/systemd/system/systemd-cryptsetup@.service.d cat > /etc/systemd/system/systemd-cryptsetup@.service.d/stop-before-udevd.conf << EOF [Unit] After=systemd-udevd.service EOF systemctl daemon-reload But seriously, this is just wack-a-mole. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 14 Nov '20

14 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c9 --- Comment #9 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- Created attachment 843606 --> http://bugzilla.opensuse.org/attachment.cgi?id=843606&action=edit Hung systemd-cryptsetup stack strace (In reply to Fabian Vogt from comment #7) > > So it seems like systemd-journald.service doesn't reach stopped for some > reason. nope. I can reproduce it using TW in QEMU installed with transnational desktop and separate /var partition. For some reasons it happens only with Plymouth disabled. I checked that systemd-journald correctly relinquishes /var and /var is unmounted. But systemd-cryptsetup hangs. I attach full log from systemd debug shell; most interesting part is stack trace. (gdb) bt #0 __semtimedop (semid=4, sops=sops@entry=0x7ffe1a874a62, nsops=nsops@entry=1, timeout=timeout@entry=0x0) at ../sysdeps/unix/sysv/linux/semtimedop.c:33 #1 0x00007fd0ebf2da4b in semop (semid=<optimized out>, sops=sops@entry=0x7ffe1a874a62, nsops=nsops@entry=1) at ../sysdeps/unix/sysv/linux/semop.c:29 #2 0x00007fd0ebac4bbd in _udev_wait (cookie=223200190, nowait=nowait@entry=0x7ffe1a874a94) at libdm-common.c:2768 #3 0x00007fd0ebac4cf8 in dm_udev_wait (cookie=<optimized out>) at libdm-common.c:2787 #4 0x00007fd0ec04afe7 in _dm_remove.constprop.0 (name=name@entry=0x7ffe1a875efe "cr_var", deferred=deferred@entry=0, udev_wait=1) at lib/libdevmapper.c:1022 #5 0x00007fd0ec0217da in dm_remove_device (cd=0x557d701ae950, name=0x7ffe1a875efe "cr_var", flags=<optimized out>) at lib/libdevmapper.c:1155 #6 0x00007fd0ec009dce in crypt_deactivate_by_name (cd=0x557d701ae950, name=0x7ffe1a875efe "cr_var", flags=0) at lib/setup.c:4510 #7 0x0000557d6fa9f286 in run (argc=3, argv=0x7ffe1a875258) at ../src/cryptsetup/cryptsetup.c:1037 #8 0x0000557d6fa9d656 in main (argc=<optimized out>, argv=<optimized out>) at ../src/cryptsetup/cryptsetup.c:1047 This appears to be fundamental problem with any device-mapper command that survives udevd. Quick glance at cryptsetup does not offer any possibility to disable udev integration for specific invocation - it is hard-coded. But that is just one of possible consumers of device-mapper, so is the wrong place to fix it in any way. I do not claim to understand what device-mapper does or waits for. Cc lvm2 maintainers ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 13 Nov '20

13 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c8 Andrei Borzenkov <arvidjaar(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar(a)gmail.com --- Comment #8 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- (In reply to Fabian Vogt from comment #7) > So it seems like systemd-journald.service doesn't reach stopped for some > reason. We do not really know it if journald stopped writing into /var. To capture what happens after that serial or net console is needed together with systemd.log_target=console. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 13 Nov '20

13 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1175850 https://bugzilla.suse.com/show_bug.cgi?id=1175850#c7 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None CC| |kubic-bugs(a)opensuse.org Component|MicroOS |Basesystem Assignee|kubic-bugs(a)opensuse.org |screening-team-bugs(a)suse.de Flags|needinfo?(mike(a)flingtoad.co | |m) | Severity|Major |Normal --- Comment #7 from Fabian Vogt <fvogt(a)suse.com> --- The last few lines are: Nov 13 12:29:00 AP17L systemd[1]: systemd-journal-flush.service: About to execute: /usr/bin/journalctl --smart-relinquish-var Nov 13 12:29:00 AP17L systemd[1]: systemd-journal-flush.service: Forked /usr/bin/journalctl as 2027 Nov 13 12:29:00 AP17L systemd[1]: systemd-journal-flush.service: Changed exited -> stop Nov 13 12:29:00 AP17L systemd[1]: Stopping Flush Journal to Persistent Storage... Nov 13 12:29:00 AP17L systemd[2027]: systemd-journal-flush.service: Executing: /usr/bin/journalctl --smart-relinquish-var Nov 13 12:29:00 AP17L systemd[1]: systemd-journald.service: Got notification message from PID 674 (FDSTORE=1) Nov 13 12:29:00 AP17L systemd[1]: systemd-journald.service: Added fd 21 (n/a) to fd store. So it seems like systemd-journald.service doesn't reach stopped for some reason. Reassigning to systemd, to provide some ideas. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 13 Nov '20

13 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Arek P. <ahhhrrreeecccek2710(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 13 Nov '20

13 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Arek P. <ahhhrrreeecccek2710(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are the assignee for the bug.

1 0