neutron-db-manage upgrade heads returned 1

Bug #1708463 reported by Matthias Runge on 2017-08-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Undecided
Unassigned

Bug Description

I'm doing a fresh deployment, and it currently fails with

2017-08-03 11:22:02 | 2017-08-03 11:22:02,236 INFO: ESC[mNotice: /Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: packet.check_error()ESC[0m
2017-08-03 11:22:02 | 2017-08-03 11:22:02,236 INFO: ESC[mNotice: /Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 393, in check
_errorESC[0m
2017-08-03 11:22:02 | 2017-08-03 11:22:02,236 INFO: ESC[mNotice: /Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: err.raise_mysql_exception(self._data)ESC[0m
2017-08-03 11:22:02 | 2017-08-03 11:22:02,237 INFO: ESC[mNotice: /Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: File "/usr/lib/python2.7/site-packages/pymysql/err.py", line 107, in raise_mysql_e
xceptionESC[0m
2017-08-03 11:22:02 | 2017-08-03 11:22:02,237 INFO: ESC[mNotice: /Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: raise errorclass(errno, errval)ESC[0m
2017-08-03 11:22:02 | 2017-08-03 11:22:02,237 INFO: ESC[mNotice: /Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: oslo_db.exception.DBError: (pymysql.err.InternalError) (1050, u"Table 'standardattributes' already exists") [SQL: u'\nCREATE TABLE standardattributes (\n\tid BIGINT NOT NULL AUTO_INCREMENT, \n\tresource_type VARCHAR(255) NOT NULL, \n\tPRIMARY KEY (id)\n)ENGINE=InnoDB\n\n']ESC[0m
2017-08-03 11:22:02 | 2017-08-03 11:22:02,237 INFO: ESC[1;31mError: /Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]: Failed to call refresh: neutron-db-manage upgrade heads returned 1 instead of one of [0]ESC[0m

The deployment is done with TripleO, I'm using CentOS 7.3, neutron packages are:

python-neutron-11.0.0-0.20170731021410.63f4d77.el7.centos.noarch
openstack-neutron-ml2-11.0.0-0.20170731021410.63f4d77.el7.centos.noarch
openstack-neutron-11.0.0-0.20170731021410.63f4d77.el7.centos.noarch
openstack-neutron-openvswitch-11.0.0-0.20170731021410.63f4d77.el7.centos.noarch
puppet-neutron-11.2.1-0.20170728192630.342cc06.el7.centos.noarch
python-neutron-lib-1.9.1-0.20170725142825.0ef54c3.el7.centos.noarch
python2-neutronclient-6.4.0-0.20170728181502.3c211f3.el7.centos.noarch
openstack-neutron-common-11.0.0-0.20170731021410.63f4d77.el7.centos.noarch

(the numbers are timestamps and git hashes from upstream)

Tags: db Edit Tag help
Changed in neutron:
milestone: none → pike-rc1
Kevin Benton (kevinbenton) wrote :

Is the migration being run concurrently by multiple machines?

Is there a way you can run that command manually so we can get the full stack trace?

Matthias Runge (mrunge) wrote :

It's run on a single machine. Yesterday, it seemed to be fixed with a checkout from the weekend.

Changed in neutron:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers