Comment # 14 on bug 1094963 from Arvin Schnell

The name of the device mapper table for the LUKS device is defined by the user,
/etc/crypttab
or whoever activates it. (Note: the logs mention cryptotab which is obsolete
for many years.)

When the LUKS device is activated the content of /etc/crypttab is in general
not yet known
(think of /etc being placed on the LUKS device itself). Thus the code generates
a arbitrary
name, cr-auto-1 in this case. So for the kernel and libstorage-ng the device is
known as
/dev/mapper/cr-auto-1 but not as cr_ata-VBOX_HARDDISK_VB355f98fa-3fd6ea5a-part3
as found in
the fstab. AFAIS the update code has to read crypttab and lookup the underlying
device of
cr_ata-VBOX_HARDDISK_VB355f98fa-3fd6ea5a-part3 and then use the device name
known to the
kernel.

BTW: Using UUIDs to identify LUKSes would likely also solve the issue. This is
done for new
installation of e.g. openSUSE Leap 15.0.