yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #15020
[Bug 1314313] Re: Firewall fails to become active within 300 seconds
Adding tempest.
Adding short delay between operations in fwaas api test may help to avoid race
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: tempest
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1314313
Title:
Firewall fails to become active within 300 seconds
Status in OpenStack Neutron (virtual network service):
Confirmed
Status in Tempest:
Confirmed
Bug description:
Upstream jobs are revealing that a FWaaS extension test is failing
because the firewall does not become active within tempest's timeout
(300 seconds).
It seems the l3 agent receives the firewall create notification from
the neutron server but then either the firewall is not processed or
the notification not sent back to the neutron server.
logstash:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVGltZWQgb3V0IHdhaXRpbmcgZm9yIGZpcmV3YWxsXCIgQU5EIG1lc3NhZ2U6XCJiZWNvbWUgQUNUSVZFXCIgQU5EIHRhZ3M6XCJjb25zb2xlXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTg3OTM2MTYxOTd9
This bug is being marked as critical because of 9 hits in the gate
queue in the past 48 hours.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1314313/+subscriptions
References