Subnet creation of 192.168.0/24 is accepted by neutron but incorrect subnet mask is used

[Colin MacGiollaEain]

Hi,

A typo in creating a neutron subnet (192.168.0/24 instead of 192.168.0.0/24) caused issues as the parameter was accepted (insufficient validation?) but then the subnet mask offered via DHCP was a /32.

For many systems omission of the last dotted quad is implicitly accepted as a .0 e.g. 192.168.0/24 -> accepted as -> 192.168.0.0/24 - why did the subnet mask change from /24 to /32

Correcting this required deleting and recreating the subnet.

Rgds,
Colin

[Praveen (praveen-karadakal)]

When subnet is crated with following command,
quantum subnet-create 1a151cc5-dd75-4b6c-a256-5f608843dc83 192.168.0/24

It is observed that agent gets configuration as 192.168.0/24. Agent fails in parsing this address.
API server should validate the address and set the right value in configuration.

Snapshot of configuration in agent:

  type:virtual-network-network-ipam
   name:attr(default-domain:admin:vn3,default-domain:default-project:default-network-ipam)

   value
    ipam-subnets
     subnet
      ip-prefix:192.168.0

      ip-prefix-len:24

     default-gateway:192.168.0.254

Adjacencies:
 virtual-network default-domain:admin:vn3
 network-ipam default-domain:default-project:default-network-ipam

[Hari Prasad Killi (haripk)]

Fixed with commit 689cd006ed3d3f95473837083f4a3469324d7749.