nova-db-sync failed when installing

Bug #1286094 reported by Vadim Rovachev
This bug report is a duplicate of:  Bug #1327987: Savanna deployment failed with error. Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
High
Fuel Library (Deprecated)

Bug Description

{"build_id": "2014-02-27_19-37-46", "mirantis": "yes", "build_number": "224", "nailgun_sha": "12a7e7a99557f2bc302f0806ad3beef02e94b974", "ostf_sha": "8e6681b6d06c7cb20a84c1cc740d5f2492fb9d85", "fuelmain_sha": "ba019bf15a9597a154e7c1d6ecc840614d21414c", "astute_sha": "10cccc87f2ee35510e43c8fa19d2bf916ca1fced", "release": "4.1", "fuellib_sha": "61d3a150402da3ce1160836c8d659f6d9d1f9640"}

Install OpenStack with NovaNetwork (any distributiv), KVM, Install Savanna.
Steps to reproduce
1. Added 1 controller node, 1 compute node.
2. Deploy Changes.

Expected result: OpenStack is installed
Actual result: one of the nodes has error status

node log (controller, puppet, ERR):
2014-02-28 11:05:35 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:119
2014-02-28 11:00:14 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:119
2014-02-28 10:54:51 ERR
 (/Stage[main]/Nova::Api/Exec[nova-db-sync]) Failed to call refresh: Command exceeded timeout at /etc/puppet/modules/nova/manifests/api.pp:119
2014-02-28 10:49:51 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:119

node log (compute, puppet, ERR):
2014-02-28 10:39:39 ERR
 (/Stage[main]/Nova::Api/Exec[nova-db-sync]) Failed to call refresh: /usr/bin/nova-manage db sync returned 1 instead of one of [0] at /etc/puppet/modules/nova/manifests/api.pp:119
2014-02-28 10:39:38 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:119

Revision history for this message
Vadim Rovachev (vrovachev) wrote :
Revision history for this message
Vadim Rovachev (vrovachev) wrote :

{"build_id": "2014-02-28_01-17-30", "mirantis": "yes", "build_number": "225", "nailgun_sha": "12a7e7a99557f2bc302f0806ad3beef02e94b974", "ostf_sha": "ceb3ea8c2c0da27306b30b9936f27dbc5044d2c6", "fuelmain_sha": "ba019bf15a9597a154e7c1d6ecc840614d21414c", "astute_sha": "f15f5615249c59c826ea05d26707f062c88db32a", "release": "4.1", "fuellib_sha": "61d3a150402da3ce1160836c8d659f6d9d1f9640"}

bug reproduced.

2014-02-28 13:48:37 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:119
2014-02-28 13:48:18 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:119
2014-02-28 13:47:59 ERR
 (/Stage[main]/Nova::Api/Exec[nova-db-sync]) Failed to call refresh: /usr/bin/nova-manage db sync returned 1 instead of one of [0] at /etc/puppet/modules/nova/manifests/api.pp:119
2014-02-28 13:47:59 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:119

Revision history for this message
Vadim Rovachev (vrovachev) wrote :

{"build_id": "2014-02-28_01-17-30", "mirantis": "yes", "build_number": "225", "nailgun_sha": "12a7e7a99557f2bc302f0806ad3beef02e94b974", "ostf_sha": "ceb3ea8c2c0da27306b30b9936f27dbc5044d2c6", "fuelmain_sha": "ba019bf15a9597a154e7c1d6ecc840614d21414c", "astute_sha": "f15f5615249c59c826ea05d26707f062c88db32a", "release": "4.1", "fuellib_sha": "61d3a150402da3ce1160836c8d659f6d9d1f9640"}

bug consistently reproduced for any distributive and any node(compute, controller).

Mike Scherbakov (mihgen)
Changed in fuel:
milestone: none → 4.1
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Did you run network verification? Looks like you have issues with networking configuration.

Changed in fuel:
milestone: 4.1 → 4.1.1
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

After a long period of testing we still were not able to reproduce this issue. Reopen it and attach all the networking configuration information along with results of pings from the compute to controller node and vice versa if you still face this issue.

Changed in fuel:
status: New → Incomplete
Changed in fuel:
status: Incomplete → Invalid
Changed in fuel:
importance: Undecided → Low
Revision history for this message
Anastasia Palkina (apalkina) wrote :

Reproduced on ISO #357
"build_id": "2014-06-09_00-40-36",
"mirantis": "yes",
"build_number": "357",
"nailgun_sha": "bdc747cd70721874d1e8af36181fd4179cce4fce",
"ostf_sha": "2b7b39e4b6ea89751b65171f24a8e80b5cac56aa",
"fuelmain_sha": "87d1db0f09ab205526895e41946a780ecca3117a",
"astute_sha": "55df06b2e84fa5d71a1cc0e78dbccab5db29d968",
"release": "4.1.1",
"fuellib_sha": "db24da4030c5d3f9e7743cd872b0deec094217d3"

1. Create new environment (Ubuntu, simple mode)
2. Choose savanna
3. Add controller, compute, cinder
4. Start deloyment. It has failed

Revision history for this message
Anastasia Palkina (apalkina) wrote :

Controller node-12

Changed in fuel:
status: Invalid → Triaged
importance: Low → High
assignee: nobody → Fuel Library Team (fuel-library)
Changed in fuel:
status: Triaged → New
milestone: 4.1.1 → none
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :
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.