Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.9.0
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
Description
Introduction
It was found out that in production environments vm_network_map table entries were slowly growing. It was investigated how this entries were cleaned up.
Behaviour
On vm creation, vm mappings are inserted on vm_network_map.
On vm stop, mappings are deleted from vm_network_map for vm, as a result of the release of its nics.
Problem
If created vm is stopped from hypervisor side (at least on vSphere in which we tested it), when CloudStack realizes vm is stopped it doesn't clean up vm_network_table, and, as cleanup is made during vm stop, when vm is eventually destroyed and expunged it won't clean up their entries in that table.
Proposed solution
We propose to move vm_network_map table cleanup to expunge command instead of stop command.
Attachments
Issue Links
- links to
