[jira] [Created] (CLOUDSTACK-6912) 4.2 32 bit system vm template job failing in jenkins

[Harikrishna Patnala (JIRA)]

Harikrishna Patnala created CLOUDSTACK-6912:
---

 Summary: 4.2 32 bit system vm template job failing in jenkins
 Key: CLOUDSTACK-6912
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6912
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: SystemVM
Affects Versions: 4.2.0, 4.2.1
Reporter: Harikrishna Patnala
Assignee: Harikrishna Patnala
Priority: Critical
 Fix For: 4.2.1, 4.2.0


4.2 32 bit system vm template job failing in jenkins

Preparing to replace libssl1.0.0:i386 1.0.1e-2 (using 
.../libssl1.0.0_1.0.1e-2+deb7u10_i386.deb) ...
Unpacking replacement libssl1.0.0:i386 ...
Selecting previously unselected package libsasl2-2:i386.
Unpacking libsasl2-2:i386 (from .../libsasl2-2_2.1.25.dfsg1-6+deb7u1_i386.deb) 
...
Selecting previously unselected package libldap-2.4-2:i386.
Unpacking libldap-2.4-2:i386 (from .../libldap-2.4-2_2.4.31-1+nmu2_i386.deb) ...
Selecting previously unselected package librtmp0:i386.
Unpacking librtmp0:i386 (from .../librtmp0_2.4+20111222.git4e06e21-1_i386.deb) 
...
Selecting previously unselected package libssh2-1:i386.
Unpacking libssh2-1:i386 (from .../libssh2-1_1.4.2-1.1_i386.deb) ...
Selecting previously unselected package libcurl3:i386.
Unpacking libcurl3:i386 (from .../libcurl3_7.26.0-1+wheezy9_i386.deb) ...
Selecting previously unselected package openssl.
Unpacking openssl (from .../openssl_1.0.1e-2+deb7u10_i386.deb) ...
Selecting previously unselected package ca-certificates.
Unpacking ca-certificates (from .../ca-certificates_20130119_all.deb) ...
Selecting previously unselected package curl.
Unpacking curl (from .../curl_7.26.0-1+wheezy9_i386.deb) ...
Selecting previously unselected package libsasl2-modules:i386.
Unpacking libsasl2-modules:i386 (from 
.../libsasl2-modules_2.1.25.dfsg1-6+deb7u1_i386.deb) ...
Selecting previously unselected package unzip.
Unpacking unzip (from .../archives/unzip_6.0-8_i386.deb) ...
Processing triggers for man-db ...
Setting up libssl1.0.0:i386 (1.0.1e-2+deb7u10) ...
Checking for services that may need to be restarted...done.
Checking for services that may need to be restarted...done.
Checking init scripts...
[?1049h[?25l(B 
   
  
  
  
  
  
  
  
  
 
     
     
 

 
     
     
 
 
     
     
 
 
     
     

  (BPackage 
configuration(0lqu(B(B 
Configuring libssl1.0.0:i386 
(0tqqkx(B(B 
  
(0x(B(B 
(B(0x(B(B There are services installed on 
your system which need to be 

[jira] [Commented] (CLOUDSTACK-6912) 4.2 32 bit system vm template job failing in jenkins

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032134#comment-14032134
 ] 

ASF subversion and git services commented on CLOUDSTACK-6912:
-

Commit a2b620c0b43dc6739dab3fdb854421bf63f72f1b in cloudstack's branch 
refs/heads/4.2 from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a2b620c ]

CLOUDSTACK-6912: 4.2 32 bit system vm template job failing in jenkins

Signed-off-by: Abhinandan Prateek aprat...@apache.org


 4.2 32 bit system vm template job failing in jenkins
 

 Key: CLOUDSTACK-6912
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6912
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: SystemVM
Affects Versions: 4.2.0, 4.2.1
Reporter: Harikrishna Patnala
Assignee: Harikrishna Patnala
Priority: Critical
 Fix For: 4.2.0, 4.2.1


 4.2 32 bit system vm template job failing in jenkins
 Preparing to replace libssl1.0.0:i386 1.0.1e-2 (using 
 .../libssl1.0.0_1.0.1e-2+deb7u10_i386.deb) ...
 Unpacking replacement libssl1.0.0:i386 ...
 Selecting previously unselected package libsasl2-2:i386.
 Unpacking libsasl2-2:i386 (from 
 .../libsasl2-2_2.1.25.dfsg1-6+deb7u1_i386.deb) ...
 Selecting previously unselected package libldap-2.4-2:i386.
 Unpacking libldap-2.4-2:i386 (from .../libldap-2.4-2_2.4.31-1+nmu2_i386.deb) 
 ...
 Selecting previously unselected package librtmp0:i386.
 Unpacking librtmp0:i386 (from 
 .../librtmp0_2.4+20111222.git4e06e21-1_i386.deb) ...
 Selecting previously unselected package libssh2-1:i386.
 Unpacking libssh2-1:i386 (from .../libssh2-1_1.4.2-1.1_i386.deb) ...
 Selecting previously unselected package libcurl3:i386.
 Unpacking libcurl3:i386 (from .../libcurl3_7.26.0-1+wheezy9_i386.deb) ...
 Selecting previously unselected package openssl.
 Unpacking openssl (from .../openssl_1.0.1e-2+deb7u10_i386.deb) ...
 Selecting previously unselected package ca-certificates.
 Unpacking ca-certificates (from .../ca-certificates_20130119_all.deb) ...
 Selecting previously unselected package curl.
 Unpacking curl (from .../curl_7.26.0-1+wheezy9_i386.deb) ...
 Selecting previously unselected package libsasl2-modules:i386.
 Unpacking libsasl2-modules:i386 (from 
 .../libsasl2-modules_2.1.25.dfsg1-6+deb7u1_i386.deb) ...
 Selecting previously unselected package unzip.
 Unpacking unzip (from .../archives/unzip_6.0-8_i386.deb) ...
 Processing triggers for man-db ...
 Setting up libssl1.0.0:i386 (1.0.1e-2+deb7u10) ...
 Checking for services that may need to be restarted...done.
 Checking for services that may need to be restarted...done.
 Checking init scripts...
 [?1049h[?25l(B   
  
 
 
 
 
 
 
 
 
    
  
    
    
    

    
    
    

 
    
    
    

    

[jira] [Assigned] (CLOUDSTACK-6792) [Automation] test_escalations_ipaddresses : Assert error during list IP address and network

[Gaurav Aradhye (JIRA)]

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

Gaurav Aradhye reassigned CLOUDSTACK-6792:
--

Assignee: Gaurav Aradhye

 [Automation] test_escalations_ipaddresses : Assert error during list IP 
 address and network
 ---

 Key: CLOUDSTACK-6792
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6792
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.4.0


 Test case failing from suite 
 integration.component.test_escalations_ipaddresses
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_07_assign_remove_lbrule_toinstance
  
 IP Addresses listed for newly created User
   begin captured stdout  -
 === TestName: test_07_assign_remove_lbrule_toinstance | Status : FAILED ===
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_15_enable_disable_staticnat_forvpc
  (from nosetests)
 Failing for the past 4 builds (Since Unstable#168 )
 Took 17 ms.
 Error Message
 VPC's Listed for newly Created User
   begin captured stdout  -
 === TestName: test_15_enable_disable_staticnat_forvpc | Status : FAILED ===
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_16_create_delete_ipforwardingrule
  (from nosetests)
 Failing for the past 4 builds (Since Unstable#168 )
 Took 29 ms.
 Error Message
 Networks listed for newly created User
   begin captured stdout  -
 === TestName: test_16_create_delete_ipforwardingrule | Status : FAILED ===
 -  end captured stdout  --



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CLOUDSTACK-6792) [Automation] test_escalations_ipaddresses : Assert error during list IP address and network

[Gaurav Aradhye (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032165#comment-14032165
 ] 

Gaurav Aradhye commented on CLOUDSTACK-6792:


Vinay's patch fixes this.
https://reviews.apache.org/r/22501/

 [Automation] test_escalations_ipaddresses : Assert error during list IP 
 address and network
 ---

 Key: CLOUDSTACK-6792
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6792
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.4.0


 Test case failing from suite 
 integration.component.test_escalations_ipaddresses
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_07_assign_remove_lbrule_toinstance
  
 IP Addresses listed for newly created User
   begin captured stdout  -
 === TestName: test_07_assign_remove_lbrule_toinstance | Status : FAILED ===
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_15_enable_disable_staticnat_forvpc
  (from nosetests)
 Failing for the past 4 builds (Since Unstable#168 )
 Took 17 ms.
 Error Message
 VPC's Listed for newly Created User
   begin captured stdout  -
 === TestName: test_15_enable_disable_staticnat_forvpc | Status : FAILED ===
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_16_create_delete_ipforwardingrule
  (from nosetests)
 Failing for the past 4 builds (Since Unstable#168 )
 Took 29 ms.
 Error Message
 Networks listed for newly created User
   begin captured stdout  -
 === TestName: test_16_create_delete_ipforwardingrule | Status : FAILED ===
 -  end captured stdout  --



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (CLOUDSTACK-6792) [Automation] test_escalations_ipaddresses : Assert error during list IP address and network

[Gaurav Aradhye (JIRA)]

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

Gaurav Aradhye resolved CLOUDSTACK-6792.


Resolution: Fixed

 [Automation] test_escalations_ipaddresses : Assert error during list IP 
 address and network
 ---

 Key: CLOUDSTACK-6792
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6792
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.4.0


 Test case failing from suite 
 integration.component.test_escalations_ipaddresses
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_07_assign_remove_lbrule_toinstance
  
 IP Addresses listed for newly created User
   begin captured stdout  -
 === TestName: test_07_assign_remove_lbrule_toinstance | Status : FAILED ===
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_15_enable_disable_staticnat_forvpc
  (from nosetests)
 Failing for the past 4 builds (Since Unstable#168 )
 Took 17 ms.
 Error Message
 VPC's Listed for newly Created User
   begin captured stdout  -
 === TestName: test_15_enable_disable_staticnat_forvpc | Status : FAILED ===
 integration.component.test_escalations_ipaddresses.TestIpAddresses.test_16_create_delete_ipforwardingrule
  (from nosetests)
 Failing for the past 4 builds (Since Unstable#168 )
 Took 29 ms.
 Error Message
 Networks listed for newly created User
   begin captured stdout  -
 === TestName: test_16_create_delete_ipforwardingrule | Status : FAILED ===
 -  end captured stdout  --



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CLOUDSTACK-6887) [Automation] Test cases not deleting account after complete the test

[Gaurav Aradhye (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032182#comment-14032182
 ] 

Gaurav Aradhye commented on CLOUDSTACK-6887:


First patch submitted, adding 2nd patch today fixing few more test suites.

 [Automation] Test cases not deleting account after complete the test 
 -

 Key: CLOUDSTACK-6887
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6887
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
 Fix For: 4.4.0


 Still there are test cases not deleting account after complete the test, i 
 can see below account exist in management server , after complete regression, 
 As per management server log,these account are not even tried to delete the 
 account 
 1) test-account-TestDeployVmWithAffinityGroup-GTFNV7
 2) test-TestAccountSnapshotClean-C1M23S
 3) test-TestSnapshotLimit-XWVZAT
 4) test-TestVolumes-test_01_volume_iso_attach-C3KHZK
 5) test-TestVolumes-test_create_volume_under_domain-9SC6RP
 6) test-TestVpnUsage-test_01_snapshot_usage-QREFF2
 7) test-TestVpnUsage-test_01_snapshot_usage-TBKTOK
 8) 
 test-TestVPCNetworkUpgrade-test_05_create_network_diff_account_1_network_offering-1KF0TL
 9) 
 test-TestPortableIpTransferAcrossNetworks-test_create_portable_ip_range_non_root_admin-EAKO69
 10) 
 test-TestPortableIpTransferAcrossNetworks-test_disassociate_ip_address_other_account-CJJ0S6
 11)test_add_remove_network_vm-TestUpdateVirtualMachineNIC-test_24_add_nw_different_domain-PKXXHF
 12) test-account-TestVPCNetworkOperations-test_vpc_delete_account-Y28RMP
 13) test-account-TestVPCNetworkOperations-test_vpc_force_delete_domain-NJTE7Y
 14) test-account-TestVPCNetworkOperations-test_vpc_force_delete_domain-9MLF0N
 15) test-TestVPC-test_15_deploy_vm_2-1I5L2M
 16) DoA-TestVPC-test_18_create_net_for_user_diff_domain_by_doadmin-80A4XM
 17) test-TestUserLogin-test_01_non_root_admin_Privileges-MCQ3HG
 18) 
 test-TestProjectSuspendActivate-test_08_cleanup_after_project_delete-MT8L6G



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6224) VM Snapshot inconsistent size

[Rajani Karuturi (JIRA)]

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

Rajani Karuturi updated CLOUDSTACK-6224:


Assignee: Likitha Shetty  (was: Rajani Karuturi)

 VM Snapshot inconsistent size
 -

 Key: CLOUDSTACK-6224
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6224
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server
Affects Versions: 4.2.1
 Environment: Cloudstack 4.2.1
 XenServer 6.2
 Vcenter 5.5 ESXi
Reporter: Artjoms Petrovs
Assignee: Likitha Shetty
  Labels: snapshot, vmware, xen

 During the creation of VM Snapshot [VMware], resulting size is written in 
 table „volumes”, column  vm_snapshot_chain_size. It seems that size of a VM 
 Snapshot is calculated manually via the method getVMSnapshotChainSize(..)  
 and it gives overexpected result ( hundreds of terabytes ) and is much larger 
 than the filesize, that we can see in VMware itself. By calculating the vmdk 
 and vmsn file sizes manually. Xen VM snapshots [disks only] give similar 
 results. For me it seems that either the method works incorrectly, either it 
 loops between some simlinks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CLOUDSTACK-6913) VM could not perform live migrate afte the template deleted.

[Guangsheng Xu (JIRA)]

Guangsheng Xu created CLOUDSTACK-6913:
-

 Summary: VM could not perform live migrate afte the template 
deleted.
 Key: CLOUDSTACK-6913
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6913
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
 Environment: Cloudstack4.3+Xenserver6.2sp1
Reporter: Guangsheng Xu


I use a template to launch a Instance, after the Instance up and running, I 
deleted the template. Then there is no response when I click 'Migrate' on this 
VM.

Catalina log shows:  GET command=findHostsForMigrationVirtualMachineId 530 null



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6913) VM could not perform live migrate afte the template deleted.

[Guangsheng Xu (JIRA)]

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

Guangsheng Xu updated CLOUDSTACK-6913:
--

Description: 
I use a template to launch a Instance, after the Instance up and running, I can 
migrate the VM to a nother host inside the Cluster via Cloudstack Web by 
clicking 'Migrate'on this VM. Butthe after I delete the template which I used 
to create this VM. Then a few minutes latter, there is no response when I click 
'Migrate' on this VM.

Catalina log shows:  GET command=findHostsForMigrationVirtualMachineId 530 null

  was:
I use a template to launch a Instance, after the Instance up and running, I 
deleted the template. Then there is no response when I click 'Migrate' on this 
VM.

Catalina log shows:  GET command=findHostsForMigrationVirtualMachineId 530 null


 VM could not perform live migrate afte the template deleted.
 

 Key: CLOUDSTACK-6913
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6913
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
 Environment: Cloudstack4.3+Xenserver6.2sp1
Reporter: Guangsheng Xu
   Original Estimate: 672h
  Remaining Estimate: 672h

 I use a template to launch a Instance, after the Instance up and running, I 
 can migrate the VM to a nother host inside the Cluster via Cloudstack Web by 
 clicking 'Migrate'on this VM. Butthe after I delete the template which I used 
 to create this VM. Then a few minutes latter, there is no response when I 
 click 'Migrate' on this VM.
 Catalina log shows:  GET command=findHostsForMigrationVirtualMachineId 530 
 null



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6913) VM could not perform live migrate afte the template deleted.

[Guangsheng Xu (JIRA)]

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

Guangsheng Xu updated CLOUDSTACK-6913:
--

Description: 
I use a template to launch a Instance, after the Instance up and running, I can 
migrate the VM to a nother host inside the Cluster via Cloudstack Web by 
clicking 'Migrate'on this VM. But after I delete the template which I used to 
create this VM. Then a few minutes latter, there is no response when I click 
'Migrate' on this VM.

Catalina log shows:  GET command=findHostsForMigrationVirtualMachineId 530 null

  was:
I use a template to launch a Instance, after the Instance up and running, I can 
migrate the VM to a nother host inside the Cluster via Cloudstack Web by 
clicking 'Migrate'on this VM. Butthe after I delete the template which I used 
to create this VM. Then a few minutes latter, there is no response when I click 
'Migrate' on this VM.

Catalina log shows:  GET command=findHostsForMigrationVirtualMachineId 530 null


 VM could not perform live migrate afte the template deleted.
 

 Key: CLOUDSTACK-6913
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6913
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
 Environment: Cloudstack4.3+Xenserver6.2sp1
Reporter: Guangsheng Xu
   Original Estimate: 672h
  Remaining Estimate: 672h

 I use a template to launch a Instance, after the Instance up and running, I 
 can migrate the VM to a nother host inside the Cluster via Cloudstack Web by 
 clicking 'Migrate'on this VM. But after I delete the template which I used to 
 create this VM. Then a few minutes latter, there is no response when I click 
 'Migrate' on this VM.
 Catalina log shows:  GET command=findHostsForMigrationVirtualMachineId 530 
 null



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6261) remove the forceful timeout setting when login to NetScaler

[Ram Ganesh (JIRA)]

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

Ram Ganesh updated CLOUDSTACK-6261:
---

Assignee: Rajesh Battala

 remove the forceful timeout setting when login to NetScaler
 ---

 Key: CLOUDSTACK-6261
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6261
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Devices
Affects Versions: 4.4.0
 Environment: NetScaler VPX/MPX 10.5+ (code does not force timeout 
 when login to SDX)
Reporter: Vijay Venkatachalam
Assignee: Rajesh Battala
Priority: Minor
  Labels: patch
 Fix For: 4.4.0

   Original Estimate: 2h
  Remaining Estimate: 2h

 Today, the NetScaler Resource forces a idle timeout of 100,000 seconds (~1 
 day and 4 hours) during login. The request is to remove forcing the timeout 
 to a specific value.
 Also, future versions of NetScaler is planning to have a cap of 1 day for 
 this setting.
 It is best to leave it to the system default which is 30 mins. This should be 
 enough, anyway there are threads for monitoring of member status, and 
 statistics collections  that keeps the session alive and it is unlikely to 
 gather idle time.
 The NetScaler resource already handles timeout expiry using retries so there 
 should not be any see side effects by leaving the idle time out to be the 
 default value 30 mins.. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (CLOUDSTACK-6868) [Hyper-V] Download of an uploaded volume is failing

[Abhinav Roy (JIRA)]

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

Abhinav Roy closed CLOUDSTACK-6868.
---


Closing the issue after fix validation

 [Hyper-V] Download of an uploaded volume is failing
 ---

 Key: CLOUDSTACK-6868
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6868
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Storage Controller
Affects Versions: 4.4.0
 Environment: Hyper-V
Reporter: Abhinav Roy
Assignee: Anshul Gangwar
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.4.0


 Steps:
 =
 1. Deploy an advanced zone Hyper-V setup.
 2. Create a VM v1
 3. Upload a volume upload1
 4. Download upload1
 Expected behavior :
 =
 Download should pass.
 Observed behavior :
 =
 Download fails with 
 2014-06-09 14:06:16,740 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-13:ctx-2b2fe04f) ===START===  10.144.7.13 -- GET  
 command=extractVolumeid=7282784d-75bf-46a4-b6a5-33fae5cda75czoneid=622e7c06-e62e-4a6b-8de6-a462a3ee7cf7mode=HTTP_DOWNLOADresponse=jsonsessionkey=RGKWL0km%2FibmrEZH39fWJsmJeeU%3D_=1402302332046
 2014-06-09 14:06:16,783 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-13:ctx-2b2fe04f ctx-676b8816) submit async job-113, details: 
 AsyncJobVO {id:113, userId: 2, accountId: 2, instanceType: Volume, 
 instanceId: 18, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:7282784d-75bf-46a4-b6a5-33fae5cda75c,sessionkey:RGKWL0km/ibmrEZH39fWJsmJeeU\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\7282784d-75bf-46a4-b6a5-33fae5cda75c\,\com.cloud.dc.DataCenter\:1},cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:622e7c06-e62e-4a6b-8de6-a462a3ee7cf7,httpmethod:GET,_:1402302332046,uuid:7282784d-75bf-46a4-b6a5-33fae5cda75c,ctxAccountId:2,ctxStartEventId:197,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-06-09 14:06:16,783 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-13:ctx-2b2fe04f ctx-676b8816) ===END===  10.144.7.13 -- GET  
 command=extractVolumeid=7282784d-75bf-46a4-b6a5-33fae5cda75czoneid=622e7c06-e62e-4a6b-8de6-a462a3ee7cf7mode=HTTP_DOWNLOADresponse=jsonsessionkey=RGKWL0km%2FibmrEZH39fWJsmJeeU%3D_=1402302332046
 2014-06-09 14:06:16,785 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-28:ctx-774021c1 job-113) Add job-113 into job monitoring
 2014-06-09 14:06:16,786 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-28:ctx-774021c1 job-113) Executing AsyncJobVO {id:113, 
 userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:7282784d-75bf-46a4-b6a5-33fae5cda75c,sessionkey:RGKWL0km/ibmrEZH39fWJsmJeeU\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\7282784d-75bf-46a4-b6a5-33fae5cda75c\,\com.cloud.dc.DataCenter\:1},cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:622e7c06-e62e-4a6b-8de6-a462a3ee7cf7,httpmethod:GET,_:1402302332046,uuid:7282784d-75bf-46a4-b6a5-33fae5cda75c,ctxAccountId:2,ctxStartEventId:197,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-06-09 14:06:16,795 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) Received unknown 
 parameters for command extractVolume. Unknown parameters : ctxdetails
 2014-06-09 14:06:16,833 DEBUG [o.a.c.s.m.AncientDataMotionStrategy] 
 (API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) copyAsync inspecting 
 src type VOLUME copyAsync inspecting dest type VOLUME
 2014-06-09 14:06:16,850 DEBUG [c.c.a.t.Request] 
 (API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) Seq 
 1-9177491615650939381: Sending  { Cmd , MgmtId: 213737702773493, via: 
 1(10.102.244.20), Ver: v1, Flags: 100011, 
 

[jira] [Closed] (CLOUDSTACK-6865) [Hyper-V]attach of an uploaded volume is failing as it is looking for a .vhdx volume even though the volume present is .vhd

[Abhinav Roy (JIRA)]

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

Abhinav Roy closed CLOUDSTACK-6865.
---


Closing the issue after fix validation

 [Hyper-V]attach of an  uploaded volume is failing as it is looking for a 
 .vhdx volume even though the volume present is .vhd
 

 Key: CLOUDSTACK-6865
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6865
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Storage Controller
Affects Versions: 4.4.0
 Environment: Hyper-V
Reporter: Abhinav Roy
Assignee: Anshul Gangwar
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.4.0

 Attachments: management-server-6865.zip


 Steps :
 ==
 1. Deploy an advanced zone Hyper-V setup.
 2. Create a VM v1
 3. Upload a volume upload1
 4. Attach upload1 to v1
 Expected Behavior :
 ==
 Attach should be successful.
 Observed behavior :
 ==
 Attach fails with the following error :
 2014-06-09 11:32:47,684 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-02af10fb) ===START===  10.144.7.13 -- GET  
 command=attachVolumeid=ddcaf328-0e71-462b-9ce6-e520dc8f15ccvirtualMachineId=ea78d7ec-6fed-4c3e-bff1-29219c70bdddresponse=jsonsessionkey=4MQxLlvkRgcp%2FMBl6tf6TodmICI%3D_=1402293458440
 2014-06-09 11:32:47,726 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-8:ctx-02af10fb ctx-dce1c925) submit async job-66, details: 
 AsyncJobVO {id:66, userId: 2, accountId: 2, instanceType: Volume, instanceId: 
 7, cmd: 
 org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin, 
 cmdInfo: 
 {response:json,id:ddcaf328-0e71-462b-9ce6-e520dc8f15cc,sessionkey:4MQxLlvkRgcp/MBl6tf6TodmICI\u003d,ctxDetails:{\com.cloud.storage.Volume\:7,\Volume\:\ddcaf328-0e71-462b-9ce6-e520dc8f15cc\,\com.cloud.vm.VirtualMachine\:5},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:ea78d7ec-6fed-4c3e-bff1-29219c70bddd,httpmethod:GET,_:1402293458440,uuid:ddcaf328-0e71-462b-9ce6-e520dc8f15cc,ctxAccountId:2,ctxStartEventId:112},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-06-09 11:32:47,727 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-02af10fb ctx-dce1c925) ===END===  10.144.7.13 -- GET  
 command=attachVolumeid=ddcaf328-0e71-462b-9ce6-e520dc8f15ccvirtualMachineId=ea78d7ec-6fed-4c3e-bff1-29219c70bdddresponse=jsonsessionkey=4MQxLlvkRgcp%2FMBl6tf6TodmICI%3D_=1402293458440
 2014-06-09 11:32:47,729 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-24:ctx-976a0ed5 job-66) Add job-66 into job monitoring
 2014-06-09 11:32:47,734 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-24:ctx-976a0ed5 job-66) Executing AsyncJobVO {id:66, 
 userId: 2, accountId: 2, instanceType: Volume, instanceId: 7, cmd: 
 org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin, 
 cmdInfo: 
 {response:json,id:ddcaf328-0e71-462b-9ce6-e520dc8f15cc,sessionkey:4MQxLlvkRgcp/MBl6tf6TodmICI\u003d,ctxDetails:{\com.cloud.storage.Volume\:7,\Volume\:\ddcaf328-0e71-462b-9ce6-e520dc8f15cc\,\com.cloud.vm.VirtualMachine\:5},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:ea78d7ec-6fed-4c3e-bff1-29219c70bddd,httpmethod:GET,_:1402293458440,uuid:ddcaf328-0e71-462b-9ce6-e520dc8f15cc,ctxAccountId:2,ctxStartEventId:112},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-06-09 11:32:47,744 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) Received unknown 
 parameters for command attachVolume. Unknown parameters : ctxdetails
 2014-06-09 11:32:47,769 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) Sync job-67 execution 
 on object VmWorkJobQueue.5
 2014-06-09 11:32:47,772 DEBUG [c.c.s.VolumeApiServiceImpl] 
 (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) New job 67, result 
 field: null
 2014-06-09 11:32:47,773 WARN  [c.c.u.d.Merovingian2] 
 (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) Was unable to find 
 lock for the key vm_instance5 and thread id 1700504230
 2014-06-09 11:32:49,461 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (AsyncJobMgr-Heartbeat-1:ctx-04e089b1) Execute sync-queue item: 
 SyncQueueItemVO {id:24, queueId: 4, contentType: AsyncJob, contentId: 67, 
 lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null, 
 

[jira] [Closed] (CLOUDSTACK-6867) [Hyper-V][UI] No option to upload a volume with .vhdx format

[Abhinav Roy (JIRA)]

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

Abhinav Roy closed CLOUDSTACK-6867.
---


Closing the issue after fix validation

 [Hyper-V][UI] No option to upload a volume with .vhdx format
 

 Key: CLOUDSTACK-6867
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6867
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.4.0
 Environment: Hyper-V
Reporter: Abhinav Roy
Assignee: Anshul Gangwar
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.4.0

 Attachments: CS-6867.jpg


 Steps :
 ===
 1. Deploy a advanced zone hyperv setup.
 2. Try to upload a volume with .vhdx format
  There is no option in the UI to upload .vhdx format volumes, only vhd is 
 there
 3. Try to upload the .vhdx volume by selecting the format as .vhd 
  Then we get this error 
  2014-06-09 13:23:28,381 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-9:ctx-c149c622 job-84) Unexpected exception while executing 
 org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin
 com.cloud.exception.InvalidParameterValueException: Please specify a valid 
 URL. URL:http://10.144.7.13/upload-data.vhdx is an invalid for the format vhd
 at 
 com.cloud.storage.VolumeApiServiceImpl.validateVolume(VolumeApiServiceImpl.java:314)
 at 
 com.cloud.storage.VolumeApiServiceImpl.uploadVolume(VolumeApiServiceImpl.java:252)
 at 
 com.cloud.storage.VolumeApiServiceImpl.uploadVolume(VolumeApiServiceImpl.java:148)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy181.uploadVolume(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin.execute(UploadVolumeCmdByAdmin.java:46)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at 

[jira] [Closed] (CLOUDSTACK-6872) [Hyper-V]Create template T1 from a volume, then deploy V1 from T1, now try to create a template T2 from V1's root volume. It is failing

[Abhinav Roy (JIRA)]

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

Abhinav Roy closed CLOUDSTACK-6872.
---


Closing the issue after fix validation

 [Hyper-V]Create template T1 from a volume, then  deploy V1 from T1, now try 
 to create a template T2 from V1's root volume. It is failing
 

 Key: CLOUDSTACK-6872
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6872
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Storage Controller
Affects Versions: 4.4.0
 Environment: Hyper-V
Reporter: Abhinav Roy
Assignee: Anshul Gangwar
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.4.0

 Attachments: CS-6872.zip


 Steps :
 
 1. Deploy Hyper-V advanced zone setup.
 2. Create a VM v1 from default centos template.
 3. Stop v1 and create template T1 from v1's root volume.
 4. create a VM v2 from T1.
 5. Stop v2 and create template T2 from v2's root volume.
 Expected Behavior :
 
 All the above steps should have succeeded.
 Observed Behavior :
 
 Step 5 is failing with the following error :
 2014-06-09 15:40:09,269 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-4:ctx-43436526) ===START===  10.144.7.13 -- GET  
 command=createTemplateresponse=jsonsessionkey=fGX4uIHoj2mx%2BzfKOA579EC%2FQjM%3DvolumeId=d33b806d-8c96-4aff-8e3f-2efa78083a7fname=tempfromvol-root12displayText=tempfromvol-root12osTypeId=a000795a-ebce-11e3-b00a-c264afd952f5isPublic=truepasswordEnabled=falseisdynamicallyscalable=falseisfeatured=true_=1402308159938
 2014-06-09 15:40:09,296 DEBUG [c.c.t.TemplateManagerImpl] 
 (catalina-exec-4:ctx-43436526 ctx-b0e507ef) This template is getting created 
 from other template, setting source template Id to: 202
 2014-06-09 15:40:09,367 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-4:ctx-43436526 ctx-b0e507ef) submit async job-122, details: 
 AsyncJobVO {id:122, userId: 2, accountId: 2, instanceType: Template, 
 instanceId: 203, cmd: 
 org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin, 
 cmdInfo: 
 {sessionkey:fGX4uIHoj2mx+zfKOA579EC/QjM\u003d,cmdEventType:TEMPLATE.CREATE,ctxUserId:2,volumeId:d33b806d-8c96-4aff-8e3f-2efa78083a7f,httpmethod:GET,osTypeId:a000795a-ebce-11e3-b00a-c264afd952f5,isPublic:true,isfeatured:true,id:203,isdynamicallyscalable:false,response:json,ctxDetails:{\com.cloud.template.VirtualMachineTemplate\:203,\com.cloud.storage.Volume\:24,\VirtualMachineTemplate\:\77913d8e-99f9-43f9-9dd2-a498ebe37d75\,\com.cloud.storage.GuestOS\:182},displayText:tempfromvol-root12,passwordEnabled:false,name:tempfromvol-root12,_:1402308159938,uuid:77913d8e-99f9-43f9-9dd2-a498ebe37d75,ctxAccountId:2,ctxStartEventId:218},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-06-09 15:40:09,368 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-4:ctx-43436526 ctx-b0e507ef) ===END===  10.144.7.13 -- GET  
 command=createTemplateresponse=jsonsessionkey=fGX4uIHoj2mx%2BzfKOA579EC%2FQjM%3DvolumeId=d33b806d-8c96-4aff-8e3f-2efa78083a7fname=tempfromvol-root12displayText=tempfromvol-root12osTypeId=a000795a-ebce-11e3-b00a-c264afd952f5isPublic=truepasswordEnabled=falseisdynamicallyscalable=falseisfeatured=true_=1402308159938
 2014-06-09 15:40:09,370 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-34:ctx-c3c1954c job-122) Add job-122 into job monitoring
 2014-06-09 15:40:09,370 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-34:ctx-c3c1954c job-122) Executing AsyncJobVO {id:122, 
 userId: 2, accountId: 2, instanceType: Template, instanceId: 203, cmd: 
 org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin, 
 cmdInfo: 
 {sessionkey:fGX4uIHoj2mx+zfKOA579EC/QjM\u003d,cmdEventType:TEMPLATE.CREATE,ctxUserId:2,volumeId:d33b806d-8c96-4aff-8e3f-2efa78083a7f,httpmethod:GET,osTypeId:a000795a-ebce-11e3-b00a-c264afd952f5,isPublic:true,isfeatured:true,id:203,isdynamicallyscalable:false,response:json,ctxDetails:{\com.cloud.template.VirtualMachineTemplate\:203,\com.cloud.storage.Volume\:24,\VirtualMachineTemplate\:\77913d8e-99f9-43f9-9dd2-a498ebe37d75\,\com.cloud.storage.GuestOS\:182},displayText:tempfromvol-root12,passwordEnabled:false,name:tempfromvol-root12,_:1402308159938,uuid:77913d8e-99f9-43f9-9dd2-a498ebe37d75,ctxAccountId:2,ctxStartEventId:218},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, 

[jira] [Created] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type

[Pavan Kumar Bandarupally (JIRA)]

Pavan Kumar Bandarupally created CLOUDSTACK-6915:


 Summary: Deleting dynamically added OS results in NPE for existing 
instances using that os type
 Key: CLOUDSTACK-6915
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Hypervisor Controller
Affects Versions: 4.4.0
 Environment: XenServer host 
Cloudstack 4.4 
Reporter: Pavan Kumar Bandarupally
Priority: Critical
 Fix For: 4.4.0


A guest OS is dynamically added and an instance is deployed successfully using 
that os type (ISO used to deploy instance was of that OS type). The custom os 
added was deleted using removeGuestOS. After this the instance is stopped and 
started again.

This start operation resulted in Null Pointer Exception.

PFA MS log.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6914) The present way of tagging the test cases has issues and is not usable. Need to modify this.

