← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1381617] Re: Check for FIP status in scenario tests cause instability in neutron gate jobs

 

Reviewed:  https://review.openstack.org/130655
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=a754e2d12cdc2c1a7f860f20f2d915dd576c5155
Submitter: Jenkins
Branch:    master

commit a754e2d12cdc2c1a7f860f20f2d915dd576c5155
Author: Carl Baldwin <carl.baldwin@xxxxxx>
Date:   Thu Oct 23 22:47:41 2014 +0000

    Allow some lag for floating IP to reach a status
    
    The current test checks the floating IP status as soon as possible
    without allowing the status to converge.  This doesn't allow for the
    fact that implementations don't report the new status until after
    connectivity has been torn down.  There may be some expected lag that
    is not allowed by the current test.
    
    Change-Id: Icfe4bb2c40fde540bc2a6371630aa3f12dd945ff
    Closes-Bug: #1381617


** Changed in: tempest
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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


References