fix(controller): bind and release link members on their live ports

Link.delete cleared the port link through the port object stored at
add_node time; a node update since then rebuilt the port list, so that
object was stale and the live port kept its link — the next link on the
port was refused with "Port is already used". Masked until now by the
older rebuild bug (c2d68a65d): links never survived a rebuild, so the
guard never fired and the stale clear never mattered.
This commit is contained in:
YueGuobin committed 2026-10-06 00:21:10 +08:00
1 parent 1e999d916d
commit 928757542e
3 files changed
+55 -12

No files matched your search

+31
View File
@@ -141,6 +141,37 @@ async def test_add_node_already_connected_after_node_update(project, compute):
await link2.add_node(node1, 0, 0)
@pytest.mark.asyncio
async def test_link_delete_after_node_update_releases_port(project, compute):
"""
Link.delete drops the port's link reference through the port object it
stored at add_node time; a node update since then rebuilt the port list,
so that stored object is stale. The delete must release the *live* port,
or the next link on it is refused with "Port is already used".
"""
project.dump = AsyncioMagicMock()
node1 = Node(project, compute, "node1", node_type="qemu")
node2 = Node(project, compute, "node2", node_type="qemu")
link = Link(project)
link.create = AsyncioMagicMock()
link.node_updated = AsyncioMagicMock()
link._project.emit_notification = MagicMock()
await link.add_node(node1, 0, 0)
await link.add_node(node2, 0, 0)
# a node update (e.g. the status change of a start) rebuilds the ports
await node1.parse_node_response({"status": "started"})
await link.delete()
link2 = Link(project)
link2.create = AsyncioMagicMock()
await link2.add_node(node1, 0, 0) # must not raise "Port is already used"
@pytest.mark.asyncio
async def test_add_node_cloud(project, compute):