Opened 7 years ago

Closed 3 years ago

#2469 closed defect (complete)

DHCPv6 Config Parser: when setting global value, values in subnets should be changed.

Reported by: marcin Owned by:
Priority: medium Milestone: Kea1.2
Component: remote-management Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by tomek)

The following scenario will not work properly with DHCPv6 config parser:

  1. Set global configuration values
  2. Add new subnet without any values other than subnet and pool (this makes the subnet inherit global values)
  3. Change any of the global values - this should force change of the particular value in the subnet object but it doesn't.

In the step 3. function that does configuration will receive the request to change global value and only global value is changed. Another thing that should happen at this point is the check that global value has been changed and all corresponding values within subnets should be affected but parsing algorithm does not force this by itself. We need to implement a logic that will iterate through all existing subnets and if their configuration is inherited from global configuration they should be updated accordingly. The major problem here is that when we create a subnet we do not record whether it is dependent on global values or local values. This has to be recorded on subnet object creation.

Subtickets

Change History (6)

comment:1 Changed 7 years ago by stephen

  • Milestone changed from Sprint-DHCP-20121115 to DHCP 2012

comment:2 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

comment:3 Changed 3 years ago by tomek

  • Description modified (diff)
  • Milestone changed from Outstanding Tasks to Kea1.2

comment:4 Changed 3 years ago by tomek

  • Component changed from dhcpconf to configuration

comment:5 Changed 3 years ago by tomek

  • Component changed from configuration to remote-management

comment:6 Changed 3 years ago by fdupont

  • Resolution set to complete
  • Status changed from new to closed

Done in #5019. Closing.

Note: See TracTickets for help on using tickets.