I can confirm this bug to be present also in lvm2 (2.02.133-1ubuntu10).
I got the affected system (upgraded via do-release-upgrade on 09.08.2016) back up with above mentioned workaround:
Creating /etc/initramfs-tools/scripts/local-top/lvm2 script doing "lvm vgchange -ay". And making it executable.
Shouldn't this bug get some priority since it possibly makes a remote-system inaccesible ?
I can confirm this bug to be present also in lvm2 (2.02.133- 1ubuntu10) .
I got the affected system (upgraded via do-release-upgrade on 09.08.2016) back up with above mentioned workaround:
Creating /etc/initramfs- tools/scripts/ local-top/ lvm2 script doing "lvm vgchange -ay". And making it executable.
Shouldn't this bug get some priority since it possibly makes a remote-system inaccesible ?