Nova says: Duplicate column name 'cleaned'

[Andrey Danin]

VERSION:
  mirantis: "no"
  release: "4.1"
  build_number: "169"
  build_id: "2014-02-20_12-38-56"
  fuellib_sha: "35299a0aa5c9f75ee20c5b05003403a3d51af11c"
  nailgun_sha: "1cafb7c9a81946a056dcaa6554d48bf396c90e9e"
  astute_sha: "3d43abeefb60677ce6cae83d31ebbba1ff3cdbe2"
  ostf_sha: "380d376b8f16d1cf040b7cabbe9133fd0dcbeadd"
  fuelmain_sha: "15637d29a59f299ee8ffe6560245a6884e954cbe"

Cluster: simple Neutron VLAN.
Nodes: 1 controller and 1 compute.
Puppet failed on Controller with a message:
ERR (/Stage[main]/Nova::Api/Exec[nova-db-sync]/returns) change from notrun to 0 failed: /usr/bin/nova-manage db sync returned 1 instead of one of [0] at /etc/puppet/modules/nova/manifests/api.pp:117
When I run /usr/bin/nova-manage db sync manually it returns: http://paste.openstack.org/show/67647/

[Vladimir Kuklin (vkuklin)]

Have 2 different envs (Centos Simple, Ubuntu-HA-GRE) and cannot reproduce it.

[Andrey Danin (gcon-monolake)]

This was because of timeout when 'nova-manage db sync' runs:
2014-02-20T14:18:00.134009+00:00 debug: Executing '/usr/bin/nova-manage db sync'
2014-02-20T14:23:00.225802+00:00 err: (/Stage[main]/Nova::Api/Exec[nova-db-sync]/returns) change from notrun to 0 failed: Command exceeded timeout at /etc/puppet/modules/nova/manifests/api.pp:117

Should we change the timeout or this is only my problem with a slow hardware?