Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-9407

vm_network_map table doesnt get cleaned up properly

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.9.0
    • 4.9.1.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

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            nicolas.vazquez Nicolas Vazquez
            nicolas.vazquez Nicolas Vazquez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment