cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9407) vm_network_map table doesnt get cleaned up properly
Date Mon, 18 Jul 2016 17:18:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9407:

Github user swill commented on the issue:
    ### CI RESULTS
    Tests Run: 85
      Skipped: 0
       Failed: 1
       Errors: 0
     Duration: 3h 52m 54s
    **Summary of the problem(s):**
    FAIL: Create a redundant VPC with 1 Tier, 1 VM, 1 ACL, 1 PF and test Network GC Nics
    Traceback (most recent call last):
      File "/data/git/cs2/cloudstack/test/integration/smoke/", line 605,
in test_04_rvpc_network_garbage_collector_nics
        self.check_routers_state(status_to_check="BACKUP", expected_count=2)
      File "/data/git/cs2/cloudstack/test/integration/smoke/", line 353,
in check_routers_state"Expected '%s' routers at state '%s', but found '%s'!" % (expected_count,
status_to_check, cnts[vals.index(status_to_check)]))
    AssertionError: Expected '2' routers at state 'BACKUP', but found '1'!
    Additional details in: /tmp/MarvinLogs/test_network_2PRTDA/results.txt
    **Associated Uploads**
    * [dc_entries.obj](
    * [failed_plus_exceptions.txt](
    * [runinfo.txt](
    * [failed_plus_exceptions.txt](
    * [results.txt](
    * [runinfo.txt](
    * [failed_plus_exceptions.txt](
    * [results.txt](
    * [runinfo.txt](
    Uploads will be available until `2016-09-17 02:00:00 +0200 CEST`
    *Comment created by [`upr comment`](*

> vm_network_map table doesnt get cleaned up properly
> ---------------------------------------------------
>                 Key: CLOUDSTACK-9407
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>            Assignee: Nicolas Vazquez
>             Fix For: 4.9.0
> h3. 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.
> h3. 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.
> h3. 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.
> h3. Proposed solution
> We propose to move {{vm_network_map}} table cleanup to expunge command instead of stop

This message was sent by Atlassian JIRA

View raw message