Bug 1462166

Summary: [Cavium 7.4 Bug] L4 iSCSI boot failure after OS installation
Product: Red Hat Enterprise Linux 7 Reporter: Nilesh Javali <nilesh.javali>
Component: iscsi-initiator-utilsAssignee: Chris Leech <cleech>
Status: CLOSED WONTFIX QA Contact: Martin Hoyer <mhoyer>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.4CC: manish.rangankar, nilesh.javali, saurav.kashyap, shyam.sundar
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-15 07:38:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
OS boot failure screenshot none

Description Nilesh Javali 2017-06-16 11:01:14 UTC
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 15:59:27 UTC
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.

Comment 6 RHEL Program Management 2021-01-15 07:38:23 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.