[jira] [Reopened] (CLOUDSTACK-1758) SSVM test cases failing in VMware with 4.1 builds

2013-06-30 Thread Brian Spindler (JIRA)

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

Brian Spindler reopened CLOUDSTACK-1758:



Should this have been:
ssh -i /var/lib/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no

And not:
ssh -i /var/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no

?

>  SSVM test cases failing in VMware with 4.1 builds
> --
>
> Key: CLOUDSTACK-1758
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1758
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.1.0, 4.2.0
> Environment: vm ware
>Reporter: Rayees Namathponnan
>Assignee: Girish Shilamkar
>Priority: Blocker
> Fix For: 4.2.0
>
>
> SVM test cases failing in VM ware, 
> Traceback (most recent call last): 
>   File 
> "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line 
> 804, in test_08_reboot_cpvm 
> self.test_04_cpvm_internals() 
>   File 
> "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line 
> 481, in test_04_cpvm_internals 
> "Check cloud service is running or not" 
> AssertionError: Check cloud service is running or not 
> I checked the ssvm, i can see cloud server is running 
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent 
> permitted by applicable law. 
> root@s-3-VM:~# service cloud status 
> cloud.com service (type=secstorage) is running: process id: 2751 
> root@s-3-VM:~# service cloud status 
> cloud.com service (type=secstorage) is running: process id: 2751 
> root@s-3-VM:~# 
> followed below steps 
> > cp /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud /tmp 
> > chmod 600 /tmp/id_rsa.cloud 
> > ssh -i /tmp/id_rsa.cloud -p 3922 root@10.223.250.122 (private ip) 

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


[jira] [Reopened] (CLOUDSTACK-1758) SSVM test cases failing in VMware with 4.1 builds

2013-06-18 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan reopened CLOUDSTACK-1758:
-


As per  https://issues.apache.org/jira/browse/CLOUDSTACK-2534, need to fix in 
test case

>  SSVM test cases failing in VMware with 4.1 builds
> --
>
> Key: CLOUDSTACK-1758
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1758
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.1.0, 4.2.0
> Environment: vm ware
>Reporter: Rayees Namathponnan
>Assignee: Girish Shilamkar
> Fix For: 4.2.0
>
>
> SVM test cases failing in VM ware, 
> Traceback (most recent call last): 
>   File 
> "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line 
> 804, in test_08_reboot_cpvm 
> self.test_04_cpvm_internals() 
>   File 
> "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line 
> 481, in test_04_cpvm_internals 
> "Check cloud service is running or not" 
> AssertionError: Check cloud service is running or not 
> I checked the ssvm, i can see cloud server is running 
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent 
> permitted by applicable law. 
> root@s-3-VM:~# service cloud status 
> cloud.com service (type=secstorage) is running: process id: 2751 
> root@s-3-VM:~# service cloud status 
> cloud.com service (type=secstorage) is running: process id: 2751 
> root@s-3-VM:~# 
> followed below steps 
> > cp /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud /tmp 
> > chmod 600 /tmp/id_rsa.cloud 
> > ssh -i /tmp/id_rsa.cloud -p 3922 root@10.223.250.122 (private ip) 

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