[Santhosh Kumar Edukulla (JIRA)]

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

Santhosh Kumar Edukulla updated CLOUDSTACK-6914:


Summary: The present way of tagging the test cases has issues and is not 
usable. Need to modify this.  (was: The present way of tagging the test cases 
as provisioning and simulator is not usable. Need to modify this.)

 The present way of tagging the test cases has issues and is not usable. Need 
 to modify this.
 

 Key: CLOUDSTACK-6914
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6914
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Bharat Kumar
Assignee: Santhosh Kumar Edukulla
 Fix For: 4.4.0


 Currently we add all the test meta data in a single tag called tags, as a 
 result we cannot use proper nosetest conditions to filter the simulator test 
 cases from provisioning. 
 Also some tests have both simulator and provisioning tags added to the same 
 test case.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type

[Pavan Kumar Bandarupally (JIRA)]

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

Pavan Kumar Bandarupally updated CLOUDSTACK-6915:
-

Attachment: management-server.log

 Deleting dynamically added OS results in NPE for existing instances using 
 that os type
 --

 Key: CLOUDSTACK-6915
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0
 Environment: XenServer host 
 Cloudstack 4.4 
Reporter: Pavan Kumar Bandarupally
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log


 A guest OS is dynamically added and an instance is deployed successfully 
 using that os type (ISO used to deploy instance was of that OS type). The 
 custom os added was deleted using removeGuestOS. After this the instance is 
 stopped and started again.
 This start operation resulted in Null Pointer Exception.
 PFA MS log.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type

[Pavan Kumar Bandarupally (JIRA)]

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

Pavan Kumar Bandarupally updated CLOUDSTACK-6915:
-

Description: 
A guest OS is dynamically added and an instance is deployed successfully using 
that os type (ISO used to deploy instance was of that OS type). The custom os 
added was deleted using removeGuestOS. After this the instance is stopped and 
started again.

This start operation resulted in Null Pointer Exception.

2014-06-16 06:50:33,350 ERROR [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Failed to start 
instance VM[User|i-2-12-VM]
java.lang.NullPointerException
at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:93)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-06-16 06:50:33,359 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Cleaning up 
resources for the vm VM[User|i-2-12-VM] in Starting state


PFA MS log.


  was:
A guest OS is dynamically added and an instance is deployed successfully using 
that os type (ISO used to deploy instance was of that OS type). The custom os 
added was deleted using removeGuestOS. After this the instance is stopped and 
started again.

This start operation resulted in Null Pointer Exception.

PFA MS log.



 Deleting dynamically added OS results in NPE for existing instances using 
 that os type
 --

 Key: CLOUDSTACK-6915
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0
 Environment: XenServer host 
 Cloudstack 4.4 
Reporter: Pavan Kumar Bandarupally
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log


 A guest OS is dynamically added and an instance is deployed successfully 
 using that os type (ISO used to deploy instance was of that OS type). The 
 custom os added was deleted using removeGuestOS. After this the instance is 
 stopped and started again.
 This start operation resulted in Null Pointer Exception.
 2014-06-16 06:50:33,350 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Failed to 
 start instance VM[User|i-2-12-VM]
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:93)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 

[jira] [Updated] (CLOUDSTACK-6914) The present way of tagging the test cases has issues and is not usable. Need to modify this.

[Santhosh Kumar Edukulla (JIRA)]

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

Santhosh Kumar Edukulla updated CLOUDSTACK-6914:


Description: 
Currently we add all the test meta data in a single tag called tags, as a 
result we cannot use proper nosetest conditions to filter the simulator test 
cases from provisioning. 

Also some tests have both simulator and provisioning tags added to the same 
test case.Some test cases have simulator, selfservice tags and others.

Tracking this bug to clean up the tags.


  was:
Currently we add all the test meta data in a single tag called tags, as a 
result we cannot use proper nosetest conditions to filter the simulator test 
cases from provisioning. 

Also some tests have both simulator and provisioning tags added to the same 
test case.



 The present way of tagging the test cases has issues and is not usable. Need 
 to modify this.
 

 Key: CLOUDSTACK-6914
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6914
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Bharat Kumar
Assignee: Santhosh Kumar Edukulla
 Fix For: 4.4.0


 Currently we add all the test meta data in a single tag called tags, as a 
 result we cannot use proper nosetest conditions to filter the simulator test 
 cases from provisioning. 
 Also some tests have both simulator and provisioning tags added to the same 
 test case.Some test cases have simulator, selfservice tags and others.
 Tracking this bug to clean up the tags.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (CLOUDSTACK-6897) [Hyper-V] In a Multi cluster setup attach of a uploaded volume to a VM on zwps is failing with scope conflict

