yahoo-eng-team team mailing list archive

[Armando Migliaccio <1636485@xxxxxxxxxxxxxxxxxx>]

For now, I'll make sure this is documented in [1], but unless someone
manages to find a better solution as those presented in #9, I think this
is not worth fixing (e.g. an internal bulk port update API)?

[1] https://review.openstack.org/#/c/361776/

** Changed in: neutron
       Status: Confirmed => Won't Fix

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

Title:
  VLAN aware VM - VM can be booted with neutron port which was
  configured as trunk-sub-port

Status in neutron:
  Won't Fix

Bug description:
  OSP10
  We created 2 internal networks, net1 and net2, created port from each network, port1 and port2.
  The port1 one was created as trunnk and port2 one as subport with vlan tag.

  We can boot VM with port2 - we should not allow that.

  BR

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