Comment # 1 on bug 1206700 from
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-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])."


You are receiving this mail because: