Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 214
    • Issues 214
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • 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
  • storkstork
  • Issues
  • #473

Closed
Open
Created Feb 01, 2021 by Marcin Siodelski@marcinMaintainer

When subnet is moved into a shared network the old subnet entry is not removed

I did the following test:

  • Started Kea with a single subnet and without any shared networks
  • I let Stork pull the subnet and store in its database
  • Stopped Kea and moved the subnet into a new shared network
  • Started Kea again and let Stork pull the updated configuration
  • Navigated to the list of subnets
  • I now see two instances of the same subnet, one under shared network and one global.
Assignee
Assign to
Time tracking