You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/09/17 23:27:51 UTC

[jira] [Created] (CLOUDSTACK-4695) [Automation] test cases from test_netscaler_lb failed during ssh connection in vmware

Rayees Namathponnan created CLOUDSTACK-4695:
-----------------------------------------------

             Summary: [Automation] test cases from test_netscaler_lb failed during ssh connection in vmware
                 Key: CLOUDSTACK-4695
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4695
             Project: CloudStack
          Issue Type: Test
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Automation, Test
    Affects Versions: 4.2.1
         Environment: Automation 
Netscaler
Vmware
            Reporter: Rayees Namathponnan
             Fix For: 4.2.1


Below two test cases failing with vmware runs, test cases failed while ssh connection 

integration.component.test_netscaler_lb.TestVmWithLb.test_07_delete_all_public_ip


Error Message

Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Network Service Provider: Netscaler is not enabled in the physical network: 201to add this device'}
-------------------- >> begin captured logging << --------------------
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Adding netscaler device: 10.223.240.174
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Checking if Netscaler network service provider is enabled?
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Netscaler service provider is already enabled.
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Adding netscaler device: 10.223.240.173
--------------------- >> end captured logging << ---------------------
Stacktrace

  File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
    testMethod()
  File "/data/Repo2/qa/cloudstack/test/integration/component/test_netscaler_nw_off.py", line 507, in test_add_mul_netscaler_diff_zone
    physicalnetworkid=physical_network.id
  File "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py", line 2820, in add
    return NetScaler(apiclient.addNetscalerLoadBalancer(cmd).__dict__)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", line 2378, in addNetscalerLoadBalancer
    response = self.connection.marvin_request(command, response_type=response, method=method)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 230, in marvin_request
    response = self.poll(asyncJobId, response_type)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 91, in poll
    "asyncquery", asyncResonse.jobresult)
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Network Service Provider: Netscaler is not enabled in the physical network: 201to add this device'}
-------------------- >> begin captured logging << --------------------
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Adding netscaler device: 10.223.240.174
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Checking if Netscaler network service provider is enabled?
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Netscaler service provider is already enabled.
test_add_mul_netscaler_diff_zone (integration.component.test_netscaler_nw_off.TestAddMultipleNSDiffZone): DEBUG: Adding netscaler device: 10.223.240.173
--------------------- >> end captured logging << --------------------- 

--
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