Unable to bulk add DHCP ranges v1.9.6

[jpatmore]

Issue type:

**Python version:2.7.12
**NetBox version:1.9.6 (running from Docker Installation : b262543ee421 (v1.9.6))

When trying to add an IP range in to a prefix, setting status to 'DHCP' i'm getting an exception error;

Adding them as individual addresses works fine - only get an error with a range e.g 10.189.47.[72-109]/24

#Edit : this doesnt just seem to affect type DHCP, I no longer seem to be able to add ranges of any type

[zevlag]

Also affecting v2.0.0-dev

[jeremystretch]

This is happening because you're attempting to create duplicate IP addresses. We just need to fix handling of the validation error.

[jpatmore]

Apologies, not sure i follow? (I want to make sure Im not doing something incorrectly). All I'm trying to do is bulk assign a range of IPs withing a prefix to a role (in this case to mark them as part of a DHCP pool), or to add the same description across multiple IPs in a prefix (ie, 'in use as part of DHCP pool'). I was able to do this previous to the upgrade, but now I receive the exception error. The method I'm following is : select a prefix->select IP Addresses tab->select '+Add an IP Address'->select bulk->Add criteria via a range ...and I receive the exception error?

…

On 26 April 2017 at 13:01, Jeremy Stretch ***@***.***> wrote: This is happening because you're attempting to create duplicate IP addresses. We just need to fix handling of the validation error. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AP8498owb2DinTjlY_Z-m6bTg9NbVN_Xks5rz3hSgaJpZM4NHh4x> .

[jeremystretch]

You can add a range of new IP addresses without issue. The error arises when one or more IP addresses that you try to add are duplicates of existing IPs (and uniqueness is enforced). The bulk creation fails because of the duplicate IPs, but the validation failure wasn't being handled properly.

For example, you can create the range 192.0.2.[1-3]/24. But if you then try to create 192.0.2.[3-5]/24, it will fail, because 192.0.2.3 already exists.

[jpatmore]

right, but I'm not trying to create a range that includes an IP that already exists? In my example, I'm trying to add the range 10.189.47.[72-109]/24, but as per the screenshot below, these addresses have not yet been allocated?

..but I get the validation error. This happens regardless of which subnet I try to do the bulk update to, and whether any IPs have been allocated in there already. I'm thinking this must be an error in how I have set up/allocated the ranges, as no-one else seems to be reporting having this issue...