releasenotes/notes/fip-janitor-53f0d42a7471c5ed.yaml
raw| 1 | --- |
| 2 | other: |
| 3 | - Due to changes in internal L3 logic, a server crash/backend failure during |
| 4 | FIP creation may leave dangling ports attached on external networks. These |
| 5 | ports can be identified by a ``PENDING`` ``device_id`` parameter. While |
| 6 | those ports can also be removed by admins, the ``neutron-server`` service |
| 7 | will now also trigger periodic (approximately once in 10 minutes) cleanup |
| 8 | to address the issue. |