[Abhinav Roy (JIRA)]

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

Abhinav Roy closed CLOUDSTACK-6897.
---


Closing the issue after fix validation

 [Hyper-V] In a Multi cluster setup attach of a uploaded volume to a VM on 
 zwps is failing with scope conflict
 -

 Key: CLOUDSTACK-6897
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6897
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Storage Controller
Affects Versions: 4.4.0
 Environment: Hyper-V multi-cluster setup, having cluster wide 
 storage, local storage and zone wide storage.
Reporter: Abhinav Roy
Assignee: Anshul Gangwar
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.4.0


 Steps :
 =
 1. Deploy a hyperv advanced zone setup with 2 clusters , c1 and c2
 2. In C1 have 2 hosts h1  h2 and 2 cluster wide primary storages p1  p2
 in C2 have 1 host h3 and 2 cluster wide primary storage p2  p4
 Also, have 2 zone wide primary stoarages, z1  z2
 3. Deploy a VM v1 on host h3 with volumes on z1.
 4. Upload a volume upload1
 5. Attach upload1 to v1
 Expected behavior :
 ===
 The attach should be successful.
 Observed behavior :
 ==
 The attach fails with the following error :
 2014-06-12 11:39:10,974 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-15:ctx-c4877d18) ===START===  10.144.6.9 -- GET  
 command=attachVolumeid=7282784d-75bf-46a4-b6a5-33fae5cda75cvirtualMachineId=69781acf-f85e-4499-8d52-ccf768ac41e4response=jsonsessionkey=cSJpXdHESvwd9ahj2OVVUqECfOw%3D_=1402553090360
 2014-06-12 11:39:11,031 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-15:ctx-c4877d18 ctx-86f37de4) submit async job-217, details: 
 AsyncJobVO {id:217, userId: 2, accountId: 2, instanceType: Volume, 
 instanceId: 18, cmd: 
 org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin, 
 cmdInfo: 
 {id:7282784d-75bf-46a4-b6a5-33fae5cda75c,response:json,sessionkey:cSJpXdHESvwd9ahj2OVVUqECfOw\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\7282784d-75bf-46a4-b6a5-33fae5cda75c\,\com.cloud.vm.VirtualMachine\:15},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:69781acf-f85e-4499-8d52-ccf768ac41e4,httpmethod:GET,_:1402553090360,uuid:7282784d-75bf-46a4-b6a5-33fae5cda75c,ctxAccountId:2,ctxStartEventId:360},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-06-12 11:39:11,032 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-15:ctx-c4877d18 ctx-86f37de4) ===END===  10.144.6.9 -- GET  
 command=attachVolumeid=7282784d-75bf-46a4-b6a5-33fae5cda75cvirtualMachineId=69781acf-f85e-4499-8d52-ccf768ac41e4response=jsonsessionkey=cSJpXdHESvwd9ahj2OVVUqECfOw%3D_=1402553090360
 2014-06-12 11:39:11,034 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-2:ctx-f62aa4c4 job-217) Add job-217 into job monitoring
 2014-06-12 11:39:11,034 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-2:ctx-f62aa4c4 job-217) Executing AsyncJobVO {id:217, 
 userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd: 
 org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin, 
 cmdInfo: 
 {id:7282784d-75bf-46a4-b6a5-33fae5cda75c,response:json,sessionkey:cSJpXdHESvwd9ahj2OVVUqECfOw\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\7282784d-75bf-46a4-b6a5-33fae5cda75c\,\com.cloud.vm.VirtualMachine\:15},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:69781acf-f85e-4499-8d52-ccf768ac41e4,httpmethod:GET,_:1402553090360,uuid:7282784d-75bf-46a4-b6a5-33fae5cda75c,ctxAccountId:2,ctxStartEventId:360},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-06-12 11:39:11,045 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-2:ctx-f62aa4c4 job-217 ctx-39e46132) Received unknown 
 parameters for command attachVolume. Unknown parameters : ctxdetails
 2014-06-12 11:39:11,059 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-2:ctx-f62aa4c4 job-217 ctx-39e46132) Sync job-218 execution 
 on object VmWorkJobQueue.15
 2014-06-12 11:39:11,062 DEBUG [c.c.s.VolumeApiServiceImpl] 
 (API-Job-Executor-2:ctx-f62aa4c4 job-217 ctx-39e46132) New job 218, result 
 field: null
 2014-06-12 11:39:11,062 WARN  [c.c.u.d.Merovingian2] 
 (API-Job-Executor-2:ctx-f62aa4c4 job-217 ctx-39e46132) Was unable to find 
 lock for the key vm_instance15 and thread id 124496084
 

