[SWARM 9.2] deploy_neutron_tun_ha_nodegroups test failed

Bug #1640191 reported by Dmitry Belyaninov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Sustaining

Bug Description

Detailed bug description:
There is failed swarm test:

https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.thread_7/119/testReport/(root)/deploy_neutron_tun_ha_nodegroups/deploy_neutron_tun_ha_nodegroups/

Task 'deploy' has incorrect status. error != ready, 'Deployment has failed. All nodes are finished. Failed tasks: Task[openstack-network-server-nova/1] Stopping the deployment process!'

Logs:
File "/usr/lib/python2.7/dist-packages/neutron/db/allowedaddresspairs_db.py", line 78, in _extend_port_dict_allowed_address_pairs
address_pair in port_db.allowed_address_pairs]
AttributeError: 'dict' object has no attribute 'allowed_address_pairs'

http://paste.openstack.org/show/588382/

Steps to reproduce:
run the test
Expected results:
pass
Actual result:
fail
Reproducibility:
 <put your information here>
Workaround:
 <put your information here>
Impact:
 <put your information here>
Description of the environment:
 Operation system: <put your information here>
 Versions of components: <put your information here>
 Reference architecture: <put your information here>
 Network model: <put your information here>
 Related projects installed: <put your information here>
Additional information:
 <put your information here>

Tags: area-library
Changed in fuel:
status: New → Confirmed
tags: added: area-neutron
Changed in fuel:
assignee: MOS Neutron (mos-neutron) → Ann Taraday (akamyshnikova)
Revision history for this message
Ann Taraday (akamyshnikova) wrote :

I investigated this problem.

In the fail_error_deploy_neutron_tun_ha_nodegroups-fuel-snapshot-2016-11-08_01-55-43.tar error with "'allowed_address_pairs" is not shown.

I deployed an environment with 9.2 and although neutron server log have a lot of traces like http://paste.openstack.org/show/588382/ environment is completely operable and neutron-server is not stopped. I filed an upstream bug about this trace - https://bugs.launchpad.net/neutron/+bug/1640701, but I'm convinced this can not be cause of failed job.

In fail_error_deploy_neutron_tun_ha_nodegroups-fuel-snapshot-2016-11-08_01-55-43.tar I noticed a lot of traces like http://paste.openstack.org/show/588659/, so I consider that cinder team should take a look on it.

tags: added: area-cinder
removed: area-neutron
Changed in fuel:
assignee: Ann Taraday (akamyshnikova) → nobody
Changed in fuel:
assignee: nobody → MOS Cinder (mos-cinder)
Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Ann, mentioned logs are not available to cinder. It's a deployment-time issue, when fuel starts cinder before DB setyp

tags: added: area-neutron
removed: area-cinder
Ivan Kolodyazhny (e0ne)
Changed in fuel:
assignee: MOS Cinder (mos-cinder) → Ann Taraday (akamyshnikova)
Revision history for this message
Ann Taraday (akamyshnikova) wrote :

Ivan, why this is Neutron issue? Can you please show a paste with Neutron error, which I should investigate?

I describe that "AttributeError: 'dict' object has no attribute 'allowed_address_pairs'" can not be related to job failure.

Revision history for this message
Ann Taraday (akamyshnikova) wrote :

I remove assignment of this bug for neutron-area.

tags: removed: area-neutron
Changed in fuel:
assignee: Ann Taraday (akamyshnikova) → nobody
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

The problem is that node-1 went offline during environment. Marking this as incomplete, please reopen as soon as we have live env to debug.

Changed in fuel:
status: Confirmed → Incomplete
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
tags: added: area-library
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Marking as Invalid, because of no reproduce.

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.