Need not add ext gw router ip to peer nat_addresses options
Bug #1655976 reported by
Dong Jun
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-ovn |
Fix Released
|
Undecided
|
Dong Jun | ||
Bug Description
Nat-addresses in lsp column are used for gratuitous ARP.
It seems that a gratuitous ARP will be sending for port IP itself,
thus only nat-addresses for floating IP are necessary.
Is that redundant adding router ip to nat-addresses? If it's necessary,
whether or not the SNAT is enable, it should be done, because IP migration
would also happen without SNAT.
| Changed in networking-ovn: | |
| assignee: | nobody → Dong Jun (dongj) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to networking-ovn (master) | #1 |
| Changed in networking-ovn: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-ovn (master) | #2 |
| Changed in networking-ovn: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/networking-ovn 2.0.0.0b3 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/