RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1368610 - LUKS over iSCSI causes delay at boot and mount failure
Summary: LUKS over iSCSI causes delay at boot and mount failure
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Chris Leech
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-20 00:23 UTC by Graham Leggett
Modified: 2021-09-03 13:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:44:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Graham Leggett 2016-08-20 00:23:25 UTC 
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:
Comment 3 RHEL Program Management 2020-12-15 07:44:49 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.