[jira] [Assigned] (CLOUDSTACK-2861) Internal LB VM stuck and does not expunge

["Alena Prokharchyk (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alena Prokharchyk reassigned CLOUDSTACK-2861:
---------------------------------------------

    Assignee: Alena Prokharchyk
    
> Internal LB VM stuck and does not expunge
> -----------------------------------------
>
>                 Key: CLOUDSTACK-2861
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2861
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: dbdump.tar.bz2, vmops.log.tar.bz2
>
>
> The internal LB vm seems to be having a problem expunging. I'm running the test test_internal_lb.py from test/integration/smoke using a simulator setup 
> Steps:
> 1. mvn -pl client jetty:run
> 2. deploy advanced zone
> mvn -Pdeveloper,marvin.setup -pl :cloud-marvin integration-test -Dmarvin.config=setup/dev/advanced.cfg
> 3. Run internal lb test
> nosetests --with-marvin --marvin-config=setup/dev/advanced.cfg test/integration/smoke/test_internal_lb.py --load
> The test ERRORs out but tearDown does not occur since the internal LB VM is stuck before expunging
> 2013-06-05 20:28:10,309 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Network-Scavenger-1:null) Waiting some more to make sure there's no activity on VM[InternalLoadBalancerVm|b-34-VM]
> 2013-06-05 20:28:12,790 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-40:job-138) Waiting some more to make sure there's no activity on VM[InternalLoadBalancerVm|b-55-QA]
> Attaching db dump and management server logs

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira