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.
Description of problem:
Our server is using OCe10102-IM card for iSCSI SAN boot. With the RHEL-6.8-20160315.0 it cannot boot after installation.
Version-Release number of selected component (if applicable):
RHEL-6.8-20160315.0
kernel-2.6.32-627.el6
iscsi-initiator-utils-6.2.0.873-20.el6
dracut-004-400.el6
Working well with:
RHEL-6.8-20160308.0
kernel-2.6.32-621.el6
iscsi-initiator-utils-6.2.0.873-19.el6
dracut-004-406.el6
How reproducible:
100%
Steps to Reproduce:
1.install RHEL-6.8-20160315.0 or newer
2.check console log while booting
Actual results:
Expected results:
Additional info:
This will impact all of our OEMs/customers (HP, Dell, Lenovo, FTS/FJJ, Hitachi, Huawei, EMC, NetApp, NEC, etc...).
Can this be resolved for RHEL6.8?
thank you
Laurie
(In reply to Harald Hoyer from comment #6)
> What was the kernel cmdline? Does it help, if you add "ip=ibft" ?
I've put ip=ibft to post installation cmd - same result.
Updating last working distro from dracut-004-400 to -406 and rebooting does not reproduce this problem.
Comment 10Maurizio Lombardi
2016-04-06 13:14:19 UTC
Martin can you try to update the last working distro to kernel-2.6.32-627.el6 too?
(In reply to Martin Hoyer from comment #9)
> Updating last working distro from dracut-004-400 to -406 and rebooting does
> not reproduce this problem.
I forgot to rebuild initrd before. Rebuilding initrd after updating dracut to -406 indeed is causing this problem. Sorry for the confusion.
Comment 12Maurizio Lombardi
2016-04-06 13:48:27 UTC
(In reply to Harald Hoyer from comment #7)
> dracut changed the behaviour:
> If "iscsistart -N" fails, no "iscsistart -b" is tried.
>
> Seems like this assumption is wrong?
I suspect (but I am not 100% sure yet) that this assumption is wrong.
I'll quote part of this bug report:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1513254
------------
Right now, the following logic is used if you pass iscsi_auto as a kernel option:
modprobe iscsi_ibft
iscsistart -b
However, in a PXE boot environment, the interface initialized will be something like the "primary" interface of the system, probably not where your iscsi traffic is running.
The '-N' flag of iscsistart should also be used to configure the networking before attempting to create a session to the target.
so:
modprobe iscsi_ibft
iscsistart -N
iscsistart -b
------------
So, in certain cases, it's not necessary to run "iscsistart -N" to guarantee that "iscsistart -b" will succeed.
Created attachment 1144752[details]
dracut-004-409.el6 boot
After Harald's update to dracut test version from comment 13, the machine boots successfully. Please see attached console log.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0954.html
Comment 19Charles Rose (Dell)
2016-11-10 12:59:26 UTC
*** Bug 1392411 has been marked as a duplicate of this bug. ***