← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1743425] [NEW] Changes to VLAN mapping results in "is not mapped" error

 

Public bug reported:

With neutron-server if you enable the type_drivers = vlan and set a
mapping in [ml2_type_vlan] then install the neutron database, the
service will start and map successfully.

However if you change the mapping after and restart the service you will
receive error:

2018-01-15 11:50:36.875 9764 ERROR neutron   File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/type_vlan.py", line 133, in _sync_vlan_allocations
2018-01-15 11:50:36.875 9764 ERROR neutron     ctx.session.delete(alloc)
2018-01-15 11:50:36.875 9764 ERROR neutron   File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 1744, in delete
2018-01-15 11:50:36.875 9764 ERROR neutron     raise exc.UnmappedInstanceError(instance)
2018-01-15 11:50:36.875 9764 ERROR neutron UnmappedInstanceError: Class 'neutron.objects.plugins.ml2.vlanallocation.VlanAllocation' is not mapped
2018-01-15 11:50:36.875 9764 ERROR neutron 


plugin.ini:
[ml2]
type_drivers = vlan
tenant_network_types = vlan
mechanism_drivers = openvswitch

[ml2_type_vlan]
network_vlan_ranges = physnet0:2:4000

sync DB:
 su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron

Start neutron-server, Success!

Now change plugin.ini to the following:

[ml2_type_vlan]
network_vlan_ranges = physnet1:2:4000

Restart neutron-server.  Failure!

Versions:
openstack-neutron-11.0.2-3.el7.noarch
openstack-neutron-ml2-11.0.2-3.el7.noarch
openstack-neutron-common-11.0.2-3.el7.noarch
openstack-neutron-openvswitch-11.0.2-3.el7.noarch
openstack-neutron-linuxbridge-11.0.2-3.el7.noarch
python-neutron-11.0.2-3.el7.noarch
python-neutron-lib-1.9.1-1.el7.noarch
python2-neutronclient-6.5.0-1.el7.noarch

pip
neutron==11.0.2
neutron-lib==1.9.1
python-neutronclient==6.5.0

CentOS 7 @ 3.10.0-693.11.6.el7.x86_64

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Changes to VLAN mapping results in "is not mapped" error

Status in neutron:
  New

Bug description:
  With neutron-server if you enable the type_drivers = vlan and set a
  mapping in [ml2_type_vlan] then install the neutron database, the
  service will start and map successfully.

  However if you change the mapping after and restart the service you
  will receive error:

  2018-01-15 11:50:36.875 9764 ERROR neutron   File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/type_vlan.py", line 133, in _sync_vlan_allocations
  2018-01-15 11:50:36.875 9764 ERROR neutron     ctx.session.delete(alloc)
  2018-01-15 11:50:36.875 9764 ERROR neutron   File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 1744, in delete
  2018-01-15 11:50:36.875 9764 ERROR neutron     raise exc.UnmappedInstanceError(instance)
  2018-01-15 11:50:36.875 9764 ERROR neutron UnmappedInstanceError: Class 'neutron.objects.plugins.ml2.vlanallocation.VlanAllocation' is not mapped
  2018-01-15 11:50:36.875 9764 ERROR neutron 

  
  plugin.ini:
  [ml2]
  type_drivers = vlan
  tenant_network_types = vlan
  mechanism_drivers = openvswitch

  [ml2_type_vlan]
  network_vlan_ranges = physnet0:2:4000

  sync DB:
   su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron

  Start neutron-server, Success!

  Now change plugin.ini to the following:

  [ml2_type_vlan]
  network_vlan_ranges = physnet1:2:4000

  Restart neutron-server.  Failure!

  Versions:
  openstack-neutron-11.0.2-3.el7.noarch
  openstack-neutron-ml2-11.0.2-3.el7.noarch
  openstack-neutron-common-11.0.2-3.el7.noarch
  openstack-neutron-openvswitch-11.0.2-3.el7.noarch
  openstack-neutron-linuxbridge-11.0.2-3.el7.noarch
  python-neutron-11.0.2-3.el7.noarch
  python-neutron-lib-1.9.1-1.el7.noarch
  python2-neutronclient-6.5.0-1.el7.noarch

  pip
  neutron==11.0.2
  neutron-lib==1.9.1
  python-neutronclient==6.5.0

  CentOS 7 @ 3.10.0-693.11.6.el7.x86_64

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


Follow ups