You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/07/25 13:07:49 UTC

[jira] [Updated] (CLOUDSTACK-3792) [Automation] InternalLb VM stops when assigned a VM to an LB rule

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

Prasanna Santhanam updated CLOUDSTACK-3792:
-------------------------------------------

    Component/s: VMware
                 Network Controller
    
> [Automation] InternalLb VM stops when assigned a VM to an LB rule
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3792
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3792
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Automation, Network Controller, VMware
>    Affects Versions: 4.2.0
>         Environment: Automation 
> VMware
>            Reporter: Rayees Namathponnan
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Steps:
> 1. create network offering with vpcvirtualrouter for use in vpc with internallbvm doing lb
> 2. create a vpc 
> 3. create a network in the VPC
> 4. deploy a vm in the network
> 5. create an application load balancer for the network, roundrobin /scheme internal
> 6. assign the VM to the LB
> internal lb vm stops and fails the test (test/integration/smoke/test_internal_lb.py)
> On the management server:
> We see : 
> 2013-07-25 06:53:16,258 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-7:job-122 = [ 19220298-7780-4c0a-8958-3e0f63f2334b ]) The guru did not like the answers so stopping VM[InternalLoadBalancerVm|b-24-VM]
> After this the internal lb vm is stopped causing the failure to assign load balancer rule.
> In the test:
> nosetests --with-marvin --marvin-config=setup/dev/advanced.cfg test/integration/smoke/test_internal_lb.py --load
> Test create, delete, assign, remove of internal loadbalancer ... ERROR
> ======================================================================
> ERROR: Test create, delete, assign, remove of internal loadbalancer
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/Users/tsp/workspace/cloudstack/incubator-cloudstack/test/integration/smoke/test_internal_lb.py", line 174, in test_internallb
>     applb.assign(self.apiclient, vms=[vm])
>   File "/Library/Python/2.7/site-packages/marvin/integration/lib/base.py", line 1543, in assign
>     apiclient.assignToLoadBalancerRule(cmd)
>   File "/Library/Python/2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", line 1899, in assignToLoadBalancerRule
>     response = self.connection.marvin_request(command, response_type=response, method=method)
>   File "/Library/Python/2.7/site-packages/marvin/cloudstackConnection.py", line 230, in marvin_request
>     response = self.poll(asyncJobId, response_type)
>   File "/Library/Python/2.7/site-packages/marvin/cloudstackConnection.py", line 91, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Failed to add specified loadbalancerruleid for vms [23]'}
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestInternalLb: DEBUG: Successfully created account: test-TestInternalLb-V6GHCD, id:                    5e9cc55d-a183-462d-b014-6ed8d77d0c4a
> testclient.testcase.TestInternalLb: DEBUG: Network ef4a7978-c9ac-45f9-ab6f-32d58752969a created in VPC c274c68f-3118-4490-a110-79237ef2c845
> testclient.testcase.TestInternalLb: DEBUG: VM 0620d84e-df78-47e4-8898-679b77d6045a deployed in VPC c274c68f-3118-4490-a110-79237ef2c845
> --------------------- >> end captured logging << ---------------------
> ----------------------------------------------------------------------
> Ran 1 test in 425.615s
> FAILED (errors=1)
> Attaching 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