← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1180944] Re: Internal Vlan assignment issue in Metaplugin while provisioning network

 

Metaplugin is dead.

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

** Changed in: neutron
     Assignee: Nachi Ueno (nati-ueno) => (unassigned)

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

Title:
  Internal Vlan assignment issue in Metaplugin while provisioning
  network

Status in neutron:
  Invalid

Bug description:
  Hi ,

  When creating the subnet for networks , few subnet's DHCP tap interfaces were being set to  internal Vlan tag  4095 ,which is a dead vlan tag and inappropriate. But its not the same case for other networks where the Vlan tag was between 1 to 4094 the valid vlan range. 
  So wherever the 4095 is not assigned the network connectivity is fine and the Vm's are able to get the DHCP ip's.

  This happens randomly.  I have isolated this by testing OVS plugin
  first and ensured no issues in network provisioning, then I tested the
  metaplugin with OVS, encountered the mentioned issue.

  Sample output:

  Bridge br-int
          Port "tapc5b0d0bd-e6"    -- dhcp tap
              tag: 4095
              Interface "tapc5b0d0bd-e6"

  
  Please let me know any further logs are needed.

  
  -Ashok

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