Bug 1462166 - [Cavium 7.4 Bug] L4 iSCSI boot failure after OS installation
[Cavium 7.4 Bug] L4 iSCSI boot failure after OS installation
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iscsi-initiator-utils (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity urgent
: rc
: ---
Assigned To: Chris Leech
Martin Hoyer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 07:01 EDT by Nilesh Javali
Modified: 2018-01-10 11:53 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
OS boot failure screenshot (153.26 KB, image/png)
2017-06-16 07:01 EDT, Nilesh Javali
no flags Details

  None (edit)
Description Nilesh Javali 2017-06-16 07:01:14 EDT
Created attachment 1288316 [details]
OS boot failure screenshot

Description of problem:
L4 iSCSI boot fails to boot after successful OS installation as SElinux denies open-iscsi services to start.

Version-Release number of selected component (if applicable):
RHEL 7.4 Snapshot2

How reproducible:
Always

Steps to Reproduce:
1. Start L4 iSCSI boot installation
2. At the kernel command line blacklist the qed,qede,qedi,qedf modules 
3. Provide dud containing out of box qed,qede,qedi,qedf drivers
4. Complete the OS installation
5. Reboot the system to see OS boot failure

Actual results:
OS boot failure

Expected results:
OS should boot successfully

Additional info:
1. SElinux denies open-iscsi services to start after pivot-root causing OS boot failure as root device is not found. (attached the failure screenshot)
2. Disabling SElinux (selinux=0) at kernel command line enables the OS to boot successfully.
Comment 2 Chris Leech 2017-06-16 11:59:27 EDT
The screenshot shows denials for access to what I think is the /var/lock/iscsi/lock file with a target context of "system_u:object_r:var_lock_t:s0"

On a working 7.4 iSCSI setup (different hardware) I see an context for that lock file of "unconfined_u:object_r:iscsi_lock_t:s0"

So it looks like the install process involving the DUD created a lock file while the SELinux context wasn't loaded?

Deleting or re-labelling that file should work.
I'll see if I can tell where it's going wrong.

Note You need to log in before you can comment on or make changes to this bug.