yahoo-eng-team team mailing list archive

[Proskurin Kirill <kproskurin@xxxxxxxxxxxx>]

Public bug reported:

Currently alembic_version table in the neutron db has no primary key.

Which is a bad thing, if you consider to use Galera as a database, since
it requires primary keys in all tables.

For example, during the "INFO  [alembic.runtime.migration] Running
upgrade  -> kilo, kilo_initial" migration you will get the:

oslo_db.exception.DBError: (pymysql.err.InternalError) (1105, u'Percona-
XtraDB-Cluster prohibits use of DML command on a table
(neutron.alembic_version) without an explicit primary key with
pxc_strict_mode = ENFORCING or MASTER') [SQL: u"INSERT INTO
alembic_version (version_num) VALUES ('kilo')"]

** Affects: neutron
     Importance: Undecided
     Assignee: Ann Taraday (akamyshnikova)
         Status: New


** Tags: db

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

Title:
  alembic_version table has no primary key

Status in neutron:
  New

Bug description:
  Currently alembic_version table in the neutron db has no primary key.

  Which is a bad thing, if you consider to use Galera as a database,
  since it requires primary keys in all tables.

  For example, during the "INFO  [alembic.runtime.migration] Running
  upgrade  -> kilo, kilo_initial" migration you will get the:

  oslo_db.exception.DBError: (pymysql.err.InternalError) (1105, u
  'Percona-XtraDB-Cluster prohibits use of DML command on a table
  (neutron.alembic_version) without an explicit primary key with
  pxc_strict_mode = ENFORCING or MASTER') [SQL: u"INSERT INTO
  alembic_version (version_num) VALUES ('kilo')"]

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