yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #89771
[Bug 1991092] [NEW] Do not retry port provisioning for "network", "neutron" and "baremetal" device_owner ports
Public bug reported:
Since [1] (up to Wallaby), the "_port_provisioned" method retries the
port provisioning if the port is unbound. This feature [2] was meant to
be implemented for VM ports, that could be affected by the race
condition during the live-migration, as described in [2]. Any other port
should be excluded from this active retry.
Also there are some ports, like the router ports in OVN, that are never
bound to a host given their decentralized nature.
[1]https://review.opendev.org/q/I50091c84e67c172c94ce9140f23235421599185c
[2]https://bugs.launchpad.net/neutron/+bug/1988199
** Affects: neutron
Importance: Undecided
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1991092
Title:
Do not retry port provisioning for "network", "neutron" and
"baremetal" device_owner ports
Status in neutron:
New
Bug description:
Since [1] (up to Wallaby), the "_port_provisioned" method retries the
port provisioning if the port is unbound. This feature [2] was meant
to be implemented for VM ports, that could be affected by the race
condition during the live-migration, as described in [2]. Any other
port should be excluded from this active retry.
Also there are some ports, like the router ports in OVN, that are
never bound to a host given their decentralized nature.
[1]https://review.opendev.org/q/I50091c84e67c172c94ce9140f23235421599185c
[2]https://bugs.launchpad.net/neutron/+bug/1988199
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1991092/+subscriptions
Follow ups