9.x.main.ubuntu.bvt_2 #666 failed

Bug #1651976 reported by Dmitry Teselkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Fuel CI

Bug Description

Job URL: https://product-ci.infra.mirantis.net/job/9.x.main.ubuntu.bvt_2/666/
Snapshot URL: N/A

Job was aborted because of timeout (180 min).

console log contains
-----
2016-12-21 15:11:47 - INFO fuel_web_client.py:1407 -- Wait for task 7800 seconds:
 status pending
 time_start None
 name deploy
 dry_run False
 cluster 1
 time_end None
 parent_id None
 result {}
 progress 0
 graph_type None
 message None
 id 5
 uuid f4fe1759-cb11-4fc0-88ee-1c796db1d9e3
Build timed out (after 180 minutes). Marking the build as aborted.
Build was aborted
Archiving artifacts
Terminated
+ ec=143
+ [ != no ]
+ find /home/jenkins/workspace/9.x.main.ubuntu.bvt_2/logs -name fail*.tar.[gx]z -type f
+ [ != yes ]
+ [ no = yes ]
+ dos.py destroy 9.x.main.ubuntu.bvt_2.666
-----

Tags: area-ci
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

I think it is related to build number, but who knows.

Changed in fuel:
assignee: nobody → Fuel CI (fuel-ci)
tags: added: area-ci
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

Was not reproduced on #667 job.

Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :

Seems like not related to number and reproduced on [1]

[1] https://ci.fuel-infra.org/job/11.0-community.main.ubuntu.bvt_2/232/

Revision history for this message
Alexander Evseev (aevseev) wrote :

fuel-qa, should we increase job timeout?

Changed in fuel:
assignee: Fuel CI (fuel-ci) → Fuel QA Team (fuel-qa)
Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

Nope, we should not increase job timeout! We should understand why usual green test wasn't successful of that server.

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Fuel CI (fuel-ci)
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

Could you identify a load on that server?

Revision history for this message
Alexander Evseev (aevseev) wrote :

No, sorry

Revision history for this message
Alexander Evseev (aevseev) wrote :

Found some info in zabbix - CPU load about 50%, RAM about 40-60GB

Changed in fuel:
milestone: none → 9.2
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Dmitry Kaigarodеsev (dkaiharodsev) wrote :

seems like bvt tests are stable in a latest few days and without any timeout aborts, please re-open this bug if will be reproduced

Changed in fuel:
status: Confirmed → Fix Committed
Roman Vyalov (r0mikiam)
Changed in fuel:
status: Fix Committed → Fix Released
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.