Comment # 39 on bug 909912 from Ancor Gonzalez Sosa

(In reply to Franck Bui from comment #36)
> 
> So I'm afraid that the only way we have is to disable the job timeout for
> the cypto device and I can only see 2 possible workarounds:
> 
>  - the one that Lennart proposed in the aforementioned BZ: disable the
> timeout for the job waiting for the crypto device by adding
> x-systemd.device-timeout=0 to the relevant entry in fstab. The installer
> should know which entries in fstab refer to crypto devices.

With storage-ng (i.e. SLE>=15, Leap>=15.0 and TW) we can easily know in advance
which entries in fstab rely on a LUKS device directly (i.e. an encrypted and
formatted partition) or indirectly (i.e. a filesystem in an LV of a VG with
encrypted PVs). Adding that option by default during installation should not be
rocket science.

>  - stop using UUID=/LABEL=/... for referring to a crypto device in fstab and
> use the devnode canonical path (/dev/mapper/xxx) instead. In this case,
> systemd automatically disables the job timeout. Again, only the installer
> can change this.

Yes, we could do that as well. Also easy to implement.

> Yast team, would that work for you ?

So technically both are possible and relatively easy to implement.

But the usage of UUID vs Label vs kernel name is a quite sensible topic. We
have got quite some bug reports about what is expected depending on the type of
device, the architecture, the product and whatnot... and everybody seems to
have a quite strong opinion about which is the correct option.

So I'm afraid of opening the can of worms behind the second option.
Implementing the first one looks like a safer bet to me.