Bug 56499
| Summary: | anaconda fails to pick up address on first pass during PXE/bootp install | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | K. Spoon <kspoon> | ||||
| Component: | anaconda | Assignee: | Matt Wilson <msw> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.2 | CC: | katzj | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2002-01-15 21:48:41 UTC | Type: | --- | ||||
| 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
K. Spoon
2001-11-20 02:14:02 UTC
Created attachment 37986 [details]
patch to anaconda to make multiple DHCP reqs for network kickstart
This is strange because we do kickstart PXE boot installs all the time. Any ideas here Matt? The big thing I'm concerned about is getting anaconda to give DHCP a couple of tries before giving up on a DHCP server. Missing one round of DHCPOFFERs isn't worth dropping out of a kickstart for, IMO. Regarding the actual cause, I think the big problem is that we're using PXELINUX (an offshoot of syslinux) that is being served up from bootp/dhcpd rather than a true PXE server. It seems as if pump is getting confused by something PXELINUX is doing and that after pumpDhcpRun() is run the first time, the problem is reset. I haven't been able to replicate it under any other circumstances. Not that I'm necessarily against the idea of adding a retry, but we use pxelinux here as well. If you take a look at the dhcp packets on the network, is there anything "strange" about them? Any more info here? Yeah, but given the security updates of the past week and some other stuff that has to get done before holidays I haven't had a chance to gather detailed info. I do recall that the "breq" field wasn't matching up with "bresp" on the first try... couldn't tell if they matched on the second try since the info scrolls off the screen. Example: installer thinks its listening for "0xb7b34f54" and dhcp server sees "0xb748514d" and responds accordingly (card's MAC is 00:02:b3:48:51:4d). It didn't look like anything strange or unexpected was happening on the network's side of things. Hopefully, before the end of the week I will have tcpdump logs and have figured out some way to capture all the info pump is spitting out. Please let me know if there's some debugging code I can turn on that might help. It seems the problem was in the version of pxelinux being used. Using version 1.65 (recent release) as well as 1.52 from the RH 7.2 CDROMs, everything is cool (response from DHCP server picked up right away), but trying a kickstart using 1.63 still seems to trip it up. It'd still be nice to have anaconda not give up so easily. :-) Multiple passess will take a very long time to time out. Normally everything works fine, but PXELINUX was known to have some bugs that caused things like this. |