Timeout for ostf stack update is too short

Bug #1567727 reported by John Hua on 2016-04-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Timur Nurlygayanov
Mitaka
High
Timur Nurlygayanov
Newton
High
Timur Nurlygayanov

Bug Description

The heat template update takes longer timer than given ESP when updating flavor(step 9) or changed from one instance to two(step 12).

Suggest in fuel_health.tests.tests_platform.test_heat.test_update, adjust the time limit for:

  step 9: from 100 to 150
  step 12: from 180 to 300

This issue is found in MOS8 but also applicable to master(MOS9).

A test report as below:

Time comsumed Time limit Steps
0 50 1.Createtestflavor.
4 20 2.Createastack.
121 300 3.Waitforthestackstatustochangeto'CREATE_COMPLETE'.
0 20 4.Changeinstancename,executeupdatestackin-place.
10 100 5.Waitforthestackstatustochangeto'UPDATE_COMPLETE'.
0 6.Checkthatinstancenamewaschanged.
0 60 7.Createonemoretestflavor.
1 20 8.Changeinstanceflavortojustcreatedandupdatestack
110 100 9.Waitforthestackstatustochangeto'UPDATE_COMPLETE'.
0 10.Checkthatinstanceflavorwaschanged.
2 20 11.Changestacktemplateandupdateit.
227 180 12.Waitforthestackstatustochangeto'UPDATE_COMPLETE'.
0 2 13.Checkthatthereareonlytwonewlycreatedstackinstances.
0 200 14.Deletethestack.
10 100 15.Waitforthestacktobedeleted.

John Hua (john-hua) on 2016-04-08
tags: added: heat
description: updated
John Hua (john-hua) on 2016-04-08
description: updated
John Hua (john-hua) on 2016-04-08
description: updated
Changed in fuel:
milestone: none → 9.0
assignee: nobody → Fuel QA Team (fuel-qa)
importance: Undecided → Medium
status: New → Confirmed
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → MOS QA Team (mos-qa)

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

expected result

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info

This is customer-found issue and it requires a small fix.
Let's fix it in 9.0 and master.

Changed in fuel:
assignee: MOS QA Team (mos-qa) → Alexander Nagovitsyn (gluk12189)
tags: added: customer-found
Changed in fuel:
importance: Medium → High

John, could you please clarify your enviroment configuration?
Need info about the numbert Cpu, Ram on compute and controller.

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

Changed in fuel:
assignee: Alexander Nagovitsyn (gluk12189) → Timur Nurlygayanov (tnurlygayanov)
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/309980
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=205d188ff6077218a3eecda58a9d55178bd93b4b
Submitter: Jenkins
Branch: master

commit 205d188ff6077218a3eecda58a9d55178bd93b4b
Author: Timur Nurlygayanov <email address hidden>
Date: Mon Apr 25 16:59:42 2016 +0300

    Increased timeout for Heat OSTF test

    It looks like Heat OSTF test has small timeouts for
    operations with stack and we need to increase timeouts
    to avid false-negative results.

    Change-Id: Ia24fda69682c7e079414f725fe78b5484a191d35
    Closes-Bug: #1567727

Changed in fuel:
status: In Progress → Fix Committed

Reviewed: https://review.openstack.org/309981
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=2ccc0e9edd80d040a3e42b19450b83fc0a2e1b66
Submitter: Jenkins
Branch: stable/mitaka

commit 2ccc0e9edd80d040a3e42b19450b83fc0a2e1b66
Author: Timur Nurlygayanov <email address hidden>
Date: Mon Apr 25 17:05:52 2016 +0300

    Increased timeout for Heat OSTF test

    It looks like Heat OSTF test has small timeouts for
    operations with stack and we need to increase timeouts
    to avid false-negative results.

    Change-Id: Ia24fda69682c7e079414f725fe78b5484a191d35
    Closes-Bug: #1567727

John Hua (john-hua) wrote :

Sorry for the silence. The problem is attributed to a bug. The default timeout value is fine.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers