Comment # 36 on bug 909912 from Franck Bui

(In reply to Olaf Hering from comment #28)
> (In reply to Thomas Blume from comment #26)
> > https://bugzilla.redhat.com/show_bug.cgi?id=861123
> 
> His first comment clearly shows that he does not understand (or just
> ignores) the underlying design bug:
> 
> The handling of user input for the passphrase and the result of this action
> (block device appears or not) has to come before any other step. And this
> step is independend from fstab actions. The latter may get a different
> timeout per entry (like setting it to 1sec for the entries which are known
> to come from crypt).
> 
> Again: do separation of 'provide block devs' from 'use block devs for fstab'.

That's not really possible with the current design of systemd: the block device
used in fstab is a dependency of a mount unit, and as such systemd simply waits
for it and there's no way to inform that it should wait for it after another
unit: device units are special, they can't be ordered, they're just active when
udev sends the respective events.

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.

 - 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.

Yast team, would that work for you ?