[Bug 1206700] New: systemd: Failed to start Create missing directories from rpmdb
http://bugzilla.opensuse.org/show_bug.cgi?id=1206700 Bug ID: 1206700 Summary: systemd: Failed to start Create missing directories from rpmdb Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: reiokorn@tutanota.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- sudo journalctl -b | grep rpm Dez 26 16:48:07 microos-pc systemd[1]: Starting Create missing directories from rpmdb... Dez 26 16:48:07 microos-pc create_dirs_from_rpmdb[921]: Failed to resolve uuidd/uuidd Dez 26 16:48:07 microos-pc systemd[1]: create-dirs-from-rpmdb.service: Main process exited, code=exited, status=1/FAILURE Dez 26 16:48:07 microos-pc systemd[1]: create-dirs-from-rpmdb.service: Failed with result 'exit-code'. Dez 26 16:48:07 microos-pc systemd[1]: Failed to start Create missing directories from rpmdb. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206700 Henrik Dermer <henrik.dermer@fouredge.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |henrik.dermer@fouredge.se -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206700 http://bugzilla.opensuse.org/show_bug.cgi?id=1206700#c1 --- Comment #1 from Henrik Dermer <henrik.dermer@fouredge.se> --- Got this issue as well and started to investigate it a little. Running the command in the unit file with the debug flag yields some more info, localhost:~ # /usr/sbin/create_dirs_from_rpmdb --debug Missing /var/lib/libuuid (drwxr-xr-x,uuidd,uuidd,2022-12-23,10:26) Failed to resolve uuidd/uuidd I can clearly see that /var/lib/libuuid isn't present in my filesystem, but searching for it gives a hit in every snapshot. localhost:~ # find / -name libuuid /.snapshots/2/snapshot/var/lib/libuuid /.snapshots/3/snapshot/var/lib/libuuid /.snapshots/5/snapshot/var/lib/libuuid /.snapshots/6/snapshot/var/lib/libuuid Checking my mounts show that /dev/sda3 is mounted to /var localhost:~ # mount | grep sda3 /dev/sda3 on /var type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=5,subvol=/) Checking my mounts when inside a transactional-update shell it shows something completely different and I can clearly see that that neither /var nor /var/lib is mounted transactional update # mount | grep sda3 /dev/sda3 on /var/log type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=5,subvol=/) /dev/sda3 on /var/lib/zypp type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=5,subvol=/) /dev/sda3 on /var/lib/ca-certificates type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=5,subvol=/) /dev/sda3 on /var/lib/selinux type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=5,subvol=/) /dev/sda3 on /var/cache type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=5,subvol=/) If I mount /var and then do the update from within the transactional-update shell (zypper up or zypper dup) and reboot. The create_dirs_from_rpmdb program (and create-dirs-from-rpmdb.service) work just fine. Since I started using MicroOS about a week ago I don't fully understand if this is by design or not. Not mounting /var that is... Since transactional-update print the message "Separate /var detected." and looking in the man pages (https://manpages.opensuse.org/Tumbleweed/transactional-update/transactional-...) it states (in the important section), "... There is also limited handling for adding files and directories to /var, however modifications of existing files (e.g. migrating databases) are supposed to be handled by systemd jobs at startup (see the initial configuration and deployment section of the packaging guidelines[1])." -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206700 http://bugzilla.opensuse.org/show_bug.cgi?id=1206700#c2 --- Comment #2 from B <reiokorn@tutanota.com> --- (In reply to Henrik Dermer from comment #1)
(...) Since I started using MicroOS about a week ago I don't fully understand if this is by design or not. Not mounting /var that is... Since transactional-update print the message "Separate /var detected." and looking in the man pages (https://manpages.opensuse.org/Tumbleweed/transactional-update/transactional- update.8.en.html) it states (in the important section), "... There is also limited handling for adding files and directories to /var, however modifications of existing files (e.g. migrating databases) are supposed to be handled by systemd jobs at startup (see the initial configuration and deployment section of the packaging guidelines[1])."
https://en.opensuse.org/Portal:MicroOS/Design look into /etc/fstab, /var is mounted: /var btrfs subvol=/@/var,x-initrd.mount 0 0 https://www.freedesktop.org/software/systemd/man/systemd.special.html#initrd... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com