Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 561
    • Issues 561
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 69
    • Merge requests 69
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #632
Closed
Open
Issue created May 27, 2019 by Marcin Siodelski@marcinDeveloper

Pools are not properly updated by MySQL CB when subnet id is modified

MySQL CB allows for modifying subnet id with remote-subnet4-set and remote-subnet6-set. However, there is a bug in MySQL logic, which causes duplication of the pool during such update. Prior to updating the subnet information, the backend deletes existing pools. Then it recreates them after the subnet is updated. The backend mistakenly uses new subnet id for deleting the pools. As a result the pools remain in the database. Recreating the pools causes duplication of the pool entry and failure to merge the configuration into the server's configuration.

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