Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network deletion doesn't trigger DHCP range deletion #136

Open
bcollet opened this issue Dec 9, 2014 · 1 comment
Open

Network deletion doesn't trigger DHCP range deletion #136

bcollet opened this issue Dec 9, 2014 · 1 comment
Labels
Milestone

Comments

@bcollet
Copy link

bcollet commented Dec 9, 2014

If a network is split in smaller subnets, but has a DHCP range larger than the smaller subnets it covers, it is not possible to edit or delete it any more.

Steps to reproduce:

  1. Create a network (say a /24).
  2. Create a DHCP range covering that network.
  3. Delete the network.
  4. Create several small networks in the former network.

The expected behaviour would be for the DHCP range to be deleted alongside the network (or for a warning to be presented to the user for him to chose what to do).

@pdav pdav modified the milestone: NYP Dec 18, 2014
@pdav pdav added the bug label Dec 18, 2014
@pdav
Copy link
Collaborator

pdav commented Apr 13, 2018

To solve this problem, the proposed solution is to add a foreign key from the dhcprange to the network id.
This way, network deletion is forbidden while a dhcprange references it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants