yahoo-eng-team team mailing list archive

[Jakub Libosvar <libosvar@xxxxxxxxxx>]

The used versions are both from master branch. Because of master can
contain database changes, you need to use neutron-db-manage [1] to make
your database up-to-date reflecting used models in the code.

I'm closing this bug as invalid as database wasn't migrated in this
case.

[1]
https://docs.openstack.org/neutron/latest/contributor/alembic_migrations.html

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

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

Title:
  Likely mismatch between code and database schema

Status in neutron:
  Invalid

Bug description:
  Description of problem: Seeing several messages like this in neutron-server logs
  https://gist.github.com/smalleni/e0422a42881f015ce3436ce7d6ac1a30

  (1054, u"Unknown column 'mtu' in 'field list'") seems to be the
  problem

  Looking at the table, there doesn't seem to be an mtu field
  MariaDB [ovs_neutron]> describe networks;
  +-------------------------+--------------+------+-----+---------+-------+
  | Field                   | Type         | Null | Key | Default | Extra |
  +-------------------------+--------------+------+-----+---------+-------+
  | project_id              | varchar(255) | YES  | MUL | NULL    |       |
  | id                      | varchar(36)  | NO   | PRI | NULL    |       |
  | name                    | varchar(255) | YES  |     | NULL    |       |
  | status                  | varchar(16)  | YES  |     | NULL    |       |
  | admin_state_up          | tinyint(1)   | YES  |     | NULL    |       |
  | vlan_transparent        | tinyint(1)   | YES  |     | NULL    |       |
  | standard_attr_id        | bigint(20)   | NO   | UNI | NULL    |       |
  | availability_zone_hints | varchar(255) | YES  |     | NULL    |       |
  +-------------------------+----

  
  Version-Release number of selected component (if applicable):
  OpenStack Pike
  puppet-neutron-11.3.0-0.20170805104936.743dde6.el7ost.noarch
  python-neutronclient-6.5.0-0.20170807200849.355983d.el7ost.noarch
  openstack-neutron-lbaas-11.0.0-0.20170807144457.c9adfd4.el7ost.noarch
  python-networking-l2gw-10.1.0-0.20170804100327.a8ae0e3.el7ost.noarch
  python-neutron-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  openstack-neutron-linuxbridge-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  openstack-neutron-common-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  openstack-neutron-ml2-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  openstack-neutron-openvswitch-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  python-neutron-lbaas-11.0.0-0.20170807144457.c9adfd4.el7ost.noarch
  python-networking-odl-11.0.0-0.20170806093629.2e78dca.el7ost.noarch
  python-networking-ovn-3.0.0-0.20170807061656.2425483.el7ost.noarch
  openstack-neutron-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  python-networking-bgpvpn-7.0.0-0.20170807233234.c54f55e.el7ost.noarch
  openstack-neutron-sriov-nic-agent-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  python-neutron-lib-1.9.1-0.20170731102145.0ef54c3.el7ost.noarch
  openstack-neutron-metering-agent-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch
  python-neutron-tests-11.0.1-0.20170913033853.6b26bc5.el7ost.noarch

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