Build timed out during 'bvt_1' system test deploy_neutron_vlan_ha_with_public_network

Bug #1375646 reported by Dennis Dmitriev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Sergey Vasilenko

Bug Description

System test 'deploy_neutron_vlan_ha_with_public_network' of the 'bvt_1' group is failed due to build timeout:
http://jenkins-product.srt.mirantis.net:8080/job/fuel_master.centos.bvt_1/386/console

========
2014-09-29 22:59:50,176 - INFO fuel_web_client.py:581 -- Wait for task {u'status': u'running', u'name': u'deploy', u'cluster': 1, u'result': {}, u'progress': 0, u'message': None, u'id': 3, u'uuid': u'21382c2a-4c7b-4951-89fc-600553bb856a'} 7800 seconds
Build timed out (after 200 minutes). Marking the build as aborted.
Build was aborted
========

Actually, there is only 50 minutes of waiting timeout by default. According to sys_test.log the test was aborted on 38 percent of progress.

summary: - Build timed out during system test
+ Build timed out during 'bvt_1' system test
deploy_neutron_vlan_ha_with_public_network
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

Please, check puppet logs for errors. Looks like some operations were timeout.

Changed in fuel:
status: New → Incomplete
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

Confirmed with the following configuration:
CentOS/HA, Neutron/VLAN, no network tagging, 3 Controller, 2 Compute.

Deploy has failed on primary controller:

==== puppet.log from node-1 =======
Tue Sep 30 09:16:45 +0000 2014 Service[neutron-l3](provider=pacemaker) (debug): LSO: {"node-1.test.domain.local"=>"stop"}
Tue Sep 30 09:16:45 +0000 2014 Service[neutron-l3](provider=pacemaker) (debug): STATUS IS: stopped
Tue Sep 30 09:16:49 +0000 2014 /Stage[main]/Neutron::Agents::L3/Service[neutron-l3] (err): Could not evaluate: undefined method `attributes' for nil:NilClass
/etc/puppet/modules/corosync/lib/puppet/provider/service/pacemaker.rb:70:in `get_service_hash'
/etc/puppet/modules/corosync/lib/puppet/provider/service/pacemaker.rb:241:in `enabled?'
/usr/lib/ruby/site_ruby/1.8/puppet/type/service.rb:56:in `retrieve'
/usr/lib/ruby/site_ruby/1.8/puppet/type.rb:1045:in `retrieve'
/usr/lib/ruby/site_ruby/1.8/puppet/type.rb:1040:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/type.rb:1040:in `retrieve'
/usr/lib/ruby/site_ruby/1.8/puppet/type.rb:1063:in `retrieve_resource'
....
===============================

===== /etc/puppet/modules/corosync/lib/puppet/provider/service/pacemaker.rb:70 :
...
      default_start_timeout = XPath.match(metadata, "//actions/action[@name=\'start\']").first.attributes['timeout'].to_i
      default_stop_timeout = XPath.match(metadata, "//actions/action[@name=\'stop\']").first.attributes['timeout'].to_i
...
=====================================================================

Changed in fuel:
status: Incomplete → Confirmed
assignee: Dennis Dmitriev (ddmitriev) → Fuel Library Team (fuel-library)
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Sergey Vasilenko (xenolog)
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

Is there an update on this bug?

Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

It is not reproducing anymore.

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