OperationalError: (OperationalError) (1054, "Unknown column 'services.disabled_reason' in 'field list'")

[Robert Collins]

in nova-conductor.

2013-06-26 08:02:44,656.656 1487 TRACE nova.openstack.common.rpc.amqp OperationalError: (OperationalError) (1054, "Unknown column 'services.disabled_reason' in 'field list'") 'SELECT services.created_at AS services_created_at, services.updated_at AS services_updated_at, services.deleted_at AS services_deleted_at, services.deleted AS services_deleted, services.id AS services_id, services.host AS services_host, services.`binary` AS services_binary, services.topic AS services_topic, services.report_count AS services_report_count, services.disabled AS services_disabled, services.disabled_reason AS services_disabled_reason \nFROM services \nWHERE services.deleted = %s AND services.host = %s AND services.`binary` = %s \n LIMIT %s' (0, 'ubuntu.localdomain', 'nova-compute', 1)

[Yaguang Tang (heut2008)]

try do nova-manage db sync then restart nova services.

[Robert Collins (lifeless)]

It was a fresh environment, db sync was done before running any services.

[David Ripton (dripton)]

The disabled_reason column was added to the services table in migration 188. Which landed in commit c741e862fd3 on February 20, 2013.

It looks like that migration didn't run on your DB, for whatever reason, and you're using code that relies on it.

What do you see if you do "select * from migrate_version" in your nova DB?

[adrian (awardell)]

mysql> select * from migrate_version;
+---------------+------------------------------------------------------------------+---------+
| repository_id | repository_path | version |
+---------------+------------------------------------------------------------------+---------+
| nova | /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/migrate_repo | 82 |
+---------------+------------------------------------------------------------------+---------+

So what do we do to resolve this issue? I'm having the same problem.

[Dan Smith (danms)]

Is this still a problem? It seems clearly related to a mismatch between code version and schema version, especially as indicated by comment #4. It's been a year since this was filed, so I expect this just needs to be closed.

[Sean Dague (sdague)]

I actually think this was probably the unbuntu cloud archive issue where the packages default to essex, but the cloud archive packages want to roll 2 releases, then don't (because we removed the ability to do that)