LUKS device nodes are created in "/dev/mapper/" location as block devices instead of symlinks

Issue

• When booting a system having many LUKS devices, it may happen that paths in /dev/mapper directory are not symlinks but block devices, as shown in the example below:

  # ls -l /dev/mapper
  total 0
  drwxr-xr-x.  2 0 0      200 Nov 21 17:22 .
  drwxr-xr-x. 20 0 0     3580 Nov 21 17:22 ..
  crw-------.  1 0 0  10, 236 Nov 21 17:22 control
  lrwxrwxrwx.  1 0 0        7 Nov 21 17:22 root -> ../dm-0
  lrwxrwxrwx.  1 0 0        7 Nov 21 17:22 tang-nvme0n1 -> ../dm-5
  lrwxrwxrwx.  1 0 0        7 Nov 21 17:22 tang-nvme1n1 -> ../dm-3
  brw-rw----.  1 0 6 253,   1 Nov 21 17:22 tang-nvme2n1
  lrwxrwxrwx.  1 0 0        7 Nov 21 17:22 tang-nvme3n1 -> ../dm-2
  brw-rw----.  1 0 6 253,   4 Nov 21 17:22 tang-nvme4n1
  lrwxrwxrwx.  1 0 0        7 Nov 21 17:22 tang-nvme5n1 -> ../dm-6
  

  Here above tang-nvme2n1 and tang-nvme4n1 nodes are not symbolic links, which is not expected.

• Additionally we see the following error messages in the journal

  [...] systemd-udevd[3269]: conflicting device node '/dev/mapper/tang-nvme2n1' found, link to '/dev/dm-1' will not be created
  [...] systemd-udevd[11356]: conflicting device node '/dev/mapper/tang-nvme4n1' found, link to '/dev/dm-4' will not be created