yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1223472] Re: firewall status does not become ACTIVE when a router does not exist

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1223472@xxxxxxxxxxxxxxxxxx>
Date: Tue, 09 Feb 2016 04:17:25 -0000
Reply-to: Bug 1223472 <1223472@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  firewall status does not become ACTIVE when  a router does not exist

Status in neutron:
  Expired

Bug description:
  I use FWaaS combined with OVS plugin and l3-agent.

  When I created a firewall with admin user, the status of the firewall
  didn't change from PENDING_CREATE to ACTIVE even after waiting for one
  or two minutes.

  On the other hand, when I created a firewall with non-admin user, the
  status of the created firewall became ACTIVE at most after 30 seconds
  (probably shorter than this).

  What is the difference between admin and non-admin?

  The detail command line log is here.
  http://paste.openstack.org/show/46493/

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