https://bugzilla.suse.com/show_bug.cgi?id=1204360 https://bugzilla.suse.com/show_bug.cgi?id=1204360#c1 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com, | |systemd-maintainers@suse.de Flags| |needinfo?(systemd-maintaine | |rs@suse.de) --- Comment #1 from Michael Chang <mchang@suse.com> --- (In reply to Markus Elfring from comment #0)

Created attachment 862208 [details] error logs as background information for another questionable software upgrade attempt

I came along the need to try another software repair out by the means of the image ���openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20221013-Media.iso���.

I could configure my software repositories then. The screen ���Installation Settings��� was finally presented with the following hint after a promising automatic software package selection.

������ Booting

Analysing your system������

The following information was displayed by a dialogue box. ���YaST2 <2>

Error

Execution of command "[["/usr/bin/grub2-editenv", "list"]]" failed. Exit code: 1 Error output: /usr/bin/grub2-editenv: error: failed to get canonical path of `/boot/grub2'. ���

It seems /boot is a separate partition

$["file":"/boot", "freq":0, "mntops":"data=ordered,noauto,comment=systemd.automount", "passno":2, "spec":"UUID=075b6893-1e36-4e57-bdc6-b261a110fe08", "vfstype":"ext3"]

... but didn't get mounted rightfully due to systemd.automount units missing?

2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Unit boot.mount does not exist, proceeding anyway. 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Unit home.mount does not exist, proceeding anyway. 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/boot.mount ��������� /dev/null. 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/home.mount ��������� /dev/null. 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/tmp.mount ��������� /dev/null. 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/var-lib-nfs-rpc_pipefs.mount

If so that would lead to any unspecified error IMHO.

See also information from previous clarification attempts: * 2022-10-15 Fixing components related to software snapshot ���20221013���

https://forums.opensuse.org/showthread.php/576670-Fixing-components-related- to-software-snapshot-%E2%80%9C20221013%E2%80%9D

* 2021-06-17 Execution failure for ���grub2-editenv��� (from snapshot 20210615?) https://bugzilla.opensuse.org/show_bug.cgi?id=1187471#c2

This was a different problem of missing command grub2-editenv itself which seem to have been fixed as the issue got reported upon executing it.

* 2020-10-21 [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc https://bugzilla.opensuse.org/show_bug.cgi?id=1177956

This was fixed already. I have changed it's resolution accordingly.

How will the chances evolve to fix the affected software components?

As a start we can check with systemd-maintainers to get better understanding the consequence of missing automount unit file mentioned above. Hi Fabian or Thomas, Would you please help to clarify on that ? Thanks in advanced. -- You are receiving this mail because: You are on the CC list for the bug.