Bug 1680185
| Summary: | iPXE fails sometimes fails to configure NIC during ironic introspection | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Mircea Vutcovici <mircea.vutcovici> |
| Component: | ipxe | Assignee: | Neil Horman <nhorman> |
| ipxe sub component: | ipxe-bootimgs | QA Contact: | Raviv Bar-Tal <rbartal> |
| Status: | CLOSED NOTABUG | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | bfournie, dsneddon, hjensas, ietingof, marjones, mburns, mircea.vutcovici, racedoro |
| Version: | 7.4 | Flags: | nhorman:
needinfo?
(mircea.vutcovici) |
| Target Milestone: | rc | ||
| Target Release: | 7.4 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-07 17:52:01 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: | |||
|
Description
Mircea Vutcovici
2019-02-22 23:31:51 UTC
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? 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. ping, mircea, see comment 9? |