Bug 540768
Summary: | DHCP Server crashes when using LTSP on a separate server | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dino Gambone <dmgambone> | ||||
Component: | dhcp | Assignee: | Jiri Popelka <jpopelka> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 10 | CC: | dcantrell, wwoods | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-12-18 09:46: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
Dino Gambone
2009-11-24 03:30:18 UTC
In the description you write that: "When the thin-client goes to boot, it correctly gets a IP from the DHCP server" and later on in results there you say that the client does not get an IP. So does or doesn't ? Can you also attach your dhcpd.conf and dhclient.conf ? (you can mark them Private if you want) I'm sorry, I incorrectly stated the first part. What it should have said was: "When the thin-client goes to boot, it correctly gets an image from the LTSP Server". So the DHCP Server is working properly is getting the PXE request for the image and sending it the correct image from the LTSP Server. However, when the thin-client is loading up and looking for an IP address, that's when it crashes the DHCP server. I'm attaching the dhcp.config file from the DHCP Server. There is no dhclient.config file on that server. Created attachment 373480 [details]
dhcpd.conf file
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |