Created attachment 815982 [details]
log of "vgs -vvvv"

OpenQA problem https://openqa.opensuse.org/tests/1018187,
installation with
openSUSE-Staging:G-Tumbleweed-DVD-x86_64-Build277.1-Media.iso,
installing on encrypted LVM.

Blocking LVM2 release (https://build.opensuse.org/request/show/725506)

ps aux shows system hanging in "vgs", called by dracut:

> root     18034  0.0  0.3   4100  3228 tty1     S+   03:06   0:00                                 \_ /bin/bash --norc /sbin/mkinitrd
> root     18047  0.0  0.4   5520  4644 tty1     S+   03:06   0:00                                      \_ /bin/bash -p /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-5.2.9-5-default 5.2.9-5-default
> root     19895  0.0  0.3   5520  3036 tty1     S+   03:23   0:00                                          \_ /bin/bash -p /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-5.2.9-5-default 5.2.9-5-default
> root     19896  0.1  0.7  10732  7580 tty1     S+   03:23   0:00                                              \_ lvm vgs --noheadings -o pv_name system

I reproduced this locally. vgs emits hundreds of messages like this:

> #device/dev-type.c:1042          Device /dev/loop0 not initialized in udev database (89/100, 8800000 microseconds).

strace shows that vgs is trying to access the udev db under /run/udev/data
directly by opening files under that directory. This fails because /run is not
mounted in the chroot (system being installed). As soon as a bind-mount is
created for /run into the chroot, vgs and then the installation proceeds and
completes:

   mount --bind /run /mnt/run

I've assigned this to the "installer" component because it can be fixed in a
simple way by bind-mounting /run. I don't know how this problem is related to
the lvm2 update from sr#725506.