[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032347#comment-14032347
 ] 

ASF subversion and git services commented on CLOUDSTACK-6282:
-

Commit 89c35abb4db0f362f9159ea39a6eb70ad4351921 in cloudstack's branch 
refs/heads/4.4-forward from [~vinayv]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=89c35ab ]

CLOUDSTACK-6282: Modified IPAddress tests to fix the failures. Modified 
Instances, snapshots, templates tests to handle KVM Hypervisor


 [Automation]: Adding new Testcases
 --

 Key: CLOUDSTACK-6282
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Vinay Vegesna
Assignee: Santhosh Kumar Edukulla

 [Automation]: Adding below new Test cases for test_escalations.py
 test_01_list_volumes_pagination
 test_02_list_volume_byid
 test_03_data_volume_resize
 test_04_custom_volume
 test_05_volume_snapshot
 test_06_volume_snapshot_policy
 test_07_volume_snapshots_pagination
 test_08_volume_extract
 test_09_volume_upload



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032350#comment-14032350
 ] 

ASF subversion and git services commented on CLOUDSTACK-6282:
-

Commit 99e4da15da73ac2ccf5597e11d805cb1438831cd in cloudstack's branch 
refs/heads/master from [~vinayv]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=99e4da1 ]

CLOUDSTACK-6282-Modified IpAddresses, Instances, Templates, Snapshots tests to 
handle KVM and modified IPAddresses for failed list cases


 [Automation]: Adding new Testcases
 --

 Key: CLOUDSTACK-6282
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Vinay Vegesna
Assignee: Santhosh Kumar Edukulla

 [Automation]: Adding below new Test cases for test_escalations.py
 test_01_list_volumes_pagination
 test_02_list_volume_byid
 test_03_data_volume_resize
 test_04_custom_volume
 test_05_volume_snapshot
 test_06_volume_snapshot_policy
 test_07_volume_snapshots_pagination
 test_08_volume_extract
 test_09_volume_upload



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CLOUDSTACK-6914) The present way of tagging the test cases has issues and is not usable. Need to modify this.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032358#comment-14032358
 ] 

