yahoo-eng-team team mailing list archive

[Armando Migliaccio <1545199@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The subnet create command [1] creates a subnet that does not belong to a
subnet pool. When a default subnet pool is present, however, the subnet
is implicitly assigned to the default pool, and hence the command
triggers prefix validation.

[1] neutron subnet-create <net> <cidr> <name>

It's probably better to preserve the semantic of the message
irrespective of the presence of the (default) pool.

If a user does want the association, he/she can either be explicit (by
passing --subnetpool/-id) or simply specify the family of the subnet,
like in [2] (by default the client chooses v4).

This happens in master.

[2] neutron subnet-create <net> --ip-version <name>

** Affects: neutron
     Importance: Low
     Assignee: Armando Migliaccio (armando-migliaccio)
         Status: Confirmed


** Tags: l3-dvr-backlog liberty-backport-potential

** Changed in: neutron
     Assignee: (unassigned) => Armando Migliaccio (armando-migliaccio)

** Changed in: neutron
   Importance: Undecided => Low

** Changed in: neutron
       Status: New => Confirmed

** Tags added: liberty-backport-potential

** Tags added: l3-dvr-backlog

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1545199

Title:
  preserve subnet-create behavior in presence of subnet pools

Status in neutron:
  Confirmed

Bug description:
  The subnet create command [1] creates a subnet that does not belong to
  a subnet pool. When a default subnet pool is present, however, the
  subnet is implicitly assigned to the default pool, and hence the
  command triggers prefix validation.

  [1] neutron subnet-create <net> <cidr> <name>

  It's probably better to preserve the semantic of the message
  irrespective of the presence of the (default) pool.

  If a user does want the association, he/she can either be explicit (by
  passing --subnetpool/-id) or simply specify the family of the subnet,
  like in [2] (by default the client chooses v4).

  This happens in master.

  [2] neutron subnet-create <net> --ip-version <name>

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1545199/+subscriptions