Cluster deployment timeout too low for Ubuntu smoke test

[Aleksandra Fedorova]

http://jenkins-product.srt.mirantis.net:8080/view/7.0/job/7.0.test_all/3/ failed with: "TimeoutError: Waiting task "deploy" timeout 3000 sec was exceeded"

This job is failing (and will continue to fail) because of a recently merged commit to fuel-qa [0] that changed the timeout for the deploy_cluster_wait method. A timeout of 3000 seconds is now passed into assert_task_wait instead of relying on its default of 7800 seconds. 3000 seconds is highly optimistic. The previously successful run of that test took over an hour.

[0] https://review.openstack.org/#/c/189274

[Aleksandra Fedorova (bookwar)]

 centos.bvt_1

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/189971

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/189971
Committed: https://git.openstack.org/cgit/stackforge/fuel-qa/commit/?id=2b3dcc8dea5deff1d1a71fdda0ada0994c4c1088
Submitter: Jenkins
Branch: master

commit 2b3dcc8dea5deff1d1a71fdda0ada0994c4c1088
Author: Ryan Moe <email address hidden>
Date: Tue Jun 9 15:58:24 2015 -0700

    Revert "Use timeout varibale for assert_task_success"

    This reverts commit ec2544ac85f63bdb55237bb17c9acd21d5f00f16.

    Change-Id: Ia921f744d8fed764544badc1cb641ebe63728ced
    Closes-bug: #1463601

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/190040
Committed: https://git.openstack.org/cgit/stackforge/fuel-qa/commit/?id=39c983a390f5a8daaa173dddef8c639510f1537e
Submitter: Jenkins
Branch: stable/6.1

commit 39c983a390f5a8daaa173dddef8c639510f1537e
Author: Nastya Urlapova <email address hidden>
Date: Wed Jun 10 06:46:37 2015 +0000

    Revert "Use timeout varibale for assert_task_success"

    This reverts commit 754044b3abdad7575f0859dd9db231a1a9536f16.

    Closes-bug: #1463601
    Change-Id: I59adbf00b6065c4e0dfc153d9a45a64afc513a53

[Ryan Moe (rmoe)]

I think the better fix for this problem is here [0]. If it had been merged instead of the reverted commit (which was basically a duplicate of [0]) this problem wouldn't have occurred.

[0] https://review.openstack.org/#/c/186672

[Nastya Urlapova (aurlapova)]

@Ryan, thank you for comment! Actually we have a rule in Fuel - if a commit brought critical regression we have to revert it asap, after that we may to do a right fix.

[Timur Nurlygayanov (tnurlygayanov)]

Tests are green now, bug verified.