yahoo-eng-team team mailing list archive

[Armando Migliaccio <1381617@xxxxxxxxxxxxxxxxxx>]

Added Tempest to the list of projects affected because of this reason:

The problem found here  stems from the fact that the tempest test does
not wait for the state transition at all:

https://review.openstack.org/#/c/102700/30/tempest/scenario/manager.py

As soon as the the FIP is no longer reachable (a), the test 'assumes'
the status is DOWN (b). However there is a lag between (a) and (b).

The method  check_floating_ip_status could be relaxed to wait until the
transition occurs.

** Also affects: tempest
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1381617

Title:
  Check for FIP status in scenario tests cause instability in neutron
  gate jobs

Status in OpenStack Neutron (virtual network service):
  In Progress
Status in Tempest:
  Opinion

Bug description:
  Since this  Tempest change:

  https://review.openstack.org/#/c/102700/

  We verify that FloatingIP changes status correctly on association and
  dis-association.

  This has shown instability of the dvr tempest job:

  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiaXMgYXQgc3RhdHVzOiBBQ1RJVkUuIGZhaWxlZCAgdG8gcmVhY2ggc3RhdHVzOiBET1dOXCIgQU5EIGZpbGVuYW1lOlwiY29uc29sZS5odG1sXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MTMzODg5NTYxMTgsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0=

  DVR is particularly affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1381617/+subscriptions