ASF subversion and git services commented on CLOUDSTACK-6914:
-

Commit 54e4c075287957821e57368f1baf401761f7bda2 in cloudstack's branch 
refs/heads/4.4-forward from Santhosh Edukulla
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=54e4c07 ]

CLOUDSTACK-6914: Fixed the Issue

Signed-off-by: Abhinandan Prateek aprat...@apache.org


 The present way of tagging the test cases has issues and is not usable. Need 
 to modify this.
 

 Key: CLOUDSTACK-6914
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6914
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Bharat Kumar
Assignee: Santhosh Kumar Edukulla
 Fix For: 4.4.0


 Currently we add all the test meta data in a single tag called tags, as a 
 result we cannot use proper nosetest conditions to filter the simulator test 
 cases from provisioning. 
 Also some tests have both simulator and provisioning tags added to the same 
 test case.Some test cases have simulator, selfservice tags and others.
 Tracking this bug to clean up the tags.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032361#comment-14032361
 ] 

ASF subversion and git services commented on CLOUDSTACK-6793:
-

Commit f89100ed72bd8e854dc01af244907fe02e7525a3 in cloudstack's branch 
refs/heads/master from Santhosh Edukulla
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f89100e ]

CLOUDSTACK-6793 : Added fix

Signed-off-by: Abhinandan Prateek aprat...@apache.org


 [Automation] CreateTagsCmd fails with db exceptions 
 

 Key: CLOUDSTACK-6793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: Santhosh Kumar Edukulla
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Steps to reproduce 
 Execute the test case integration.component.test_tags.TestResourceTags
 Test case perform below steps 
 # 1. Create a tag on template/ISO using createTags API
 # 2. Delete above created tag using deleteTags API
 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END===
   10.223.240.193 -- GET  
 apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd
 EQresourcetype=TemplateresourceIds=35e10eef-7980-4085-8b6c-c68174f1b529command=createTagssignature=pIJSk7ekg0Tlf
 RN%2FWfdp8U42Bgs%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] 
 (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin
 g back the transaction: Time = 4 Name =  API-Job-Executor-89; called by 
 -TransactionLegacy.rollback:903-TransactionL
 egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.
 proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2
 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn
 Transaction:25-Transaction$2.doInTransaction:49
 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-dbbc3135) ===START===  10.223.240.193 -- GET
  
 jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z
 1t-oO1g9F4-EiUZx9BdEQcommand=queryAsyncJobResultresponse=jsonsignature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D
 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while 
 executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags 
 (resource_tags.uuid, resource_tags.key, resource_tags.value, 
 resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, 
 resource_tags.resource_uuid, resource_tags.resource_type, 
 resource_tags.customer) VALUES 
 (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', 
 -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null)
 at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400)
 at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy52.persist(Unknown Source)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6912) 4.2 32 bit system vm template job failing in jenkins

[Harikrishna Patnala (JIRA)]

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

Harikrishna Patnala resolved CLOUDSTACK-6912.
-

Resolution: Fixed

 4.2 32 bit system vm template job failing in jenkins
 

 Key: CLOUDSTACK-6912
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6912
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: SystemVM
Affects Versions: 4.2.0, 4.2.1
Reporter: Harikrishna Patnala
Assignee: Harikrishna Patnala
Priority: Critical
 Fix For: 4.2.1, 4.2.0


 4.2 32 bit system vm template job failing in jenkins
 Preparing to replace libssl1.0.0:i386 1.0.1e-2 (using 
 .../libssl1.0.0_1.0.1e-2+deb7u10_i386.deb) ...
 Unpacking replacement libssl1.0.0:i386 ...
 Selecting previously unselected package libsasl2-2:i386.
 Unpacking libsasl2-2:i386 (from 
 .../libsasl2-2_2.1.25.dfsg1-6+deb7u1_i386.deb) ...
 Selecting previously unselected package libldap-2.4-2:i386.
 Unpacking libldap-2.4-2:i386 (from .../libldap-2.4-2_2.4.31-1+nmu2_i386.deb) 
 ...
 Selecting previously unselected package librtmp0:i386.
 Unpacking librtmp0:i386 (from 
 .../librtmp0_2.4+20111222.git4e06e21-1_i386.deb) ...
 Selecting previously unselected package libssh2-1:i386.
 Unpacking libssh2-1:i386 (from .../libssh2-1_1.4.2-1.1_i386.deb) ...
 Selecting previously unselected package libcurl3:i386.
 Unpacking libcurl3:i386 (from .../libcurl3_7.26.0-1+wheezy9_i386.deb) ...
 Selecting previously unselected package openssl.
 Unpacking openssl (from .../openssl_1.0.1e-2+deb7u10_i386.deb) ...
 Selecting previously unselected package ca-certificates.
 Unpacking ca-certificates (from .../ca-certificates_20130119_all.deb) ...
 Selecting previously unselected package curl.
 Unpacking curl (from .../curl_7.26.0-1+wheezy9_i386.deb) ...
 Selecting previously unselected package libsasl2-modules:i386.
 Unpacking libsasl2-modules:i386 (from 
 .../libsasl2-modules_2.1.25.dfsg1-6+deb7u1_i386.deb) ...
 Selecting previously unselected package unzip.
 Unpacking unzip (from .../archives/unzip_6.0-8_i386.deb) ...
 Processing triggers for man-db ...
 Setting up libssl1.0.0:i386 (1.0.1e-2+deb7u10) ...
 Checking for services that may need to be restarted...done.
 Checking for services that may need to be restarted...done.
 Checking init scripts...
 [?1049h[?25l(B   
  
 
 
 
 
 
 
 
 
    
  
    
    
    

    
    
    

 
    
    
    

    
    
    
 (BPackage 
 configuration(0lqu(B(B 
 Configuring libssl1.0.0:i386 
 

[jira] [Commented] (CLOUDSTACK-6862) [Automation] Test case TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm faling during BVT

[Alex Brett (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032413#comment-14032413
 ] 

Alex Brett commented on CLOUDSTACK-6862:


It looks like the fix for CLOUDSTACK-6914 should resolve this, I suggest this 
ticket gets closed off as a duplicate...

 [Automation] Test case TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm 
 faling during BVT 
 -

 Key: CLOUDSTACK-6862
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6862
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.4.0


 Test case 
 integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm
  failing in BVT 
 Error Message
 Execute cmd: createserviceoffering failed, due to: errorCode: 401, 
 errorText:unable to verify user credentials and/or request signature
   begin captured stdout  -
 === TestName: test_deploy_vgpu_enabled_vm | Status : EXCEPTION ===
 -  end captured stdout  --
   begin captured logging  
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: STARTED : TC: test_deploy_vgpu_enabled_vm :::
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Payload: {'apiKey': 
 u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
  'command': 'listDomains', 'signature': '8Yh5KlFqCsxhD/NB2fOBHSPL1kI=', 
 'response': 'json'}
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Sending GET Cmd : listDomains===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 172.16.88.21
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5Acommand=listDomainsresponse=jsonsignature=8Yh5KlFqCsxhD%2FNB2fOBHSPL1kI%3D
  HTTP/1.1 200 159
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Response : [{path : u'ROOT', haschild : False, id : 
 u'6b3a436e-ef1f-11e3-a141-00163e189e44', name : u'ROOT', level : 0}]
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Payload: {'apiKey': 
 u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
  'name': 'zone-xen', 'command': 'listZones', 'signature': 
 'Z7nIBao2vEVG1YiHM2kVrh6QcPY=', 'response': 'json'}
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Sending GET Cmd : listZones===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 172.16.88.21
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?response=jsonapiKey=8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5Acommand=listZonesname=zone-xensignature=Z7nIBao2vEVG1YiHM2kVrh6QcPY%3D
  HTTP/1.1 200 446
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Response : [{localstorageenabled : False, name : u'zone-xen', 
 guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken : 
 u'562e3c93-9149-38c6-8555-de48e3e6c847', dns2 : u'8.8.4.4', dns1 : 
 u'8.8.8.8', securitygroupsenabled : False, allocationstate : u'Enabled', 
 internaldns1 : u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype : 
 u'Advanced', id : u'ad43d834-dc57-4da5-b3ae-0ef3f106192b', internaldns2 : 
 u'172.16.88.8'}]
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Payload: {'apiKey': 
 u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
  'templatefilter': 'featured', 'command': 'listTemplates', 'signature': 
 'KGHcOyWgw042qhRsMQWkZ7VdUIM=', 'zoneid': 
 u'ad43d834-dc57-4da5-b3ae-0ef3f106192b', 'response': 'json'}
 test_deploy_vgpu_enabled_vm 
 (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): 
 DEBUG: Sending GET Cmd : listTemplates===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 172.16.88.21
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 

[jira] [Created] (CLOUDSTACK-6916) supporting nfs protocol and resize feature for managed storage in xenserver

[punith (JIRA)]

punith created CLOUDSTACK-6916:
--

 Summary: supporting nfs protocol and resize feature for managed 
storage in xenserver
 Key: CLOUDSTACK-6916
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6916
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.5.0
Reporter: punith


currently managed storage only supports iscsi protocol.

hence now adding support for nfs protocol and also resizing the vdi to the SR 
size, hence fully utilizing the SR space in managed storage.

to support nfs, the getNfsSR method's signature has to changed similar to 
existing getIscsiSR method.

SR will be created based on the volume's protocoltype. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (CLOUDSTACK-6908) ipv6 enabled by default

[Daan Hoogland (JIRA)]

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

Daan Hoogland closed CLOUDSTACK-6908.
-

Resolution: Fixed

 ipv6 enabled by default
 ---

 Key: CLOUDSTACK-6908
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6908
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.3.0
Reporter: Daan Hoogland
Assignee: Sheng Yang
Priority: Critical
 Fix For: 4.4.0


 ipv6 is enabled by default on the system vm templates but there is no way to 
 configure the iptables for it or otherwise firewall against ipv6 base 
 attacks. Can the ipv6 be disabled by default or otherwised be set to disabled 
 by a zone or system property?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CLOUDSTACK-6919) CancelMaintenanceMode: when restart vms, don't attempt to restart user vm not having a ROOT volume

[Alena Prokharchyk (JIRA)]

Alena Prokharchyk created CLOUDSTACK-6919:
-

 Summary: CancelMaintenanceMode: when restart vms, don't attempt to 
restart user vm not having a ROOT volume
 Key: CLOUDSTACK-6919
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6919
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.4.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


Steps to reproduce:
===
1) Deploy a vm
2) Put the Storage the vm's volumes are located, into maintenance mode. 
3) The vm gets stopped.
4) Once the Maintenance operation is completed, detach root volume from the vm.
5) CancelMaintenance for the host.

As a part of cancelMaintenance, all the vms that were stopped as a part of 
enableMaintenance, get restarted again.

Bug: we shouldn't attempt to restart the vm having no root volumes



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CLOUDSTACK-6919) CancelMaintenanceMode: when restart vms, don't attempt to restart user vm not having a ROOT volume

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14033096#comment-14033096
 ] 

