test_live_migration_actions notification sample test fails intermittently with 'notification instance.live_migration_rollback.start hasn't been received'

Bug #1742688 reported by Balazs Gibizer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Balazs Gibizer

Bug Description

Traceback (most recent call last):
  File "nova/tests/functional/notification_sample_tests/test_instance.py", line 63, in test_live_migration_actions
    action(server)
  File "/home/zuul/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched
    return func(*args, **keywargs)
  File "nova/tests/functional/notification_sample_tests/test_instance.py", line 78, in _test_live_migration_rollback
    self._wait_for_notification('instance.live_migration_rollback.start')
  File "nova/tests/functional/notification_sample_tests/notification_sample_base.py", line 231, in _wait_for_notification
    'notification %s hasn\'t been received' % event_type)
  File "/home/zuul/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/unittest2/case.py", line 702, in assertTrue
    raise self.failureException(msg)
AssertionError: False is not true : notification instance.live_migration_rollback.start hasn't been received

There was 5 failures in the last 7 days.

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22AssertionError%3A%20False%20is%20not%20true%20%3A%20notification%20instance.live_migration_rollback.start%20hasn't%20been%20received%5C%22

Tags: testing
Changed in nova:
assignee: nobody → Balazs Gibizer (balazs-gibizer)
Revision history for this message
Balazs Gibizer (balazs-gibizer) wrote :

The logs does not show anything unusual. Locally I was not able to reproduce the problem during more than 50 trials. By comparing the logs between the local successful run and the gate failures the only interesting thing differences is timing. On my machine the it took less then a second from starting the second compute to execute the live migration and receive the rollback notification. On the gate failure it took 4 seconds from starting the second compute to get the last log message before the test failed. So it seems that the gate execution a lot slower. Currently the timeout to wait for the rollback notification to arrive is 1 second. So it is possible that the test times out on the gate before the notification has a chance to arrive.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: New → In Progress
melanie witt (melwitt)
tags: added: testing
Changed in nova:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/532816
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8b444de795263fc65128030098708331e8ff0afb
Submitter: Zuul
Branch: master

commit 8b444de795263fc65128030098708331e8ff0afb
Author: Balazs Gibizer <email address hidden>
Date: Thu Jan 11 14:23:15 2018 +0100

    Increase notification wait timeout in functional tests

    In the baseline the wait_for_notification() functional test util
    function by default waits maximum 1 second for a notification to
    arrive. Based on recent gate failures it seems that it is not enough
    in some cases for the notitification to arrive. Therefore this patch
    bumps the default timeout to 10 seconds. This will only make the test
    execution slower if the notifiication arrives later or does not even
    arrive. So in the happy case the test execution will not be slower.

    Change-Id: I75e2bcd87535de7e44bdf317c3ab12ba8952dcca
    Closes-Bug: #1742688

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 17.0.0.0b3

This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.

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.