[jira] [Resolved] (CLOUDSTACK-7053) [Automation] Tasks for writing automated test cases for few product bugs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7053. -- Resolution: Fixed > [Automation] Tasks for writing automated test cases for few product bugs > > > Key: CLOUDSTACK-7053 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7053 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Affects Versions: 4.5.0 >Reporter: Srikanteswararao Talluri >Assignee: Srikanteswararao Talluri > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7053) [Automation] Tasks for writing automated test cases for few product bugs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-7053. > [Automation] Tasks for writing automated test cases for few product bugs > > > Key: CLOUDSTACK-7053 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7053 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Affects Versions: 4.5.0 >Reporter: Srikanteswararao Talluri >Assignee: Srikanteswararao Talluri > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6183) Unplug the nic when all the ips of public subnet is released
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120983#comment-14120983 ] Jayapal Reddy commented on CLOUDSTACK-6183: --- Problem: --- All the ips from the public subnet are removed then also nic corresponding to public subnet in VR is not removed. Due to this nics are not reusable in VR. There is limitation (Max nics) for VM from the hypervisor. Root Cause Analysis: -- When all the ips are removed there is no nic unplug command is called. Proposed solution: --- If last ip address is removed from a specific public subnet then nic unplug is called to remove the nic from VR. Verification steps: -- 1. Add one public subnet 2. Aquire ips from the two subnets and configure the rules so that the nics get plugged in VR. 3. Release all the ips from the subnet Expected: 4. After all ips release the nic on the VR specific to this subnet get removed. The nic should unplugged and it should be reused for other subnets if we add. > Unplug the nic when all the ips of public subnet is released > > > Key: CLOUDSTACK-6183 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6183 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy >Priority: Critical > Fix For: 4.3.0, 4.4.0 > > > 1. Add one public subnet > 2. Aquire ips from the two subnets and configure the rules so that the nics > get plugged in VR. > 3. Release all the ips from the subnet > Expected: > 4. After all ips release the nic on the VR specific to this subnet get > removed. > Bug: The nic is not unplugged and it can't be reused for other subnets if we > add. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7484) [LXC] meaningful message neededcwhen trying to attach a data disk on nfs to a LXC VM
shweta agarwal created CLOUDSTACK-7484:
--
Summary: [LXC] meaningful message neededcwhen trying to attach a
data disk on nfs to a LXC VM
Key: CLOUDSTACK-7484
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7484
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Minor
Fix For: 4.5.0
Repro steps:
Create a LXC VM
Create a data disk on nfs storage
Attach the created disk to LXC VM
Bug:
We gets message unexpected exception
Expected Result :
1. Message should be more meaningful
2. We see exception raised in MS logs which should not be the case. we should
handle it gracefully.
Ms log hows :
2014-09-04 10:45:33,826 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-75:ctx-4a189e50 job-324/job-325 ctx-b838130b) Seq
4-433471464134412663: Sending { Cmd , MgmtId: 233845178472723, via:
4(Rack3Pod1Host49), Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"47e710d5-c35f-4926-9be9-351f5f6a9955","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"dfa2ec3c-d133-3284-8583-0a0845aa4424","id":1,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/shweta/goleta.lxc.primary","port":2049,"url":"NetworkFilesystem://10.147.28.7/export/home/shweta/goleta.lxc.primary/?ROLE=Primary&STOREUUID=dfa2ec3c-d133-3284-8583-0a0845aa4424"}},"name":"Gunjan
Das","size":5368709120,"path":"47e710d5-c35f-4926-9be9-351f5f6a9955","volumeId":23,"accountId":2,"format":"QCOW2","provisioningType":"THIN","id":23,"hypervisorType":"LXC"}},"diskSeq":1,"path":"47e710d5-c35f-4926-9be9-351f5f6a9955","type":"DATADISK","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"5368709120"}},"vmName":"i-2-18-VM","inSeq":false,"wait":0}}]
}
2014-09-04 10:45:33,898 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-3:ctx-66f694f1) Seq 4-433471464134412663: Processing: {
Ans: , MgmtId: 233845178472723, via: 4, Ver: v1, Flags: 10,
[{"org.apache.cloudstack.storage.command.AttachAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
unsupported configuration: Can't setup disk for non-block device","wait":0}}] }
2014-09-04 10:45:33,898 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-75:ctx-4a189e50 job-324/job-325 ctx-b838130b) Seq
4-433471464134412663: Received: { Ans: , MgmtId: 233845178472723, via: 4, Ver:
v1, Flags: 10, { AttachAnswer } }
2014-09-04 10:45:33,900 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-75:ctx-4a189e50 job-324/job-325 ctx-b838130b) Invocation
exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Failed
to attach volume Gunjan Das to VM VM-b5938b03-420e-4f6c-8d60-2e0e086cd08b;
org.libvirt.LibvirtException: unsupported configuration: Can't setup disk for
non-block device
2014-09-04 10:45:33,900 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-75:ctx-4a189e50 job-324/job-325 ctx-b838130b) Rethrow
exception com.cloud.utils.exception.CloudRuntimeException: Failed to attach
volume Gunjan Das to VM VM-b5938b03-420e-4f6c-8d60-2e0e086cd08b;
org.libvirt.LibvirtException: unsupported configuration: Can't setup disk for
non-block device
2014-09-04 10:45:33,900 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-75:ctx-4a189e50 job-324/job-325) Done with run of VM work
job: com.cloud.storage.VmWorkAttachVolume for VM 18, job origin: 324
2014-09-04 10:45:33,900 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-75:ctx-4a189e50 job-324/job-325) Unable to complete
AsyncJobVO {id:325, userId: 2, accountId: 2, instanceType: null, instanceId:
null, cmd: com.cloud.storage.VmWorkAttachVolume, cmdInfo:
rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACABJ0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABgAX,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 233845178472723, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Thu Sep 04 10:45:32 IST 2014}, job origin:324
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume Gunjan
Das to VM VM-b5938b03-420e-4f6c-8d60-2e0e086cd08b;
org.libvirt.LibvirtException: unsupported configuration: Can't setup disk for
non-block device
at
com.cloud.storage.VolumeApiServiceImpl.sendAttachVolu
[jira] [Commented] (CLOUDSTACK-7291) LXC: Mgmt server/agent keeps killing systemvms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120965#comment-14120965 ] Kishan Kavala commented on CLOUDSTACK-7291: --- this is already fixed in 4.5/master. commit 6d4b979c4d0afee85d3244e07e6233ee8784db4f. > LXC: Mgmt server/agent keeps killing systemvms > -- > > Key: CLOUDSTACK-7291 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0, 4.3.1 >Reporter: Rohit Yadav >Assignee: Kishan Kavala >Priority: Blocker > Fix For: 4.3.1 > > > Followed installation and setup docs of 4.3, was unable to get LXC to work on > Ubuntu 14.04/trusty. The systemvms kept coming up and result from > ssvm_check.sh was good and it was able to reach mgmt server /host, even then > mgmt server complained that it was unable to contact agent on the systemvm > (ping), while the agent would gracefully shutdown the systemvm (by killing > them). > Relevant log: > 2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode] > (secstorage-1:ctx-fc57ef43) Could not find exception: > com.cloud.exception.OperationTimedoutException in error code list for > exceptions > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache] > (consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling. > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679) > Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host > id = 1, name = bluebox1.bhaisaab.org] > 2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl] > (secstorage-1:ctx-fc57ef43) Scheduled > HAWork[12-CheckStop-2-Starting-Scheduled] > 2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage > vm > com.cloud.exception.AgentUnavailableException: Resource [Host:1] is > unreachable: Host 1: Unable to start s-2-VM > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > >---at > >com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) > ... > ... > ... > Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 > to Host 1 timed out after 3600 > >---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439) > > > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394) > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989) > >---... 24 more > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7291) LXC: Mgmt server/agent keeps killing systemvms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-7291: -- Assignee: (was: Kishan Kavala) > LXC: Mgmt server/agent keeps killing systemvms > -- > > Key: CLOUDSTACK-7291 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0, 4.3.1 >Reporter: Rohit Yadav >Priority: Blocker > Fix For: 4.3.1 > > > Followed installation and setup docs of 4.3, was unable to get LXC to work on > Ubuntu 14.04/trusty. The systemvms kept coming up and result from > ssvm_check.sh was good and it was able to reach mgmt server /host, even then > mgmt server complained that it was unable to contact agent on the systemvm > (ping), while the agent would gracefully shutdown the systemvm (by killing > them). > Relevant log: > 2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode] > (secstorage-1:ctx-fc57ef43) Could not find exception: > com.cloud.exception.OperationTimedoutException in error code list for > exceptions > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache] > (consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling. > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679) > Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host > id = 1, name = bluebox1.bhaisaab.org] > 2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl] > (secstorage-1:ctx-fc57ef43) Scheduled > HAWork[12-CheckStop-2-Starting-Scheduled] > 2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage > vm > com.cloud.exception.AgentUnavailableException: Resource [Host:1] is > unreachable: Host 1: Unable to start s-2-VM > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > >---at > >com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) > ... > ... > ... > Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 > to Host 1 timed out after 3600 > >---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439) > > > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394) > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989) > >---... 24 more > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7291) LXC: Mgmt server/agent keeps killing systemvms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-7291: -- Fix Version/s: (was: 4.5.0) (was: Future) 4.3.1 > LXC: Mgmt server/agent keeps killing systemvms > -- > > Key: CLOUDSTACK-7291 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0, 4.3.1 >Reporter: Rohit Yadav >Assignee: Kishan Kavala >Priority: Blocker > Fix For: 4.3.1 > > > Followed installation and setup docs of 4.3, was unable to get LXC to work on > Ubuntu 14.04/trusty. The systemvms kept coming up and result from > ssvm_check.sh was good and it was able to reach mgmt server /host, even then > mgmt server complained that it was unable to contact agent on the systemvm > (ping), while the agent would gracefully shutdown the systemvm (by killing > them). > Relevant log: > 2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode] > (secstorage-1:ctx-fc57ef43) Could not find exception: > com.cloud.exception.OperationTimedoutException in error code list for > exceptions > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache] > (consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling. > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679) > Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host > id = 1, name = bluebox1.bhaisaab.org] > 2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl] > (secstorage-1:ctx-fc57ef43) Scheduled > HAWork[12-CheckStop-2-Starting-Scheduled] > 2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage > vm > com.cloud.exception.AgentUnavailableException: Resource [Host:1] is > unreachable: Host 1: Unable to start s-2-VM > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > >---at > >com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) > ... > ... > ... > Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 > to Host 1 timed out after 3600 > >---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439) > > > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394) > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989) > >---... 24 more > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7422) [Automation] Attach volume test case failing with error "Invalid configuration for device '0'"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120960#comment-14120960
]
Amogh Vasekar commented on CLOUDSTACK-7422:
---
Hi,
I suspect this is a test case issue. I tried the following manually on VMware
set-up and it worked :
1. Create 5 volumes of random sizes
2. Create VM using centos 5.3 template
3. Attach 5 volumes
4. Detach a few volumes
5. Re-attach volumes
6. Attach and then detach ISO, check contents of ISO for sanity.
> [Automation] Attach volume test case failing with error "Invalid
> configuration for device '0'"
> --
>
> Key: CLOUDSTACK-7422
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7422
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.5.0
> Environment: Vmware 5.0
> build 4.5
>Reporter: Rayees Namathponnan
>Assignee: Amogh Vasekar
>Priority: Critical
> Fix For: 4.5.0
>
>
> Steps to reproduce the defect
> Run the test
> integration.component.test_volumes.TestAttachVolumeISO.test_01_volume_iso_attach
> This test case performing below steps
> 678 # Validate the following
> 679 # 1. Create and attach 5 data volumes to VM
> 680 # 2. Create an ISO. Attach it to VM instance
> 681 # 3. Verify that attach ISO is successful
> Here attach volume fails with below error
> {noformat}
> a5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAZh0ABRWb2x1
> bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAACnNxAH4ABgHJ
> , cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 90928106758026, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: Sat Aug 23 14:45:42 PDT 2014}, job
> origin:3043
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> TestDiskServ to VM TestVM-24cfe95b-8976-48af-ba42-459b37cfb89c; AttachV
> olumeCommand failed due to Exception: java.lang.RuntimeException
> Message: Invalid configuration for device '0'.
> at
> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2248)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1216)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2615)
> at sun.reflect.GeneratedMethodAccessor855.invoke(Unknown Source)
> 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.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2654)
> at sun.reflect.GeneratedMethodAccessor568.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.$Proxy184.handleVmWorkJob(Unknown Source)
> 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.runWithCont
[jira] [Commented] (CLOUDSTACK-6236) Negative ref_cnt of template(snapshot/volume)_store_ref results in out-of-range error in Mysql
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120947#comment-14120947
]
ASF subversion and git services commented on CLOUDSTACK-6236:
-
Commit e454acc2c02a549dd5e05091aa11cca14cbf6c7e in cloudstack's branch
refs/heads/4.4 from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e454acc ]
CLOUDSTACK-6236:fix a copy-and-paste error for decrRefCnt in
VolumeDataStoreVO.
> Negative ref_cnt of template(snapshot/volume)_store_ref results in
> out-of-range error in Mysql
> --
>
> Key: CLOUDSTACK-6236
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6236
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: Min Chen
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.4.0
>
>
> Steps:
> 1. Deploy CS with ESXi5.5 and NFS secondary storage.
> 2. Create a VM and take the snapshot of root volume.
> 3. Create a template from snapshot.
> 4. Migrate the secondary NFS to S3.
> 5. Download the template created from snapshot (step3). Now the template will
> be in S3.
> 6. Tried to delete the template now.
> Observation:
> Template got deleted from S3 but observing an exception while deleting it
> from ImageCache.
> 2014-03-04 16:19:58,227 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-14:null) SeqA 2-9302: Sending Seq 2-9302: { Ans: ,
> MgmtId: 6758231703598, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2014-03-04 16:19:58,255 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-51:Job-47) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.DeleteTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
> com.mysql.jdbc.JDBC4PreparedStatement@5cb563d: SELECT template_store_ref.id,
> template_store_ref.store_id, template_store_ref.template_id,
> template_store_ref.store_role, template_store_ref.created,
> template_store_ref.last_updated, template_store_ref.download_pct,
> template_store_ref.size, template_store_ref.physical_size,
> template_store_ref.download_state, template_store_ref.local_path,
> template_store_ref.error_str, template_store_ref.job_id,
> template_store_ref.install_path, template_store_ref.url,
> template_store_ref.is_copy, template_store_ref.destroyed,
> template_store_ref.update_count, template_store_ref.updated,
> template_store_ref.state, template_store_ref.ref_cnt FROM template_store_ref
> WHERE template_store_ref.template_id = 202 AND template_store_ref.store_role
> = 'ImageCache'
> at
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:421)
> at
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:356)
> at com.cloud.utils.db.GenericDaoBase.search(GenericDaoBase.java:340)
> at com.cloud.utils.db.GenericDaoBase.search(GenericDaoBase.java:1243)
> at
> org.apache.cloudstack.storage.image.db.TemplateDataStoreDaoImpl.listOnCache(TemplateDataStoreDaoImpl.java:365)
> 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:616)
> 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:33)
> 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 $Proxy108.listOnCache(Unknown Source)
> at
> org.apache.cloudstack.storage.image.TemplateDataFactoryImpl.listTemplateOnCache(TemplateDataFactoryImpl.java:147)
> at
> com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:355)
> at
> com.cloud.template.TemplateManagerImpl.deleteTemplate(TemplateManagerImpl.java:1097)
>
[jira] [Updated] (CLOUDSTACK-7483) UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only a
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7483: - Attachment: 2_when_OSType_is_not_Windows.PNG 1_when_OSType_is_Windows.PNG > UI > instance page, template page > hide "Original XS Version is 6.1+" field > when OS Type is not Windows since property > jsonObj.details.hypervisortoolsversion only applies to Windows. > --- > > Key: CLOUDSTACK-7483 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7483 > 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_when_OSType_is_Windows.PNG, > 2_when_OSType_is_not_Windows.PNG > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7483) UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120705#comment-14120705 ] ASF subversion and git services commented on CLOUDSTACK-7483: - Commit 659eafffe1c59ed8f4c4eb3e157fbdcdd7674879 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=659eaff ] CLOUDSTACK-7483: UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only applies to Windows - case sensitive when comparing OS Type. > UI > instance page, template page > hide "Original XS Version is 6.1+" field > when OS Type is not Windows since property > jsonObj.details.hypervisortoolsversion only applies to Windows. > --- > > Key: CLOUDSTACK-7483 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7483 > 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-5664) XEN patch/hotfix certification - after XS 6.0.2 XS602E030 patch installation VMs deployed before patch installation does not acquire new rules set
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120675#comment-14120675 ] Anthony Xu commented on CLOUDSTACK-5664: it is invalid > XEN patch/hotfix certification - after XS 6.0.2 XS602E030 patch installation > VMs deployed before patch installation does not acquire new rules set > --- > > Key: CLOUDSTACK-5664 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5664 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: angeline shen >Assignee: Anthony Xu >Priority: Critical > Fix For: 4.5.0 > > Attachments: 513SMlog, 513xensource.log, 513xenstored-access.log, > 513xenstored-access.log.1, 513xenstored-access.log.2, > 513xenstored-access.log.3, 514SMlog, 514xensource.log, > 514xenstored-access.log, management-server.log.gz > > > XEN hotfix installation procedure > 1. Hosts master slave installed with > XS 6.0.2 base + Hotfix XS602E001 to XS602E029 + CSPs > 2. Basic zone with cluster of above master & slave hosts > security group default with NO security rules > Deploy two VMs > 3. MS: master host put to maintenance mode - VMs migrate to slave host > 4. MS: unmanage cluster > 5. master host: install hotfix XS602E030 + CSP , reboot master > 6. MS: master host cancel maintenance mode > 7. MS: manage cluster > 8. MS: slave host put to maintenance mode - VMs migrate to master host > 9. MS: Add security rules: ingress TCP 1 - 80900.0.0.0/0 > ingress ICMP -1 -10.0.0.0/0 > egress TCP1 - 80900.0.0.0/0 > egress ICMP -1 -10.0.0.0/0 > 10. MS: slave host cancel maintenance mode > 11. stop/start SSVMVR > 12. Deploy two more VMs > Test result: > VMs deployed after HotFix XS602E030 installation correctly acquired 4 new > ingress + egress rules > VMs deployed before HotFix XS602E030 installation did not acquire 4 new > ingress & egress rules - error > Also there are errors encountered when attempt to apply these rules to old > VMs: > 2013-12-27 12:14:37,294 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-21:job-21 = [ 94abc9ec-19fc-4d8b-916c-531e161c8525 ]) Done > executing > org.apache.cloudstack.api.command.user.securitygroup.AuthorizeSecurityGroupIngressCmd > for job-21 = [ 94abc9ec-19fc-4d8b-916c-531e161c8525 ] > 2013-12-27 12:14:37,471 WARN [xen.resource.CitrixResourceBase] > (DirectAgent-204:null) callHostPlugin failed for cmd: network_rules with args > seqno: 8, vmIP: 10.223.51.30, deflated: true, secIps: 0:, vmID: 5, vmMAC: > 06:37:9c:00:00:10, vmName: i-2-5-VM, rules: > eJzztCpJLrAytLIwsDSwMtADQ30DHT/XiBAFAGbLBq8=, signature: > 8683b82a9b77d8ece0dd135304fbdb8a, due to There was a failure communicating > with the plugin. > 2013-12-27 12:14:37,472 WARN [agent.manager.DirectAgentAttache] > (DirectAgent-204:null) Seq 1-1198391355: Exception Caught while executing > command > com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for > cmd: network_rules with args seqno: 8, vmIP: 10.223.51.30, deflated: true, > secIps: 0:, vmID: 5, vmMAC: 06:37:9c:00:00:10, vmName: i-2-5-VM, rules: > eJzztCpJLrAytLIwsDSwMtADQ30DHT/XiBAFAGbLBq8=, signature: > 8683b82a9b77d8ece0dd135304fbdb8a, due to There was a failure communicating > with the plugin. > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:4181) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:5775) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:565) > at > com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > 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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java
[jira] [Resolved] (CLOUDSTACK-5664) XEN patch/hotfix certification - after XS 6.0.2 XS602E030 patch installation VMs deployed before patch installation does not acquire new rules set
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu resolved CLOUDSTACK-5664. Resolution: Fixed We don't have CSP for XS602E030, so it won't work for basic zone > XEN patch/hotfix certification - after XS 6.0.2 XS602E030 patch installation > VMs deployed before patch installation does not acquire new rules set > --- > > Key: CLOUDSTACK-5664 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5664 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: angeline shen >Assignee: Anthony Xu >Priority: Critical > Fix For: 4.5.0 > > Attachments: 513SMlog, 513xensource.log, 513xenstored-access.log, > 513xenstored-access.log.1, 513xenstored-access.log.2, > 513xenstored-access.log.3, 514SMlog, 514xensource.log, > 514xenstored-access.log, management-server.log.gz > > > XEN hotfix installation procedure > 1. Hosts master slave installed with > XS 6.0.2 base + Hotfix XS602E001 to XS602E029 + CSPs > 2. Basic zone with cluster of above master & slave hosts > security group default with NO security rules > Deploy two VMs > 3. MS: master host put to maintenance mode - VMs migrate to slave host > 4. MS: unmanage cluster > 5. master host: install hotfix XS602E030 + CSP , reboot master > 6. MS: master host cancel maintenance mode > 7. MS: manage cluster > 8. MS: slave host put to maintenance mode - VMs migrate to master host > 9. MS: Add security rules: ingress TCP 1 - 80900.0.0.0/0 > ingress ICMP -1 -10.0.0.0/0 > egress TCP1 - 80900.0.0.0/0 > egress ICMP -1 -10.0.0.0/0 > 10. MS: slave host cancel maintenance mode > 11. stop/start SSVMVR > 12. Deploy two more VMs > Test result: > VMs deployed after HotFix XS602E030 installation correctly acquired 4 new > ingress + egress rules > VMs deployed before HotFix XS602E030 installation did not acquire 4 new > ingress & egress rules - error > Also there are errors encountered when attempt to apply these rules to old > VMs: > 2013-12-27 12:14:37,294 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-21:job-21 = [ 94abc9ec-19fc-4d8b-916c-531e161c8525 ]) Done > executing > org.apache.cloudstack.api.command.user.securitygroup.AuthorizeSecurityGroupIngressCmd > for job-21 = [ 94abc9ec-19fc-4d8b-916c-531e161c8525 ] > 2013-12-27 12:14:37,471 WARN [xen.resource.CitrixResourceBase] > (DirectAgent-204:null) callHostPlugin failed for cmd: network_rules with args > seqno: 8, vmIP: 10.223.51.30, deflated: true, secIps: 0:, vmID: 5, vmMAC: > 06:37:9c:00:00:10, vmName: i-2-5-VM, rules: > eJzztCpJLrAytLIwsDSwMtADQ30DHT/XiBAFAGbLBq8=, signature: > 8683b82a9b77d8ece0dd135304fbdb8a, due to There was a failure communicating > with the plugin. > 2013-12-27 12:14:37,472 WARN [agent.manager.DirectAgentAttache] > (DirectAgent-204:null) Seq 1-1198391355: Exception Caught while executing > command > com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for > cmd: network_rules with args seqno: 8, vmIP: 10.223.51.30, deflated: true, > secIps: 0:, vmID: 5, vmMAC: 06:37:9c:00:00:10, vmName: i-2-5-VM, rules: > eJzztCpJLrAytLIwsDSwMtADQ30DHT/XiBAFAGbLBq8=, signature: > 8683b82a9b77d8ece0dd135304fbdb8a, due to There was a failure communicating > with the plugin. > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:4181) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:5775) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:565) > at > com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > 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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[jira] [Updated] (CLOUDSTACK-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer ve
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7480: - Attachment: 2_after_UI_change.PNG 1_before_UI_change.PNG > UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original > XS Version is 6.1+" because what the field really presents is the original > XenServer version when a VM is initially created. > -- > > Key: CLOUDSTACK-7480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 > 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.PNG, 2_after_UI_change.PNG > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer ve
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7480: - Attachment: (was: 2_after_UI_change.PNG) > UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original > XS Version is 6.1+" because what the field really presents is the original > XenServer version when a VM is initially created. > -- > > Key: CLOUDSTACK-7480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 > 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-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer ve
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7480: - Attachment: (was: 1_before_UI_change.PNG) > UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original > XS Version is 6.1+" because what the field really presents is the original > XenServer version when a VM is initially created. > -- > > Key: CLOUDSTACK-7480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 > 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-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer ve
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7480: - Attachment: 2_after_UI_change.PNG 1_before_UI_change.PNG > UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original > XS Version is 6.1+" because what the field really presents is the original > XenServer version when a VM is initially created. > -- > > Key: CLOUDSTACK-7480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 > 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.PNG, 2_after_UI_change.PNG > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7483) UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-7483. -- Resolution: Fixed > UI > instance page, template page > hide "Original XS Version is 6.1+" field > when OS Type is not Windows since property > jsonObj.details.hypervisortoolsversion only applies to Windows. > --- > > Key: CLOUDSTACK-7483 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7483 > 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-7483) UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only ap
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7483. > UI > instance page, template page > hide "Original XS Version is 6.1+" field > when OS Type is not Windows since property > jsonObj.details.hypervisortoolsversion only applies to Windows. > --- > > Key: CLOUDSTACK-7483 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7483 > 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-7483) UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120570#comment-14120570 ] ASF subversion and git services commented on CLOUDSTACK-7483: - Commit 801a98617c4fbec46c9fab65a9f05608f5574991 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=801a986 ] CLOUDSTACK-7483: UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only applies to Windows. > UI > instance page, template page > hide "Original XS Version is 6.1+" field > when OS Type is not Windows since property > jsonObj.details.hypervisortoolsversion only applies to Windows. > --- > > Key: CLOUDSTACK-7483 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7483 > 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] [Created] (CLOUDSTACK-7483) UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only a
Jessica Wang created CLOUDSTACK-7483: Summary: UI > instance page, template page > hide "Original XS Version is 6.1+" field when OS Type is not Windows since property jsonObj.details.hypervisortoolsversion only applies to Windows. Key: CLOUDSTACK-7483 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7483 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] [Created] (CLOUDSTACK-7482) Ajax calls in mgmt UI causing log pollution
Kedron Touvell created CLOUDSTACK-7482:
--
Summary: Ajax calls in mgmt UI causing log pollution
Key: CLOUDSTACK-7482
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7482
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Affects Versions: 4.4.0
Reporter: Kedron Touvell
Priority: Minor
Many of the ajax calls in the mgmt UI are specifying a listAll parameter,
despite the fact that the underlying API call does not support listAll. This
is causing a decent amount of log pollution:
{quote}
2014-09-03 10:54:21,475 WARN [c.c.a.d.ParamGenericValidationWorker]
(catalina-exec-8:ctx-aefb6d5e ctx-08b63c18) Received unknown parameters for
command listImageStores. Unknown parameters : listall type
{quote}
These parameters are set in {{ui/scripts/system.js}}, for example:
{noformat}
systemVmCount: function (data) {
$.ajax({
url: createURL('listSystemVms'),
data: {
listAll: true,
{noformat}
Here's the list of API calls that I see generating warnings:
* listClusters
* listHosts
* listImageStores
* listNetworkOfferings
* listPods
* listRegions
* listServiceOfferings
* listStoragePools
* listSystemVms
* listZones
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer ver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7480. > UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original > XS Version is 6.1+" because what the field really presents is the original > XenServer version when a VM is initially created. > -- > > Key: CLOUDSTACK-7480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 > 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-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer v
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-7480. -- Resolution: Fixed > UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original > XS Version is 6.1+" because what the field really presents is the original > XenServer version when a VM is initially created. > -- > > Key: CLOUDSTACK-7480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 > 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] [Created] (CLOUDSTACK-7481) Assertion/exception in listVolumes call from UI with assert enabled
Nitin Mehta created CLOUDSTACK-7481: --- Summary: Assertion/exception in listVolumes call from UI with assert enabled Key: CLOUDSTACK-7481 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7481 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.5.0 A quick look at searchForVolumesInternal() indicated some inconsistency in the use of entity().isDisplayVolume() property – used twice as “display” and “displayVolume” in search criteria. And then exception/assert happens while setting the property. 2014-09-02 14:49:25.257:WARN::Error for /client/api java.lang.AssertionError: Couldn't find displayVolume at com.cloud.utils.db.SearchCriteria.setParameters(SearchCriteria.java:161) at com.cloud.api.query.QueryManagerImpl.searchForVolumesInternal(QueryManagerImpl.java:1764) at com.cloud.api.query.QueryManagerImpl.searchForVolumes(QueryManagerImpl.java:1650) at org.apache.cloudstack.api.command.user.volume.ListVolumesCmd.execute(ListVolumesCmd.java:152) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:273) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:117) 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:114) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:76) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120232#comment-14120232 ] ASF subversion and git services commented on CLOUDSTACK-7480: - Commit 5e55b6b478c9a919976e399eb9bf85cfd91c118b in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5e55b6b ] CLOUDSTACK-7480: UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer version when a VM is initially created. > UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original > XS Version is 6.1+" because what the field really presents is the original > XenServer version when a VM is initially created. > -- > > Key: CLOUDSTACK-7480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 > 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] [Created] (CLOUDSTACK-7480) UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer ve
Jessica Wang created CLOUDSTACK-7480: Summary: UI > instance page > change "XenServer Tools Version 6.1+ field" to "Original XS Version is 6.1+" because what the field really presents is the original XenServer version when a VM is initially created. Key: CLOUDSTACK-7480 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7480 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-6236) Negative ref_cnt of template(snapshot/volume)_store_ref results in out-of-range error in Mysql
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120149#comment-14120149
]
ASF subversion and git services commented on CLOUDSTACK-6236:
-
Commit 672bb353be2f159966f351ab2de914b433a934f9 in cloudstack's branch
refs/heads/master from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=672bb35 ]
CLOUDSTACK-6236:fix a copy-and-paste error for decrRefCnt in
VolumeDataStoreVO.
> Negative ref_cnt of template(snapshot/volume)_store_ref results in
> out-of-range error in Mysql
> --
>
> Key: CLOUDSTACK-6236
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6236
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: Min Chen
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.4.0
>
>
> Steps:
> 1. Deploy CS with ESXi5.5 and NFS secondary storage.
> 2. Create a VM and take the snapshot of root volume.
> 3. Create a template from snapshot.
> 4. Migrate the secondary NFS to S3.
> 5. Download the template created from snapshot (step3). Now the template will
> be in S3.
> 6. Tried to delete the template now.
> Observation:
> Template got deleted from S3 but observing an exception while deleting it
> from ImageCache.
> 2014-03-04 16:19:58,227 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-14:null) SeqA 2-9302: Sending Seq 2-9302: { Ans: ,
> MgmtId: 6758231703598, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2014-03-04 16:19:58,255 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-51:Job-47) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.DeleteTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
> com.mysql.jdbc.JDBC4PreparedStatement@5cb563d: SELECT template_store_ref.id,
> template_store_ref.store_id, template_store_ref.template_id,
> template_store_ref.store_role, template_store_ref.created,
> template_store_ref.last_updated, template_store_ref.download_pct,
> template_store_ref.size, template_store_ref.physical_size,
> template_store_ref.download_state, template_store_ref.local_path,
> template_store_ref.error_str, template_store_ref.job_id,
> template_store_ref.install_path, template_store_ref.url,
> template_store_ref.is_copy, template_store_ref.destroyed,
> template_store_ref.update_count, template_store_ref.updated,
> template_store_ref.state, template_store_ref.ref_cnt FROM template_store_ref
> WHERE template_store_ref.template_id = 202 AND template_store_ref.store_role
> = 'ImageCache'
> at
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:421)
> at
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:356)
> at com.cloud.utils.db.GenericDaoBase.search(GenericDaoBase.java:340)
> at com.cloud.utils.db.GenericDaoBase.search(GenericDaoBase.java:1243)
> at
> org.apache.cloudstack.storage.image.db.TemplateDataStoreDaoImpl.listOnCache(TemplateDataStoreDaoImpl.java:365)
> 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:616)
> 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:33)
> 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 $Proxy108.listOnCache(Unknown Source)
> at
> org.apache.cloudstack.storage.image.TemplateDataFactoryImpl.listTemplateOnCache(TemplateDataFactoryImpl.java:147)
> at
> com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:355)
> at
> com.cloud.template.TemplateManagerImpl.deleteTemplate(TemplateManagerImpl.java:1097)
[jira] [Updated] (CLOUDSTACK-7442) [Automation] Fix the script "test_project_resources.py" - No permissions updated, please verify the account names
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye updated CLOUDSTACK-7442:
---
Status: Reviewable (was: In Progress)
> [Automation] Fix the script "test_project_resources.py" - No permissions
> updated, please verify the account names
> -
>
> Key: CLOUDSTACK-7442
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7442
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
>Affects Versions: 4.5.0
>Reporter: Chandan Purushothama
>Assignee: Gaurav Aradhye
>Priority: Critical
> Fix For: 4.5.0
>
>
> The following script failed during regression run:
> integration.component.test_project_resources.TestTemplates.test_05_use_private_template_in_project
>
> *Error Message*
> Exception occured: Execute cmd: updatetemplatepermissions failed, due to:
> errorCode: 431, errorText:Unable to grant a launch permission to account
> PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75,
> account not found. No permissions updated, please verify the account names
> and retry. Logs available at
> http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogs&id=804076&phase=Parallel&test=project_resources
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 332, in run
> testMethod()
> File
> "/root/cloudstack/test/integration/component/test_project_resources.py", line
> 768, in test_05_use_private_template_in_project
> self.fail("Exception occured: %s" % e)
> File "/usr/lib/python2.7/unittest/case.py", line 413, in fail
> raise self.failureException(msg)
> 'Exception occured: Execute cmd: updatetemplatepermissions failed, due to:
> errorCode: 431, errorText:Unable to grant a launch permission to account
> PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75,
> account not found. No permissions updated, please verify the account names
> and retry.\n
> Logs available at
> http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogs&id=804076&phase=Parallel&test=project_resources
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7284) Holder for KVM regression test script issues
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye closed CLOUDSTACK-7284. -- Resolution: Fixed Closing this bug as issues are tracked through individual bugs and this holder bug is no longer needed. > Holder for KVM regression test script issues > > > Key: CLOUDSTACK-7284 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7284 > 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: KVM >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > This bug is holder for all test script issues identified in KVM regression > run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7116) unable to add KVM host to MS with error java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : Unsupported major.minor version 51.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7116. - Resolution: Not a Problem Not seeing this anymore... > unable to add KVM host to MS with error > java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : > Unsupported major.minor version 51.0 > - > > Key: CLOUDSTACK-7116 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7116 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.5.0 >Reporter: shweta agarwal >Assignee: Damodar Reddy T >Priority: Blocker > Fix For: 4.5.0 > > Attachments: cloudstack-agent.err, management-server.log.tar.gz > > > Repro steps: > 1. Create a KVM host on rhel 6.3 > As I used following build > http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/master/CloudPlatform-4.5.0-57-rhel6.3.tar.gz > so i need to install jsvc outside of cloudstack for which I have done the > following step: > yum install java-gcj-compat > rpm -Uvh > ftp://rpmfind.net/linux/centos/6.5/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > and then I installed agent > Once agent installation is complete I tried to add this KVM host to MS > and host addition failed with MS logs showing > 2014-07-16 06:09:19,082 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] > (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Timeout, to wait for the host > connecting to mgt svr, assuming it is failed > 2014-07-16 06:09:19,083 WARN [c.c.r.ResourceManagerImpl] > (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Unable to find the server > resources at http://10.147.40.23 > 2014-07-16 06:09:19,084 INFO [c.c.u.e.CSExceptionErrorCode] > (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Could not find exception: > com.cloud.exception.DiscoveryException in error code list for exceptions > 2014-07-16 06:09:19,084 WARN [o.a.c.a.c.a.h.AddHostCmd] > (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Exception: > com.cloud.exception.DiscoveryException: Unable to add the host > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586) > 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 $Proxy148.discoverHosts(Unknown Source) > at > org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517) > at > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) > 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115) > at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > or
[jira] [Created] (CLOUDSTACK-7479) [LXC]need a check that LXC VM's root disk only goes to nfs or local storage even if ceph storage is also there
shweta agarwal created CLOUDSTACK-7479: -- Summary: [LXC]need a check that LXC VM's root disk only goes to nfs or local storage even if ceph storage is also there Key: CLOUDSTACK-7479 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7479 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Kishan Kavala Priority: Critical Fix For: 4.5.0 Repro steps: 1. Create a LXC zone with two primary storage one NFS and the other RBD ceph 2. Create a VM with both root and data disk. Bug: VM creation fails as it tries to create root disk in Ceph. so we need to have certain type of check which force to create root disk only on nfs and local . At the same time we also need to have a check which force to create data disk only on LXC . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7378) [rhel7] usage server installation is failing with java7 dependency
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7378. - Resolution: Fixed > [rhel7] usage server installation is failing with java7 dependency > -- > > Key: CLOUDSTACK-7378 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7378 > 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: shweta agarwal >Assignee: Damodar Reddy T >Priority: Blocker > Fix For: 4.5.0 > > > usage server installation is failing with java7 dependency on rhel 7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6694) [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic primary and secondary IPS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Turner updated CLOUDSTACK-6694: --- Assignee: Jessica Wang > [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic > primary and secondary IPS. > --- > > Key: CLOUDSTACK-6694 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6694 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0 >Reporter: manasaveloori >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.4.0 > > Attachments: InternalLB.jpg > > Original Estimate: 72h > Time Spent: 24h > Remaining Estimate: 48h > > 1. Create VPC. > 2. Create a tier network using the network offering having internal LB > support. > 3. Deploy VMs under this network.Acquire secondary Ips. > 4.Goto VPC ->configure->tier-> internal LB.configure internal LB. > 5. Assign VM to LB rule. > Observation: > There is no listing of primary and secondary IPs for the VM while assigning > it internal LB rule. > attaching the screen shot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7468) NetScaler SSL Termination does not handle Projects as expected
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119895#comment-14119895 ] ASF subversion and git services commented on CLOUDSTACK-7468: - Commit 5d11385c31ed43d5424f161533eeb2c3d61b7726 in cloudstack's branch refs/heads/CLOUDSTACK-7468 from [~wstevens] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5d11385 ] CLOUDSTACK-7468: Fixed the NetScaler SSL Termination behavior with Projects Signed-off-by: Will Stevens > NetScaler SSL Termination does not handle Projects as expected > -- > > Key: CLOUDSTACK-7468 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7468 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Affects Versions: 4.5.0, 4.4.1 >Reporter: Will Stevens >Assignee: Will Stevens > Attachments: > CLOUDSTACK-7468-Fixed-NetScaler-SSL-Termination-for-Projects.patch > > > Currently the 'uploadSslCert' api call does not take any details about who > should own the SSL Cert. It basically assigns the cert to the caller and > thats it. > This breaks the expected behavior for projects and also does not allow for an > admin to upload certificates on behalf of one of their users. > This fix should not adjust the database entities at all, but should allow the > API calls to handle the additional cases. > The following changes should be made: > - If 'uploadSslCert' is called without any account details, it should behave > how it does now and assign the cert to the caller. > - If 'uploadSslCert' includes option 'account' and 'domainId' fields, the > uploaded cert will be applied to that account. > - If 'uploadSslCert' includes a 'projectId', then the cert is applied to that > project. > - The 'listSslCerts' api should also take an optional 'projectid' field to > list the ssl certs associated with that project. > - The api response for both 'uploadSslCert' and 'listSslCerts' should be > updated to include additional information about the account or project as > well as the domain in which the cert is assigned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7478) [LXC] VM creation should fail when creating LXC VM with data disk and w/o having ceph as primary storage
shweta agarwal created CLOUDSTACK-7478: -- Summary: [LXC] VM creation should fail when creating LXC VM with data disk and w/o having ceph as primary storage Key: CLOUDSTACK-7478 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7478 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Kishan Kavala Priority: Critical Fix For: 4.5.0 Attachments: agent.log.tar.gz, ms.tar.gz Repro steps: 1. Create a LXC zone with only nfs 2. Create a VM with data disk Bug: VM creations passes without giving error that data disk needs ceph storage Even usage events for data disk is also generated. VM shows no data disk with it dumxml of VM shows: i-2-21-VM 7da917bf-dd91-4185-92ce-a419b6a7e396 CentOS 6.3 (64-bit) 524288 524288 1 500 /machine exe /sbin/init destroy restart destroy /usr/libexec/libvirt_lxc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7316) hitting java.lang.reflect.InvocationTargetException while starting usage server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119851#comment-14119851 ] Damodar Reddy T commented on CLOUDSTACK-7316: - yeah this change is introduced recently. Earlier we were reading it from the hard coded path "/etc/cloudstack/management/key" but now we are trying to load it from the class path. This should be an issue for upgrades as well. As I have added this in %post usage section it should take care of upgrades as well. Anyhow I will test it before closing this... > hitting java.lang.reflect.InvocationTargetException while starting usage > server > --- > > Key: CLOUDSTACK-7316 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7316 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.5.0 >Reporter: shweta agarwal >Assignee: Damodar Reddy T >Priority: Blocker > Fix For: 4.5.0 > > Attachments: usage.tar.gz > > > Repro steps: > Install MS and usage server > Start MS and usage server > Bug: > Usage server will stop after starting > usage log shows : > java.lang.reflect.InvocationTargetException > 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.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'vmDiskUsageParser': Injection of autowired > dependencies failed; nested exception is > org.springframework.beans.factory.BeanCreationException: Could not autowire > field: private com.cloud.usage.dao.UsageDao > com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'usageDaoImpl' defined in URL > [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4.5.0-SNAPSHOT.jar!/com/cloud/usage/dao/UsageDaoImpl.class]: > BeanPostProcessor before instantiation of bean failed; nested exception is > net.sf.cglib.core.CodeGenerationException: > java.lang.ExceptionInInitializerError-->null > at > org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:288) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1116) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) > at > org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139) > at > org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83) > at com.cloud.usage.UsageServer.start(UsageServer.java:57) > ... 5 more > Caused by: org.springframework.beans.factory.BeanCreationException: Could not > autowire field: private com.cloud.usage.dao.UsageDao > com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'usageDaoImpl' defined in URL > [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4
[jira] [Updated] (CLOUDSTACK-7473) [LXC]putting host into maintenance is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shweta agarwal updated CLOUDSTACK-7473:
---
Assignee: Kishan Kavala
> [LXC]putting host into maintenance is failing
> --
>
> Key: CLOUDSTACK-7473
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7473
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
>Affects Versions: 4.5.0
>Reporter: shweta agarwal
>Assignee: Kishan Kavala
>Priority: Blocker
> Attachments: agent.log.tar.gz, ms.tar.gz
>
>
> Repro stesp:
> 1. create a zone with a LXC cluster having 2 host
> 2. create few LXC vms
> 3. Put one host into maintenance which has some VM running
> Bug:
> Putting host into maintenance will never pass. host will remain in preparing
> for maintenance stage and then goes to disconnect state.
> Agent log shows :
> 2014-09-02 19:08:12,663 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-1:null) Failed to execute while migrating domain:
> org.libvirt.LibvirtException: this function is not supported by the
> connection driver: virDomainMigrate2
> 2014-09-02 19:08:12,665 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-1:null) Seq 1-3693233169420517550: { Ans: , MgmtId:
> 233845178472723, via: 1, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
> this function is not supported by the connection driver:
> virDomainMigrate2","wait":0}}] }
> 2014-09-02 19:08:13,004 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-4:null) Request:Seq 1-3693233169420517551: { Cmd ,
> MgmtId: 233845178472723, via: 1, Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.MigrateCommand":{"vmName":"i-2-7-VM","destIp":"10.147.28.49","hostGuid":"2b2a1b9f-7582-378f-b54f-1dbb8f69e239-LibvirtComputingResource","isWindows":false,"vmTO":{"id":7,"name":"i-2-7-VM","type":"User","cpus":1,"minSpeed":128,"maxSpeed":128,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Red
> Hat Enterprise Linux
> 7.0","platformEmulator":"Other","bootArgs":"","enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"QY0cKnTfogzaS49R283f1g==","params":{"Message.ReservedCapacityFreed.Flag":"false"},"uuid":"caf07a92-9f6c-49df-a7e4-27289e715448","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"981fe152-6ee5--ae41-474736c881cf","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"dfa2ec3c-d133-3284-8583-0a0845aa4424","id":1,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/shweta/goleta.lxc.primary","port":2049,"url":"NetworkFilesystem://10.147.28.7/export/home/shweta/goleta.lxc.primary/?ROLE=Primary&STOREUUID=dfa2ec3c-d133-3284-8583-0a0845aa4424"}},"name":"ROOT-7","size":647321600,"path":"981fe152-6ee5--ae41-474736c881cf","volumeId":7,"vmName":"i-2-7-VM","accountId":2,"format":"DIR","provisioningType":"THIN","id":7,"deviceId":0,"hypervisorType":"LXC"}},"diskSeq":0,"path":"981fe152-6ee5--ae41-474736c881cf","type":"ROOT","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"647321600"}},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"pxeDisable":false,"nicUuid":"95826449-4163-46b8-91b7-8bf94f19ab8e","uuid":"d4db3da8-4e6c-4e29-b6bb-a6613d55fa2f","ip":"10.147.30.166","netmask":"255.255.255.0","gateway":"10.147.30.1","mac":"06:54:96:00:00:07","dns1":"10.140.50.6","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://30","isolationUri":"vlan://30","isSecurityGroupEnabled":true}]},"executeInSequence":false,"wait":0}}]
> }
> 2014-09-02 19:08:13,005 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-4:null) Processing command:
> com.cloud.agent.api.MigrateCommand
> 2014-09-02 19:08:13,006 DEBUG [kvm.resource.LibvirtConnection]
> (agentRequest-Handler-4:null) can't find connection: KVM, for vm: i-2-7-VM,
> continue
> 2014-09-02 19:08:13,018 INFO [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-4:null) Live migration of instance i-2-7-VM initiated
> 2014-09-02 19:08:13,103 INFO [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-5:null) Waiting for migration of s-1-VM to complete,
> waited 1000ms
> 2014-09-02 19:08:13,118 INFO [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-4:null) Migration thread for i-2-7-VM is done
> 2014-09-02 19:08:13,119 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-4:null) Failed to execute while migrating domain:
> org.libvirt.Lib
[jira] [Updated] (CLOUDSTACK-7378) [rhel7] usage server installation is failing with java7 dependency
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7378: Status: Reviewable (was: In Progress) > [rhel7] usage server installation is failing with java7 dependency > -- > > Key: CLOUDSTACK-7378 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7378 > 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: shweta agarwal >Assignee: Damodar Reddy T >Priority: Blocker > Fix For: 4.5.0 > > > usage server installation is failing with java7 dependency on rhel 7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7477) [LXC] the workaround for cpu,cpuacct are co-mounted problem of libvirt is removed when agent shutsdown and restarted
shweta agarwal created CLOUDSTACK-7477: -- Summary: [LXC] the workaround for cpu,cpuacct are co-mounted problem of libvirt is removed when agent shutsdown and restarted Key: CLOUDSTACK-7477 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7477 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Kishan Kavala Priority: Blocker Repro steps: 1. Create a LXC setup 2. create few vms 3. shut down host LXC agent 4. Once Agent states become disconnected start host gain Bug Note all the mounts in host mount proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel) devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=3981488k,nr_inodes=995372,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,seclabel,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) configfs on /sys/kernel/config type configfs (rw,relatime) /dev/mapper/rhel_rack3pod1host49-root on / type xfs (rw,relatime,seclabel,attr2,inode64,noquota) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel) debugfs on /sys/kernel/debug type debugfs (rw,relatime) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) sunrpc on /proc/fs/nfsd type nfsd (rw,relatime) /dev/mapper/rhel_rack3pod1host49-home on /home type xfs (rw,relatime,seclabel,attr2,inode64,noquota) /dev/sda1 on /boot type xfs (rw,relatime,seclabel,attr2,inode64,noquota) 10.147.28.7:/export/home/shweta/goleta.lxc.primary on /mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424 type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.147.28.7,mountvers=3,mountport=47246,mountproto=udp,local_lock=none,addr=10.147.28.7) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) it again contains all those cgroups mount point which we deleted earlier as a part of LXC agent instalation . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-7291) LXC: Mgmt server/agent keeps killing systemvms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119779#comment-14119779 ] Alex Brett edited comment on CLOUDSTACK-7291 at 9/3/14 11:47 AM: - Upping this to blocker as I'm also seeing this on rhel7 and it is preventing me starting VMs on LXC was (Author: alexbre): Upping this to blocker as I'm also seeing it and it is preventing me starting VMs on LXC > LXC: Mgmt server/agent keeps killing systemvms > -- > > Key: CLOUDSTACK-7291 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0, 4.3.1 >Reporter: Rohit Yadav >Assignee: Kishan Kavala >Priority: Blocker > Fix For: Future, 4.5.0 > > > Followed installation and setup docs of 4.3, was unable to get LXC to work on > Ubuntu 14.04/trusty. The systemvms kept coming up and result from > ssvm_check.sh was good and it was able to reach mgmt server /host, even then > mgmt server complained that it was unable to contact agent on the systemvm > (ping), while the agent would gracefully shutdown the systemvm (by killing > them). > Relevant log: > 2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode] > (secstorage-1:ctx-fc57ef43) Could not find exception: > com.cloud.exception.OperationTimedoutException in error code list for > exceptions > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache] > (consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling. > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679) > Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host > id = 1, name = bluebox1.bhaisaab.org] > 2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl] > (secstorage-1:ctx-fc57ef43) Scheduled > HAWork[12-CheckStop-2-Starting-Scheduled] > 2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage > vm > com.cloud.exception.AgentUnavailableException: Resource [Host:1] is > unreachable: Host 1: Unable to start s-2-VM > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > >---at > >com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) > ... > ... > ... > Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 > to Host 1 timed out after 3600 > >---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439) > > > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394) > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989) > >---... 24 more > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7464) Management Server setup doesn't proceed to completion - org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7464. - Resolution: Invalid Resolving this issue as the culprit commit that caused this has been reverted by Hugo. > Management Server setup doesn't proceed to completion - > org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException > - > > Key: CLOUDSTACK-7464 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7464 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: Pavan Kumar Bandarupally >Assignee: Damodar Reddy T >Priority: Blocker > Fix For: 4.5.0 > > Attachments: catalina.out, localhost.2014-09-02.log, > management-server.log, setupManagement.log > > > After installation of management server, and database schema update, the > setup is stuck at a point and doesn't proceed further. User will not be able > to access the MS URL. The server is listening on port 8080 but a connection > won't establish. The traces show that it is stuck at a point in the setup. > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_aeac22f4 > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_958692e5 > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_90d5183f > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_e8137795 > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_1344120a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7462) UI: Edit tags buttons do not work on ACL List tab
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119792#comment-14119792 ] Ilia Shakitko commented on CLOUDSTACK-7462: --- Joining this thread... Same issue appears if you try to implement 'tags' action on any other new taggable resources. > UI: Edit tags buttons do not work on ACL List tab > - > > Key: CLOUDSTACK-7462 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7462 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0 >Reporter: Gabor Apati-Nagy > Attachments: tags_jsonobj_empty.jpg > > > Steps to reproduce: > -Go to Network > -Select VPC view from the dropdown > -Create a VPC if there is none present > -On a VPC, click on "Configure" button > -If needed, proceed and set the minimal required settings (eg. tier) > -Click on the Routers Network ACL Lists button, the ACLs are now listed > -Click on any item to open its detail view > -Select the ACL List Rules tab > Click on the "Edit tags" button of any the existing entries in the grid > Expected result: > -Tag editor should appear and tags should be editable > Actual result: > -Tag editor appears, but empty. Missing features: list, add, remove tags. > Note: > -Tag editor has a "Done" button, so it can be closed and the user can proceed > using the UI, however tags are not listable and editable. Loss of "tags" > functionality. > -The issue is seems to be related to CLOUDSTACK-5486. > -Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7478) [LXC] VM creation should fail when creating LXC VM with data disk and w/o having ceph as primary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal updated CLOUDSTACK-7478: --- Attachment: ms.tar.gz agent.log.tar.gz > [LXC] VM creation should fail when creating LXC VM with data disk and w/o > having ceph as primary storage > > > Key: CLOUDSTACK-7478 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7478 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.5.0 >Reporter: shweta agarwal >Assignee: Kishan Kavala >Priority: Critical > Fix For: 4.5.0 > > Attachments: agent.log.tar.gz, ms.tar.gz > > > Repro steps: > 1. Create a LXC zone with only nfs > 2. Create a VM with data disk > Bug: > VM creations passes without giving error that data disk needs ceph storage > Even usage events for data disk is also generated. > VM shows no data disk with it > dumxml of VM shows: > > i-2-21-VM > 7da917bf-dd91-4185-92ce-a419b6a7e396 > CentOS 6.3 (64-bit) > 524288 > 524288 > 1 > > 500 > > > /machine > > > exe > /sbin/init > > > > > > > > > > > > destroy > restart > destroy > > /usr/libexec/libvirt_lxc > >dir='/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/138ef448-03d7-4344-92a9-3e981b8826b6'/> > > > > > > > > > > > > > > > > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7291) LXC: Mgmt server/agent keeps killing systemvms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Brett updated CLOUDSTACK-7291: --- Priority: Blocker (was: Major) Upping this to blocker as I'm also seeing it and it is preventing me starting VMs on LXC > LXC: Mgmt server/agent keeps killing systemvms > -- > > Key: CLOUDSTACK-7291 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0, 4.3.1 >Reporter: Rohit Yadav >Assignee: Kishan Kavala >Priority: Blocker > Fix For: Future, 4.5.0 > > > Followed installation and setup docs of 4.3, was unable to get LXC to work on > Ubuntu 14.04/trusty. The systemvms kept coming up and result from > ssvm_check.sh was good and it was able to reach mgmt server /host, even then > mgmt server complained that it was unable to contact agent on the systemvm > (ping), while the agent would gracefully shutdown the systemvm (by killing > them). > Relevant log: > 2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode] > (secstorage-1:ctx-fc57ef43) Could not find exception: > com.cloud.exception.OperationTimedoutException in error code list for > exceptions > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache] > (consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling. > 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] > (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host > Host[-1-Routing] > 2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679) > Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host > id = 1, name = bluebox1.bhaisaab.org] > 2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl] > (secstorage-1:ctx-fc57ef43) Scheduled > HAWork[12-CheckStop-2-Starting-Scheduled] > 2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage > vm > com.cloud.exception.AgentUnavailableException: Resource [Host:1] is > unreachable: Host 1: Unable to start s-2-VM > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) > >---at > >com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > >---at > >com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > >---at > >com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) > ... > ... > ... > Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 > to Host 1 timed out after 3600 > >---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439) > > > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394) > >---at > >com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920) > >---at > >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989) > >---... 24 more > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7468) NetScaler SSL Termination does not handle Projects as expected
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119740#comment-14119740 ] ASF subversion and git services commented on CLOUDSTACK-7468: - Commit 92339bca0b0c8ecfc8b190e176dabfb0e8440f67 in cloudstack's branch refs/heads/4.4 from [~wstevens] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=92339bc ] CLOUDSTACK-7468: Fixed the NetScaler SSL Termination behavior with Projects > NetScaler SSL Termination does not handle Projects as expected > -- > > Key: CLOUDSTACK-7468 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7468 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Affects Versions: 4.5.0, 4.4.1 >Reporter: Will Stevens >Assignee: Will Stevens > Attachments: > CLOUDSTACK-7468-Fixed-NetScaler-SSL-Termination-for-Projects.patch > > > Currently the 'uploadSslCert' api call does not take any details about who > should own the SSL Cert. It basically assigns the cert to the caller and > thats it. > This breaks the expected behavior for projects and also does not allow for an > admin to upload certificates on behalf of one of their users. > This fix should not adjust the database entities at all, but should allow the > API calls to handle the additional cases. > The following changes should be made: > - If 'uploadSslCert' is called without any account details, it should behave > how it does now and assign the cert to the caller. > - If 'uploadSslCert' includes option 'account' and 'domainId' fields, the > uploaded cert will be applied to that account. > - If 'uploadSslCert' includes a 'projectId', then the cert is applied to that > project. > - The 'listSslCerts' api should also take an optional 'projectid' field to > list the ssl certs associated with that project. > - The api response for both 'uploadSslCert' and 'listSslCerts' should be > updated to include additional information about the account or project as > well as the domain in which the cert is assigned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7464) Management Server setup doesn't proceed to completion - org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-7464: --- Assignee: Damodar Reddy T > Management Server setup doesn't proceed to completion - > org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException > - > > Key: CLOUDSTACK-7464 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7464 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: Pavan Kumar Bandarupally >Assignee: Damodar Reddy T >Priority: Blocker > Fix For: 4.5.0 > > Attachments: catalina.out, localhost.2014-09-02.log, > management-server.log, setupManagement.log > > > After installation of management server, and database schema update, the > setup is stuck at a point and doesn't proceed further. User will not be able > to access the MS URL. The server is listening on port 8080 but a connection > won't establish. The traces show that it is stuck at a point in the setup. > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_aeac22f4 > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_958692e5 > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_90d5183f > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_e8137795 > 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] > (localhost-startStop-1:null) Starting > com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_1344120a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6990) VM console displays blank page.AgentControlChannelException in cloud.log
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119715#comment-14119715
]
Rajesh Battala commented on CLOUDSTACK-6990:
This is solve by this bug CLOUDSTACK-5946
please use required procedure from the above bug.
QA had already closed and verified it.
> VM console displays blank page.AgentControlChannelException in cloud.log
>
>
> Key: CLOUDSTACK-6990
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6990
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.4.0
>Reporter: manasaveloori
>Assignee: Rajesh Battala
>Priority: Critical
> Labels: DEVREV
> Fix For: 4.4.0, 4.5.0
>
> Attachments: cloud.log, management-server.rar
>
>
> Deployed Cloudstack using the build :
> [root@RHEL63test ~]# cloudstack-sccs
> 9024ad14681858ac7caafaf86f267a213ce6b61c
> Deployed a user VM.
> Now try to open the console of any VM.
> It is displaying blank page.
> In CPVM cloud.log observed the following exception continuously:
> 2014-06-25 06:31:14,620 INFO [utils.exception.CSExceptionErrorCode] (Console
> Proxy GC Thread:null) Could not find exception:
> com.cloud.exception.AgentControlChannelException in error code list for
> exceptions
> 2014-06-25 06:31:14,621 ERROR [resource.consoleproxy.ConsoleProxyResource]
> (Console Proxy GC Thread:null) Unable to send out load info due to Unable to
> post agent control request as link is not available
> com.cloud.exception.AgentControlChannelException: Unable to post agent
> control request as link is not available
> at com.cloud.agent.Agent.postRequest(Agent.java:689)
> at com.cloud.agent.Agent.postRequest(Agent.java:677)
> at
> com.cloud.agent.resource.consoleproxy.ConsoleProxyResource.reportLoadInfo(ConsoleProxyResource.java:418)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.consoleproxy.ConsoleProxy.reportLoadInfo(ConsoleProxy.java:227)
> at
> com.cloud.consoleproxy.ConsoleProxyGCThread.run(ConsoleProxyGCThread.java:102)
> 2014-06-25 06:31:14,621 DEBUG [cloud.consoleproxy.ConsoleProxyGCThread]
> (Console Proxy GC Thread:null) Report load change : {
> "connections": []
> }
> 2014-06-25 06:31:14,897 INFO [cloud.agent.Agent] (Agent-Handler-4:null)
> Reconnecting...
> 2014-06-25 06:31:14,897 INFO [utils.nio.NioClient] (Agent-Selector:null)
> Connecting to 10.147.59.222:8250
> Attaching the Ms logs and CPVM log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6990) VM console displays blank page.AgentControlChannelException in cloud.log
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Battala updated CLOUDSTACK-6990:
---
Labels: DEVREV (was: )
> VM console displays blank page.AgentControlChannelException in cloud.log
>
>
> Key: CLOUDSTACK-6990
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6990
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.4.0
>Reporter: manasaveloori
>Assignee: Rajesh Battala
>Priority: Critical
> Labels: DEVREV
> Fix For: 4.4.0, 4.5.0
>
> Attachments: cloud.log, management-server.rar
>
>
> Deployed Cloudstack using the build :
> [root@RHEL63test ~]# cloudstack-sccs
> 9024ad14681858ac7caafaf86f267a213ce6b61c
> Deployed a user VM.
> Now try to open the console of any VM.
> It is displaying blank page.
> In CPVM cloud.log observed the following exception continuously:
> 2014-06-25 06:31:14,620 INFO [utils.exception.CSExceptionErrorCode] (Console
> Proxy GC Thread:null) Could not find exception:
> com.cloud.exception.AgentControlChannelException in error code list for
> exceptions
> 2014-06-25 06:31:14,621 ERROR [resource.consoleproxy.ConsoleProxyResource]
> (Console Proxy GC Thread:null) Unable to send out load info due to Unable to
> post agent control request as link is not available
> com.cloud.exception.AgentControlChannelException: Unable to post agent
> control request as link is not available
> at com.cloud.agent.Agent.postRequest(Agent.java:689)
> at com.cloud.agent.Agent.postRequest(Agent.java:677)
> at
> com.cloud.agent.resource.consoleproxy.ConsoleProxyResource.reportLoadInfo(ConsoleProxyResource.java:418)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.consoleproxy.ConsoleProxy.reportLoadInfo(ConsoleProxy.java:227)
> at
> com.cloud.consoleproxy.ConsoleProxyGCThread.run(ConsoleProxyGCThread.java:102)
> 2014-06-25 06:31:14,621 DEBUG [cloud.consoleproxy.ConsoleProxyGCThread]
> (Console Proxy GC Thread:null) Report load change : {
> "connections": []
> }
> 2014-06-25 06:31:14,897 INFO [cloud.agent.Agent] (Agent-Handler-4:null)
> Reconnecting...
> 2014-06-25 06:31:14,897 INFO [utils.nio.NioClient] (Agent-Selector:null)
> Connecting to 10.147.59.222:8250
> Attaching the Ms logs and CPVM log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7472) Change cloudstack agent.properties file for rhel 7 to include kvmclock.disable=true
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Brett updated CLOUDSTACK-7472: --- Description: We need to minimize manual steps that needs to be done after agent installation so change cloudstack agent.properties file for rhel 7 to include kvmclock.disable=true was: We need to minimize manual steps that needs to be done after agent installation so change cloudstack agent.properties file for rhel 7 to include kvmclock.disable=true Summary: Change cloudstack agent.properties file for rhel 7 to include kvmclock.disable=true (was: [LXC] change cloudstack agent.properties file for rhel 7 to include kvmclock.disable=true) Removing LXC tag as this also affects KVM on RHEL7 > Change cloudstack agent.properties file for rhel 7 to include > kvmclock.disable=true > --- > > Key: CLOUDSTACK-7472 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7472 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.5.0 >Reporter: shweta agarwal >Assignee: Kishan Kavala >Priority: Critical > Fix For: 4.5.0 > > > We need to minimize manual steps that needs to be done after agent > installation so change cloudstack agent.properties file for rhel 7 to include > kvmclock.disable=true -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7476) centos cloudstack-usage script does not always pass along $JAVA_HOME
Leo Simons created CLOUDSTACK-7476: -- Summary: centos cloudstack-usage script does not always pass along $JAVA_HOME Key: CLOUDSTACK-7476 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7476 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.5.0 Environment: secured centos/redhat Reporter: Leo Simons Fix For: 4.5.0 /etc/init.d/cloudstack-usage finds a $JAVA_HOME and makes sure the environment variable is set, then assumes this variable will be picked up by JSVC. However, on a secured environment (selinux w/ env_reset enabled in sudoers), the runuser command that is invoked by the daemon() function does not pass along environment variables, so $JAVA_HOME is empty, and JSVC falls back to its default behavior, which may not find java or may not find the intended java. The simple solution is to pass -home to JSVC, passing it on the command line instead of as an environment variable. I'll provide a patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7475) [UI] UX improvement for instances page quickview
Alessandro Lepore created CLOUDSTACK-7475: - Summary: [UI] UX improvement for instances page quickview Key: CLOUDSTACK-7475 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7475 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Alessandro Lepore Priority: Minor Hi, i'm using cloudstack "4.4.0-SNAPSHOT" and i noticed an UX problems on the instances page. Imho it's not only a cosmetic problem because it can easily lead to errors, like accidentally editing the wrong instance. Hope this is the right place to report this kind of issues. How to reproduce: If i'm going over a "quickview" button and during the mouse movement i accidentally pass over a quickview button of another instance, the quickview of the first instance is the one that will remain open. So every time i open a quickview i must double check that i'm actually on the right instance because i can't be sure. quick video: http://youtu.be/YA8h5auXEfU here i want to edit the top instance but what's opening is actually the bottom instance quickview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7228) [Automation] Unable to shrink data disk attached to a VM on XenServer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119475#comment-14119475
]
ASF subversion and git services commented on CLOUDSTACK-7228:
-
Commit 9b783d19ad7e784d3751f4eaa2a672401d122a01 in cloudstack's branch
refs/heads/master from [~johnmdilley]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9b783d1 ]
CLOUDSTACK-7228 Only shrink disk when CLVM is in use.
Signed-off-by: SrikanteswaraRao Talluri
> [Automation] Unable to shrink data disk attached to a VM on XenServer
> -
>
> Key: CLOUDSTACK-7228
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7228
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test, Volumes
>Affects Versions: 4.5.0
>Reporter: Chandan Purushothama
>Assignee: Chandan Purushothama
>Priority: Critical
> Fix For: 4.5.0
>
> Attachments: management-server.zip
>
>
> ==
> Automation Code:
> ==
> def test_08_resize_volume(self):
> """Test resize a volume"""
> #Verify the size is the new size is what we wanted it to be.
> self.debug(
> "Attaching volume (ID: %s) to VM (ID: %s)" % (
> self.volume.id,
> self.virtual_machine.id
> ))
> self.virtual_machine.attach_volume(self.apiClient, self.volume)
> self.attached = True
> hosts = Host.list(self.apiClient, id=self.virtual_machine.hostid)
> self.assertTrue(isinstance(hosts, list))
> self.assertTrue(len(hosts) > 0)
> self.debug("Found %s host" % hosts[0].hypervisor)
> if hosts[0].hypervisor == "XenServer":
> self.virtual_machine.stop(self.apiClient)
> elif hosts[0].hypervisor.lower() == "vmware":
> self.skipTest("Resize Volume is unsupported on VmWare")
> #resize the data disk
> self.debug("Resize Volume ID: %s" % self.volume.id)
> self.services["disk_offering"]["disksize"] = 20
> disk_offering_20_GB = DiskOffering.create(
> self.apiclient,
> self.services["disk_offering"]
> )
> self.cleanup.append(disk_offering_20_GB)
> cmd= resizeVolume.resizeVolumeCmd()
> cmd.id = self.volume.id
> cmd.diskofferingid = disk_offering_20_GB.id
> self.apiClient.resizeVolume(cmd)
> ===
> Error Thrown in Automation Logs:
> ===
> =
> ERROR: Test resize a volume
>
> Traceback (most recent call last):
> File "/home/chandan/test_volumes.py", line 693, in test_08_resize_volume
> self.apiClient.resizeVolume(cmd)
> File
> "/usr/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 1672, in resizeVolume
> response = self.connection.marvinRequest(command, response_type=response,
> method=method)
> File "/usr/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 379, in marvinRequest
> raise e
> Exception: Job failed: {jobprocstatus : 0, created :
> u'2014-08-07T16:45:25-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin',
> userid : u'89a9018a-12a8-11e4-b75e-06098c000757', jobstatus : 2, jobid :
> u'7d5c9749-67d6-4fab-a0bf-f5bc8722b276', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Job failed due to
> exception failed to resize volume:SR_BACKEND_FAILURE_79VDI Invalid size
> [opterr=shrinking not allowed]'}, accountid :
> u'89a8f4e2-12a8-11e4-b75e-06098c000757'}
> >> begin captured stdout << -
> === TestName: test_08_resize_volume | Status : EXCEPTION ===
> ==
> Error in Management Server Log:
> ==
> 2014-08-07 14:15:39,459 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-23:ctx-62ca6450 job-1314/job-1315 ctx-0761b68e) Execute VM
> work job:
> com.cloud.storage.VmWorkResizeVolume{"volumeId":172,"currentSize":21474836480,"newSize":10737418240,"newServiceOfferingId":43,"shrinkOk":true,"userId":2,"accountId":2,"vmId":162,"handlerName":"VolumeApiServiceImpl"}
> 2014-08-07 14:15:39,487 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-23:ctx-62ca6450 job-1314/job-1315 ctx-0761b68e) Seq
> 1-1425952232016183856: Sending { Cmd , MgmtId: 6638
