Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 514
    • Issues 514
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 49
    • Merge requests 49
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #451

Closed
Open
Created Feb 05, 2019 by Marcin Siodelski@marcinDeveloper

MySQL config backend must not set timers to default value of 0

Currently, when the MySQL Config Backend finds NULL DHCP timer value (e.g. renew-timer) it will use a value of 0 as a default. The subnet logic, though, treats unspecified value differently than the 0 value. The 0 value has a meaning (at least in v6) that it is up to the client to determine when to renew. The unspecified value causes the server to calculate the times based on the percentages.

We need to adjust the backend to store unspecified timers (triplets) as NULL. Then, the backend has to turn NULLs to unspecified triplets.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking