[jira] [Commented] (CLOUDSTACK-7674) Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161524#comment-14161524 ] ASF subversion and git services commented on CLOUDSTACK-7674: - Commit 1a1190eb1dea8057c4ac5fef7811c5f37d162954 in cloudstack's branch refs/heads/4.3 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1a1190e ] CLOUDSTACK-7674 throw an exception when encountered Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type --- Key: CLOUDSTACK-7674 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7674 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Upgrade Affects Versions: 4.3.1 Environment: CS Manager on Ubuntu 12.04 from standard repo Hosts: XenServer 6.0.2 Zone: Basic Network Offering: DefaultSharedNetworkOffering Reporter: Carlos Reategui Priority: Critical In previous versions, the broadcast_uri in the Networks table was NULL for Guest network in a Basic Zone with a network offering of DefaultSharedNetworkOffering. From 4.3.1 (maybe 4.3.0 too but not sure) it can not be NULL and must be set to vlan://untagged. The upgrade scripts do not do this and therefore one is unable to create new instances. I don't know if this affect other hypervisors besides XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7219) Cannot display Cluster Settings after 4.4 Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161525#comment-14161525 ] Wei Zhou commented on CLOUDSTACK-7219: -- Branch: refs/heads/hotfix/4.4/CLOUDSTACK-7219 Commit: 0b31732bb18983db6cdd747a6c2f6056cf81a85e Parents: 63fbd16 Author: Harikrishna Patnala harikrishna.patn...@citrix.com Authored: Fri Feb 7 16:44:11 2014 +0530 Committer: Wei Zhou w.z...@tech.leaseweb.com Committed: Thu Oct 2 12:18:13 2014 +0200 Cannot display Cluster Settings after 4.4 Upgrade - Key: CLOUDSTACK-7219 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7219 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Affects Versions: 4.4.0 Environment: CentOS 6, KVM Hypervisor Reporter: Prieur Leary Priority: Blocker Fix For: 4.4.1 Attachments: cluster.png After upgrading MS to 4.4, when you to go: Home - Infrastructure - Clusters - Cluster 1 - Settings It does not display the settings underneath the column heading just, ERROR. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7674) Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161537#comment-14161537 ] Carlos Reategui commented on CLOUDSTACK-7674: - Not sure that will fix my problem. My vlan table got updated properly by this code. The problem was the networks table. from my prior backup: INSERT INTO `vlan` VALUES (1,'5ebc3075-2946-4be4-9e7a-f32a86e7edfc','untagged','172.30.45.1','255.255.255.0','172.30.45.100-172.30.45.174','DirectAttached',1,204,200,NULL,NULL,NULL); after update: INSERT INTO `vlan` VALUES (1,'5ebc3075-2946-4be4-9e7a-f32a86e7edfc','vlan://untagged','172.30.45.1','255.255.255.0','172.30.45.100-172.30.45.174','DirectAttached',1,204,200,NULL,NULL,NULL); As you can see the vlan_id got updated properly. The problem for me was that the broadcast_uri for the guest network in the `networks` table stayed NULL. Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type --- Key: CLOUDSTACK-7674 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7674 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Upgrade Affects Versions: 4.3.1 Environment: CS Manager on Ubuntu 12.04 from standard repo Hosts: XenServer 6.0.2 Zone: Basic Network Offering: DefaultSharedNetworkOffering Reporter: Carlos Reategui Priority: Critical In previous versions, the broadcast_uri in the Networks table was NULL for Guest network in a Basic Zone with a network offering of DefaultSharedNetworkOffering. From 4.3.1 (maybe 4.3.0 too but not sure) it can not be NULL and must be set to vlan://untagged. The upgrade scripts do not do this and therefore one is unable to create new instances. I don't know if this affect other hypervisors besides XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7654) createtmplt.sh (invoked by cloud-install-sys-tmplt) is not able to seed zipped templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161569#comment-14161569 ] ASF subversion and git services commented on CLOUDSTACK-7654: - Commit 67ff7dac8290560715629241e09fe9fb0359c990 in cloudstack's branch refs/heads/master from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=67ff7da ] CLOUDSTACK-7654 fixed issues with zip format templates. createtmplt.sh (invoked by cloud-install-sys-tmplt) is not able to seed zipped templates Key: CLOUDSTACK-7654 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7654 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Priority: Critical Fix For: 4.5.0 I tried to seed the hyper-v template which is now in zipped format and the script seems to be failing to do the same although there is no explicit error message. Template used : from jenkins job Steps: = 1. Mount the secondary storage in a local mount point 2. Seed the system vm template using /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /temp -u http://10.102.192.128/templates/systemvm64template-master-hyperv.vhd.zip -h hyperv 3. Verify after the set up is brought up Result = System VMs fail to come up since the system vm template in the secondary storage is corrupted. Following is the error message from Hyper-V install: Failed to open attachment '\\smb19\hyperv-share\sowmya-ps1\9e5ee642-ce2a-44fc-bb65-690936634b0f.vhd'. Error: 'The file or directory is corrupted and unreadable The cloud-install-sys-tmplt seems to invoke the createtmplt.sh script to uncompress and copy the template to secondary storage. But is probably failing to uncompress. While executing the script, I get the following message which implies that it is failing to uncompress the zipped file: File /usr/share/cloudstack-common/scripts/storage/secondary/2618f45e-c2fc-445b-81cd-b93906d23dda.vhd does not appear to be compressed Further, when we manually unzip the above zipped template file and launch a VM from the unzipped vhd, it launches the VM properly. This implies that it is either not un compressed or somewhere corrupting the file before copying over to the secondary storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7677) 4.2 systemvm template job failing
Harikrishna Patnala created CLOUDSTACK-7677: --- Summary: 4.2 systemvm template job failing Key: CLOUDSTACK-7677 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7677 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.2.0 Reporter: Harikrishna Patnala Assignee: Harikrishna Patnala Fix For: 4.2.0 4.2 system template job is failing with following error + vboxmanage internalcommands converttoraw -format vdi ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' img.raw VBoxManage: error: VD: error VERR_FILE_NOT_FOUND opening image file ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7678) volumes are getting uploaded successfully with wrong url
prashant kumar mishra created CLOUDSTACK-7678: - Summary: volumes are getting uploaded successfully with wrong url Key: CLOUDSTACK-7678 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7678 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Volumes Affects Versions: 4.5.0 Reporter: prashant kumar mishra steps to reproduce - try to upload a volume with wrong url (ex:http://10.147.28.7/templates/4.2/systemvmtemplate-4.2-vh7.wrong.ova) expected upload volume should fail with error message actual volume got uploaded without any error ;volume state=Allocated ,status=empty -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7678) volumes are getting uploaded successfully with wrong url
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-7678:
--
Description:
steps to reproduce
-
try to upload a volume with wrong url
(ex:http://10.147.28.7/templates/4.2/systemvmtemplate-4.2-vh7.wrong.ova)
expected
upload volume should fail with error message
actual
volume got uploaded without any error ;volume state=Allocated ,status=empty
LOG
2014-10-07 14:06:28,065 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-10:ctx-e194f749 ctx-d4dd2a52) submit async job-578, details:
AsyncJobVO {id:578, userId: 2, accountId: 2, instanceType: None, instanceId:
null, cmd:
org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin, cmdInfo:
{sessionkey:O23XzQurR1dEYRv5vCw7aueeRKo\u003d,cmdEventType:VOLUME.UPLOAD,ctxUserId:2,httpmethod:GET,format:OVA,url:http://10.147.28.7/templates/4.2/systemvmtemplate-4.2-vh7.wrong.ova,zoneId:41d605d3-1f77-4878-9559-4710a3b1a8f4,response:json,ctxDetails:{\com.cloud.dc.DataCenter\:\41d605d3-1f77-4878-9559-4710a3b1a8f4\},name:vol,_:1412670977063,ctxAccountId:2,ctxStartEventId:982},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7407677735140, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-10-07 14:06:28,067 DEBUG [c.c.a.ApiServlet] (catalina-exec-10:ctx-e194f749
ctx-d4dd2a52) ===END=== 10.252.193.17 -- GET
command=uploadVolumeresponse=jsonsessionkey=O23XzQurR1dEYRv5vCw7aueeRKo%3Dname=volzoneId=41d605d3-1f77-4878-9559-4710a3b1a8f4format=OVAurl=http%3A%2F%2F10.147.28.7%2Ftemplates%2F4.2%2Fsystemvmtemplate-4.2-vh7.wrong.ova_=1412670977063
2014-10-07 14:06:28,082 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-47:ctx-af7d36d6 job-578) Add job-578 into job monitoring
2014-10-07 14:06:28,082 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-47:ctx-af7d36d6 job-578) Executing AsyncJobVO {id:578,
userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin, cmdInfo:
{sessionkey:O23XzQurR1dEYRv5vCw7aueeRKo\u003d,cmdEventType:VOLUME.UPLOAD,ctxUserId:2,httpmethod:GET,format:OVA,url:http://10.147.28.7/templates/4.2/systemvmtemplate-4.2-vh7.wrong.ova,zoneId:41d605d3-1f77-4878-9559-4710a3b1a8f4,response:json,ctxDetails:{\com.cloud.dc.DataCenter\:\41d605d3-1f77-4878-9559-4710a3b1a8f4\},name:vol,_:1412670977063,ctxAccountId:2,ctxStartEventId:982},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7407677735140, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-10-07 14:06:28,250 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgentCronJob-436:ctx-fb02db4a) Ping from 1(10.147.40.11)
2014-10-07 14:06:28,251 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Process host VM state report from ping
process. host: 1
2014-10-07 14:06:28,255 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: i-4-20-VM
2014-10-07 14:06:28,258 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: i-4-40-VM
2014-10-07 14:06:28,277 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: i-4-42-VM
2014-10-07 14:06:28,323 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: fa4150b3b46f4386862d37b942a07ca7
2014-10-07 14:06:28,401 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Process VM state report. host: 1, number
of records in report: 7
2014-10-07 14:06:28,404 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM state report. host: 1, vm id: 1, power
state: PowerOn
2014-10-07 14:06:28,419 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM power state does not change, skip DB
writing. vm id: 1
2014-10-07 14:06:28,419 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM state report. host: 1, vm id: 2, power
state: PowerOn
2014-10-07 14:06:28,437 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM power state does not change, skip DB
writing. vm id: 2
2014-10-07 14:06:28,437 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM state report. host: 1, vm id: 3, power
state: PowerOn
2014-10-07 14:06:28,451 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM power state does not change, skip DB
writing. vm id: 3
2014-10-07
[jira] [Updated] (CLOUDSTACK-7678) volumes are getting uploaded successfully with wrong url
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-7678:
--
Attachment: Logs_Db.rar
volumes are getting uploaded successfully with wrong url
-
Key: CLOUDSTACK-7678
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7678
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.5.0
Reporter: prashant kumar mishra
Attachments: Logs_Db.rar
steps to reproduce
-
try to upload a volume with wrong url
(ex:http://10.147.28.7/templates/4.2/systemvmtemplate-4.2-vh7.wrong.ova)
expected
upload volume should fail with error message
actual
volume got uploaded without any error ;volume state=Allocated ,status=empty
LOG
2014-10-07 14:06:28,065 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-10:ctx-e194f749 ctx-d4dd2a52) submit async job-578, details:
AsyncJobVO {id:578, userId: 2, accountId: 2, instanceType: None, instanceId:
null, cmd:
org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin,
cmdInfo:
{sessionkey:O23XzQurR1dEYRv5vCw7aueeRKo\u003d,cmdEventType:VOLUME.UPLOAD,ctxUserId:2,httpmethod:GET,format:OVA,url:http://10.147.28.7/templates/4.2/systemvmtemplate-4.2-vh7.wrong.ova,zoneId:41d605d3-1f77-4878-9559-4710a3b1a8f4,response:json,ctxDetails:{\com.cloud.dc.DataCenter\:\41d605d3-1f77-4878-9559-4710a3b1a8f4\},name:vol,_:1412670977063,ctxAccountId:2,ctxStartEventId:982},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7407677735140, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-10-07 14:06:28,067 DEBUG [c.c.a.ApiServlet]
(catalina-exec-10:ctx-e194f749 ctx-d4dd2a52) ===END=== 10.252.193.17 -- GET
command=uploadVolumeresponse=jsonsessionkey=O23XzQurR1dEYRv5vCw7aueeRKo%3Dname=volzoneId=41d605d3-1f77-4878-9559-4710a3b1a8f4format=OVAurl=http%3A%2F%2F10.147.28.7%2Ftemplates%2F4.2%2Fsystemvmtemplate-4.2-vh7.wrong.ova_=1412670977063
2014-10-07 14:06:28,082 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-47:ctx-af7d36d6 job-578) Add job-578 into job monitoring
2014-10-07 14:06:28,082 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-47:ctx-af7d36d6 job-578) Executing AsyncJobVO {id:578,
userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin,
cmdInfo:
{sessionkey:O23XzQurR1dEYRv5vCw7aueeRKo\u003d,cmdEventType:VOLUME.UPLOAD,ctxUserId:2,httpmethod:GET,format:OVA,url:http://10.147.28.7/templates/4.2/systemvmtemplate-4.2-vh7.wrong.ova,zoneId:41d605d3-1f77-4878-9559-4710a3b1a8f4,response:json,ctxDetails:{\com.cloud.dc.DataCenter\:\41d605d3-1f77-4878-9559-4710a3b1a8f4\},name:vol,_:1412670977063,ctxAccountId:2,ctxStartEventId:982},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7407677735140, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-10-07 14:06:28,250 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgentCronJob-436:ctx-fb02db4a) Ping from 1(10.147.40.11)
2014-10-07 14:06:28,251 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Process host VM state report from ping
process. host: 1
2014-10-07 14:06:28,255 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: i-4-20-VM
2014-10-07 14:06:28,258 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: i-4-40-VM
2014-10-07 14:06:28,277 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: i-4-42-VM
2014-10-07 14:06:28,323 INFO [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Unable to find matched VM in CloudStack
DB. name: fa4150b3b46f4386862d37b942a07ca7
2014-10-07 14:06:28,401 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) Process VM state report. host: 1,
number of records in report: 7
2014-10-07 14:06:28,404 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM state report. host: 1, vm id: 1,
power state: PowerOn
2014-10-07 14:06:28,419 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-436:ctx-fb02db4a) VM power state does not change, skip DB
writing. vm id: 1
2014-10-07 14:06:28,419 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
[jira] [Commented] (CLOUDSTACK-7677) 4.2 systemvm template job failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161689#comment-14161689 ] ASF subversion and git services commented on CLOUDSTACK-7677: - Commit 2ad26d772334e8788f4ecf02f3f4fb05ff879f72 in cloudstack's branch refs/heads/4.2 from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2ad26d7 ] CLOUDSTACK-7677: 4.2 systemvm template job failing Fixed the trailing and leading whitespaces in the hdd path Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org 4.2 systemvm template job failing - Key: CLOUDSTACK-7677 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7677 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.2.0 Reporter: Harikrishna Patnala Assignee: Harikrishna Patnala Fix For: 4.2.0 4.2 system template job is failing with following error + vboxmanage internalcommands converttoraw -format vdi ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' img.raw VBoxManage: error: VD: error VERR_FILE_NOT_FOUND opening image file ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161692#comment-14161692 ] ASF subversion and git services commented on CLOUDSTACK-7671: - Commit e8f1c592120707ac214d535a6637fa7dc5826289 in cloudstack's branch refs/heads/master from [~damoder.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e8f1c59 ] CLOUDSTACK-7671: Management server restart failed after reboot [RHEL7] management server failed to start once machine is rebooted -- Key: CLOUDSTACK-7671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Damodar Reddy T Assignee: Damodar Reddy T Repro stesp: Create a rhel 7 host Install MS Start MS Once MS is up and running . Reboot MS . Notice Cloudstack-management service status Bug: Notice MS fails to start even after calling service cloudstack-management restart it failed to start systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min 28s ago Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. [root@Rack1Pod1Host27 run]# service cloudstack-management status Redirecting to /bin/systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s ago Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7679) bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5
Murali Reddy created CLOUDSTACK-7679: Summary: bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5 Key: CLOUDSTACK-7679 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7679 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.1.0, 4.3.0, 4.4.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.5.0 When management server is run with event bus enabled for longer duration like week or so, it is observed that there is locking issues due to which management server will become un-responsive. Stack trace is observed as below. 2670351 catalina-exec-25 daemon prio=10 tid=0x7f6a04bbf000 nid=0x17dc in Object.wait() [0x7f69f30ae000] 2670352 java.lang.Thread.State: WAITING (on object monitor) 2670353 ---at java.lang.Object.wait(Native Method) 2670354 waiting on 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670355 ---at java.lang.Object.wait(Object.java:502) 2670356 ---at com.rabbitmq.utility.BlockingCell.get(BlockingCell.java:50) 2670357 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670358 ---at com.rabbitmq.utility.BlockingCell.uninterruptibleGet(BlockingCell.java:89) 2670359 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670360 ---at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:33) 2670361 ---at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:343) 2670362 ---at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:216) 2670363 ---at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:118) 2670364 ---at com.rabbitmq.client.impl.ChannelN.open(ChannelN.java:125) 2670365 ---at com.rabbitmq.client.impl.ChannelManager.createChannel(ChannelManager.java:121) 2670366 ---at com.rabbitmq.client.impl.AMQConnection.createChannel(AMQConnection.java:466) 2670367 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.createChannel(RabbitMQEventBus.java:389) 2670368 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.publish(RabbitMQEventBus.java:242) 2670369 ---at com.cloud.event.ActionEventUtils.publishOnEventBus(ActionEventUtils.java:224) 2670370 ---at com.cloud.event.ActionEventUtils.onActionEvent(ActionEventUtils.java:78) 2670371 ---at com.cloud.user.AccountManagerImpl.authenticateUser(AccountManagerImpl.java:1942) 2670372 ---at sun.reflect.GeneratedMethodAccessor355.invoke(Unknown Source) 2670373 ---at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2670374 ---at java.lang.reflect.Method.invoke(Method.java:616) 2670375 ---at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) 2670376 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) 2670377 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) 2670378 ---at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) 2670379 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) 2670380 ---at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) 2670381 ---at $Proxy83.authenticateUser(Unknown Source) 2670382 ---at com.cloud.api.ApiServer.loginUser(ApiServer.java:893) In the latest version of rabbitMQ java AMQP client seems to have fixed some of issues. This bug is to bump up the client version to use latest RabbitMQ AMQP client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7679) bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161702#comment-14161702 ] ASF subversion and git services commented on CLOUDSTACK-7679: - Commit ff797dfa5943c4e02acc87466c4638e97d2c2eb0 in cloudstack's branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ff797df ] CLOUDSTACK-7679: bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5 3.3.5 is the latest stable version of AMQP client, which is also backward comaptible. Successfully tested with updated client library. bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5 - Key: CLOUDSTACK-7679 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7679 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0, 4.3.0, 4.4.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.5.0 When management server is run with event bus enabled for longer duration like week or so, it is observed that there is locking issues due to which management server will become un-responsive. Stack trace is observed as below. 2670351 catalina-exec-25 daemon prio=10 tid=0x7f6a04bbf000 nid=0x17dc in Object.wait() [0x7f69f30ae000] 2670352 java.lang.Thread.State: WAITING (on object monitor) 2670353 ---at java.lang.Object.wait(Native Method) 2670354 waiting on 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670355 ---at java.lang.Object.wait(Object.java:502) 2670356 ---at com.rabbitmq.utility.BlockingCell.get(BlockingCell.java:50) 2670357 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670358 ---at com.rabbitmq.utility.BlockingCell.uninterruptibleGet(BlockingCell.java:89) 2670359 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670360 ---at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:33) 2670361 ---at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:343) 2670362 ---at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:216) 2670363 ---at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:118) 2670364 ---at com.rabbitmq.client.impl.ChannelN.open(ChannelN.java:125) 2670365 ---at com.rabbitmq.client.impl.ChannelManager.createChannel(ChannelManager.java:121) 2670366 ---at com.rabbitmq.client.impl.AMQConnection.createChannel(AMQConnection.java:466) 2670367 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.createChannel(RabbitMQEventBus.java:389) 2670368 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.publish(RabbitMQEventBus.java:242) 2670369 ---at com.cloud.event.ActionEventUtils.publishOnEventBus(ActionEventUtils.java:224) 2670370 ---at com.cloud.event.ActionEventUtils.onActionEvent(ActionEventUtils.java:78) 2670371 ---at com.cloud.user.AccountManagerImpl.authenticateUser(AccountManagerImpl.java:1942) 2670372 ---at sun.reflect.GeneratedMethodAccessor355.invoke(Unknown Source) 2670373 ---at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2670374 ---at java.lang.reflect.Method.invoke(Method.java:616) 2670375 ---at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) 2670376 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) 2670377 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) 2670378 ---at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) 2670379 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) 2670380 ---at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) 2670381 ---at $Proxy83.authenticateUser(Unknown Source) 2670382 ---at com.cloud.api.ApiServer.loginUser(ApiServer.java:893) In the latest version of rabbitMQ java AMQP client seems to have fixed some of issues. This bug is to bump up the client version to use latest RabbitMQ AMQP client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7679) bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-7679. -- Resolution: Fixed bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5 - Key: CLOUDSTACK-7679 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7679 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0, 4.3.0, 4.4.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.5.0 When management server is run with event bus enabled for longer duration like week or so, it is observed that there is locking issues due to which management server will become un-responsive. Stack trace is observed as below. 2670351 catalina-exec-25 daemon prio=10 tid=0x7f6a04bbf000 nid=0x17dc in Object.wait() [0x7f69f30ae000] 2670352 java.lang.Thread.State: WAITING (on object monitor) 2670353 ---at java.lang.Object.wait(Native Method) 2670354 waiting on 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670355 ---at java.lang.Object.wait(Object.java:502) 2670356 ---at com.rabbitmq.utility.BlockingCell.get(BlockingCell.java:50) 2670357 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670358 ---at com.rabbitmq.utility.BlockingCell.uninterruptibleGet(BlockingCell.java:89) 2670359 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670360 ---at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:33) 2670361 ---at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:343) 2670362 ---at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:216) 2670363 ---at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:118) 2670364 ---at com.rabbitmq.client.impl.ChannelN.open(ChannelN.java:125) 2670365 ---at com.rabbitmq.client.impl.ChannelManager.createChannel(ChannelManager.java:121) 2670366 ---at com.rabbitmq.client.impl.AMQConnection.createChannel(AMQConnection.java:466) 2670367 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.createChannel(RabbitMQEventBus.java:389) 2670368 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.publish(RabbitMQEventBus.java:242) 2670369 ---at com.cloud.event.ActionEventUtils.publishOnEventBus(ActionEventUtils.java:224) 2670370 ---at com.cloud.event.ActionEventUtils.onActionEvent(ActionEventUtils.java:78) 2670371 ---at com.cloud.user.AccountManagerImpl.authenticateUser(AccountManagerImpl.java:1942) 2670372 ---at sun.reflect.GeneratedMethodAccessor355.invoke(Unknown Source) 2670373 ---at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2670374 ---at java.lang.reflect.Method.invoke(Method.java:616) 2670375 ---at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) 2670376 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) 2670377 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) 2670378 ---at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) 2670379 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) 2670380 ---at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) 2670381 ---at $Proxy83.authenticateUser(Unknown Source) 2670382 ---at com.cloud.api.ApiServer.loginUser(ApiServer.java:893) In the latest version of rabbitMQ java AMQP client seems to have fixed some of issues. This bug is to bump up the client version to use latest RabbitMQ AMQP client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7660) Enhance system vm template to support baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161716#comment-14161716 ] ASF subversion and git services commented on CLOUDSTACK-7660: - Commit c1aa35fc0fb594f74041a025bdc8ef219f6df8c0 in cloudstack's branch refs/heads/baremetal-systemvm from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c1aa35f ] CLOUDSTACK-7660: Enhance system vm template to support baremetal Installed Package flask and merged the disk partitions Enhance system vm template to support baremetal --- Key: CLOUDSTACK-7660 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7660 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.5.0 Reporter: frank zhang Assignee: Harikrishna Patnala Fix For: 4.5.0 Two things need doing: 1. pip install flask when building template 2. merge 7 disk partitions to single one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7680) Adding kwargs to volume.upload in base.py
prashant kumar mishra created CLOUDSTACK-7680: - Summary: Adding kwargs to volume.upload in base.py Key: CLOUDSTACK-7680 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7680 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Reporter: prashant kumar mishra Assignee: prashant kumar mishra modifying volume.upload to take number of parameter like checksum, projectid, magestoreuuid, diskofferingid etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7087) [VR] [VPN] Downgrade openswan to previous version for VPN services to fix OSX client
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161731#comment-14161731 ] ASF subversion and git services commented on CLOUDSTACK-7087: - Commit d0db137d808f924dedf372d6824bc09f98e0135c in cloudstack's branch refs/heads/4.2 from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d0db137 ] CLOUDSTACK-7087: Downgrade openswan to previous version for VPN services to fix OSX client Downgrading openswan version to 1:2.6.37-3 Signed-off-by: Jayapal jaya...@apache.org [VR] [VPN] Downgrade openswan to previous version for VPN services to fix OSX client Key: CLOUDSTACK-7087 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7087 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Virtual Router Affects Versions: 4.2.0, 4.3.0 Reporter: Sheng Yang Assignee: Harikrishna Patnala Fix For: 4.4.0, 4.3.1 Latest OpenSwan fail to work with OSX/IOS after latest Debian security update(Mar 2014, https://www.debian.org/security/2014/dsa-2893 ). And why Debian didn’t fix it officially, is because Debian decided to drop the support for OpenSwan(since nobody is maintaining it and it hasn’t been updated for 2 years before this security fix). We would need to move to other VPN software in the future. Here is the Debian bugzilla for the issue. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744717 So far, downgrade openswan is only an intermediate solution. We need to move to other VPN software(e.g. StrongSwan) which is still maintained by Debain in the near future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7680) Adding kwargs to volume.upload in base.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161744#comment-14161744 ] ASF subversion and git services commented on CLOUDSTACK-7680: - Commit 4a1018e23b0ea80ba8b7cdb80a5efebdb50afea1 in cloudstack's branch refs/heads/master from [~prashantkm] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4a1018e ] CLOUDSTACK-7680:Adding kwargs to volume.upload in base.py Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org Adding kwargs to volume.upload in base.py - Key: CLOUDSTACK-7680 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7680 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Reporter: prashant kumar mishra Assignee: prashant kumar mishra modifying volume.upload to take number of parameter like checksum, projectid, magestoreuuid, diskofferingid etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161770#comment-14161770 ] ASF subversion and git services commented on CLOUDSTACK-6650: - Commit d910b4ff14bcf5d9e7892b5ffd39acb47745f106 in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d910b4f ] CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment. Cluster reordering is based on the number of unique host tags in a cluster, cluster with most number of unique host tags will put at the end of list. Hosts with GPU capability will get tagged with implicit tags defined by global config param 'implicit.host.tags' at the time os host discovery. Also added FirstFitPlannerTest unit test file. Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment -- Key: CLOUDSTACK-6650 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6650 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 If CS environment has GPU cards then for non-GPU enabled VM deployments, deployment planner should check the non-GPU hosts first and if they are out of capacity then deploy in GPU enabled hosts. For now, this restriction is imposed at cluster level not at zone level, so to protect GPU resources, CS should give lower priority to clusters which has GPU enabled host and high priority to clusters which contains non-GPU enabled hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7649) test_lb_secondary_ip.py - test case failing during SSH when VM is detroyed and recovered
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161787#comment-14161787 ] ASF subversion and git services commented on CLOUDSTACK-7649: - Commit 69bd2d3c7c0b7b2d994da43f8090b29c468cae65 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=69bd2d3 ] CLOUDSTACK-7649: test_lb_secondary_ip.py - Removed SSH trying step after Destroying and Recovering VM because secondary IP information does not retain on VM after destroying it and SSH will not be successful in that case Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test_lb_secondary_ip.py - test case failing during SSH when VM is detroyed and recovered Key: CLOUDSTACK-7649 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7649 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Environment: Observed on KVM Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.5.0 The test case test_20_destroy_recover_vm fails while SSH connection after destroying and recovering VM. It fails because the secondary IP configuration is lost when VM is destroyed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7671. - Resolution: Fixed [RHEL7] management server failed to start once machine is rebooted -- Key: CLOUDSTACK-7671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Damodar Reddy T Assignee: Damodar Reddy T Repro stesp: Create a rhel 7 host Install MS Start MS Once MS is up and running . Reboot MS . Notice Cloudstack-management service status Bug: Notice MS fails to start even after calling service cloudstack-management restart it failed to start systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min 28s ago Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. [root@Rack1Pod1Host27 run]# service cloudstack-management status Redirecting to /bin/systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s ago Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7644) test_persistent_networks.py - SSH failure in case of LB rules due to port mismatch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161797#comment-14161797 ] ASF subversion and git services commented on CLOUDSTACK-7644: - Commit cd672709c35e92a4a5a9767e2d2e60aa91fd8e73 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cd67270 ] CLOUDSTACK-7644: test_persistent_networks.py - SSH failure in case of LB rule due to port mismatch Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test_persistent_networks.py - SSH failure in case of LB rules due to port mismatch -- Key: CLOUDSTACK-7644 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7644 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Environment: Observed in KVM Regression runs Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.5.0 Test case which try SSH to VM after creating LB rule fail during SSH. The SSH method tries to connect via SSH to default port 22, but LB rule is created for public port . Hence in this case, port number should be explicitly passed while trying SSH. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7646) test_nuage_vsp.py - Fix indentation issues and list out of index, mark test case as invalid, should be moved to BVT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161798#comment-14161798 ] ASF subversion and git services commented on CLOUDSTACK-7646: - Commit 5408e0b8d195fa32a0a9a59ea2e3535ed083ee8e in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5408e0b ] CLOUDSTACK-7646: test_nuage_vsp.py - Fixed basic indentation issues, list index issues, marked it as invalid because the test cases needs attention by the original author as it does not pass even after fixing the issues. Also moving it to smoke folder as clearly it is a Basic Validation test Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test_nuage_vsp.py - Fix indentation issues and list out of index, mark test case as invalid, should be moved to BVT --- Key: CLOUDSTACK-7646 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7646 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Environment: Observed on KVM Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.5.0 This test has many indentation issues and list index issues. Also even after fixing the issues the test case does not pass which indicates it has not run before adding to regression test cases. It should be marked as Invalid. After author fixes the remaining issues, this test suite should be moved to Smoke (BVT) as it has only one test case which is clearly a BVT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7679) bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162110#comment-14162110 ] ASF subversion and git services commented on CLOUDSTACK-7679: - Commit 6d0a9b2482101141dafbb16e69c417054fa652fa in cloudstack's branch refs/heads/4.3 from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6d0a9b2 ] CLOUDSTACK-7679: bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5 3.3.5 is the latest stable version of AMQP client, which is also backward comaptible. Successfully tested with updated client library. (cherry picked from commit ff797dfa5943c4e02acc87466c4638e97d2c2eb0) Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com bump up the RabbitMQ AMQP java client version from 2.8.7 to 3.3.5 - Key: CLOUDSTACK-7679 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7679 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0, 4.3.0, 4.4.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.5.0 When management server is run with event bus enabled for longer duration like week or so, it is observed that there is locking issues due to which management server will become un-responsive. Stack trace is observed as below. 2670351 catalina-exec-25 daemon prio=10 tid=0x7f6a04bbf000 nid=0x17dc in Object.wait() [0x7f69f30ae000] 2670352 java.lang.Thread.State: WAITING (on object monitor) 2670353 ---at java.lang.Object.wait(Native Method) 2670354 waiting on 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670355 ---at java.lang.Object.wait(Object.java:502) 2670356 ---at com.rabbitmq.utility.BlockingCell.get(BlockingCell.java:50) 2670357 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670358 ---at com.rabbitmq.utility.BlockingCell.uninterruptibleGet(BlockingCell.java:89) 2670359 locked 0x00075c1687e8 (a com.rabbitmq.utility.BlockingValueOrException) 2670360 ---at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:33) 2670361 ---at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:343) 2670362 ---at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:216) 2670363 ---at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:118) 2670364 ---at com.rabbitmq.client.impl.ChannelN.open(ChannelN.java:125) 2670365 ---at com.rabbitmq.client.impl.ChannelManager.createChannel(ChannelManager.java:121) 2670366 ---at com.rabbitmq.client.impl.AMQConnection.createChannel(AMQConnection.java:466) 2670367 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.createChannel(RabbitMQEventBus.java:389) 2670368 ---at org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus.publish(RabbitMQEventBus.java:242) 2670369 ---at com.cloud.event.ActionEventUtils.publishOnEventBus(ActionEventUtils.java:224) 2670370 ---at com.cloud.event.ActionEventUtils.onActionEvent(ActionEventUtils.java:78) 2670371 ---at com.cloud.user.AccountManagerImpl.authenticateUser(AccountManagerImpl.java:1942) 2670372 ---at sun.reflect.GeneratedMethodAccessor355.invoke(Unknown Source) 2670373 ---at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2670374 ---at java.lang.reflect.Method.invoke(Method.java:616) 2670375 ---at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) 2670376 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) 2670377 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) 2670378 ---at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) 2670379 ---at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) 2670380 ---at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) 2670381 ---at $Proxy83.authenticateUser(Unknown Source) 2670382 ---at com.cloud.api.ApiServer.loginUser(ApiServer.java:893) In the latest version of rabbitMQ java AMQP client seems to have fixed some of issues. This bug is to bump up the client version to use latest RabbitMQ AMQP client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7681) UI zone wizard Advanced zone hypervisor = do not support BareMetal
Jessica Wang created CLOUDSTACK-7681: Summary: UI zone wizard Advanced zone hypervisor = do not support BareMetal Key: CLOUDSTACK-7681 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7681 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7681) UI zone wizard Advanced zone hypervisor = do not support BareMetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-7681. -- Resolution: Fixed UI zone wizard Advanced zone hypervisor = do not support BareMetal - Key: CLOUDSTACK-7681 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7681 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7681) UI zone wizard Advanced zone hypervisor = do not support BareMetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162203#comment-14162203 ] ASF subversion and git services commented on CLOUDSTACK-7681: - Commit 3b704ac6f3f3575f45722308cd1f882acd097fb1 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b704ac ] CLOUDSTACK-7681: UI zone wizard Advanced zone hypervisor = do not support BareMetal UI zone wizard Advanced zone hypervisor = do not support BareMetal - Key: CLOUDSTACK-7681 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7681 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7681) UI zone wizard Advanced zone hypervisor = do not support BareMetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7681. UI zone wizard Advanced zone hypervisor = do not support BareMetal - Key: CLOUDSTACK-7681 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7681 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7681) UI zone wizard Advanced zone hypervisor = do not support BareMetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7681: - Attachment: 2_after_UI_change.jpg 1_before_UI_change.jpg UI zone wizard Advanced zone hypervisor = do not support BareMetal - Key: CLOUDSTACK-7681 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7681 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Attachments: 1_before_UI_change.jpg, 2_after_UI_change.jpg -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7661) UI - VM Wizard - add Keyboard Language dropdown.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-7661: - Assignee: Jessica Wang (was: Brian Federle) Jessica, I just made the changes. You will now see 'keyboardLanguage' in args.data for the wizard action function. UI - VM Wizard - add Keyboard Language dropdown. Key: CLOUDSTACK-7661 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7661 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7661) UI - VM Wizard - add Keyboard Language dropdown.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162473#comment-14162473 ] ASF subversion and git services commented on CLOUDSTACK-7661: - Commit f4326aec82dd34da3660c1b089e23e0c50dd21b8 in cloudstack's branch refs/heads/master from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f4326ae ] CLOUDSTACK-7661: VM wizard: Add keyboard language dropdown UI - VM Wizard - add Keyboard Language dropdown. Key: CLOUDSTACK-7661 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7661 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Brian Federle -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162476#comment-14162476 ] ASF subversion and git services commented on CLOUDSTACK-7671: - Commit e2ca6e38d5e850d820fa0ebfacb7dca9f1f06095 in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e2ca6e3 ] Revert CLOUDSTACK-7671: Management server restart failed after reboot This reverts commit e8f1c592120707ac214d535a6637fa7dc5826289. [RHEL7] management server failed to start once machine is rebooted -- Key: CLOUDSTACK-7671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Damodar Reddy T Assignee: Damodar Reddy T Repro stesp: Create a rhel 7 host Install MS Start MS Once MS is up and running . Reboot MS . Notice Cloudstack-management service status Bug: Notice MS fails to start even after calling service cloudstack-management restart it failed to start systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min 28s ago Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. [root@Rack1Pod1Host27 run]# service cloudstack-management status Redirecting to /bin/systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s ago Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-4987) Able to add isolated network belonging to an account to a virtual machine belonging to different account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162556#comment-14162556 ] ASF subversion and git services commented on CLOUDSTACK-4987: - Commit 794ee6929d078fd919842f2c1f55156f133d7934 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=794ee69 ] CLOUDSTACK-4987: UI Instances detailView NICs tab Add network to VM Network dropdown = (1) For root-admin, populate networks of all accounts. (2) For regular-user/domain-admin, populate only networks belonging to this VM owner. Able to add isolated network belonging to an account to a virtual machine belonging to different account Key: CLOUDSTACK-4987 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4987 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0, 4.3.0 Environment: Observed on KVM. Did not test on Xen and VMware yet. Reporter: Gaurav Aradhye Assignee: Jessica Wang Fix For: 4.4.0 1. Deploy an instance in an account 2. Create an isolated network in different account 3. Add this isolated network to the VM (both belong to different accounts within same domain) As per the test plan - Test case no. 18 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+networks+to+VM+Test+cases), API should fail in this case. But it has been observed that network gets added successfully and new NIC can be seen in VM's NICs list for this network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4987) Able to add isolated network belonging to an account to a virtual machine belonging to different account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-4987: - Attachment: jessica2.PNG jessica1.PNG Able to add isolated network belonging to an account to a virtual machine belonging to different account Key: CLOUDSTACK-4987 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4987 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0, 4.3.0 Environment: Observed on KVM. Did not test on Xen and VMware yet. Reporter: Gaurav Aradhye Assignee: Jessica Wang Fix For: 4.4.0 Attachments: jessica1.PNG, jessica2.PNG 1. Deploy an instance in an account 2. Create an isolated network in different account 3. Add this isolated network to the VM (both belong to different accounts within same domain) As per the test plan - Test case no. 18 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+networks+to+VM+Test+cases), API should fail in this case. But it has been observed that network gets added successfully and new NIC can be seen in VM's NICs list for this network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4987) Able to add isolated network belonging to an account to a virtual machine belonging to different account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-4987: - Attachment: (was: jessica1.PNG) Able to add isolated network belonging to an account to a virtual machine belonging to different account Key: CLOUDSTACK-4987 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4987 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0, 4.3.0 Environment: Observed on KVM. Did not test on Xen and VMware yet. Reporter: Gaurav Aradhye Assignee: Jessica Wang Fix For: 4.4.0 Attachments: 2014_10_07_jessica1.PNG, 2014_10_07_jessica2.PNG 1. Deploy an instance in an account 2. Create an isolated network in different account 3. Add this isolated network to the VM (both belong to different accounts within same domain) As per the test plan - Test case no. 18 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+networks+to+VM+Test+cases), API should fail in this case. But it has been observed that network gets added successfully and new NIC can be seen in VM's NICs list for this network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-4987) Able to add isolated network belonging to an account to a virtual machine belonging to different account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-4987. -- Resolution: Fixed Able to add isolated network belonging to an account to a virtual machine belonging to different account Key: CLOUDSTACK-4987 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4987 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0, 4.3.0 Environment: Observed on KVM. Did not test on Xen and VMware yet. Reporter: Gaurav Aradhye Assignee: Jessica Wang Fix For: 4.4.0 Attachments: 2014_10_07_jessica1.PNG, 2014_10_07_jessica2.PNG 1. Deploy an instance in an account 2. Create an isolated network in different account 3. Add this isolated network to the VM (both belong to different accounts within same domain) As per the test plan - Test case no. 18 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+networks+to+VM+Test+cases), API should fail in this case. But it has been observed that network gets added successfully and new NIC can be seen in VM's NICs list for this network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4987) Able to add isolated network belonging to an account to a virtual machine belonging to different account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-4987: - Attachment: 2014_10_07_jessica2.PNG 2014_10_07_jessica1.PNG Able to add isolated network belonging to an account to a virtual machine belonging to different account Key: CLOUDSTACK-4987 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4987 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0, 4.3.0 Environment: Observed on KVM. Did not test on Xen and VMware yet. Reporter: Gaurav Aradhye Assignee: Jessica Wang Fix For: 4.4.0 Attachments: 2014_10_07_jessica1.PNG, 2014_10_07_jessica2.PNG 1. Deploy an instance in an account 2. Create an isolated network in different account 3. Add this isolated network to the VM (both belong to different accounts within same domain) As per the test plan - Test case no. 18 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+networks+to+VM+Test+cases), API should fail in this case. But it has been observed that network gets added successfully and new NIC can be seen in VM's NICs list for this network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4987) Able to add isolated network belonging to an account to a virtual machine belonging to different account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-4987: - Attachment: (was: jessica2.PNG) Able to add isolated network belonging to an account to a virtual machine belonging to different account Key: CLOUDSTACK-4987 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4987 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0, 4.3.0 Environment: Observed on KVM. Did not test on Xen and VMware yet. Reporter: Gaurav Aradhye Assignee: Jessica Wang Fix For: 4.4.0 Attachments: 2014_10_07_jessica1.PNG, 2014_10_07_jessica2.PNG 1. Deploy an instance in an account 2. Create an isolated network in different account 3. Add this isolated network to the VM (both belong to different accounts within same domain) As per the test plan - Test case no. 18 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+networks+to+VM+Test+cases), API should fail in this case. But it has been observed that network gets added successfully and new NIC can be seen in VM's NICs list for this network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7677) 4.2 systemvm template job failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162636#comment-14162636 ] Animesh Chaturvedi commented on CLOUDSTACK-7677: Should this be resolved ? 4.2 systemvm template job failing - Key: CLOUDSTACK-7677 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7677 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.2.0 Reporter: Harikrishna Patnala Assignee: Harikrishna Patnala Fix For: 4.2.0 4.2 system template job is failing with following error + vboxmanage internalcommands converttoraw -format vdi ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' img.raw VBoxManage: error: VD: error VERR_FILE_NOT_FOUND opening image file ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162752#comment-14162752 ] ASF subversion and git services commented on CLOUDSTACK-3195: - Commit 925f30a41b0dc5c4eddf6061852d9e73e9623d99 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=925f30a ] CLOUDSTACK-3195: UI IP Address detailView Configuration tab Port Forwarding for regular-user, if underlying VM has been destroyed (i.e. listVirtualMachines API returns nothing), compose vm object from limited vm data in port forwarding rule object. So, a vm object (required in widget code) can be passed to widget code. cannot view/delete forward rules if underlying/target VM is destroyed first --- Key: CLOUDSTACK-3195 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.0 Environment: CentOS 6.4+latest patches with official 4.1.0 RPM release from Apache Reporter: Bryan Whitehead Assignee: Jessica Wang Fix For: 4.4.0 As a non-admin user, create a new Isolated network with SNAT. Build a VM using this network. After VM is up, In the new isolated network add a firewall rule (port 22 as example). Next add a forward for private range 22-22 and public 22-22, choose the VM in network. Verify the forward and firewall rule work (ssh SNAT-IP etc). KEY BUG: Delete the VM in the isolated network. After the delete there will be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN user) Create a new VM using the same isolated network. When attempting to setup a new forward to this VM you'll get an error about a rule already existing as a conflict - however you won't be able to delete it. The admin user can see the bogus rule and delete it. Then everything works as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-3195. -- Resolution: Fixed cannot view/delete forward rules if underlying/target VM is destroyed first --- Key: CLOUDSTACK-3195 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.0 Environment: CentOS 6.4+latest patches with official 4.1.0 RPM release from Apache Reporter: Bryan Whitehead Assignee: Jessica Wang Fix For: 4.4.0 As a non-admin user, create a new Isolated network with SNAT. Build a VM using this network. After VM is up, In the new isolated network add a firewall rule (port 22 as example). Next add a forward for private range 22-22 and public 22-22, choose the VM in network. Verify the forward and firewall rule work (ssh SNAT-IP etc). KEY BUG: Delete the VM in the isolated network. After the delete there will be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN user) Create a new VM using the same isolated network. When attempting to setup a new forward to this VM you'll get an error about a rule already existing as a conflict - however you won't be able to delete it. The admin user can see the bogus rule and delete it. Then everything works as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-3195: - Attachment: 2014_10_07_jessica3.PNG 2014_10_07_jessica2.PNG 2014_10_07_jessica1.PNG cannot view/delete forward rules if underlying/target VM is destroyed first --- Key: CLOUDSTACK-3195 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.0 Environment: CentOS 6.4+latest patches with official 4.1.0 RPM release from Apache Reporter: Bryan Whitehead Assignee: Jessica Wang Fix For: 4.4.0 Attachments: 2014_10_07_jessica1.PNG, 2014_10_07_jessica2.PNG, 2014_10_07_jessica3.PNG As a non-admin user, create a new Isolated network with SNAT. Build a VM using this network. After VM is up, In the new isolated network add a firewall rule (port 22 as example). Next add a forward for private range 22-22 and public 22-22, choose the VM in network. Verify the forward and firewall rule work (ssh SNAT-IP etc). KEY BUG: Delete the VM in the isolated network. After the delete there will be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN user) Create a new VM using the same isolated network. When attempting to setup a new forward to this VM you'll get an error about a rule already existing as a conflict - however you won't be able to delete it. The admin user can see the bogus rule and delete it. Then everything works as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7677) 4.2 systemvm template job failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-7677. - Resolution: Fixed 4.2 systemvm template job failing - Key: CLOUDSTACK-7677 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7677 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.2.0 Reporter: Harikrishna Patnala Assignee: Harikrishna Patnala Fix For: 4.2.0 4.2 system template job is failing with following error + vboxmanage internalcommands converttoraw -format vdi ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' img.raw VBoxManage: error: VD: error VERR_FILE_NOT_FOUND opening image file ' /home/jenkins/VirtualBox VMs/systemvmtemplate/systemvmtemplate1.vdi' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7682) test_01_template_usage failing because TEMPLATE.CREATE usage event does not exist for account
Gaurav Aradhye created CLOUDSTACK-7682: -- Summary: test_01_template_usage failing because TEMPLATE.CREATE usage event does not exist for account Key: CLOUDSTACK-7682 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7682 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 The events TEMPLATE.CREATE and TEMPLATE.DELETE does not exist in usage event table against that particular account because the template is not created using the api client of the account and hence the template belongs to the root admin account. Changes required: Use the api client of the account against which we are checking the usage while creating and deleting the template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7683) NPE while expunging the failed VM
Sailaja Mada created CLOUDSTACK-7683: Summary: NPE while expunging the failed VM Key: CLOUDSTACK-7683 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7683 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Steps: 1. Install and configure with XS 6.5 2. Tried to Deployed VM (Windows 7) . It failed to deploy VM due to resources not being available 3. Deleted this VM which is in Error state Observation:NPE while expunging the failed VM 2014-10-08 11:09:11,894 DEBUG [o.a.c.s.v.VolumeObject] (API-Job-Executor-58:ctx-bdc8e992 job-4398 ctx-8115790b) Failed to update state java.lang.NullPointerException at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:101) at org.apache.cloudstack.storage.volume.VolumeObject.stateTransit(VolumeObject.java:185) at org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:325) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.deleteVolumeCallback(VolumeServiceImpl.java:339) at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.datastore.driver.CloudStackPrimaryDataStoreDriverImpl.deleteAsync(CloudStackPrimaryDataStoreDriverImpl.java:222) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.expungeVolumeAsync(VolumeServiceImpl.java:323) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.cleanupVolumes(VolumeOrchestrator.java:862) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:522) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:454) at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1709) at sun.reflect.GeneratedMethodAccessor803.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 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.$Proxy212.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:738) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:665) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1444) at sun.reflect.GeneratedMethodAccessor816.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 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.$Proxy212.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:738) at
[jira] [Updated] (CLOUDSTACK-7683) NPE while expunging the failed VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7683: - Fix Version/s: 4.5.0 NPE while expunging the failed VM - Key: CLOUDSTACK-7683 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7683 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.5.0 Steps: 1. Install and configure with XS 6.5 2. Tried to Deployed VM (Windows 7) . It failed to deploy VM due to resources not being available 3. Deleted this VM which is in Error state Observation:NPE while expunging the failed VM 2014-10-08 11:09:11,894 DEBUG [o.a.c.s.v.VolumeObject] (API-Job-Executor-58:ctx-bdc8e992 job-4398 ctx-8115790b) Failed to update state java.lang.NullPointerException at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:101) at org.apache.cloudstack.storage.volume.VolumeObject.stateTransit(VolumeObject.java:185) at org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:325) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.deleteVolumeCallback(VolumeServiceImpl.java:339) at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.datastore.driver.CloudStackPrimaryDataStoreDriverImpl.deleteAsync(CloudStackPrimaryDataStoreDriverImpl.java:222) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.expungeVolumeAsync(VolumeServiceImpl.java:323) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.cleanupVolumes(VolumeOrchestrator.java:862) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:522) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:454) at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1709) at sun.reflect.GeneratedMethodAccessor803.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 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.$Proxy212.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:738) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:665) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1444) at sun.reflect.GeneratedMethodAccessor816.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 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at
