Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1312485

Summary: RHEL7.1 installation is booting to Dracut shell if iBFT parameters are passed into grub
Product: Red Hat Enterprise Linux 7 Reporter: Laurie Barry <laurie.barry>
Component: dracutAssignee: dracut-maint
Status: CLOSED CURRENTRELEASE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: abeausol, be2net-dev.pdl, dracut-maint-list, dracut-maint, harald, jitendra.bhivare, ketan.mukadam, laurie.barry, ramkumar.keshavamurthy, vinaykumar.laghavarapu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-01 17:19:31 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
console logs
none
screen shot none

Description Laurie Barry 2016-02-26 20:47:20 UTC
Error_screenshot

Chassis Model: BX400S1
Firmware Version: 6.75

Switch type: PY CB Eth Switch/IBP 1Gb 36/8+2(Mode:Switch)

Switch FW: 6.46

Blade Model: BX2580 M1
BIOS: V5.0.0.9 R1.26.00 for D3321-A1x
iRMC: 8.08F

Adapter(s): OCl14102-LOM
Type: SKH - LOM
Revision: Skyhawk
Firmware: 11.1.1.3
Device driver: NA
OCM: NA
Personality: NIC-Only
Multichannel (vNIC): NA

Steps to reproduce:
1) Flash 11.1.1.3 firmware on Skyhawk 1G LOM.
2) Add iBFT iscsi configuration attempts for generating user configurable iqn
address.
3) Make sure initiator iqn can be reachable to target.
4) Register initiator iqn in target and add a LUN to it.
5) Mount RHEL 7.1 GA'ed OS and boot to CD-ROM
6) During installation pass "ip=ibft" parameter under grub and continue
installation.
7) After some time installation is booting to Dracut Emergency shell.

Note: Installation of RHEL7.2 and SLES12 GMC3 OS is fine with "ip=ibft" kernel
parameter passed during installation.

EXPECTED RESULTS:
Installation should proceed fine 

ACTUAL RESULTS:
Installation is booting to Dracut emergency shell after passing ip=ibft
parameter.

Attaching screenshot.


IP address of ibft0

ibft0 interface created has been assigned different IP address than what is in
iBFT configuration.

When ibft0 is assigned the IP address in configuration, 172.168.5.200, then
initiator is able to login to the target and device appears.

Bring up of ibft0 from the configuration is done by boot and installer script
of RHEL7. Please raise a bz for this in RedHat bugzilla.

Comment 1 Laurie Barry 2016-02-26 20:50:29 UTC
Created attachment 1130901 [details]
console logs

Comment 2 Laurie Barry 2016-02-26 20:51:03 UTC
Created attachment 1130902 [details]
screen shot

Comment 4 Harald Hoyer 2016-02-29 10:13:09 UTC
Have you tried RHEL-7.2?

Comment 5 Vinaykumar 2016-03-01 10:45:37 UTC
(In reply to Harald Hoyer from comment #4)
> Have you tried RHEL-7.2?

With RHEL7.2 it is working fine. We are able to boot to SAN OS (iBFT).

Comment 6 Harald Hoyer 2016-03-01 17:21:16 UTC
or do you expect a fix of the 7.1/7.0 installation media?

Comment 7 Ramkumar 2016-03-02 06:49:39 UTC
We see that this issue is closed for the Current Release when the issue is still persistent on RHEL 7.1. Can we know why was this issue was closed without proper resolution comments ?

Comment 8 Harald Hoyer 2016-06-16 16:42:04 UTC
(In reply to Ramkumar from comment #7)
> We see that this issue is closed for the Current Release when the issue is
> still persistent on RHEL 7.1. Can we know why was this issue was closed
> without proper resolution comments ?

Do you expect a z-stream fix for 7.1? 7.2 is not good enough?

Comment 9 Ramkumar 2016-10-04 04:05:24 UTC
A quick fix for 7.1 will work. Our Automation scripts are failing on 7.1 because of this issue. We are supporting 7.1 drivers for all our OEM's.