Erros with sqlite3.OperationalError traces during "heat-manage db_sync" execution

Bug #1562753 reported by Ivan Udovichenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
New
Undecided
Unassigned

Bug Description

The command which was used to sync the DB:
$ heat-manage -d --config-file /etc/heat/heat.conf db_sync

heat.conf file contents:
Full: http://paste.openstack.org/show/492012/
Without comments and empty lines: http://paste.openstack.org/show/492013/

Below you may see the example of errors in log file:
"""
2016-03-28 11:17:17.976 18138 ERROR oslo_service.service OperationalError: (sqlite3.OperationalError) no such table: service [SQL: u'SELECT service.created_at AS service_created_at, service.updated_at AS service_updated_at, service.deleted_at AS service_deleted_at, service.id AS service_id, service.engine_id AS service_engine_id, service.host AS service_host, service.hostname AS service_hostname, service.binary AS service_binary, service.topic AS service_topic, service.report_interval AS service_report_interval \nFROM service \nWHERE service.host = ? AND service.binary = ? AND service.hostname = ?'] [parameters: ('ubuntuos', 'heat-engine', 'ubuntuos')]
...
2016-03-28 11:17:17.967 18140 ERROR oslo_service.service OperationalError: (sqlite3.OperationalError) no such table: service [SQL: u'SELECT service.created_at AS service_created_at, service.updated_at AS service_updated_at, service.deleted_at AS service_deleted_at, service.id AS service_id, service.engine_id AS service_engine_id, service.host AS service_host, service.hostname AS service_hostname, service.binary AS service_binary, service.topic AS service_topic, service.report_interval AS service_report_interval \nFROM service \nWHERE service.host = ? AND service.binary = ? AND service.hostname = ?'] [parameters: ('ubuntuos', 'heat-engine', 'ubuntuos')]
"""

Excerpt from the log file:
http://paste.openstack.org/show/492014/

Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.