Bug 133223
Summary: | IP reservation does not work while lease is alive | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Andrew Martynov <andrewm> |
Component: | dhcp | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | shillman |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-06-02 15:47:47 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: | |||
Bug Depends On: | |||
Bug Blocks: | 153928 |
Description
Andrew Martynov
2004-09-22 15:05:05 UTC
Please try the latest version of DHCP-3.0.1 for EL3, that will be in RHEL-3-U4, but which meanwhile is available from: http://people.redhat.com/~jvdias/DHCP/RHEL-3 I think the above issue is actually a "feature" : if the last recorded lease in /var/lib/dhcp/dhclient.leases has not expired, then dhclient will try to renew the existing lease, not request a new one. Yes, it looks like a feature, but it does not documented anywhere. This is strange, as client meaning of lease activity should not has primary role. I suppose server configuration should dominate in lease renew process. I can reproduce this situation in new version. Internal RFE bug #153928 entered; will be considered for future releases. I think this is the way DHCP is meant to work: - When the server grants the 172.16.0.127 static lease for ab:cd:ef:ab:cd:ef, it creates an entry in its lease database /var/lib/dhcp/dhcpd.leases, and the client creates an entry in its lease database /usr/lib/dhcp/dhclient-${IF}.leases . - When the server is restarted with the static lease commented out, it still has the 172.16.0.127 lease in its lease database, which is also valid in the dynamic lease pool, so it allows the client to renew this lease, which is its default behaviour. So I don't think this issue is a bug. Please try the latest dhcp version in RHEL-3: dhcp-3.0.1-10 , and let me know if this issue is still a problem for you; if so, I'll re-open this bug. |