fwaas v1 with DVR: l3 agent can't restore the NAT rules for floatingIP

Bug #1653633 reported by shihanzhang
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

With neutron and FWaas master branch and in DVR mode, I create a VM with floatingIP, it works ok, but when i restart the related l3-agent, i can't reach the VM via FloatingIP, then check the NAT rules in router namespace, i found the NAT rules did not be restored.

reproduce steps:
1. in DVR mode
2. create a VM with floatingIP
3. restart the related l3 agent on compute node
we can check that the NAT rule for floatingIP did not be restored.

tags: added: dvr
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

You mentioned FWaaS in the bug report, but it seems irrelevant when looking at the steps to repro. Could you clarify?

tags: added: l3-dvr-backlog
removed: dvr
Changed in neutron:
status: New → Incomplete
Revision history for this message
Brian Haley (brian-haley) wrote :

I tried this both with and with FWaaSv1 enabled with DVR on devstack (dvr_snat mode) and could not reproduce it, NAT rule was always restored. Can you give more information on your config as well as any info from log files that might help?

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers