Segmentation_id beyond specified range does not raise an error

[sandeep mane]

Problem in segment-Id range, it should belongs to given range,
command to reproduce :

neutron net-create demo_net --provider:network_type gre --provider:Segmentation_id 2000

right now its allowing to create.

expected:
neutron should give an error if we give Segmentation_id beyond specified range.

[Eugene Nikanorov (enikanorov)]

I think that was done specifically to allow admin to allocate networks with specific segmentation_ids while regular ranges work with those IDs that are allocated.

I believe that is intentional and should be restricted.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/240882

[Sean M. Collins (scollins)]

This is still an opinion bug, looks like changing it to invalid caused someone to think it should be worked on.....

[OpenStack Infra (hudson-openstack)]

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/240882
Reason: As per reviewers' comments, there is no need to fix the intended behavior. That said, we should perhaps document it somewhere so that it's clear.

[Armando Migliaccio (armando-migliaccio)]

The segmentation range is to be used internally by Neutron for tenant networks, the admin instead is in full charge of his/her own destiny.

We should probably document this somewhere, but in practice no fix is required.

[Kyle Mestery (mestery)]

Lets make this "Won't Fix" instead then.