Overview:

Something about the upgrade from 4.4.1-1 to 4.4.2-1 or dracut 044-3.1 ->
044-4.1 or another recent (last ~week) package change broke initrd for all
installed kernels, even ones that existed before the upgrade.
I'm currently on tumbleweed, version_id=20160229


Steps to Reproduce:
 * Install OpenSuse Tumbleweed a week ago
 * During setup, choose to have an encrypted LVM install with separate /home
and / partitions + encrypted swap (not sure this is important) and an
unencrypted /boot.
 * remove "quiet" and "splash" from kernel boot cmdline. In my case it was via
/etc/default/grub and grub2-mkconfig
 * Perform kernel upgrade
 * reboot


Actual behavior:

After asking for my password to decrypt sda1 (swap), boot fails and dumps me
into the dracut recovery prompt with a message that "/dev/mapper/system-root"
couldn't be found.


Expected behavior:

Ask for my password once, boot to my login manager, etc.


Additional information/tedious long-winded explanation:

I have a Tumbleweed install that I set up a week ago Monday. During
installation I opted for an LVM managed full-disk encryption that could suspend
to disk. This ended up creating what looks like an encrypted swap partition on
/dev/sda1 and a encrypted / and /home on /dev/sda3. /boot is at /dev/sda2,
unencrypted.

Yesterday I did an update with zypper, which included a kernel update from
4.4.1-1 to 4.4.2-1, (though there were a little over 300 updates total).

Upon booting I get dropped into the dracut recovery shell with a message that
"/dev/mapper/system-root" doesn't exist. It definitely doesn't, though
system-swap does. One thing I noticed was that /dev/sda1 is the only entry in
my /etc/crypttab under dracut, I'm not sure if that's normal or what.

I was able to boot by doing:

> cryptsetup -v luksOpen /dev/sda3 cr_sda3 # this gave me /dev/mapper/cr_sda3
> lvm vgchange -a y system # this gave me /dev/mapper/system-root and /dev/mapper/system-home, plus /dev/system/root and /dev/system/home
> ^D // ctrl+d

Then it asked me for my password again for cr_ata-...-sda3.

Finally it booted and I rebuilt initrd with

> mkinitrd -f -v /boot/initrd-$(uname -r).img $(uname -r)

Now everything is fine (I can reboot, etc).