BIND 10 #3358: Default dhcp-ddns config does not have all elements
BIND 10 Development
do-not-reply at isc.org
Thu Mar 13 11:06:42 UTC 2014
#3358: Default dhcp-ddns config does not have all elements
-------------------------------------+-------------------------------------
Reporter: tmark | Owner: tmark
Type: defect | Status:
Priority: high | reviewing
Component: dhcp-ddns | Milestone: DHCP-
Keywords: | Kea0.9
Sensitive: 0 | Resolution:
Sub-Project: DHCP | CVSS Scoring:
Estimated Difficulty: 8 | Defect Severity: N/A
Total Hours: 16 | Feature Depending on Ticket:
| Add Hours to Ticket: 1
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by tmark):
Replying to [comment:11 marcin]:
> Reviewed commit a8560aefbfaffd86f4c63b500c38ee4a1bd8f8de
>
> In the dhcp4.spec there is this:
> {{{
> {
>
> "item_name": "always-include-fqdn",
> "item_type": "boolean",
> "item_optional": true,
> "item_default": false,
> "item_description": "Enable always including the FQDN
option in its response"
> },
>
> }}}
>
> but there is no corresponding constant specifying a default.
>
> In fact, I just saw that the false value is explicitly specified as
!''false!'' in the build function. Maybe you intended to specify a
constant for this default value too?
>
>
>
>
>
This option is actual supposed to be removed under #3294, however for
completeness sake I have added a constant for it. Also, the !ChangeLog
entry will now be:
{{{
7xx. [bug] tmark
Configuration parsing in b10-dchp6 and b10-dhcp4 for the "dhcp-ddns"
section of their configurations now supplies hard-coded default values
rather than those from their spec files. This is a temporary solution
to circumvent an issue in the configuration libraries which causes
map-items to behave incorrectly.
(Trac #3358, git TBD)
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/3358#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list