yahoo-eng-team team mailing list archive

[Armando Migliaccio <1381617@xxxxxxxxxxxxxxxxxx>]

Perhaps a more promising course of action here is to relax the Tempest
test to allow for some slack in waiting for the status to go from ACTIVE
to DOWN. This sounds sensible to me, but I don't understand why the test
was not designed this way in the first place.

** Changed in: tempest
       Status: New => Invalid

** Changed in: tempest
       Status: Invalid => Confirmed

** Changed in: tempest
       Status: Confirmed => Opinion

-- 
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