Report information
The Basics
Id:
45398
Status:
open
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
(no value)
Severity:
(no value)
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
(no value)

Dates
Created:Fri, 16 Jun 2017 12:17:40 -0400
Updated:Wed, 26 Jul 2017 11:27:18 -0400
Closed:Not set



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: omapi leases query ignores state
Date: Fri, 16 Jun 2017 17:17:30 +0100
To: dhcp-bugs@isc.org
From: "Ian Jackson" <ian.jackson@eu.citrix.com>
When looking up a lease via omapi, the dhcpd ignores the "state" field of the query key object. This can prevent the query from working at all, because there can easily be multiple objects which are distinguished only by "state": > new lease obj: lease > set hardware-address = 5a:36:0e:9d:00:01 obj: lease hardware-address = 5a:36:0e:9d:00:01 > open can't open object: more than one object matches key obj: lease hardware-address = 5a:36:0e:9d:00:01 > set state = 00:00:00:02 obj: lease hardware-address = 5a:36:0e:9d:00:01 state = 00:00:00:02 > open can't open object: more than one object matches key obj: lease hardware-address = 5a:36:0e:9d:00:01 state = 00:00:00:02 > This bug seems to be described here: https://lists.isc.org/pipermail/dhcp-hackers/2005-August/001399.html Sadly no-one seems to have given any useful pointers to Robin Breathe in 2005 and the bug remains unfixed at least in my current distro. As as result, the "lookup_ip" function in pypureomapi does not work reliably (and cannot be made to work reliably). (I'm using Debian's isc-dhcp-server version 4.2.2.dfsg.1-5+deb70u8.) Ian.
Dear Ian: Thank you for your submission. We are nearing completion of our upcoming releases for 4.3.6 adn 4.1-ESV-R15 due out 7/31/17. This close to a release we are not likely to address additional issues in them. We will, however, consider your issue for our next release 4.4.0. It's due date is TBD but is likely to be Q4/17 or Q1/18. It may be that a patch becomes available before then and in any event, you should receive notifications as things progress. I realize this issue dates back quite some time but as a small, non-profit we work on what we can as priority dictates. Thank you for taking the time to report the matter. Sincerely, Thomas Markwalder ISC Software Engineering