set floatingip status to DOWN during creation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Opinion
|
Undecided
|
venkata anil |
Bug Description
floatingip status is not reliable as it is set to active during creation itself [1] rather than waiting for agent [2] to update it once agent finishes adding SNAT/DNAT rules.
[1] https:/
[2] https:/
User can check floatingip status after creation and can initiate data traffic before agent finishes
processing floatingip resulting in connection failures. Also fixing this can help tempest tests to initiate connection only after agent has finished floatingip processing and avoid failures.
Also floatingip status has to be properly updated during migration of router.
Changed in neutron: | |
assignee: | nobody → venkata anil (anil-venkata) |
tags: | added: l3-dvr-backlog l3-ha |
Changed in neutron: | |
status: | New → Opinion |