yahoo-eng-team team mailing list archive

[Miguel Lavalle <miguel@xxxxxxxxxxxx>]

This bug was discussed today during the L3 subteam meeting and the
agreement was that is is invalid. Please see discussion log here:
http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-08-03-15.00.log.html#l-90

** Changed in: neutron
       Status: In Progress => Invalid

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

Title:
  Differece behavior about enable subnet service types scenario

Status in neutron:
  Invalid

Bug description:
  Repro:
  1. create a net and a subnet 'A-compute-nova' with service_types "compute:nova"
  2. exec neutron port-create only specified the network ID/name.
     This will return "No valid service subnet for the given device owner."
     We only can create port with device_owner "compute:nova"
  3. create another subnet 'B-None', no specify the service_types.
  Then create port with device_owner=compute:nova and fixed_ip from 'B-None', it create successful.
  But why not raise the error just the same with step 2? As we wish the IPs of port always allocate from the subnet which service_type is 'compute:nova'.

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