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.
DescriptionMircea Vutcovici
2019-02-22 23:31:51 UTC
Description of problem:
Running ironic introspect fails from time to time during iPXE network boot.
Recent versions of iPXE seems stable.
Version-Release number of selected component (if applicable):
4e85b27 - broken
272fe32 - working
How reproducible:
20-30%
Steps to Reproduce:
1. run ironic introspection a couple of times
2.
3.
Actual results:
No configuration methods succeeded (http://ipxe.org/040ee119)
No DHCP requests from iPXE. However we can see the DHCP requests from PXE/UNDI see po108-22.pcap.gz file attached to the case)
Expected results:
iPXE to send a DHCP Discover
Additional info:
We compiled iPXE that is working with following command line:
make bin/undionly.kpxe DEBUG=scsi:3,iscsi:3,http:7,undi:7,undirom:7,pci:3
This is the working commit:
commit 272fe32529103dd39875a9fbed5cfdf1a059e294 (HEAD -> master, origin/master, origin/HEAD)
Date: Thu Feb 21 11:32:25 2019 +0000
there should be plenty of debugging available in ipxe, at least to start work on this problem. If you rebuild the package with the environment DEBUG=bnx2:8 or DEBUG=net:8, you should get significant output detailing operations on the network card in question
The fact that introspection fails intermittently indicates that there might be a race condition. It might be worth reducing the LACP fallback timeout, that way the link will be available as an individual link earlier in the boot cycle. The default is 90 seconds, but 60 seconds might be more likely to succeed. The default LACP reception interval is 30 seconds, and this value needs to be higher than that.
interface Port-Channel119
port-channel lacp fallback timeout 60
Hi,
I do not think the issue is caused by LACP fallback timeout. The reasons are:
- PXE has never problem in doing a DHCP transaction then TFTP doenaload
- if we go into iPXE command line, and run `ifconf` manually, we are not able to obtain an IP no mater how many times we try
- Soft reboot initiated by iPXE solves the problem after a few reboots
- LACP timeout is not variable. The issue would show all the times.
wait, are you running bonding in ipxe? Does this work if you don't configure bonding?
Comment 10Mircea Vutcovici
2019-03-01 15:05:52 UTC
iPXE doesn't support bonding. This means it will try to use the links directly not as a LACP member. However the switch is configured for LACP fallback and it will reconfigure the switch ports to behave as normal ports when no LACP frames are received in 60 seconds.
(In reply to Mircea Vutcovici from comment #8)
> Hi,
>
> I do not think the issue is caused by LACP fallback timeout. The reasons are:
> - PXE has never problem in doing a DHCP transaction then TFTP doenaload
> - if we go into iPXE command line, and run `ifconf` manually, we are not
> able to obtain an IP no mater how many times we try
> - Soft reboot initiated by iPXE solves the problem after a few reboots
> - LACP timeout is not variable. The issue would show all the times.
I agree that given the above, LACP timeout is not likely to be the culprit.