Deployment failed on controller during sync neutron-db-manage

Bug #1498499 reported by Vasily Gorin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Fuel Library (Deprecated)

Bug Description

Build 298

Scenario:

1. Create new environment
2. Choose Neutron, VLAN
3. Add 1 controller
4. Add 1 compute
5. Add 1 cinder
6. Add 1 operating system
7. Verify networks
8. Deploy the environment

Expected result:
Deployment was successfully .

Actual result:
Deploy failed on deploying controller.

2015-09-22 10:09:05 +0000 /Stage[main]/Neutron::Server/Exec[neutron-db-sync] (err): Failed to call refresh: neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade head returned 1 instead of one of [0]

2015-09-22 10:14:26 +0000 Puppet (debug): Executing '/usr/bin/neutron net-list --format=csv --column=id --quote=none'
2015-09-22 10:14:27 +0000 Puppet::Type::Neutron_network::ProviderNeutron (notice): Unable to complete neutron request due to non-fatal error: "Execution of '/usr/bin/neutron net-list --format=csv --column=id --quote=none' returned 1: Request Failed: internal server error while processing your request.

ENV was kept

Tags: area-library
Revision history for this message
Vasily Gorin (vgorin) wrote :
Revision history for this message
Alexander Gordeev (a-gordeev) wrote :

Looks like a library bug, re-assigning to fuel-library.

Andrey Maximov (maximov)
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → MOS Neutron (mos-neutron)
Changed in fuel:
assignee: MOS Neutron (mos-neutron) → Fuel Library Team (fuel-library)
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → MOS Neutron (mos-neutron)
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

Scenario is pretty general, I have a feeling that issue was on local env. I've decreased this one to Incomplete state.
Vasiliy please reproduce failure.

Changed in fuel:
importance: Critical → Undecided
status: New → Incomplete
Revision history for this message
Alexander Gordeev (a-gordeev) wrote :

grep -r 'Failed to call refresh' var/log/docker-logs/remote/
var/log/docker-logs/remote/node-33.test.domain.local/puppet-apply.log:2015-09-22T09:44:40.773521+00:00 err: (/Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]) Failed to call refresh: keystone-manage db_sync returned 1 instead of one of [0]
var/log/docker-logs/remote/node-33.test.domain.local/puppet-apply.log:2015-09-22T09:55:50.117532+00:00 err: (/Stage[main]/Cinder::Api/Exec[cinder-manage db_sync]) Failed to call refresh: cinder-manage db sync returned 1 instead of one of [0]
var/log/docker-logs/remote/node-33.test.domain.local/puppet-apply.log:2015-09-22T10:09:05.473816+00:00 err: (/Stage[main]/Neutron::Server/Exec[neutron-db-sync]) Failed to call refresh: neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade head returned 1 instead of one of [0]

there's a plenty of DB related errors. So, i think something wrong happened with DB or just with connection to it. I'm pretty sure, that observed issue has nothing to do with python related things.

Library guys, please take a look for sure. Assigning back to fuel-library.

Changed in fuel:
assignee: MOS Neutron (mos-neutron) → Fuel Library Team (fuel-library)
Changed in fuel:
milestone: 7.0 → 8.0
Dmitry Pyzhov (dpyzhov)
tags: added: area-library
Maciej Relewicz (rlu)
Changed in fuel:
status: Incomplete → New
Maciej Relewicz (rlu)
Changed in fuel:
importance: Undecided → Medium
Dmitry Klenov (dklenov)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Sergey Vasilenko (xenolog) wrote :

Looks like you use very old ISO.

> "Execution of '/usr/bin/neutron net-list --format=csv --column=id --quote=none' returned 1: Request Failed: internal server error while processing your request.

it's a bug, fixed a week ago,
> "Execution of '/usr/bin/neutron net-list --format=json ...
should be instead

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

10 days of inactivity -> Invalid

Changed in fuel:
status: Incomplete → Invalid
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.