Comment # 32 on bug 1051354 from Thomas Blume

(In reply to Lee Martin from comment #30)

> I only installed my 42.3 a few days ago using the initial udev-228-27.2 from
> the ISO, which created the following /etc/crypttab:
> 
>  # cat /etc/crypttab
> cr_-Samsung_SSD_960_PRO_2TB_S3EXNCAHB01257A-part3
> /dev/disk/by-id/-Samsung_SSD_960_PRO_2TB_S3EXNCAHB01257A-part3 none      
> none

That is actually bug 1048679.

> So, now with a corrected crypttab and the standard udev-228-32.2 I'm fine. 
> 
> HOWEVER this indicates to me that this Leap 42.3 update around udev is
> changing many device names at boot versus the ISO installation, so anything
> dependent on specific device names (like LUKS) is at risk of not working
> after this update. Therefore a fix of somekind is necessary since imagine
> LUKs setups to be relatively common on the desktop.

Hm, the only fix I can imagine with an update is to re-add the broken symlinks.
The consequence would be to carry something that is broken for a quite long
time.
I'd prefer if we would document this behaviour and provide an Driver Update for
the 42.3 installation system instead.

Steffen, would this be feasible?