Description of problem:
If we use an encrypted PV to boot from and at the same time want to mount an ecrypted iSCSI disk, we add both these entries to /etc/crypttab. Now while non-iSCSI disk is available for cryptsetup in very early booting stages, iSCSI is only available after network starts (later than /etc/crypttab is processed). This introduces a delay in boot.
Is an option similar to fstab's _netdev available? This would tell cryptsetup to process this concrete line later, when iSCSI is ready
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. enter both boot disk / LV and an iSCSI disk in /etc/crypttab
cryptsetup will start (and process /etc/crypttab) before iSCSI has established connection with the target (network is not ready). This introduces delay in boot and the volume is not mounted.
Have cryptsetup distinguish between items it needs to process in early stages of boot (rootfs) and those that will be mounted later via iSCSI. The desired effect is similar to _netdev parameter in fstab.
Reassigning to more appropriate component. A crypttab file is managed and interpreted solely in systemd as of now. cryptsetup has currently no means to perform any auto-activation on device discovery
fix merged to upstream staging branch -> https://github.com/lnykryn/systemd-rhel/pull/141 -> post
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.