Duplicated port binding registers per port, due to live-migration failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Committed
|
Medium
|
Rodolfo Alonso |
Bug Description
Related bugzilla: https:/
Description:
This issue has been reported frequently by our customers. If during a live migration [1] Neutron does not respond fast enough and fails during the activation step, the live migration process is reverted. The VM will continue running in the source host. However this process can leave a leftover in the Neutron database: two port binding registers pointing to the same port. Database will look like [2].
If Nova tries to bind the port again, Neutron will raise an error [3].
Steps to Reproduce:
1. Put some sleep, like 120 seconds, in Neutron activate method [4].
2. Run live migration
3. Observe ml2_port_bindings table for the VM port
This bug proposes:
- To have a periodic worker (same as OVN mech driver "MaintenanceWorker" or "DbQuotaNoLockD
- Add a task inside this periodic worker to monitor the port binding table, looking for duplicated records. Of course, we should not interfere any migration process. Those duplicated port binding registers should
[1]https:/
[2]https:/
[3]https:/
[4]https:/
Changed in neutron: | |
assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
Changed in neutron: | |
importance: | Undecided → Medium |
description: | updated |
Fix proposed to branch: master /review. opendev. org/c/openstack /neutron/ +/846422
Review: https:/