[
https://issues.apache.org/jira/browse/CLOUDSTACK-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733339#comment-13733339
]
Sowmya Krishnan commented on CLOUDSTACK-3760:
---------------------------------------------
Following Configurations need to be done for this test:
Ensure that there is only one Netscaler device (the one mentioned in the
script) attached to the cloud. If there are more, we cannot be sure which NS
the LB rule might be deployed if it's a shared device. This is an assumption
made by the script.
> [Automation] Test suite test_netscaler_lb_sticky.TestLbStickyPolicy failed
> with ssh connection error
> ----------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3760
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3760
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
> Affects Versions: 4.2.0
> Environment: KVM
> Netscaler
> Automation : 4.2
> Reporter: Rayees Namathponnan
> Assignee: Sowmya Krishnan
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Tets case test_netscaler_lb_sticky.TestLbStickyPolicy; failed with ssh
> connection error
> This test case was passing only july 16th run; test case broken after this.
> Observed below error in log
> SH Access failed for 10.223.52.7: 'SourceBased' sticky policy should be
> configured on NS
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestLbStickyPolicy: DEBUG: Creating LB rule for IP
> address: 10.223.122.94 with round robin algo
> testclient.testcase.TestLbStickyPolicy: DEBUG: Created the load balancing
> rule for public IP: 10.223.122.94
> testclient.testcase.TestLbStickyPolicy: DEBUG: Assigning VM instance:
> 81c28371-ed68-4d6d-8fc3-cbd2604511b9 to LB rule: SSH
> testclient.testcase.TestLbStickyPolicy: DEBUG: Assigned VM instance:
> 81c28371-ed68-4d6d-8fc3-cbd2604511b9 to lb rule: SSH
> testclient.testcase.TestLbStickyPolicy: DEBUG: Configuring 'SourceBased'
> Sticky policy on lb rule: SSH
> testclient.testcase.TestLbStickyPolicy: DEBUG: Response: {stickinesspolicy :
> [{methodname : u'SourceBased', params : {holdtime : u'20'}, id :
> u'5a17015e-5855-4423-9dc9-922150cf6437', name : u'SourceBasedRR'}], lbruleid
> : u'2c11ff27-a821-4af8-bc89-69e9971e79af', domainid :
> u'aa3e580a-f35a-11e2-9abc-1a6f7bb0d0a8', account : u'test-W0L468', domain :
> u'ROOT'}
> testclient.testcase.TestLbStickyPolicy: DEBUG: SSH into Netscaler to check
> whether sticky policy configured properly or not?
> testclient.testcase.TestLbStickyPolicy: DEBUG: SSH into netscaler: 10.223.52.7
> paramiko.transport: DEBUG: starting thread (client mode): 0x1cb8fc50L
> paramiko.transport: INFO: Connected (version 2.0, client OpenSSH_4.5p1)
> paramiko.transport: DEBUG: kex algos:['diffie-hellman-group-exchange-sha256',
> 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1',
> 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256',
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc',
> 'aes192-cbc', 'aes256-cbc', 'arcfour', '[email protected]'] server
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256',
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc',
> 'aes192-cbc', 'aes256-cbc', 'arcfour', '[email protected]'] client
> mac:['hmac-md5', 'hmac-sha1', 'hmac-ripemd160', '[email protected]',
> 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hmac-md5', 'hmac-sha1',
> 'hmac-ripemd160', '[email protected]', 'hmac-sha1-96',
> 'hmac-md5-96'] client compress:['none', '[email protected]'] server
> compress:['none', '[email protected]'] client lang:[''] server lang:[''] kex
> follows?False
> paramiko.transport: DEBUG: Ciphers agreed: local=aes128-ctr, remote=aes128-ctr
> paramiko.transport: DEBUG: using kex diffie-hellman-group1-sha1; server key
> type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local
> hmac-sha1, remote hmac-sha1; compression: local none, remote none
> paramiko.transport: DEBUG: Switch to new keys ...
> paramiko.transport: DEBUG: Adding ssh-rsa host key for 10.223.52.7:
> 42e8284df7a6750a4cec86d8098d082d
> paramiko.transport: DEBUG: Trying discovered key
> 76be480fa6b8ad3b78082d6d19e4ee44 in /root/.ssh/id_rsa
> paramiko.transport: DEBUG: userauth is OK
> paramiko.transport: INFO: Authentication (publickey) failed.
> paramiko.transport: DEBUG: userauth is OK
> paramiko.transport: INFO: Authentication (password) successful!
> sshClient: DEBUG: SSH connect: [email protected] with passwd nsroot
> testclient.testcase.TestLbStickyPolicy: DEBUG: command: show lb vserver
> Cloud-VirtualServer-10.223.122.94-22
> paramiko.transport: DEBUG: [chan 1] Max packet in: 34816 bytes
> paramiko.transport: DEBUG: [chan 1] Max packet out: 32768 bytes
> paramiko.transport: INFO: Secsh channel 1 opened.
> paramiko.transport: DEBUG: [chan 1] Sesch channel 1 request ok
> paramiko.transport: DEBUG: [chan 1] EOF received (1)
> paramiko.transport: DEBUG: [chan 1] EOF sent (1)
> sshClient: DEBUG: {Cmd: show lb vserver Cloud-VirtualServer-10.223.122.94-22
> via Host: 10.223.52.7} {returns: [' Done', 'ERROR: No such resource [name,
> Cloud-VirtualServer-10.223.122.94-22]']}
> testclient.testcase.TestLbStickyPolicy: DEBUG: Output: [' Done', 'ERROR: No
> such resource [name, Cloud-VirtualServer-10.223.122.94-22]']
> --------------------- >> end captured logging << ---------------------
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_netscaler_lb_sticky.py",
> line 307, in test_01_source_based_roundrobin
> (self.services["netscaler"]["ipaddress"], e))
> File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
> raise self.failureException(msg)
> SSH Access failed for 10.223.52.7: 'SourceBased' sticky policy should be
> configured on NS
--
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
