← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1318498] [NEW] Neutron db migration failed due to "reorg pending" if engine is DB2.

 

Public bug reported:

Since db2 limitation, table will be in "reorg pending" state after some continuous alter table operations(add column, drop column). This means that the table is inaccessible for almost all operations until you perform a REORG. 
When run neutron db upgrade, from 4ca36cfc898c to 157a5d299379,  the alembic scripts in that range added 3 columns and dropped 1 column for table "ml2_port_bindings". That resulted in failure of table "ml2_port_bindings" in "reorg pending" state.
Same problem for downgrade migration.

environment: Openstack icehouse + DB2 10.5.

We can't restrict community developers how to operate tables and this
only happen on DB2 but not other engines.  So we could only test the
alembic scripts on DB2 and fix it.

** Affects: neutron
     Importance: Undecided
     Assignee: Wang Bo (chrische)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Wang Bo (chrische)

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

Title:
  Neutron db migration failed due to "reorg pending" if engine is DB2.

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Since db2 limitation, table will be in "reorg pending" state after some continuous alter table operations(add column, drop column). This means that the table is inaccessible for almost all operations until you perform a REORG. 
  When run neutron db upgrade, from 4ca36cfc898c to 157a5d299379,  the alembic scripts in that range added 3 columns and dropped 1 column for table "ml2_port_bindings". That resulted in failure of table "ml2_port_bindings" in "reorg pending" state.
  Same problem for downgrade migration.

  environment: Openstack icehouse + DB2 10.5.

  We can't restrict community developers how to operate tables and this
  only happen on DB2 but not other engines.  So we could only test the
  alembic scripts on DB2 and fix it.

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


Follow ups

References