Bug 1324340
| Summary: | be2iscsi iSCSI boot server does not boot after installation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Hoyer <mhoyer> | ||||||
| Component: | dracut | Assignee: | Harald Hoyer <harald> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Hoyer <mhoyer> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.8 | CC: | agrover, bgoncalv, cleech, coughlan, dracut-maint-list, harald, jkachuck, laurie.barry, mlombard, paul.rivera, revers, shubhrata_priyadarsh, tlavigne, trinh.dao | ||||||
| Target Milestone: | rc | Keywords: | Regression | ||||||
| Target Release: | --- | Flags: | harald:
needinfo-
harald: needinfo- |
||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-05-11 01:10:14 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1202403, 1309862, 1319034 | ||||||||
| Attachments: |
|
||||||||
|
Description
Martin Hoyer
2016-04-06 06:33:36 UTC
Created attachment 1144114 [details]
console
Attachment with console log from both booting and not booting distros.
Hello Harald, could this be related to dracut? No changes in the be2iscsi driver between kernel-2.6.32-621 and kernel-2.6.32-627 What was the kernel cmdline? Does it help, if you add "ip=ibft" ? dracut changed the behaviour: If "iscsistart -N" fails, no "iscsistart -b" is tried. Seems like this assumption is wrong? 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. 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. (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. Works well dracut-004-409.el6 Regression tests are passed on iSCSI boot machines. 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 *** Bug 1392411 has been marked as a duplicate of this bug. *** |