Hide Forgot
Description of problem: If an attempt is made to connection to an iscsi drive, then add LVM, then add LUKS, then add an XFS filesystem, this works. When an attempt is made to reboot the machine, long delays appear at boot as services are started up in the wrong order. The mount does not occur, and has to be performed manually. It appears that iscsi is not properly supported in RHEL7. Version-Release number of selected component (if applicable): iscsi-initiator-utils-iscsiuio-6.2.0.873-33.el7_2.2.x86_64 iscsi-initiator-utils-6.2.0.873-33.el7_2.2.x86_64 How reproducible: - Configure an iscsi drive. Add this drive to an LVM volume group and create a logical volume. - Encrypt the logical volume with LUKS, format encrypted partition with xfs. - Configure /etc/crypttab as follows to unlock drive automatically at boot: home_vmail UUID="b79e45cf-89aa-40f2-9fb1-f62f0c795e88" /etc/keyfile - Configure /etc/fstab to mount decryped drive automatically at boot: UUID=c2e2a3c3-8c98-4ce7-ab1b-283ddf836907 /home/vmail xfs _netdev 0 0 Steps to Reproduce: 1. 2. 3. Actual results: - Machine boots up. LUKS attempts to unlock the drive, which somehow triggers iscsi to start up before networking has started. - Machine bootup hangs until a 90 second timeout. - Machine eventually boots up with LUKS successful, but the mount does not happen, and has to be run manually with "mount -a". Expected results: - iscsi start happens after networking start - LUKS unlock happens after iscsi start for iscsi devices - final mount successful. Additional info:
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.