ASF subversion and git services commented on CLOUDSTACK-6919:
-

Commit 09a97e1968c610ae5435e4df3ed279b51fc33cd9 in cloudstack's branch 
refs/heads/master from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=09a97e1 ]

CLOUDSTACK-6919: don't attempt to restart user vms having no Root volume 
attached


 CancelMaintenanceMode: when restart vms, don't attempt to restart user vm not 
 having a ROOT volume
 --

 Key: CLOUDSTACK-6919
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6919
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 Steps to reproduce:
 ===
 1) Deploy a vm
 2) Put the Storage the vm's volumes are located, into maintenance mode. 
 3) The vm gets stopped.
 4) Once the Maintenance operation is completed, detach root volume from the 
 vm.
 5) CancelMaintenance for the host.
 As a part of cancelMaintenance, all the vms that were stopped as a part of 
 enableMaintenance, get restarted again.
 Bug: we shouldn't attempt to restart the vm having no root volumes



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CLOUDSTACK-6921) Support listing of LBStickinesspolicy with LBStickiness policy ID

[Rajesh Battala (JIRA)]

Rajesh Battala created CLOUDSTACK-6921:
--

 Summary: Support listing of LBStickinesspolicy with LBStickiness 
policy ID
 Key: CLOUDSTACK-6921
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6921
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller
Affects Versions: 4.4.0
Reporter: Rajesh Battala
Assignee: Rajesh Battala
 Fix For: 4.4.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (CLOUDSTACK-6831) [Hyper-V] Improve the logging for VM snapshot failures as it is not supported. Right now it is throwing NPEs

[Abhinav Roy (JIRA)]

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

Abhinav Roy closed CLOUDSTACK-6831.
---


Closing the issue after fix validation

 [Hyper-V] Improve the logging for VM snapshot failures as it is not 
 supported. Right now it is throwing NPEs
 

 Key: CLOUDSTACK-6831
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6831
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
 Environment: HyperV
Reporter: Abhinav Roy
Assignee: Rajesh Battala
 Fix For: 4.4.0


 Steps :
 
 1. Deploy a advanced zone hyperv setup.
 2. Create a VM v1.
 3. Create a VM snapshot on v1
 Expected behavior :
 
 Since VM snapshot is not supported in 4.4.0 for HyperV, the operation should 
 fail gracefully with appropriate error message.
 Observed behavior :
 ===
 VM snapshot operation fails with a NPE 
 2014-06-03 15:21:25,150 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-7:ctx-8ce4a754) ===START===  10.144.7.13 -- GET  
 command=createVMSnapshotvirtualmachineid=fb624f96-c70f-4e25-94a0-65f9daf145aasnapshotmemory=falsequiescevm=falsename=ssresponse=jsonsessionkey=o%2F8Vw1YoKZS4JAca7rkI3sCMSDs%3D_=1401788814498
 2014-06-03 15:21:25,168 ERROR [c.c.a.ApiServer] (catalina-exec-7:ctx-8ce4a754 
 ctx-ce4443a6) unhandled exception executing api command: 
 [Ljava.lang.String;@7cfb6b51
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.dao.HypervisorCapabilitiesDaoImpl.isVmSnapshotEnabled(HypervisorCapabilitiesDaoImpl.java:104)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy179.isVmSnapshotEnabled(Unknown Source)
 at 
 com.cloud.vm.snapshot.VMSnapshotManagerImpl.allocVMSnapshot(VMSnapshotManagerImpl.java:265)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy182.allocVMSnapshot(Unknown Source)
 at 
 org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd.create(CreateVMSnapshotCmd.java:92)
 at 
 com.cloud.api.dispatch.CommandCreationWorker.handle(CommandCreationWorker.java:47)
 at 
 com.cloud.api.dispatch.DispatchChain.dispatch(DispatchChain.java:37)
 at 
 com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:79)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:614)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:506)
 at