Fix timeout in change_pacemaker_parameter_not_break_rabbitmq test

Bug #1566324 reported by Volodymyr Shypyguzov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Volodymyr Shypyguzov
Mitaka
Fix Released
High
Volodymyr Shypyguzov
Newton
Fix Committed
High
Volodymyr Shypyguzov

Bug Description

We need to increase timeout to at least 2-3 minutes. Now it's about 20 seconds and tests are sometimes failing because of that with AssertionError: No running rabbitmq nodes found on slave-02.

Changed in fuel:
milestone: none → 9.0
importance: Undecided → Medium
status: New → Confirmed
tags: added: area-qa
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Marcellin Fom Tchassem (mf6510)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (master)

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

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Alexandr Kostrikov (akostrikov-mirantis) wrote :
Revision history for this message
Alexandr Kostrikov (akostrikov-mirantis) wrote :
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

It affects swarm results, let's fix it in mitaka too

tags: added: swarm-fail
Changed in fuel:
assignee: Marcellin Fom Tchassem (mf6510) → Volodymyr Shypyguzov (vshypyguzov)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-qa (master)

Reviewed: https://review.openstack.org/302314
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=8aae1fc4484ad232ff115b11e8eab3c1b9826649
Submitter: Jenkins
Branch: master

commit 8aae1fc4484ad232ff115b11e8eab3c1b9826649
Author: Marcellin Fom Tchassem <email address hidden>
Date: Wed Apr 6 10:04:19 2016 -0500

    Remove assert from the get_rabbit_running_nodes

    In the method change_pacemaker_parameter_not_break_rabbitmq,
    the timeout for the count_run_rabbit is too short.
    That causes sometimes tests to fail with the AssertionError:
    No Running rabbitmq nodes found.
    + increase the timeout and the interval
    + remove assert from get_rabbit_running_nodes method

    Change-Id: I73fe407078121f8ef4d46120299c86e45c879009
    Closes-Bug: #1566324

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/326407

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-qa (stable/mitaka)

Reviewed: https://review.openstack.org/326407
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=4179f95a6e9648185451554e684f5ba936cb619b
Submitter: Jenkins
Branch: stable/mitaka

commit 4179f95a6e9648185451554e684f5ba936cb619b
Author: Marcellin Fom Tchassem <email address hidden>
Date: Wed Apr 6 10:04:19 2016 -0500

    Remove assert from the get_rabbit_running_nodes

    In the method change_pacemaker_parameter_not_break_rabbitmq,
    the timeout for the count_run_rabbit is too short.
    That causes sometimes tests to fail with the AssertionError:
    No Running rabbitmq nodes found.
    + increase the timeout and the interval
    + remove assert from get_rabbit_running_nodes method

    Change-Id: I73fe407078121f8ef4d46120299c86e45c879009
    Closes-Bug: #1566324
    (cherry picked from commit 8aae1fc4484ad232ff115b11e8eab3c1b9826649)

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.