[Yahoo-eng-team] [Bug 1696093] [NEW] When update a firewall, we should update the iptables firstly, and then clear the conntrack record, just like the function create_firewall(). Otherwise, the contra

.#neutron firewall-update f1 --no-routers 2.vm ping external ip address all the time 3.#neutron firewall-update f1 --router demo-router We can found that vm still can ping external ip address successfully. ** Affects: neutron Importance: Undecided Assignee: wujun (wujun) Status

[Yahoo-eng-team] [Bug 1665318] Re: Fwaas(bind a firewall to a legacy router that without qrouter namespace):iptables rules do not tabke effect after the qrouter namespace created.

** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1665318 Title: Fwaas(bind a firewall to a legacy router that without qrouter namespa

[Yahoo-eng-team] [Bug 1665330] [NEW] Fwaas(reduce the associated floatingip count to zero):the firewall rules which in the qrouter namespace will not be cleaned, after delete the firewall.

: neutron Importance: Undecided Assignee: wujun (wujun) Status: New ** Tags: fwaas ** Tags added: fwaas ** Changed in: neutron Assignee: (unassigned) => wujun (wujun) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which

[Yahoo-eng-team] [Bug 1665326] [NEW] Fwaas:it will execute firewall rules twice for a router, when update the firewall.

ist = self._get_router_info_list_for_tenant( router_ids + firewall['router_ids'], firewall['tenant_id']) ... But the "router_ids" is the same with "firewall['router_ids'] ** Affects: neutron Importance: Undecided Assignee: wujun

[Yahoo-eng-team] [Bug 1665323] [NEW] Fwaas:When update the firewall name, the neutron-l3-agent will be called to reload the firewall rules.

Public bug reported: environment: Mitaka Update the firewall name, the neutron-l3-agent will be called to reload the firewall rules. When update the firewall name, it should be only updated the DB. ** Affects: neutron Importance: Undecided Assignee: wujun (wujun) Status: New

[Yahoo-eng-team] [Bug 1665318] [NEW] Fwaas(bind a firewall to a legacy router that without qrouter namespace):iptables rules do not tabke effect after the qrouter namespace created.

Public bug reported: environment: Mitaka 1.create a legacy router (do not add interface and set gateway), so there is no qrouter namespace 2.bind a firewall to the router 3.add interface or set gateway for the router, qrouter namespace is created now The problem is there no firewall rule in the

[Yahoo-eng-team] [Bug 1656754] [NEW] Fwaas (Bind a firewall to DVR router when its floating-ip count is zero): The firewall does not take effect for a VM after binding a floating ip to the VM.

Public bug reported: environment: Mitaka In the DVR mode: 1. create a router, a firewall and a VM 2. bind the firewall to the router of VM Now, the firewall rule take effect in the snat namespace. It is normal. 3. bind a floatingip to the VM Now, the firewall rule does not take effect in the q

[Yahoo-eng-team] [Bug 1644433] [NEW] The wrong default-prefixlen have not checked, when create a subnetpool

Public bug reported: In Newton environment. ** Affects: neutron Importance: Undecided Assignee: wujun (wujun) Status: New ** Changed in: neutron Assignee: (unassigned) => wujun (wujun) -- You received this bug notification because you are a member of Yahoo! Engineer

[Yahoo-eng-team] [Bug 1641811] [NEW] Wrong ha_state, when l3-agent that host the master router is down

e1 and the keepalived work normally. I think the ha_state of node1 shoud be "active". ** Affects: neutron Importance: Undecided Assignee: wujun (wujun) Status: New ** Changed in: neutron Assignee: (unassigned) => wujun (wujun) ** Description changed: - In an L3 HA Setu

[Yahoo-eng-team] [Bug 1580927] Re: spans beyond the subnet for /31 and /32 in IPam

** Changed in: neutron Status: Invalid => 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/1580927 Title: spans beyond the subnet for /31 and /32 in IPam Status in neutro

[Yahoo-eng-team] [Bug 1580927] Re: spans beyond the subnet for /31 and /32 in IPam

I think it is not a bug. When needing to create a point to point connection via a subnet, /30 is the recommended cidr. Because the first IP address is considered as Network ID, and the last IP address is considered as broadcast address, the other IP address can be allocated, in a given subnet.