[jira] [Created] (CLOUDSTACK-6866) First Class object hiding feature is not working for VirtualMachine and Networks resources
Girish Chaudhari created CLOUDSTACK-6866: Summary: First Class object hiding feature is not working for VirtualMachine and Networks resources Key: CLOUDSTACK-6866 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6866 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Environment: Observed it on 4.4 branch. Reporter: Girish Chaudhari Using Admin user, the Display flag can be applied for Virtual Machine and Networks resources. But when the list API get called on the respective resources, it is returning wrong results. The object get hided from normal users as well from Admin user. I haven't check rest of the mentioned first class resources yet. Expected results: The resource which is marked with Display flag as '0' (False) should be hided from normal user only, not from the Admin user -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6795) [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murali Reddy updated CLOUDSTACK-6795:
-
Issue Type: New Feature (was: Bug)
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> --
>
> Key: CLOUDSTACK-6795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6795
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
> Environment: Latest build from 4.4 with commit
> d130530bd3e1cd6d8249d5045e00e4e4e2201521
>Reporter: Sanjeev N
>Assignee: Murali Reddy
>Priority: Critical
> Labels: ovs
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> Steps to reproduce:
> ==
> 1.Bring up CS in advanced zone with xen cluster
> 2.Create physical network with GRE isolation
> 3.Create an isolated network offering with default offering
> "DefaultIsolatedNetworkOfferingWithSourceNatService"
> 4.Deploy one vm using above network offering
> 5.Create another guest network with Virtual networking and OVS as the
> connectivity service provider
> 6.Stop the vm and upgrade network with above network offering
> Result:
> =
> Failed to upgrade network with the offering which has connectivity service
> and ovs as the provider
> Observations:
> ==
> Following is the log snippet from MS log:
> 2014-05-28 07:27:28,419 DEBUG [c.c.a.t.Request]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Seq
> 4-1333065489701674831: Received: { Ans: , MgmtId: 7332683579487, via: 4,
> Ver: v1, Flags: 10, { Answer } }
> 2014-05-28 07:27:28,429 INFO [o.a.c.s.v.VolumeServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Volume 26 is not
> referred anywhere, remove it from volumes table
> 2014-05-28 07:27:28,435 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Expunged
> VM[DomainRouter|r-26-VM]
> 2014-05-28 07:27:28,458 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-b2ec9be1) Zone 1 is ready to launch console proxy
> 2014-05-28 07:27:28,480 DEBUG [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Implementing the
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update
> 2014-05-28 07:27:28,486 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Asking Ovs to
> implemenet Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15]
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) entering OvsElement
> implement function for network vlan1 (state Implemented)
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Checking if
> OvsElement can handle service Connectivity on network vlan1
> 2014-05-28 07:27:28,487 WARN [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Failed to implement
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update due to
> com.cloud.utils.exception.CloudRuntimeException: Failed to implement provider
> Ovs for network with specified id
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1081)
> at
> com.cloud.network.NetworkServiceImpl.updateGuestNetwork(NetworkServiceImpl.java:2303)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInter
[jira] [Updated] (CLOUDSTACK-6795) [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murali Reddy updated CLOUDSTACK-6795:
-
Fix Version/s: (was: 4.4.0)
Future
This is not a bug so marking bug as new feature.
Basically at present network offering upgraded does support a case where there
is mismatch in the services between the old and new offering. First we need to
enable the functionality where we can upgrade a network from offerings with
different set of services.
Once this feature is in, then supporting from offering (with out connectivity
service which implicitly assumes VLAN isolation) with VALN isolation to network
offering with OVS being the provider for connectivity service.
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> --
>
> Key: CLOUDSTACK-6795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6795
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
> Environment: Latest build from 4.4 with commit
> d130530bd3e1cd6d8249d5045e00e4e4e2201521
>Reporter: Sanjeev N
>Assignee: Murali Reddy
>Priority: Critical
> Labels: ovs
> Fix For: Future
>
> Attachments: management-server.rar
>
>
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> Steps to reproduce:
> ==
> 1.Bring up CS in advanced zone with xen cluster
> 2.Create physical network with GRE isolation
> 3.Create an isolated network offering with default offering
> "DefaultIsolatedNetworkOfferingWithSourceNatService"
> 4.Deploy one vm using above network offering
> 5.Create another guest network with Virtual networking and OVS as the
> connectivity service provider
> 6.Stop the vm and upgrade network with above network offering
> Result:
> =
> Failed to upgrade network with the offering which has connectivity service
> and ovs as the provider
> Observations:
> ==
> Following is the log snippet from MS log:
> 2014-05-28 07:27:28,419 DEBUG [c.c.a.t.Request]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Seq
> 4-1333065489701674831: Received: { Ans: , MgmtId: 7332683579487, via: 4,
> Ver: v1, Flags: 10, { Answer } }
> 2014-05-28 07:27:28,429 INFO [o.a.c.s.v.VolumeServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Volume 26 is not
> referred anywhere, remove it from volumes table
> 2014-05-28 07:27:28,435 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Expunged
> VM[DomainRouter|r-26-VM]
> 2014-05-28 07:27:28,458 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-b2ec9be1) Zone 1 is ready to launch console proxy
> 2014-05-28 07:27:28,480 DEBUG [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Implementing the
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update
> 2014-05-28 07:27:28,486 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Asking Ovs to
> implemenet Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15]
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) entering OvsElement
> implement function for network vlan1 (state Implemented)
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Checking if
> OvsElement can handle service Connectivity on network vlan1
> 2014-05-28 07:27:28,487 WARN [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Failed to implement
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update due to
> com.cloud.utils.exception.CloudRuntimeException: Failed to implement provider
> Ovs for network with specified id
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1081)
> at
> com.cloud.network.NetworkServiceImpl.updateGuestNetwork(NetworkServiceImpl.java:2303)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> a
[jira] [Created] (CLOUDSTACK-6867) [Hyper-V][UI] No option to upload a volume with .vhdx format
Abhinav Roy created CLOUDSTACK-6867:
---
Summary: [Hyper-V][UI] No option to upload a volume with .vhdx
format
Key: CLOUDSTACK-6867
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6867
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Affects Versions: 4.4.0
Environment: Hyper-V
Reporter: Abhinav Roy
Priority: Critical
Fix For: 4.4.0
Steps :
===
1. Deploy a advanced zone hyperv setup.
2. Try to upload a volume with .vhdx format
There is no option in the UI to upload .vhdx format volumes, only vhd is
there
3. Try to upload the .vhdx volume by selecting the format as .vhd
Then we get this error
2014-06-09 13:23:28,381 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-9:ctx-c149c622 job-84) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin
com.cloud.exception.InvalidParameterValueException: Please specify a valid URL.
URL:http://10.144.7.13/upload-data.vhdx is an invalid for the format vhd
at
com.cloud.storage.VolumeApiServiceImpl.validateVolume(VolumeApiServiceImpl.java:314)
at
com.cloud.storage.VolumeApiServiceImpl.uploadVolume(VolumeApiServiceImpl.java:252)
at
com.cloud.storage.VolumeApiServiceImpl.uploadVolume(VolumeApiServiceImpl.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy181.uploadVolume(Unknown Source)
at
org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin.execute(UploadVolumeCmdByAdmin.java:46)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-06-09 13:23:28,384 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-9:ctx-c149c622 job-84) Complete async job-84, jobStatus:
FAILED, resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Please
specify a valid URL. URL:http://10.144.7.13/upload-data.vhdx is an invalid for
the format vhd"}
--
This message
[jira] [Updated] (CLOUDSTACK-6865) [Hyper-V]attach of an uploaded volume is failing as it is looking for a .vhdx volume even though the volume present is .vhd
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Roy updated CLOUDSTACK-6865:
Attachment: management-server-6865.zip
Attaching MS logs
> [Hyper-V]attach of an uploaded volume is failing as it is looking for a
> .vhdx volume even though the volume present is .vhd
>
>
> Key: CLOUDSTACK-6865
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6865
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Storage Controller
>Affects Versions: 4.4.0
> Environment: Hyper-V
>Reporter: Abhinav Roy
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
> Attachments: management-server-6865.zip
>
>
> Steps :
> ==
> 1. Deploy an advanced zone Hyper-V setup.
> 2. Create a VM v1
> 3. Upload a volume upload1
> 4. Attach upload1 to v1
> Expected Behavior :
> ==
> Attach should be successful.
> Observed behavior :
> ==
> Attach fails with the following error :
> 2014-06-09 11:32:47,684 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-8:ctx-02af10fb) ===START=== 10.144.7.13 -- GET
> command=attachVolume&id=ddcaf328-0e71-462b-9ce6-e520dc8f15cc&virtualMachineId=ea78d7ec-6fed-4c3e-bff1-29219c70bddd&response=json&sessionkey=4MQxLlvkRgcp%2FMBl6tf6TodmICI%3D&_=1402293458440
> 2014-06-09 11:32:47,726 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-8:ctx-02af10fb ctx-dce1c925) submit async job-66, details:
> AsyncJobVO {id:66, userId: 2, accountId: 2, instanceType: Volume, instanceId:
> 7, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"response":"json","id":"ddcaf328-0e71-462b-9ce6-e520dc8f15cc","sessionkey":"4MQxLlvkRgcp/MBl6tf6TodmICI\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":7,\"Volume\":\"ddcaf328-0e71-462b-9ce6-e520dc8f15cc\",\"com.cloud.vm.VirtualMachine\":5}","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"ea78d7ec-6fed-4c3e-bff1-29219c70bddd","httpmethod":"GET","_":"1402293458440","uuid":"ddcaf328-0e71-462b-9ce6-e520dc8f15cc","ctxAccountId":"2","ctxStartEventId":"112"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-06-09 11:32:47,727 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-8:ctx-02af10fb ctx-dce1c925) ===END=== 10.144.7.13 -- GET
> command=attachVolume&id=ddcaf328-0e71-462b-9ce6-e520dc8f15cc&virtualMachineId=ea78d7ec-6fed-4c3e-bff1-29219c70bddd&response=json&sessionkey=4MQxLlvkRgcp%2FMBl6tf6TodmICI%3D&_=1402293458440
> 2014-06-09 11:32:47,729 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-24:ctx-976a0ed5 job-66) Add job-66 into job monitoring
> 2014-06-09 11:32:47,734 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-24:ctx-976a0ed5 job-66) Executing AsyncJobVO {id:66,
> userId: 2, accountId: 2, instanceType: Volume, instanceId: 7, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"response":"json","id":"ddcaf328-0e71-462b-9ce6-e520dc8f15cc","sessionkey":"4MQxLlvkRgcp/MBl6tf6TodmICI\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":7,\"Volume\":\"ddcaf328-0e71-462b-9ce6-e520dc8f15cc\",\"com.cloud.vm.VirtualMachine\":5}","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"ea78d7ec-6fed-4c3e-bff1-29219c70bddd","httpmethod":"GET","_":"1402293458440","uuid":"ddcaf328-0e71-462b-9ce6-e520dc8f15cc","ctxAccountId":"2","ctxStartEventId":"112"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-06-09 11:32:47,744 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) Received unknown
> parameters for command attachVolume. Unknown parameters : ctxdetails
> 2014-06-09 11:32:47,769 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) Sync job-67 execution
> on object VmWorkJobQueue.5
> 2014-06-09 11:32:47,772 DEBUG [c.c.s.VolumeApiServiceImpl]
> (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) New job 67, result
> field: null
> 2014-06-09 11:32:47,773 WARN [c.c.u.d.Merovingian2]
> (API-Job-Executor-24:ctx-976a0ed5 job-66 ctx-1d0f4aec) Was unable to find
> lock for the key vm_instance5 and thread id 1700504230
> 2014-06-09 11:32:49,461 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-04e08
[jira] [Updated] (CLOUDSTACK-6867) [Hyper-V][UI] No option to upload a volume with .vhdx format
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Roy updated CLOUDSTACK-6867: Attachment: CS-6867.jpg Attaching screenshot > [Hyper-V][UI] No option to upload a volume with .vhdx format > > > Key: CLOUDSTACK-6867 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6867 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.4.0 > > Attachments: CS-6867.jpg > > > Steps : > === > 1. Deploy a advanced zone hyperv setup. > 2. Try to upload a volume with .vhdx format > There is no option in the UI to upload .vhdx format volumes, only vhd is > there > 3. Try to upload the .vhdx volume by selecting the format as .vhd > Then we get this error > 2014-06-09 13:23:28,381 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-9:ctx-c149c622 job-84) Unexpected exception while executing > org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin > com.cloud.exception.InvalidParameterValueException: Please specify a valid > URL. URL:http://10.144.7.13/upload-data.vhdx is an invalid for the format vhd > at > com.cloud.storage.VolumeApiServiceImpl.validateVolume(VolumeApiServiceImpl.java:314) > at > com.cloud.storage.VolumeApiServiceImpl.uploadVolume(VolumeApiServiceImpl.java:252) > at > com.cloud.storage.VolumeApiServiceImpl.uploadVolume(VolumeApiServiceImpl.java:148) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy181.uploadVolume(Unknown Source) > at > org.apache.cloudstack.api.command.admin.volume.UploadVolumeCmdByAdmin.execute(UploadVolumeCmdByAdmin.java:46) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at > com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(Thread
[jira] [Created] (CLOUDSTACK-6868) [Hyper-V] Download of an uploaded volume is failing
Abhinav Roy created CLOUDSTACK-6868:
---
Summary: [Hyper-V] Download of an uploaded volume is failing
Key: CLOUDSTACK-6868
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6868
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, Storage Controller
Affects Versions: 4.4.0
Environment: Hyper-V
Reporter: Abhinav Roy
Priority: Critical
Fix For: 4.4.0
Steps:
=
1. Deploy an advanced zone Hyper-V setup.
2. Create a VM v1
3. Upload a volume upload1
4. Download upload1
Expected behavior :
=
Download should pass.
Observed behavior :
=
Download fails with
2014-06-09 14:06:16,740 DEBUG [c.c.a.ApiServlet]
(catalina-exec-13:ctx-2b2fe04f) ===START=== 10.144.7.13 -- GET
command=extractVolume&id=7282784d-75bf-46a4-b6a5-33fae5cda75c&zoneid=622e7c06-e62e-4a6b-8de6-a462a3ee7cf7&mode=HTTP_DOWNLOAD&response=json&sessionkey=RGKWL0km%2FibmrEZH39fWJsmJeeU%3D&_=1402302332046
2014-06-09 14:06:16,783 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-13:ctx-2b2fe04f ctx-676b8816) submit async job-113, details:
AsyncJobVO {id:113, userId: 2, accountId: 2, instanceType: Volume, instanceId:
18, cmd: org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd,
cmdInfo:
{"response":"json","id":"7282784d-75bf-46a4-b6a5-33fae5cda75c","sessionkey":"RGKWL0km/ibmrEZH39fWJsmJeeU\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"7282784d-75bf-46a4-b6a5-33fae5cda75c\",\"com.cloud.dc.DataCenter\":1}","cmdEventType":"VOLUME.EXTRACT","ctxUserId":"2","zoneid":"622e7c06-e62e-4a6b-8de6-a462a3ee7cf7","httpmethod":"GET","_":"1402302332046","uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","ctxAccountId":"2","ctxStartEventId":"197","mode":"HTTP_DOWNLOAD"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-09 14:06:16,783 DEBUG [c.c.a.ApiServlet] (catalina-exec-13:ctx-2b2fe04f
ctx-676b8816) ===END=== 10.144.7.13 -- GET
command=extractVolume&id=7282784d-75bf-46a4-b6a5-33fae5cda75c&zoneid=622e7c06-e62e-4a6b-8de6-a462a3ee7cf7&mode=HTTP_DOWNLOAD&response=json&sessionkey=RGKWL0km%2FibmrEZH39fWJsmJeeU%3D&_=1402302332046
2014-06-09 14:06:16,785 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-28:ctx-774021c1 job-113) Add job-113 into job monitoring
2014-06-09 14:06:16,786 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-28:ctx-774021c1 job-113) Executing AsyncJobVO {id:113,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo:
{"response":"json","id":"7282784d-75bf-46a4-b6a5-33fae5cda75c","sessionkey":"RGKWL0km/ibmrEZH39fWJsmJeeU\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"7282784d-75bf-46a4-b6a5-33fae5cda75c\",\"com.cloud.dc.DataCenter\":1}","cmdEventType":"VOLUME.EXTRACT","ctxUserId":"2","zoneid":"622e7c06-e62e-4a6b-8de6-a462a3ee7cf7","httpmethod":"GET","_":"1402302332046","uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","ctxAccountId":"2","ctxStartEventId":"197","mode":"HTTP_DOWNLOAD"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-09 14:06:16,795 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) Received unknown
parameters for command extractVolume. Unknown parameters : ctxdetails
2014-06-09 14:06:16,833 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) copyAsync inspecting
src type VOLUME copyAsync inspecting dest type VOLUME
2014-06-09 14:06:16,850 DEBUG [c.c.a.t.Request]
(API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) Seq
1-9177491615650939381: Sending { Cmd , MgmtId: 213737702773493, via:
1(10.102.244.20), Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"641da331-d6d6-3224-b53a-0dad93667d30","id":2,"poolType":"SMB","host":"SMB19","path":"/hyperv-share/abhinav-ps1?user=abhinavroy&domain=BLR","port":445,"url":"SMB://SMB19/hyperv-share/abhinav-ps1?user=abhinavroy&domain=BLR/?ROLE=Primary&STOREUUID=641da331-d6d6-3224-b53a-0dad93667d30"}},"name":"upload3","size":21474836480,"volumeId":18,"accountId":2,"format":"VHDX","id":18,"hypervisorType":"Hyperv"}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","volumeType
[jira] [Updated] (CLOUDSTACK-6868) [Hyper-V] Download of an uploaded volume is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Roy updated CLOUDSTACK-6868:
Description:
Steps:
=
1. Deploy an advanced zone Hyper-V setup.
2. Create a VM v1
3. Upload a volume upload1
4. Download upload1
Expected behavior :
=
Download should pass.
Observed behavior :
=
Download fails with
2014-06-09 14:06:16,740 DEBUG [c.c.a.ApiServlet]
(catalina-exec-13:ctx-2b2fe04f) ===START=== 10.144.7.13 -- GET
command=extractVolume&id=7282784d-75bf-46a4-b6a5-33fae5cda75c&zoneid=622e7c06-e62e-4a6b-8de6-a462a3ee7cf7&mode=HTTP_DOWNLOAD&response=json&sessionkey=RGKWL0km%2FibmrEZH39fWJsmJeeU%3D&_=1402302332046
2014-06-09 14:06:16,783 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-13:ctx-2b2fe04f ctx-676b8816) submit async job-113, details:
AsyncJobVO {id:113, userId: 2, accountId: 2, instanceType: Volume, instanceId:
18, cmd: org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd,
cmdInfo:
{"response":"json","id":"7282784d-75bf-46a4-b6a5-33fae5cda75c","sessionkey":"RGKWL0km/ibmrEZH39fWJsmJeeU\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"7282784d-75bf-46a4-b6a5-33fae5cda75c\",\"com.cloud.dc.DataCenter\":1}","cmdEventType":"VOLUME.EXTRACT","ctxUserId":"2","zoneid":"622e7c06-e62e-4a6b-8de6-a462a3ee7cf7","httpmethod":"GET","_":"1402302332046","uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","ctxAccountId":"2","ctxStartEventId":"197","mode":"HTTP_DOWNLOAD"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-09 14:06:16,783 DEBUG [c.c.a.ApiServlet] (catalina-exec-13:ctx-2b2fe04f
ctx-676b8816) ===END=== 10.144.7.13 -- GET
command=extractVolume&id=7282784d-75bf-46a4-b6a5-33fae5cda75c&zoneid=622e7c06-e62e-4a6b-8de6-a462a3ee7cf7&mode=HTTP_DOWNLOAD&response=json&sessionkey=RGKWL0km%2FibmrEZH39fWJsmJeeU%3D&_=1402302332046
2014-06-09 14:06:16,785 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-28:ctx-774021c1 job-113) Add job-113 into job monitoring
2014-06-09 14:06:16,786 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-28:ctx-774021c1 job-113) Executing AsyncJobVO {id:113,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo:
{"response":"json","id":"7282784d-75bf-46a4-b6a5-33fae5cda75c","sessionkey":"RGKWL0km/ibmrEZH39fWJsmJeeU\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"7282784d-75bf-46a4-b6a5-33fae5cda75c\",\"com.cloud.dc.DataCenter\":1}","cmdEventType":"VOLUME.EXTRACT","ctxUserId":"2","zoneid":"622e7c06-e62e-4a6b-8de6-a462a3ee7cf7","httpmethod":"GET","_":"1402302332046","uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","ctxAccountId":"2","ctxStartEventId":"197","mode":"HTTP_DOWNLOAD"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-09 14:06:16,795 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) Received unknown
parameters for command extractVolume. Unknown parameters : ctxdetails
2014-06-09 14:06:16,833 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) copyAsync inspecting
src type VOLUME copyAsync inspecting dest type VOLUME
2014-06-09 14:06:16,850 DEBUG [c.c.a.t.Request]
(API-Job-Executor-28:ctx-774021c1 job-113 ctx-351bc29f) Seq
1-9177491615650939381: Sending { Cmd , MgmtId: 213737702773493, via:
1(10.102.244.20), Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"641da331-d6d6-3224-b53a-0dad93667d30","id":2,"poolType":"SMB","host":"SMB19","path":"/hyperv-share/abhinav-ps1?user=abhinavroy&domain=BLR","port":445,"url":"SMB://SMB19/hyperv-share/abhinav-ps1?user=abhinavroy&domain=BLR/?ROLE=Primary&STOREUUID=641da331-d6d6-3224-b53a-0dad93667d30"}},"name":"upload3","size":21474836480,"volumeId":18,"accountId":2,"format":"VHDX","id":18,"hypervisorType":"Hyperv"}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"7282784d-75bf-46a4-b6a5-33fae5cda75c","volumeType":"DATADISK","dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"cifs://10.102.192.19/hyperv-share/abhinav-ss1?user=abhinavroy&domain=BLR","_role":"Image"}},"name":"upload3","size":21474836480,"path":"volumes/2/18","volumeId":18,"accountId":2,"format":"VHDX","id":18,"hypervisorType":"Hyperv"}},"executeInSequence":false,"options":{},"wait":10800}}]
}
2014-06-09 14:06:16,852 DEBUG [c.c.a.t.
[jira] [Resolved] (CLOUDSTACK-6819) [OVs] delete network/account sends OvsDestroyBridgeCommand to only one host
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murali Reddy resolved CLOUDSTACK-6819.
--
Resolution: Cannot Reproduce
Sanjeev,
I am able to see that OvsDestroyBridge command being sent to all the hosts.
Please note that when you can delete a network, its possible only in case when
all the VM's in the network are already expunged including VR.
OvsDestroyBridge is sent to a host when last VM running on the host is
destroyed, which will result in cleaning up the bridge on the host, deleting
the tunnel ports and deleting dom0 vif as well.
So you may actually not see ant OvsDestroyBridge commands when a network is
destroyed, but rather when a last VM is deleted on the host.
> [OVs] delete network/account sends OvsDestroyBridgeCommand to only one host
>
>
> Key: CLOUDSTACK-6819
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6819
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
> Environment: Latest build from 4.4 with commit
> 32bbc84db99d0e5f7f9b2a3fb41e4e783a2de350
>Reporter: Sanjeev N
>Assignee: Murali Reddy
>Priority: Critical
> Labels: ovs
> Fix For: 4.4.0
>
> Attachments: management-server.rar, ovstunnel-host13.log,
> ovstunnel-host14.log
>
>
> [OVs] delete network/account sends OvsDestroyBridgeCommand to only one host
> even though the network spanned more than one host
> Steps to reproduce:
> ===
> 1.Bring up CS in advanced zone with multiple clusters(2-3 clusters with 1
> host in each cluster)
> 2.Create network offering with connectivity service and OVS as the service
> provider
> 3.Add one guest account and deploy few vms with this new account
> 4.Use host tags to deploy vms in all the clusters to make sure that network
> is spanned accross all the clusters
> 5.Delete the account
> Result:
> =
> Account deletion was successful and also ovs bridges were deleted from both
> the hosts but the ovsTunnel porr(vif) for this network was unplugged only
> from one host's dom0(the host to which OvsDestroyBridgeCommand was sent) but
> not from the other host's dom0
> Observations:
> ===
> Following is the log snippet from MS log file during account deletion:
> Network was snapped across two hosts Rack1Pod1Host14 and Rack1Pod1Host13 but
> OvsDestroyBridgeCommand was sent only to Rack1Pod1Host13
> 2014-06-02 07:11:19,838 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Work-Job-Executor-18:ctx-c73e49f0 job-56/job-57 ctx-e2515de4) Asking Ovs to
> release NicProfile[26-16-2e06143e-28bd-4b43-ae0b-23a71bf0ed35-10.1.1.197-null
> 2014-06-02 07:11:19,839 DEBUG [c.c.n.e.OvsElement]
> (Work-Job-Executor-18:ctx-c73e49f0 job-56/job-57 ctx-e2515de4) Checking if
> OvsElement can handle service Connectivity on network acc2-cs-gre
> 2014-06-02 07:11:45,654 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Work-Job-Executor-19:ctx-39832471 job-56/job-58 ctx-67dba604) Asking Ovs to
> release NicProfile[30-18-273ebec1-867a-4081-8607-cb19af4c133d-10.1.1.52-null
> 2014-06-02 07:11:45,655 DEBUG [c.c.n.e.OvsElement]
> (Work-Job-Executor-19:ctx-39832471 job-56/job-58 ctx-67dba604) Checking if
> OvsElement can handle service Connectivity on network acc2-cs-gre
> 2014-06-02 07:11:45,665 DEBUG [c.c.n.o.OvsTunnelManagerImpl]
> (Work-Job-Executor-19:ctx-39832471 job-56/job-58 ctx-67dba604) Destroying
> bridge for network 207 on host:1
> 2014-06-02 07:11:45,670 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-19:ctx-39832471 job-56/job-58 ctx-67dba604) Seq
> 1-8504203471359062600: Sending { Cmd , MgmtId: 7332683579487, via:
> 1(Rack1Pod1Host13), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.OvsDestroyBridgeCommand":{"networkId":207,"name":"OVSTunnel992","hostId":1,"wait":0}}]
> }
> 2014-06-02 07:11:45,670 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-19:ctx-39832471 job-56/job-58 ctx-67dba604) Seq
> 1-8504203471359062600: Executing: { Cmd , MgmtId: 7332683579487, via:
> 1(Rack1Pod1Host13), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.OvsDestroyBridgeCommand":{"networkId":207,"name":"OVSTunnel992","hostId":1,"wait":0}}]
> }
> 2014-06-02 07:11:45,761 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-148:ctx-0a89d399) Xen Server network for tunnels
> found:OVSTunnel992
> 2014-06-02 07:11:45,807 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-148:ctx-0a89d399) Destroy temp dom0 vifOVSTunnel992 success
> 2014-06-02 07:11:46,127 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-148:ctx-0a89d399) OVS Bridge destroyed
> 2014-06-02 07:11:46,232 DEBUG [c.c.n.o.OvsTunnelManagerImpl]
> (Work-Job-Executor-19:ct
[jira] [Created] (CLOUDSTACK-6869) Public key content is overridden by template's meta data when you create a instance
Hiroki Ohashi created CLOUDSTACK-6869:
-
Summary: Public key content is overridden by template's meta data
when you create a instance
Key: CLOUDSTACK-6869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6869
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API, Management Server, Template
Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0
Reporter: Hiroki Ohashi
Priority: Blocker
A public key content is overridden by detail value of 'SSH.PublicKey' from a
template created by an instance ROOT volume with public key specification.
This results in delivery of the template owner's ssh key for a instance created
from the template to virtual router inspite of specification of instance
owner's ssh key.
It is caused by import of resource detail values at commitUserVm method
like below.
{code}
Map details = template.getDetails();
if (details != null && !details.isEmpty()) {
vm.details.putAll(details);
}
{code}
Reproduction procedure:
# Deploy an instance with a ssh key A by specifying 'keypair' value.
# Create a template from this instance.
# Deploy an instance with another ssh key B by specifying 'keypair' value.
Database example:
{noformat}
mysql> select * from cloud.template_view where id=207 \G;
*** 1. row ***
id: 207
uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
name: cluster_frontend-20140520.2
public: 1
featured: 0
type: USER
hvm: 1
bits: 64
url: NULL
format: QCOW2
created: 2014-05-20 09:33:47
checksum: NULL
display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
enable_password: 1
dynamically_scalable: 0
template_state: Active
guest_os_id: 182
guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
guest_os_name: CentOS 6.4 (64-bit)
bootable: 1
prepopulate: 0
cross_zones: 0
hypervisor_type: KVM
extractable: 0
template_tag: NULL
sort_key: 0
removed: NULL
enable_sshkey: 0
source_template_id: 205
source_template_uuid: c131680c-3e0e-4d7c-b554-02dabc10ade1
account_id: 3
account_uuid: f9e4e1ca-69fd-4ae3-b70c-15bbcc13406e
account_name: sgcadm
account_type: 0
domain_id: 2
domain_uuid: 84dd635d-fb99-4895-b199-7d777aa144d5
domain_name: default
domain_path: /default/
project_id: NULL
project_uuid: NULL
project_name: NULL
data_center_id: NULL
data_center_uuid: NULL
data_center_name: NULL
lp_account_id: NULL
store_id: 3
store_scope: REGION
state: Ready
download_state: DOWNLOADED
download_pct: 100
error_str: NULL
size: 18465816576
destroyed: 0
created_on_store: 2014-05-20 09:33:47
detail_name: Message.ReservedCapacityFreed.Flag
detail_value: false
tag_id: NULL
tag_uuid: NULL
tag_key: NULL
tag_value: NULL
tag_domain_id: NULL
tag_account_id: NULL
tag_resource_id: NULL
tag_resource_uuid: NULL
tag_resource_type: NULL
tag_customer: NULL
temp_zone_pair: 207_0
*** 2. row ***
id: 207
uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
name: cluster_frontend-20140520.2
public: 1
featured: 0
type: USER
hvm: 1
bits: 64
url: NULL
format: QCOW2
created: 2014-05-20 09:33:47
checksum: NULL
display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
enable_password: 1
dynamically_scalable: 0
template_state: Active
guest_os_id: 182
guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
guest_os_name: CentOS 6.4 (64-bit)
bootable: 1
prepopulate: 0
cross_zones: 0
hypervisor_type: KVM
extractable: 0
template_tag: NULL
sort_key: 0
removed: NULL
enable_sshkey: 0
source_template_id: 205
source_template_uuid: c131680c-3e0e-4d7c-b554-02dabc10ade1
account_id: 3
account_uuid: f9e4e1ca-69fd-4ae3-b70c-15bbcc13406e
account_name: sgcadm
account_type: 0
domain_id: 2
domain_uuid: 84d
[jira] [Updated] (CLOUDSTACK-6795) [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murali Reddy updated CLOUDSTACK-6795:
-
Priority: Major (was: Critical)
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> --
>
> Key: CLOUDSTACK-6795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6795
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
> Environment: Latest build from 4.4 with commit
> d130530bd3e1cd6d8249d5045e00e4e4e2201521
>Reporter: Sanjeev N
>Assignee: Murali Reddy
> Labels: ovs
> Fix For: Future
>
> Attachments: management-server.rar
>
>
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> Steps to reproduce:
> ==
> 1.Bring up CS in advanced zone with xen cluster
> 2.Create physical network with GRE isolation
> 3.Create an isolated network offering with default offering
> "DefaultIsolatedNetworkOfferingWithSourceNatService"
> 4.Deploy one vm using above network offering
> 5.Create another guest network with Virtual networking and OVS as the
> connectivity service provider
> 6.Stop the vm and upgrade network with above network offering
> Result:
> =
> Failed to upgrade network with the offering which has connectivity service
> and ovs as the provider
> Observations:
> ==
> Following is the log snippet from MS log:
> 2014-05-28 07:27:28,419 DEBUG [c.c.a.t.Request]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Seq
> 4-1333065489701674831: Received: { Ans: , MgmtId: 7332683579487, via: 4,
> Ver: v1, Flags: 10, { Answer } }
> 2014-05-28 07:27:28,429 INFO [o.a.c.s.v.VolumeServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Volume 26 is not
> referred anywhere, remove it from volumes table
> 2014-05-28 07:27:28,435 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Expunged
> VM[DomainRouter|r-26-VM]
> 2014-05-28 07:27:28,458 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-b2ec9be1) Zone 1 is ready to launch console proxy
> 2014-05-28 07:27:28,480 DEBUG [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Implementing the
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update
> 2014-05-28 07:27:28,486 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Asking Ovs to
> implemenet Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15]
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) entering OvsElement
> implement function for network vlan1 (state Implemented)
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Checking if
> OvsElement can handle service Connectivity on network vlan1
> 2014-05-28 07:27:28,487 WARN [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Failed to implement
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update due to
> com.cloud.utils.exception.CloudRuntimeException: Failed to implement provider
> Ovs for network with specified id
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1081)
> at
> com.cloud.network.NetworkServiceImpl.updateGuestNetwork(NetworkServiceImpl.java:2303)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
> at
> or
[jira] [Resolved] (CLOUDSTACK-6720) Async job events are not published on event bus
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-6720. -- Resolution: Fixed > Async job events are not published on event bus > --- > > Key: CLOUDSTACK-6720 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6720 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Murali Reddy >Assignee: Murali Reddy > Fix For: 4.4.0 > > > Async job events are not published on event bus after underlying mechanism to > publish the events is changed to use message bus. > publishOnEventBus is not called in AsyncJobManagerImpl.java after submit, > update, complete phases of async job. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6721) VolumeApiServiceImpl is sending wrong type for updateAsyncJobAttachment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-6721. -- Resolution: Fixed > VolumeApiServiceImpl is sending wrong type for updateAsyncJobAttachment > --- > > Key: CLOUDSTACK-6721 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6721 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Murali Reddy >Assignee: Murali Reddy > Fix For: 4.4.0 > > > VolumeApiServiceImpl is sending wrong type for updateAsyncJobAttachment. Its > sending lower case 'volume' instead of 'Volume' resulting in instance type > matching logic failure in APIDB utils -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6869) Public key content is overridden by template's meta data when you create a instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiroki Ohashi updated CLOUDSTACK-6869:
--
Description:
A public key content is overridden by detail value of 'SSH.PublicKey' from a
template created by an instance ROOT volume with public key specification.
This results in delivery of the template owner's ssh key for a instance created
from the template to virtual router inspite of specification of instance
owner's ssh key.
It is caused by import of resource detail values at commitUserVm method like
below.
{code}
Map details = template.getDetails();
if (details != null && !details.isEmpty()) {
vm.details.putAll(details);
}
{code}
Reproduction procedure:
# Deploy an instance with a ssh key A by specifying 'keypair' value.
# Create a template from this instance.
# Deploy an instance with another ssh key B by specifying 'keypair' value.
Database example:
{noformat}
mysql> select * from cloud.template_view where id=207 \G;
*** 1. row ***
id: 207
uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
name: cluster_frontend-20140520.2
public: 1
featured: 0
type: USER
hvm: 1
bits: 64
url: NULL
format: QCOW2
created: 2014-05-20 09:33:47
checksum: NULL
display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
enable_password: 1
dynamically_scalable: 0
template_state: Active
guest_os_id: 182
guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
guest_os_name: CentOS 6.4 (64-bit)
bootable: 1
prepopulate: 0
cross_zones: 0
hypervisor_type: KVM
extractable: 0
template_tag: NULL
sort_key: 0
removed: NULL
enable_sshkey: 0
source_template_id: 205
source_template_uuid: c131680c-3e0e-4d7c-b554-02dabc10ade1
account_id: 3
account_uuid: f9e4e1ca-69fd-4ae3-b70c-15bbcc13406e
account_name: sgcadm
account_type: 0
domain_id: 2
domain_uuid: 84dd635d-fb99-4895-b199-7d777aa144d5
domain_name: default
domain_path: /default/
project_id: NULL
project_uuid: NULL
project_name: NULL
data_center_id: NULL
data_center_uuid: NULL
data_center_name: NULL
lp_account_id: NULL
store_id: 3
store_scope: REGION
state: Ready
download_state: DOWNLOADED
download_pct: 100
error_str: NULL
size: 18465816576
destroyed: 0
created_on_store: 2014-05-20 09:33:47
detail_name: Message.ReservedCapacityFreed.Flag
detail_value: false
tag_id: NULL
tag_uuid: NULL
tag_key: NULL
tag_value: NULL
tag_domain_id: NULL
tag_account_id: NULL
tag_resource_id: NULL
tag_resource_uuid: NULL
tag_resource_type: NULL
tag_customer: NULL
temp_zone_pair: 207_0
*** 2. row ***
id: 207
uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
name: cluster_frontend-20140520.2
public: 1
featured: 0
type: USER
hvm: 1
bits: 64
url: NULL
format: QCOW2
created: 2014-05-20 09:33:47
checksum: NULL
display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
enable_password: 1
dynamically_scalable: 0
template_state: Active
guest_os_id: 182
guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
guest_os_name: CentOS 6.4 (64-bit)
bootable: 1
prepopulate: 0
cross_zones: 0
hypervisor_type: KVM
extractable: 0
template_tag: NULL
sort_key: 0
removed: NULL
enable_sshkey: 0
source_template_id: 205
source_template_uuid: c131680c-3e0e-4d7c-b554-02dabc10ade1
account_id: 3
account_uuid: f9e4e1ca-69fd-4ae3-b70c-15bbcc13406e
account_name: sgcadm
account_type: 0
domain_id: 2
domain_uuid: 84dd635d-fb99-4895-b199-7d777aa144d5
domain_name: default
domain_path: /default/
project_id: NULL
project_uuid: NULL
project_name: NULL
data_center_id: NULL
data_center_uuid: NULL
data_center_name: NULL
lp_account_id: NULL
store_id: 3
store_scope: REGION
state: Ready
download_stat
[jira] [Commented] (CLOUDSTACK-6709) [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021802#comment-14021802 ] Murali Reddy commented on CLOUDSTACK-6709: -- In general, i have explained logic of deleting bridge and tunnel ports in the bug 6819. When a last VM from the host is removed bridge and tunnel ports get deleted. I am seeing the bridge and tunnel ports are deleted as well. Please put specific case where you are observing that bridge is not getting deleted. Also, how is this bug different from 6819. > [SDN] Deleting network does not delete the tunnel ports and the bridge from > the hypervisor > -- > > Key: CLOUDSTACK-6709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller >Affects Versions: 4.4.0 > Environment: Latest build from 4.4 with commit > e6961fd21bb6d793302c234d0f409f66dc498072 >Reporter: Sanjeev N >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.4.0 > > Attachments: management-server.rar, ovstunnel-host13.log, > ovstunnel-host14.log > > > [SDN] Deleting network does not delete the tunnel ports and the bridge from > the hypervisor > Steps to Reproduce: > = > 1.Bring up CS in advanced zone with two xen hosts in a cluster > 2.Add physical network with GRE isolation > 3.Create network with connectivity service and ovs as the service provider > 4.Deploy few vms in the above network and make sure that vms are spanned > across both the hosts > 5.Destroy and expunge all the vms in the network and delete the network > Expected result: > = > Network deletion should be successful and all the tunnel ports and brige > created for the network should be deleted from both the hosts > Actual Result: > > Network deletion was successful but failed to delete ovs bridge and the > tunnel ports. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6709) [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-6709. -- Resolution: Cannot Reproduce > [SDN] Deleting network does not delete the tunnel ports and the bridge from > the hypervisor > -- > > Key: CLOUDSTACK-6709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller >Affects Versions: 4.4.0 > Environment: Latest build from 4.4 with commit > e6961fd21bb6d793302c234d0f409f66dc498072 >Reporter: Sanjeev N >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.4.0 > > Attachments: management-server.rar, ovstunnel-host13.log, > ovstunnel-host14.log > > > [SDN] Deleting network does not delete the tunnel ports and the bridge from > the hypervisor > Steps to Reproduce: > = > 1.Bring up CS in advanced zone with two xen hosts in a cluster > 2.Add physical network with GRE isolation > 3.Create network with connectivity service and ovs as the service provider > 4.Deploy few vms in the above network and make sure that vms are spanned > across both the hosts > 5.Destroy and expunge all the vms in the network and delete the network > Expected result: > = > Network deletion should be successful and all the tunnel ports and brige > created for the network should be deleted from both the hosts > Actual Result: > > Network deletion was successful but failed to delete ovs bridge and the > tunnel ports. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6870) getDomainId implementation returns invalid value at places
Santhosh Kumar Edukulla created CLOUDSTACK-6870:
---
Summary: getDomainId implementation returns invalid value at places
Key: CLOUDSTACK-6870
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6870
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Santhosh Kumar Edukulla
Assignee: Santhosh Kumar Edukulla
Fix For: 4.5.0
Few classes implementing getDomainId derived from the below interface, seems to
have invalid value returned for domainid. EX: VMTemplateVO, implementing this
method returns -1. This behavior is creating issues at some places in code.
The respective tables EX: vm_template dont have column say domainid and so it
returns -1.
Though the domainid information is available with account and domain tables, it
is not able to retrieve this information because of some api semantics. This
bug is logged to track and provide fix for this issue. We can discuss as either
adding a column is apt way or a better way to refactor few apis to get this
information done with out adding extra columns.
*/
public interface PartOf {
/**
* @return domain id that the object belongs to.
*/
long getDomainId();
}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-6871) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 3200, will recycle it and start a new one
Sohal Sharma created CLOUDSTACK-6871: Summary: Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 3200, will recycle it and start a new one Key: CLOUDSTACK-6871 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6871 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.2.1 Environment: Centos 6.5 minimal_64bit Reporter: Sohal Sharma Fix For: 4.2.1 ZoneWideStoragePoolAllocator to find storage pool 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable pools found for volume: Vol[3201|vm=3200|ROOT] under cluster: 1 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable pools found 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable storagePools found under this Cluster: 1 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Searching all possible resources under this Zone: 1 2014-06-09 14:37:57,151 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 2014-06-09 14:37:57,152 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Removing from the clusterId list these clusters from avoid set: [1] 2014-06-09 14:37:57,152 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No clusters found after removing disabled clusters and clusters in avoid list, returning. 2014-06-09 14:37:57,168 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: null 2014-06-09 14:37:57,169 WARN [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Exception while trying to start secondary storage vm com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-3200-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:267) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:696) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) 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:104) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) 2014-06-09 14:37:57,170 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 3200, will recycle it and start a new one -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6871) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 3200, will recycle it and start a new one
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021864#comment-14021864 ] Sohal Sharma commented on CLOUDSTACK-6871: -- If someone know solution of this error log then kindly update via comment on the same. > Unable to start secondary storage vm for standby capacity, secStorageVm vm Id > : 3200, will recycle it and start a new one > - > > Key: CLOUDSTACK-6871 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6871 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.2.1 > Environment: Centos 6.5 minimal_64bit >Reporter: Sohal Sharma > Fix For: 4.2.1 > > > ZoneWideStoragePoolAllocator to find storage pool > 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) No suitable pools found for volume: > Vol[3201|vm=3200|ROOT] under cluster: 1 > 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) No suitable pools found > 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) No suitable storagePools found under this Cluster: 1 > 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) Could not find suitable Deployment Destination for this > VM under any clusters, returning. > 2014-06-09 14:37:57,150 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Searching all possible resources under this Zone: 1 > 2014-06-09 14:37:57,151 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Listing clusters in order of aggregate capacity, that > have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 > 2014-06-09 14:37:57,152 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Removing from the clusterId list these clusters from > avoid set: [1] > 2014-06-09 14:37:57,152 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) No clusters found after removing disabled clusters and > clusters in avoid list, returning. > 2014-06-09 14:37:57,168 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Starting to Stopped with event: > OperationFailedvm's original host id: null new host id: null host id before > state transition: null > 2014-06-09 14:37:57,169 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[SecondaryStorageVm|s-3200-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:267) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:696) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) > 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:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > 2014-06-09 14:37:57,170 IN
[jira] [Created] (CLOUDSTACK-6872) [Hyper-V]Create template T1 from a volume, then deploy V1 from T1, now try to create a template T2 from V1's root volume. It is failing
Abhinav Roy created CLOUDSTACK-6872:
---
Summary: [Hyper-V]Create template T1 from a volume, then deploy
V1 from T1, now try to create a template T2 from V1's root volume. It is failing
Key: CLOUDSTACK-6872
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6872
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, Storage Controller
Affects Versions: 4.4.0
Environment: Hyper-V
Reporter: Abhinav Roy
Priority: Critical
Fix For: 4.4.0
Steps :
1. Deploy Hyper-V advanced zone setup.
2. Create a VM v1 from default centos template.
3. Stop v1 and create template T1 from v1's root volume.
4. create a VM v2 from T1.
5. Stop v2 and create template T2 from v2's root volume.
Expected Behavior :
All the above steps should have succeeded.
Observed Behavior :
Step 5 is failing with the following error :
2014-06-09 15:40:09,269 DEBUG [c.c.a.ApiServlet] (catalina-exec-4:ctx-43436526)
===START=== 10.144.7.13 -- GET
command=createTemplate&response=json&sessionkey=fGX4uIHoj2mx%2BzfKOA579EC%2FQjM%3D&volumeId=d33b806d-8c96-4aff-8e3f-2efa78083a7f&name=tempfromvol-root12&displayText=tempfromvol-root12&osTypeId=a000795a-ebce-11e3-b00a-c264afd952f5&isPublic=true&passwordEnabled=false&isdynamicallyscalable=false&isfeatured=true&_=1402308159938
2014-06-09 15:40:09,296 DEBUG [c.c.t.TemplateManagerImpl]
(catalina-exec-4:ctx-43436526 ctx-b0e507ef) This template is getting created
from other template, setting source template Id to: 202
2014-06-09 15:40:09,367 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-4:ctx-43436526 ctx-b0e507ef) submit async job-122, details:
AsyncJobVO {id:122, userId: 2, accountId: 2, instanceType: Template,
instanceId: 203, cmd:
org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin,
cmdInfo:
{"sessionkey":"fGX4uIHoj2mx+zfKOA579EC/QjM\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","volumeId":"d33b806d-8c96-4aff-8e3f-2efa78083a7f","httpmethod":"GET","osTypeId":"a000795a-ebce-11e3-b00a-c264afd952f5","isPublic":"true","isfeatured":"true","id":"203","isdynamicallyscalable":"false","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":203,\"com.cloud.storage.Volume\":24,\"VirtualMachineTemplate\":\"77913d8e-99f9-43f9-9dd2-a498ebe37d75\",\"com.cloud.storage.GuestOS\":182}","displayText":"tempfromvol-root12","passwordEnabled":"false","name":"tempfromvol-root12","_":"1402308159938","uuid":"77913d8e-99f9-43f9-9dd2-a498ebe37d75","ctxAccountId":"2","ctxStartEventId":"218"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-09 15:40:09,368 DEBUG [c.c.a.ApiServlet] (catalina-exec-4:ctx-43436526
ctx-b0e507ef) ===END=== 10.144.7.13 -- GET
command=createTemplate&response=json&sessionkey=fGX4uIHoj2mx%2BzfKOA579EC%2FQjM%3D&volumeId=d33b806d-8c96-4aff-8e3f-2efa78083a7f&name=tempfromvol-root12&displayText=tempfromvol-root12&osTypeId=a000795a-ebce-11e3-b00a-c264afd952f5&isPublic=true&passwordEnabled=false&isdynamicallyscalable=false&isfeatured=true&_=1402308159938
2014-06-09 15:40:09,370 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-34:ctx-c3c1954c job-122) Add job-122 into job monitoring
2014-06-09 15:40:09,370 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-34:ctx-c3c1954c job-122) Executing AsyncJobVO {id:122,
userId: 2, accountId: 2, instanceType: Template, instanceId: 203, cmd:
org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin,
cmdInfo:
{"sessionkey":"fGX4uIHoj2mx+zfKOA579EC/QjM\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","volumeId":"d33b806d-8c96-4aff-8e3f-2efa78083a7f","httpmethod":"GET","osTypeId":"a000795a-ebce-11e3-b00a-c264afd952f5","isPublic":"true","isfeatured":"true","id":"203","isdynamicallyscalable":"false","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":203,\"com.cloud.storage.Volume\":24,\"VirtualMachineTemplate\":\"77913d8e-99f9-43f9-9dd2-a498ebe37d75\",\"com.cloud.storage.GuestOS\":182}","displayText":"tempfromvol-root12","passwordEnabled":"false","name":"tempfromvol-root12","_":"1402308159938","uuid":"77913d8e-99f9-43f9-9dd2-a498ebe37d75","ctxAccountId":"2","ctxStartEventId":"218"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-09 15:40:09,378 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-34:ctx-c3c1954c job-122 ctx-ad188c83) Received unknown
parameters for command createTemplate. Unknown parameters : ct
[jira] [Commented] (CLOUDSTACK-6727) [Automation] Deployment of Virtual Machine is failing on Xenserver host causing many BVT test cases to fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021870#comment-14021870
]
Abhinandan Prateek commented on CLOUDSTACK-6727:
The template issues are now fixed.
> [Automation] Deployment of Virtual Machine is failing on Xenserver host
> causing many BVT test cases to fail
> ---
>
> Key: CLOUDSTACK-6727
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6727
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server
>Affects Versions: 4.4.0
>Reporter: Syed Mohtashim Ahmad
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: management-server.zip
>
>
> {noformat}
> There are many test cases failing one of them is
> test_nic_secondaryip_add_remove test case in test_multipleips_per_nic.py
> Management server logs are also attached
> Execute cmd: deployvirtualmachine failed, due to: errorCode: 431,
> errorText:Unable to find network by id 206
> >> begin captured stdout << -
> === TestName: test_nic_secondaryip_add_remove | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Payload:
> {'signature': 'CVZAuHBDhvRBjxJXCQeTZxXyE0k=', 'apiKey':
> u'1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA',
> 'command': 'deleteAccount', 'id': u'f4389b5a-c880-4107-8dcf-1e2881d86c75',
> 'response': 'json'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Sending
> GET Cmd : deleteAccount===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.220.80.13
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=CVZAuHBDhvRBjxJXCQeTZxXyE0k%3D&apiKey=1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA&command=deleteAccount&id=f4389b5a-c880-4107-8dcf-1e2881d86c75&response=json
> HTTP/1.1" 200 78
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: === Jobid:
> 4fed98d8-e929-4853-b8ba-4364f4dd00e7 Started ===
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Payload:
> {'signature': 'oUrKKe/zdGFzDPbcRzqnHwyTE28=', 'apiKey':
> u'1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'4fed98d8-e929-4853-b8ba-4364f4dd00e7'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Sending
> GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.220.80.13
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=oUrKKe%2FzdGFzDPbcRzqnHwyTE28%3D&apiKey=1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA&command=queryAsyncJobResult&response=json&jobid=4fed98d8-e929-4853-b8ba-4364f4dd00e7
> HTTP/1.1" 200 343
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Response :
> {jobprocstatus : 0, created : u'2014-05-20T12:07:47+', cmd :
> u'org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd', userid :
> u'eea15962-e011-11e3-a4b4-9e7c113c3a29', jobstatus : 0, jobid :
> u'4fed98d8-e929-4853-b8ba-4364f4dd00e7', jobresultcode : 0, accountid :
> u'eea1474c-e011-11e3-a4b4-9e7c113c3a29'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: ===
> JobId:4fed98d8-e929-4853-b8ba-4364f4dd00e7 is Still Processing, Will TimeOut
> in:3595
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Payload:
> {'signature': 'oUrKKe/zdGFzDPbcRzqnHwyTE28=', 'apiKey':
> u'1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'4fed98d8-e929-4853-b8ba-4364f4dd00e7'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Sending
> GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.220.80.13
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=oUrKKe%2FzdGFzDPbcRzqnHwyTE28%3D&apiKey=1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA&command=queryAsyncJobResult&response=json&jobid=4fed98d8-e929-4853-b8ba-4364f4dd00e7
> HTTP/1.1" 200 397
> test_06_copy_iso (integration.smoke.test_iso.Tes
[jira] [Resolved] (CLOUDSTACK-6727) [Automation] Deployment of Virtual Machine is failing on Xenserver host causing many BVT test cases to fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek resolved CLOUDSTACK-6727.
Resolution: Fixed
> [Automation] Deployment of Virtual Machine is failing on Xenserver host
> causing many BVT test cases to fail
> ---
>
> Key: CLOUDSTACK-6727
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6727
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server
>Affects Versions: 4.4.0
>Reporter: Syed Mohtashim Ahmad
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: management-server.zip
>
>
> {noformat}
> There are many test cases failing one of them is
> test_nic_secondaryip_add_remove test case in test_multipleips_per_nic.py
> Management server logs are also attached
> Execute cmd: deployvirtualmachine failed, due to: errorCode: 431,
> errorText:Unable to find network by id 206
> >> begin captured stdout << -
> === TestName: test_nic_secondaryip_add_remove | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Payload:
> {'signature': 'CVZAuHBDhvRBjxJXCQeTZxXyE0k=', 'apiKey':
> u'1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA',
> 'command': 'deleteAccount', 'id': u'f4389b5a-c880-4107-8dcf-1e2881d86c75',
> 'response': 'json'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Sending
> GET Cmd : deleteAccount===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.220.80.13
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=CVZAuHBDhvRBjxJXCQeTZxXyE0k%3D&apiKey=1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA&command=deleteAccount&id=f4389b5a-c880-4107-8dcf-1e2881d86c75&response=json
> HTTP/1.1" 200 78
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: === Jobid:
> 4fed98d8-e929-4853-b8ba-4364f4dd00e7 Started ===
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Payload:
> {'signature': 'oUrKKe/zdGFzDPbcRzqnHwyTE28=', 'apiKey':
> u'1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'4fed98d8-e929-4853-b8ba-4364f4dd00e7'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Sending
> GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.220.80.13
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=oUrKKe%2FzdGFzDPbcRzqnHwyTE28%3D&apiKey=1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA&command=queryAsyncJobResult&response=json&jobid=4fed98d8-e929-4853-b8ba-4364f4dd00e7
> HTTP/1.1" 200 343
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Response :
> {jobprocstatus : 0, created : u'2014-05-20T12:07:47+', cmd :
> u'org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd', userid :
> u'eea15962-e011-11e3-a4b4-9e7c113c3a29', jobstatus : 0, jobid :
> u'4fed98d8-e929-4853-b8ba-4364f4dd00e7', jobresultcode : 0, accountid :
> u'eea1474c-e011-11e3-a4b4-9e7c113c3a29'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: ===
> JobId:4fed98d8-e929-4853-b8ba-4364f4dd00e7 is Still Processing, Will TimeOut
> in:3595
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Payload:
> {'signature': 'oUrKKe/zdGFzDPbcRzqnHwyTE28=', 'apiKey':
> u'1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'4fed98d8-e929-4853-b8ba-4364f4dd00e7'}
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Sending
> GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.220.80.13
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=oUrKKe%2FzdGFzDPbcRzqnHwyTE28%3D&apiKey=1icw25VMYy1cFaf2Y92-X49fBWabij_OBk70QARr_a0h6dMxQkXN16Fzb3EcbUHLLbEujC6YnXpnApiRtVB7TA&command=queryAsyncJobResult&response=json&jobid=4fed98d8-e929-4853-b8ba-4364f4dd00e7
> HTTP/1.1" 200 397
> test_06_copy_iso (integration.smoke.test_iso.TestISO): DEBUG: Response :
> {jobprocstatus : 0, created : u'2014-05-
[jira] [Updated] (CLOUDSTACK-6872) [Hyper-V]Create template T1 from a volume, then deploy V1 from T1, now try to create a template T2 from V1's root volume. It is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Roy updated CLOUDSTACK-6872:
Attachment: CS-6872.zip
Attaching MS logs and DB dump
> [Hyper-V]Create template T1 from a volume, then deploy V1 from T1, now try
> to create a template T2 from V1's root volume. It is failing
>
>
> Key: CLOUDSTACK-6872
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6872
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Storage Controller
>Affects Versions: 4.4.0
> Environment: Hyper-V
>Reporter: Abhinav Roy
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
> Attachments: CS-6872.zip
>
>
> Steps :
>
> 1. Deploy Hyper-V advanced zone setup.
> 2. Create a VM v1 from default centos template.
> 3. Stop v1 and create template T1 from v1's root volume.
> 4. create a VM v2 from T1.
> 5. Stop v2 and create template T2 from v2's root volume.
> Expected Behavior :
>
> All the above steps should have succeeded.
> Observed Behavior :
>
> Step 5 is failing with the following error :
> 2014-06-09 15:40:09,269 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-4:ctx-43436526) ===START=== 10.144.7.13 -- GET
> command=createTemplate&response=json&sessionkey=fGX4uIHoj2mx%2BzfKOA579EC%2FQjM%3D&volumeId=d33b806d-8c96-4aff-8e3f-2efa78083a7f&name=tempfromvol-root12&displayText=tempfromvol-root12&osTypeId=a000795a-ebce-11e3-b00a-c264afd952f5&isPublic=true&passwordEnabled=false&isdynamicallyscalable=false&isfeatured=true&_=1402308159938
> 2014-06-09 15:40:09,296 DEBUG [c.c.t.TemplateManagerImpl]
> (catalina-exec-4:ctx-43436526 ctx-b0e507ef) This template is getting created
> from other template, setting source template Id to: 202
> 2014-06-09 15:40:09,367 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-4:ctx-43436526 ctx-b0e507ef) submit async job-122, details:
> AsyncJobVO {id:122, userId: 2, accountId: 2, instanceType: Template,
> instanceId: 203, cmd:
> org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin,
> cmdInfo:
> {"sessionkey":"fGX4uIHoj2mx+zfKOA579EC/QjM\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","volumeId":"d33b806d-8c96-4aff-8e3f-2efa78083a7f","httpmethod":"GET","osTypeId":"a000795a-ebce-11e3-b00a-c264afd952f5","isPublic":"true","isfeatured":"true","id":"203","isdynamicallyscalable":"false","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":203,\"com.cloud.storage.Volume\":24,\"VirtualMachineTemplate\":\"77913d8e-99f9-43f9-9dd2-a498ebe37d75\",\"com.cloud.storage.GuestOS\":182}","displayText":"tempfromvol-root12","passwordEnabled":"false","name":"tempfromvol-root12","_":"1402308159938","uuid":"77913d8e-99f9-43f9-9dd2-a498ebe37d75","ctxAccountId":"2","ctxStartEventId":"218"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-06-09 15:40:09,368 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-4:ctx-43436526 ctx-b0e507ef) ===END=== 10.144.7.13 -- GET
> command=createTemplate&response=json&sessionkey=fGX4uIHoj2mx%2BzfKOA579EC%2FQjM%3D&volumeId=d33b806d-8c96-4aff-8e3f-2efa78083a7f&name=tempfromvol-root12&displayText=tempfromvol-root12&osTypeId=a000795a-ebce-11e3-b00a-c264afd952f5&isPublic=true&passwordEnabled=false&isdynamicallyscalable=false&isfeatured=true&_=1402308159938
> 2014-06-09 15:40:09,370 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-34:ctx-c3c1954c job-122) Add job-122 into job monitoring
> 2014-06-09 15:40:09,370 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-34:ctx-c3c1954c job-122) Executing AsyncJobVO {id:122,
> userId: 2, accountId: 2, instanceType: Template, instanceId: 203, cmd:
> org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin,
> cmdInfo:
> {"sessionkey":"fGX4uIHoj2mx+zfKOA579EC/QjM\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","volumeId":"d33b806d-8c96-4aff-8e3f-2efa78083a7f","httpmethod":"GET","osTypeId":"a000795a-ebce-11e3-b00a-c264afd952f5","isPublic":"true","isfeatured":"true","id":"203","isdynamicallyscalable":"false","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":203,\"com.cloud.storage.Volume\":24,\"VirtualMachineTemplate\":\"77913d8e-99f9-43f9-9dd2-a498ebe37d75\",\"com.cloud.storage.GuestOS\":182}","displayText":"tempfromvol-root12","passwordEnabled":"false","name":"tempfromvol-root12","_":"140230
[jira] [Resolved] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6793. - Resolution: Fixed > [Automation] CreateTagsCmd fails with db exceptions > > > Key: CLOUDSTACK-6793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar > > > Steps to reproduce > Execute the test case integration.component.test_tags.TestResourceTags > Test case perform below steps > # 1. Create a tag on template/ISO using createTags API > # 2. Delete above created tag using deleteTags API > 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] > (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END=== > 10.223.240.193 -- GET > apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd > EQ&resourcetype=Template&resourceIds=35e10eef-7980-4085-8b6c-c68174f1b529&command=createTags&signature=pIJSk7ekg0Tlf > RN%2FWfdp8U42Bgs%3D&tags%5B0%5D.key=OS&response=json&tags%5B0%5D.value=CentOS > 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin > g back the transaction: Time = 4 Name = API-Job-Executor-89; called by > -TransactionLegacy.rollback:903-TransactionL > egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation. > proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2 > 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn > Transaction:25-Transaction$2.doInTransaction:49 > 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] > (catalina-exec-22:ctx-dbbc3135) ===START=== 10.223.240.193 -- GET > > jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642&apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z > 1t-oO1g9F4-EiUZx9BdEQ&command=queryAsyncJobResult&response=json&signature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D > 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while > executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags > (resource_tags.uuid, resource_tags.key, resource_tags.value, > resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, > resource_tags.resource_uuid, resource_tags.resource_type, > resource_tags.customer) VALUES > (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', > -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null) > at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400) > at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at com.sun.proxy.$Proxy52.persist(Unknown Source) > at > com.cloud.tags.TaggedResourceManagerImpl$1.doInTransactionWithoutResult(TaggedResourceManagerImpl.java:245) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49
[jira] [Commented] (CLOUDSTACK-6603) [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021875#comment-14021875 ] ASF subversion and git services commented on CLOUDSTACK-6603: - Commit c282bb3a1293fbbfdb306263ea52464862670fb3 in cloudstack's branch refs/heads/4.4-forward from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c282bb3 ] CLOUDSTACK-6603 [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to 4.4 > [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to > 4.4 > > > Key: CLOUDSTACK-6603 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6603 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.4.0 >Reporter: manasaveloori >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar, mysqldump43.dmp, mysqldump44.dmp > > > 1. Deploy CS 4.3 with 2 zones using xen 6.1 and KVM hypervisor. > 2. Configured LB rules,firewall rules. > 3. Registered the template for 4.4 (using the naming convention > systemvm-xenserver-4.4,systemvm-kvm-4.4) > 4. Upgraded to 4.4 > Start the management server: > Below are the observations: > 2014-05-05 05:05:13,567 DEBUG [c.c.s.StatsCollector] > (StatsCollector-4:ctx-e36f20e1) AutoScaling Monitor is running... > 2014-05-05 05:05:13,577 ERROR [c.c.s.StatsCollector] > (StatsCollector-4:ctx-e36f20e1) Error trying to monitor autoscaling > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@5b140551: SELECT autoscale_vmgroups.id, > autoscale_vmgroups.uuid, autoscale_vmgroups.zone_id, > autoscale_vmgroups.domain_id, autoscale_vmgroups.account_id, > autoscale_vmgroups.load_balancer_id, autoscale_vmgroups.min_members, > autoscale_vmgroups.max_members, autoscale_vmgroups.member_port, > autoscale_vmgroups.interval, autoscale_vmgroups.last_interval, > autoscale_vmgroups.profile_id, autoscale_vmgroups.removed, > autoscale_vmgroups.created, autoscale_vmgroups.state, > autoscale_vmgroups.display FROM autoscale_vmgroups WHERE > autoscale_vmgroups.removed IS NULL > at com.cloud.utils.db.GenericDaoBase.executeList(GenericDaoBase.java:1127) > at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1150) > at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1136) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at com.sun.proxy.$Proxy220.listAll(Unknown Source) > at > com.cloud.server.StatsCollector$AutoScaleMonitor.runInContext(StatsCollector.java:673) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$Scheduled
[jira] [Commented] (CLOUDSTACK-6708) [Automation]: Few suites were failing on simulator run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021876#comment-14021876 ] Koushik Das commented on CLOUDSTACK-6708: - integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure is not yet fixed as part of this. This test is based on simulator mocks, which can be scoped to a zone, pod, cluster or host. The mock gets executed for any test that targets the specific host for which mock is defined. Due to this, tests using mock needs to be executed in sequence otherwise it may interfere with other tests and cause random failures. The current test framework always executes tests in parallel and needs to be fixed to execute selective tests in sequence. I will create a separate bug for it. > [Automation]: Few suites were failing on simulator run > -- > > Key: CLOUDSTACK-6708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6708 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure > integration.smoke.test_hosts.TestHosts.test_01_clusters > integration.smoke.test_network.TestDeleteAccount.test_delete_account > integration.smoke.test_network.TestPublicIP.test_public_ip_admin_account > integration.smoke.test_network.TestReleaseIP.test_releaseIP > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_08_migrate_vm > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6874) automation test failures.
Bharat Kumar created CLOUDSTACK-6874: Summary: automation test failures. Key: CLOUDSTACK-6874 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6874 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Bharat Kumar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6873) [Automation] Ability to execute tests in sequence
Koushik Das created CLOUDSTACK-6873: --- Summary: [Automation] Ability to execute tests in sequence Key: CLOUDSTACK-6873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6873 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Koushik Das Assignee: Abhinandan Prateek Fix For: 4.5.0 Currently BVT/regression tests are executed in parallel by the test infrastructure. It needs to be enhanced to add capability to execute a selective set of tests in sequence. Specific scenario is tests that uses simulator mocks. These mocks are scoped to a zone, pod, cluster or host. Once defined any tests targeting a specific host will execute as per the mocks defined. Now in the current framework it is not possible to prevent existing tests from going to a specific host. As a result there needs to be a capability to execute a specific set of test cases in sequence. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6873) [Automation] Ability to execute tests in sequence
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021893#comment-14021893 ] ASF subversion and git services commented on CLOUDSTACK-6873: - Commit 89a03c7099fb5f0d6a3a892b036d064bfc2acb71 in cloudstack's branch refs/heads/4.4-forward from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=89a03c7 ] CLOUDSTACK-6873: Tagged tests based on the limitation described in the bug > [Automation] Ability to execute tests in sequence > - > > Key: CLOUDSTACK-6873 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6873 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Koushik Das >Assignee: Abhinandan Prateek > Fix For: 4.5.0 > > > Currently BVT/regression tests are executed in parallel by the test > infrastructure. It needs to be enhanced to add capability to execute a > selective set of tests in sequence. > Specific scenario is tests that uses simulator mocks. These mocks are scoped > to a zone, pod, cluster or host. Once defined any tests targeting a specific > host will execute as per the mocks defined. Now in the current framework it > is not possible to prevent existing tests from going to a specific host. As a > result there needs to be a capability to execute a specific set of test cases > in sequence. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6869) Public key content is overridden by template's meta data when you create a instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala updated CLOUDSTACK-6869:
Priority: Critical (was: Blocker)
> Public key content is overridden by template's meta data when you create a
> instance
> ---
>
> Key: CLOUDSTACK-6869
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6869
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server, Template
>Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0
>Reporter: Hiroki Ohashi
>Priority: Critical
>
> A public key content is overridden by detail value of 'SSH.PublicKey' from a
> template created by an instance ROOT volume with public key specification.
> This results in delivery of the template owner's ssh key for a instance
> created from the template to virtual router inspite of specification of
> instance owner's ssh key.
> It is caused by import of resource detail values at commitUserVm method like
> below.
> {code}
> Map details = template.getDetails();
> if (details != null && !details.isEmpty()) {
> vm.details.putAll(details);
> }
> {code}
> Reproduction procedure:
> # Deploy an instance with a ssh key A by specifying 'keypair' value.
> # Create a template from this instance.
> # Deploy an instance with another ssh key B by specifying 'keypair' value.
> Database example:
> {noformat}
> mysql> select * from cloud.template_view where id=207 \G;
> *** 1. row ***
> id: 207
> uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
> unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
> name: cluster_frontend-20140520.2
> public: 1
> featured: 0
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: QCOW2
> created: 2014-05-20 09:33:47
> checksum: NULL
> display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
> enable_password: 1
> dynamically_scalable: 0
> template_state: Active
> guest_os_id: 182
>guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
>guest_os_name: CentOS 6.4 (64-bit)
> bootable: 1
> prepopulate: 0
> cross_zones: 0
> hypervisor_type: KVM
> extractable: 0
> template_tag: NULL
> sort_key: 0
> removed: NULL
>enable_sshkey: 0
> source_template_id: 205
> source_template_uuid: c131680c-3e0e-4d7c-b554-02dabc10ade1
> account_id: 3
> account_uuid: f9e4e1ca-69fd-4ae3-b70c-15bbcc13406e
> account_name: sgcadm
> account_type: 0
>domain_id: 2
> domain_uuid: 84dd635d-fb99-4895-b199-7d777aa144d5
> domain_name: default
> domain_path: /default/
> project_id: NULL
> project_uuid: NULL
> project_name: NULL
> data_center_id: NULL
> data_center_uuid: NULL
> data_center_name: NULL
>lp_account_id: NULL
> store_id: 3
> store_scope: REGION
>state: Ready
> download_state: DOWNLOADED
> download_pct: 100
>error_str: NULL
> size: 18465816576
>destroyed: 0
> created_on_store: 2014-05-20 09:33:47
> detail_name: Message.ReservedCapacityFreed.Flag
> detail_value: false
> tag_id: NULL
> tag_uuid: NULL
> tag_key: NULL
>tag_value: NULL
>tag_domain_id: NULL
> tag_account_id: NULL
> tag_resource_id: NULL
>tag_resource_uuid: NULL
>tag_resource_type: NULL
> tag_customer: NULL
> temp_zone_pair: 207_0
> *** 2. row ***
> id: 207
> uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
> unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
> name: cluster_frontend-20140520.2
> public: 1
> featured: 0
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: QCOW2
> created: 2014-05-20 09:33:47
> checksum: NULL
> display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
> enable_password: 1
> dynamically_scalable: 0
> template_state: Active
> guest_os_id: 182
>guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
>guest_os_name: CentOS 6.4 (64-bit)
>
[jira] [Assigned] (CLOUDSTACK-6869) Public key content is overridden by template's meta data when you create a instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala reassigned CLOUDSTACK-6869:
---
Assignee: Harikrishna Patnala
> Public key content is overridden by template's meta data when you create a
> instance
> ---
>
> Key: CLOUDSTACK-6869
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6869
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server, Template
>Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0
>Reporter: Hiroki Ohashi
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.4.0, 4.5.0
>
>
> A public key content is overridden by detail value of 'SSH.PublicKey' from a
> template created by an instance ROOT volume with public key specification.
> This results in delivery of the template owner's ssh key for a instance
> created from the template to virtual router inspite of specification of
> instance owner's ssh key.
> It is caused by import of resource detail values at commitUserVm method like
> below.
> {code}
> Map details = template.getDetails();
> if (details != null && !details.isEmpty()) {
> vm.details.putAll(details);
> }
> {code}
> Reproduction procedure:
> # Deploy an instance with a ssh key A by specifying 'keypair' value.
> # Create a template from this instance.
> # Deploy an instance with another ssh key B by specifying 'keypair' value.
> Database example:
> {noformat}
> mysql> select * from cloud.template_view where id=207 \G;
> *** 1. row ***
> id: 207
> uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
> unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
> name: cluster_frontend-20140520.2
> public: 1
> featured: 0
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: QCOW2
> created: 2014-05-20 09:33:47
> checksum: NULL
> display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
> enable_password: 1
> dynamically_scalable: 0
> template_state: Active
> guest_os_id: 182
>guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
>guest_os_name: CentOS 6.4 (64-bit)
> bootable: 1
> prepopulate: 0
> cross_zones: 0
> hypervisor_type: KVM
> extractable: 0
> template_tag: NULL
> sort_key: 0
> removed: NULL
>enable_sshkey: 0
> source_template_id: 205
> source_template_uuid: c131680c-3e0e-4d7c-b554-02dabc10ade1
> account_id: 3
> account_uuid: f9e4e1ca-69fd-4ae3-b70c-15bbcc13406e
> account_name: sgcadm
> account_type: 0
>domain_id: 2
> domain_uuid: 84dd635d-fb99-4895-b199-7d777aa144d5
> domain_name: default
> domain_path: /default/
> project_id: NULL
> project_uuid: NULL
> project_name: NULL
> data_center_id: NULL
> data_center_uuid: NULL
> data_center_name: NULL
>lp_account_id: NULL
> store_id: 3
> store_scope: REGION
>state: Ready
> download_state: DOWNLOADED
> download_pct: 100
>error_str: NULL
> size: 18465816576
>destroyed: 0
> created_on_store: 2014-05-20 09:33:47
> detail_name: Message.ReservedCapacityFreed.Flag
> detail_value: false
> tag_id: NULL
> tag_uuid: NULL
> tag_key: NULL
>tag_value: NULL
>tag_domain_id: NULL
> tag_account_id: NULL
> tag_resource_id: NULL
>tag_resource_uuid: NULL
>tag_resource_type: NULL
> tag_customer: NULL
> temp_zone_pair: 207_0
> *** 2. row ***
> id: 207
> uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
> unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
> name: cluster_frontend-20140520.2
> public: 1
> featured: 0
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: QCOW2
> created: 2014-05-20 09:33:47
> checksum: NULL
> display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
> enable_password: 1
> dynamically_scalable: 0
> template_state: Active
> guest_os_id: 182
>guest_os_uuid: 9d3c42d8-caab
[jira] [Updated] (CLOUDSTACK-6869) Public key content is overridden by template's meta data when you create a instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala updated CLOUDSTACK-6869:
Fix Version/s: 4.5.0
4.4.0
> Public key content is overridden by template's meta data when you create a
> instance
> ---
>
> Key: CLOUDSTACK-6869
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6869
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server, Template
>Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0
>Reporter: Hiroki Ohashi
>Priority: Critical
> Fix For: 4.4.0, 4.5.0
>
>
> A public key content is overridden by detail value of 'SSH.PublicKey' from a
> template created by an instance ROOT volume with public key specification.
> This results in delivery of the template owner's ssh key for a instance
> created from the template to virtual router inspite of specification of
> instance owner's ssh key.
> It is caused by import of resource detail values at commitUserVm method like
> below.
> {code}
> Map details = template.getDetails();
> if (details != null && !details.isEmpty()) {
> vm.details.putAll(details);
> }
> {code}
> Reproduction procedure:
> # Deploy an instance with a ssh key A by specifying 'keypair' value.
> # Create a template from this instance.
> # Deploy an instance with another ssh key B by specifying 'keypair' value.
> Database example:
> {noformat}
> mysql> select * from cloud.template_view where id=207 \G;
> *** 1. row ***
> id: 207
> uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
> unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
> name: cluster_frontend-20140520.2
> public: 1
> featured: 0
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: QCOW2
> created: 2014-05-20 09:33:47
> checksum: NULL
> display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
> enable_password: 1
> dynamically_scalable: 0
> template_state: Active
> guest_os_id: 182
>guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
>guest_os_name: CentOS 6.4 (64-bit)
> bootable: 1
> prepopulate: 0
> cross_zones: 0
> hypervisor_type: KVM
> extractable: 0
> template_tag: NULL
> sort_key: 0
> removed: NULL
>enable_sshkey: 0
> source_template_id: 205
> source_template_uuid: c131680c-3e0e-4d7c-b554-02dabc10ade1
> account_id: 3
> account_uuid: f9e4e1ca-69fd-4ae3-b70c-15bbcc13406e
> account_name: sgcadm
> account_type: 0
>domain_id: 2
> domain_uuid: 84dd635d-fb99-4895-b199-7d777aa144d5
> domain_name: default
> domain_path: /default/
> project_id: NULL
> project_uuid: NULL
> project_name: NULL
> data_center_id: NULL
> data_center_uuid: NULL
> data_center_name: NULL
>lp_account_id: NULL
> store_id: 3
> store_scope: REGION
>state: Ready
> download_state: DOWNLOADED
> download_pct: 100
>error_str: NULL
> size: 18465816576
>destroyed: 0
> created_on_store: 2014-05-20 09:33:47
> detail_name: Message.ReservedCapacityFreed.Flag
> detail_value: false
> tag_id: NULL
> tag_uuid: NULL
> tag_key: NULL
>tag_value: NULL
>tag_domain_id: NULL
> tag_account_id: NULL
> tag_resource_id: NULL
>tag_resource_uuid: NULL
>tag_resource_type: NULL
> tag_customer: NULL
> temp_zone_pair: 207_0
> *** 2. row ***
> id: 207
> uuid: c96f0d9a-0a56-4d30-af73-fe8b31ae37c3
> unique_name: 2219faa5a-4e7b-3425-b6e6-135ab210422b
> name: cluster_frontend-20140520.2
> public: 1
> featured: 0
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: QCOW2
> created: 2014-05-20 09:33:47
> checksum: NULL
> display_text: Cluster Frontend VM CentOS 6.5 ver.20140520.2
> enable_password: 1
> dynamically_scalable: 0
> template_state: Active
> guest_os_id: 182
>guest_os_uuid: 9d3c42d8-caab-11e3-9125-001e679910a0
>
[jira] [Created] (CLOUDSTACK-6875) test_volumes is failing on simulator runs
Bharat Kumar created CLOUDSTACK-6875:
Summary: test_volumes is failing on simulator runs
Key: CLOUDSTACK-6875
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6875
Project: CloudStack
Issue Type: Sub-task
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation
Reporter: Bharat Kumar
Error Message
Job failed: {jobprocstatus : 0, created : u'2014-06-08T20:26:20-0700', cmd :
u'org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin',
userid : u'36a2cda6-ef83-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
u'b263a941-29b1-4ab8-9c00-7a0d2678b591', jobresultcode : 530, jobresulttype :
u'object', jobresult : {errorcode : 530, errortext : u'Unexpected exception'},
accountid : u'36a29ade-ef83-11e3-a86b-00163e0af42c'}
>> begin captured stdout << -
=== TestName: test_09_delete_detached_volume | Status : EXCEPTION ===
- >> end captured stdout << --
>> begin captured logging <<
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: STARTED : TC: test_09_delete_detached_volume :::
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Delete Volume ID: 24051890-92ad-4cee-8ca3-119d278b072a
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Payload: {'account': u'test-account-TestCreateVolume-N2SRV2',
'domainid': u'36a27fb8-ef83-11e3-a86b-00163e0af42c', 'name': 'Test Volume',
'zoneid': u'ef5040e4-6e78-433b-a21a-656a7ab31e80', 'apiKey':
u'Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ',
'command': 'createVolume', 'signature': 'O0mZxBTYte8bIWPhtBYKUycq8Yo=',
'diskofferingid': u'92b2888e-c624-4042-82b4-632bed2bb38d', 'response': 'json'}
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Sending GET Cmd : createVolume===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.23
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?account=test-account-TestCreateVolume-N2SRV2&domainid=36a27fb8-ef83-11e3-a86b-00163e0af42c&name=Test+Volume&zoneid=ef5040e4-6e78-433b-a21a-656a7ab31e80&apiKey=Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ&command=createVolume&signature=O0mZxBTYte8bIWPhtBYKUycq8Yo%3D&diskofferingid=92b2888e-c624-4042-82b4-632bed2bb38d&response=json
HTTP/1.1" 200 121
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: === Jobid: 2249fb73-7560-4d22-a7f9-dba0507b096e Started ===
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Payload: {'signature': '8di/lZIPnn9qCgFh0fHVVrH7/8U=', 'apiKey':
u'Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ',
'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
u'2249fb73-7560-4d22-a7f9-dba0507b096e'}
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Sending GET Cmd : queryAsyncJobResult===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.23
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?jobid=2249fb73-7560-4d22-a7f9-dba0507b096e&apiKey=Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ&command=queryAsyncJobResult&response=json&signature=8di%2FlZIPnn9qCgFh0fHVVrH7%2F8U%3D
HTTP/1.1" 200 430
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Response : {jobprocstatus : 0, created : u'2014-06-08T20:26:14-0700',
cmd : u'org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin',
userid : u'36a2cda6-ef83-11e3-a86b-00163e0af42c', jobstatus : 0, jobid :
u'2249fb73-7560-4d22-a7f9-dba0507b096e', jobresultcode : 0, jobinstanceid :
u'c936802c-42f3-4ff3-9eb2-dd003517a8ef', jobinstancetype : u'Volume', accountid
: u'36a29ade-ef83-11e3-a86b-00163e0af42c'}
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: === JobId:2249fb73-7560-4d22-a7f9-dba0507b096e is Still Processing, Will
TimeOut in:3595
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Payload: {'signature': '8di/lZIPnn9qCgFh0fHVVrH7/8U=', 'apiKey':
u'Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ',
'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
u'2249fb73-7560-4d22-a7f9-dba0507b096e'}
test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Sending GET Cmd : queryAsyncJobResult===
requests.packages.urllib3.connectionpool: INFO: Starting new
[jira] [Updated] (CLOUDSTACK-6876) test_deploy_vgpu_enabled_vm is failing on xen and Kvm runs.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar updated CLOUDSTACK-6876:
-
Summary: test_deploy_vgpu_enabled_vm is failing on xen and Kvm runs. (was:
test_deploy_vgpu_enabled_vm is failing on xen and ivm runs.)
> test_deploy_vgpu_enabled_vm is failing on xen and Kvm runs.
> ---
>
> Key: CLOUDSTACK-6876
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6876
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Bharat Kumar
>
> Error Message
> Execute cmd: createserviceoffering failed, due to: errorCode: 401,
> errorText:unable to verify user credentials and/or request signature
> >> begin captured stdout << -
> === TestName: test_deploy_vgpu_enabled_vm | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: STARTED : TC: test_deploy_vgpu_enabled_vm :::
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Payload: {'apiKey':
> u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
> 'command': 'listDomains', 'signature': 'lalPSnJlAM6GkRDFC2sNKSa5T+o=',
> 'response': 'json'}
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Sending GET Cmd : listDomains===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listDomains&response=json&signature=lalPSnJlAM6GkRDFC2sNKSa5T%2Bo%3D
> HTTP/1.1" 200 159
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Response : [{path : u'ROOT', haschild : False, id :
> u'b5e7af36-ef7f-11e3-a141-00163e189e44', name : u'ROOT', level : 0}]
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Payload: {'apiKey':
> u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
> 'name': 'zone-xen', 'command': 'listZones', 'signature':
> 'TFpPtnJ8uzOTOnEQ53yyluY5Ed0=', 'response': 'json'}
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listZones&name=zone-xen&signature=TFpPtnJ8uzOTOnEQ53yyluY5Ed0%3D
> HTTP/1.1" 200 446
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Response : [{localstorageenabled : False, name : u'zone-xen',
> guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
> u'21715335-f736-3016-9d97-0765620600c0', dns2 : u'8.8.4.4', dns1 :
> u'8.8.8.8', securitygroupsenabled : False, allocationstate : u'Enabled',
> internaldns1 : u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype :
> u'Advanced', id : u'243eb08f-31e9-4283-953b-52578d8b1c6a', internaldns2 :
> u'172.16.88.8'}]
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Payload: {'apiKey':
> u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
> 'templatefilter': 'featured', 'command': 'listTemplates', 'signature':
> 'eIj8lFw1ONlBOoquO50AKcXIBEI=', 'zoneid':
> u'243eb08f-31e9-4283-953b-52578d8b1c6a', 'response': 'json'}
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Sending GET Cmd : listTemplates===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?templatefilter=featured&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&zoneid=243eb08f-31e9-4283-953b-52578d8b1c6a&command=listTemplates&signature=eIj8lFw1ONlBOoquO50AKcXIBEI%3D&response=json
> HTTP/1.1" 200 818
> test_deploy_vg
[jira] [Created] (CLOUDSTACK-6876) test_deploy_vgpu_enabled_vm is failing on xen and ivm runs.
Bharat Kumar created CLOUDSTACK-6876:
Summary: test_deploy_vgpu_enabled_vm is failing on xen and ivm
runs.
Key: CLOUDSTACK-6876
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6876
Project: CloudStack
Issue Type: Sub-task
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Bharat Kumar
Error Message
Execute cmd: createserviceoffering failed, due to: errorCode: 401,
errorText:unable to verify user credentials and/or request signature
>> begin captured stdout << -
=== TestName: test_deploy_vgpu_enabled_vm | Status : EXCEPTION ===
- >> end captured stdout << --
>> begin captured logging <<
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
STARTED : TC: test_deploy_vgpu_enabled_vm :::
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Payload: {'apiKey':
u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
'command': 'listDomains', 'signature': 'lalPSnJlAM6GkRDFC2sNKSa5T+o=',
'response': 'json'}
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Sending GET Cmd : listDomains===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listDomains&response=json&signature=lalPSnJlAM6GkRDFC2sNKSa5T%2Bo%3D
HTTP/1.1" 200 159
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Response : [{path : u'ROOT', haschild : False, id :
u'b5e7af36-ef7f-11e3-a141-00163e189e44', name : u'ROOT', level : 0}]
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Payload: {'apiKey':
u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
'name': 'zone-xen', 'command': 'listZones', 'signature':
'TFpPtnJ8uzOTOnEQ53yyluY5Ed0=', 'response': 'json'}
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Sending GET Cmd : listZones===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?response=json&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listZones&name=zone-xen&signature=TFpPtnJ8uzOTOnEQ53yyluY5Ed0%3D
HTTP/1.1" 200 446
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Response : [{localstorageenabled : False, name : u'zone-xen', guestcidraddress
: u'10.1.1.0/24', tags : [], zonetoken :
u'21715335-f736-3016-9d97-0765620600c0', dns2 : u'8.8.4.4', dns1 : u'8.8.8.8',
securitygroupsenabled : False, allocationstate : u'Enabled', internaldns1 :
u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype : u'Advanced', id
: u'243eb08f-31e9-4283-953b-52578d8b1c6a', internaldns2 : u'172.16.88.8'}]
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Payload: {'apiKey':
u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
'templatefilter': 'featured', 'command': 'listTemplates', 'signature':
'eIj8lFw1ONlBOoquO50AKcXIBEI=', 'zoneid':
u'243eb08f-31e9-4283-953b-52578d8b1c6a', 'response': 'json'}
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Sending GET Cmd : listTemplates===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?templatefilter=featured&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&zoneid=243eb08f-31e9-4283-953b-52578d8b1c6a&command=listTemplates&signature=eIj8lFw1ONlBOoquO50AKcXIBEI%3D&response=json
HTTP/1.1" 200 818
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM): DEBUG:
Response : [{domain : u'ROOT', domainid :
u'b5e7af36-ef7f-11e3-a141-00163e189e44', ostypename : u'CentOS 5.6 (64-bit)',
zoneid : u'243eb08f-31e9-4283-953b-52578d8b1c6a', displaytext : u'CentOS
5.6(64-bit) no GUI (XenServer)', ostypeid :
u'b5829966-ef7f-11e3-a141-00163e189e44', passwordenabled : False, id :
u'b57c835a-ef7f-11e3-a141-00163e189e44', size : 21474836480, isready : True,
form
[jira] [Commented] (CLOUDSTACK-6862) [Automation] Test case TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm faling during BVT
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14024138#comment-14024138
]
Alex Brett commented on CLOUDSTACK-6862:
There are two issues with this test - the first is it requires CLOUDSTACK-6759
to be completed for the API to actually exist. The second is that it runs on
*every* BVT, despite the fact that:
# vGPU only works on XenServer, there is no support in KVM or any other
hypervisor
# It requires specific vGPU enabled hardware, which the BVTs do not run on
As such I think it should be removed from the BVT, and also have logic added so
it skips itself if run on any hypervisor other than XenServer. I'm happy to do
these changes if we think this is the right thing to do?
> [Automation] Test case TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm
> faling during BVT
> -
>
> Key: CLOUDSTACK-6862
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6862
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Test case
> integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm
> failing in BVT
> Error Message
> Execute cmd: createserviceoffering failed, due to: errorCode: 401,
> errorText:unable to verify user credentials and/or request signature
> >> begin captured stdout << -
> === TestName: test_deploy_vgpu_enabled_vm | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: STARTED : TC: test_deploy_vgpu_enabled_vm :::
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Payload: {'apiKey':
> u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
> 'command': 'listDomains', 'signature': '8Yh5KlFqCsxhD/NB2fOBHSPL1kI=',
> 'response': 'json'}
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Sending GET Cmd : listDomains===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A&command=listDomains&response=json&signature=8Yh5KlFqCsxhD%2FNB2fOBHSPL1kI%3D
> HTTP/1.1" 200 159
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Response : [{path : u'ROOT', haschild : False, id :
> u'6b3a436e-ef1f-11e3-a141-00163e189e44', name : u'ROOT', level : 0}]
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Payload: {'apiKey':
> u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
> 'name': 'zone-xen', 'command': 'listZones', 'signature':
> 'Z7nIBao2vEVG1YiHM2kVrh6QcPY=', 'response': 'json'}
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A&command=listZones&name=zone-xen&signature=Z7nIBao2vEVG1YiHM2kVrh6QcPY%3D
> HTTP/1.1" 200 446
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Response : [{localstorageenabled : False, name : u'zone-xen',
> guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
> u'562e3c93-9149-38c6-8555-de48e3e6c847', dns2 : u'8.8.4.4', dns1 :
> u'8.8.8.8', securitygroupsenabled : False, allocationstate : u'Enabled',
> internaldns1 : u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype :
> u'Advanced', id : u'ad43d834-dc57-4da5-b3ae-0ef3f106192b', internaldns2 :
> u'172.16.88.8'}]
> test_deploy_vgpu_enabled_vm
> (integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
> DEBUG: Payload: {'apiKey':
> u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
> 'templatef
[jira] [Created] (CLOUDSTACK-6877) test_01_sys_vm_start from suite test_secondary storage is failing on xen and kvm
Bharat Kumar created CLOUDSTACK-6877:
Summary: test_01_sys_vm_start from suite test_secondary storage is
failing on xen and kvm
Key: CLOUDSTACK-6877
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6877
Project: CloudStack
Issue Type: Sub-task
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation
Reporter: Bharat Kumar
Error Message
Check whether state of SSVM is running
>> begin captured stdout << -
=== TestName: test_01_sys_vm_start | Status : FAILED ===
- >> end captured stdout << --
>> begin captured logging <<
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
STARTED : TC: test_01_sys_vm_start :::
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Payload: {'apiKey':
u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
'name': u'zone-xen', 'command': 'listZones', 'signature':
'TFpPtnJ8uzOTOnEQ53yyluY5Ed0=', 'response': 'json'}
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Sending GET Cmd : listZones===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?response=json&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listZones&name=zone-xen&signature=TFpPtnJ8uzOTOnEQ53yyluY5Ed0%3D
HTTP/1.1" 200 446
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Response : [{localstorageenabled : False, name : u'zone-xen', guestcidraddress
: u'10.1.1.0/24', tags : [], zonetoken :
u'21715335-f736-3016-9d97-0765620600c0', dns2 : u'8.8.4.4', dns1 : u'8.8.8.8',
securitygroupsenabled : False, allocationstate : u'Enabled', internaldns1 :
u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype : u'Advanced', id
: u'243eb08f-31e9-4283-953b-52578d8b1c6a', internaldns2 : u'172.16.88.8'}]
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Payload: {'apiKey':
u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
'command': 'listPods', 'signature': 'NShFYMTbzFapYtW58DbrDRIaYDc=', 'zoneid':
u'243eb08f-31e9-4283-953b-52578d8b1c6a', 'response': 'json'}
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Sending GET Cmd : listPods===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?zoneid=243eb08f-31e9-4283-953b-52578d8b1c6a&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listPods&response=json&signature=NShFYMTbzFapYtW58DbrDRIaYDc%3D
HTTP/1.1" 200 308
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Response : [{endip : u'172.16.88.40', name : u'z0p0', startip :
u'172.16.88.13', allocationstate : u'Enabled', zoneid :
u'243eb08f-31e9-4283-953b-52578d8b1c6a', netmask : u'255.255.255.0', gateway :
u'172.16.88.1', id : u'53e93054-4d0c-4110-9699-314d37ce3e90', zonename :
u'zone-xen'}]
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Payload: {'apiKey':
u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
'name': u'zone-xen2', 'command': 'listZones', 'signature':
'E7MrZsFm+8NgyoakHaXWYy7JN6I=', 'response': 'json'}
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Sending GET Cmd : listZones===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: "GET
/client/api?response=json&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listZones&name=zone-xen2&signature=E7MrZsFm%2B8NgyoakHaXWYy7JN6I%3D
HTTP/1.1" 200 430
test_01_sys_vm_start
(integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
Response : [{localstorageenabled : False, name : u'zone-xen2', guestcidraddress
: u'10.1.1.0/24', tags : [], zonetoken :
u'a372ca2f-24cd-34eb-bf89-861c7e4afd44', dns1 : u'8.8.8.8',
securitygroupsenabled : False, allocationstate : u'Enabled', internaldns1 :
u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype : u'Advanced', id
: u'916485d1-8b0f-476d-9e25-31b0c5e3a81e', internaldns2 : u'172.16.88.8'}]
test_01_sys_vm_start
(integration.smoke
[jira] [Created] (CLOUDSTACK-6878) test_snapshots.TestSnapshotRootDisk.test_01_snapshot_root_disk is failing on xen, kvm
Bharat Kumar created CLOUDSTACK-6878:
Summary:
test_snapshots.TestSnapshotRootDisk.test_01_snapshot_root_disk is failing on
xen, kvm
Key: CLOUDSTACK-6878
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6878
Project: CloudStack
Issue Type: Sub-task
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation
Reporter: Bharat Kumar
Standard Error
Trying SSH Connection: Host:172.16.88.21 User:root
Port:22 RetryCnt:60===
===SSH to Host 172.16.88.21 port : 22 SUCCESSFUL===
{Cmd: mkdir -p %s /mnt/tmp via Host: 172.16.88.21} {returns: []}
{Cmd: mount -t nfs
nfs-server.automation.hyd.com::/export/automation/1/z0secondary /mnt/tmp via
Host: 172.16.88.21} {returns: [u'mount.nfs: access denied by server while
mounting nfs-server.automation.hyd.com::/export/automation/1/z0secondary']}
{Cmd: test -f /mnt/tmp/snapshots/20/38/9831d613-3410-43d0-9d95-7570a7d8be40.vhd
&& echo 'snapshot exists' via Host: 172.16.88.21} {returns: []}
{Cmd: cd via Host: 172.16.88.21} {returns: []}
{Cmd: umount /mnt/tmp via Host: 172.16.88.21} {returns: [u'umount: /mnt/tmp:
not mounted']}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6877) test_01_sys_vm_start from suite test_secondary storage is failing on xen
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar updated CLOUDSTACK-6877:
-
Summary: test_01_sys_vm_start from suite test_secondary storage is failing
on xen (was: test_01_sys_vm_start from suite test_secondary storage is failing
on xen and kvm)
> test_01_sys_vm_start from suite test_secondary storage is failing on xen
>
>
> Key: CLOUDSTACK-6877
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6877
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Bharat Kumar
>
> Error Message
> Check whether state of SSVM is running
> >> begin captured stdout << -
> === TestName: test_01_sys_vm_start | Status : FAILED ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> STARTED : TC: test_01_sys_vm_start :::
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Payload: {'apiKey':
> u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
> 'name': u'zone-xen', 'command': 'listZones', 'signature':
> 'TFpPtnJ8uzOTOnEQ53yyluY5Ed0=', 'response': 'json'}
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listZones&name=zone-xen&signature=TFpPtnJ8uzOTOnEQ53yyluY5Ed0%3D
> HTTP/1.1" 200 446
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Response : [{localstorageenabled : False, name : u'zone-xen',
> guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
> u'21715335-f736-3016-9d97-0765620600c0', dns2 : u'8.8.4.4', dns1 :
> u'8.8.8.8', securitygroupsenabled : False, allocationstate : u'Enabled',
> internaldns1 : u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype :
> u'Advanced', id : u'243eb08f-31e9-4283-953b-52578d8b1c6a', internaldns2 :
> u'172.16.88.8'}]
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Payload: {'apiKey':
> u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
> 'command': 'listPods', 'signature': 'NShFYMTbzFapYtW58DbrDRIaYDc=',
> 'zoneid': u'243eb08f-31e9-4283-953b-52578d8b1c6a', 'response': 'json'}
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Sending GET Cmd : listPods===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?zoneid=243eb08f-31e9-4283-953b-52578d8b1c6a&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listPods&response=json&signature=NShFYMTbzFapYtW58DbrDRIaYDc%3D
> HTTP/1.1" 200 308
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Response : [{endip : u'172.16.88.40', name : u'z0p0', startip :
> u'172.16.88.13', allocationstate : u'Enabled', zoneid :
> u'243eb08f-31e9-4283-953b-52578d8b1c6a', netmask : u'255.255.255.0', gateway
> : u'172.16.88.1', id : u'53e93054-4d0c-4110-9699-314d37ce3e90', zonename :
> u'zone-xen'}]
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Payload: {'apiKey':
> u'N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA',
> 'name': u'zone-xen2', 'command': 'listZones', 'signature':
> 'E7MrZsFm+8NgyoakHaXWYy7JN6I=', 'response': 'json'}
> test_01_sys_vm_start
> (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG:
> Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=N9xuraDqhuIDa7f0I_v0nkI3Kk2wLZ5w9UH3F86H-TeAnoXJ1iRnOaYMLJDd2w-rjwH6LCiSEnw24lNX6LH8iA&command=listZones&name=zone-xen2&signature=E7MrZsFm%2B8NgyoakHaXWYy7JN6I%3D
> HTTP/1.1" 200 430
> test_01_sys_vm_start
> (integration.smoke.test_secon
[jira] [Updated] (CLOUDSTACK-6875) test_volumes.TestVolumes.test_09_delete_detached_volume is failing on simulator runs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar updated CLOUDSTACK-6875:
-
Summary: test_volumes.TestVolumes.test_09_delete_detached_volume is failing
on simulator runs (was: test_volumes is failing on simulator runs)
> test_volumes.TestVolumes.test_09_delete_detached_volume is failing on
> simulator runs
>
>
> Key: CLOUDSTACK-6875
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6875
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Bharat Kumar
>
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-06-08T20:26:20-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin',
> userid : u'36a2cda6-ef83-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
> u'b263a941-29b1-4ab8-9c00-7a0d2678b591', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Unexpected
> exception'}, accountid : u'36a29ade-ef83-11e3-a86b-00163e0af42c'}
> >> begin captured stdout << -
> === TestName: test_09_delete_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: STARTED : TC: test_09_delete_detached_volume :::
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Delete Volume ID: 24051890-92ad-4cee-8ca3-119d278b072a
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'account': u'test-account-TestCreateVolume-N2SRV2',
> 'domainid': u'36a27fb8-ef83-11e3-a86b-00163e0af42c', 'name': 'Test Volume',
> 'zoneid': u'ef5040e4-6e78-433b-a21a-656a7ab31e80', 'apiKey':
> u'Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ',
> 'command': 'createVolume', 'signature': 'O0mZxBTYte8bIWPhtBYKUycq8Yo=',
> 'diskofferingid': u'92b2888e-c624-4042-82b4-632bed2bb38d', 'response': 'json'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : createVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?account=test-account-TestCreateVolume-N2SRV2&domainid=36a27fb8-ef83-11e3-a86b-00163e0af42c&name=Test+Volume&zoneid=ef5040e4-6e78-433b-a21a-656a7ab31e80&apiKey=Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ&command=createVolume&signature=O0mZxBTYte8bIWPhtBYKUycq8Yo%3D&diskofferingid=92b2888e-c624-4042-82b4-632bed2bb38d&response=json
> HTTP/1.1" 200 121
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === Jobid: 2249fb73-7560-4d22-a7f9-dba0507b096e Started ===
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'signature': '8di/lZIPnn9qCgFh0fHVVrH7/8U=', 'apiKey':
> u'Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'2249fb73-7560-4d22-a7f9-dba0507b096e'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=2249fb73-7560-4d22-a7f9-dba0507b096e&apiKey=Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ&command=queryAsyncJobResult&response=json&signature=8di%2FlZIPnn9qCgFh0fHVVrH7%2F8U%3D
> HTTP/1.1" 200 430
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Response : {jobprocstatus : 0, created : u'2014-06-08T20:26:14-0700',
> cmd :
> u'org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin',
> userid : u'36a2cda6-ef83-11e3-a86b-00163e0af42c', jobstatus : 0, jobid :
> u'2249fb73-7560-4d22-a7f9-dba0507b096e', jobresultcode : 0, jobinstanceid :
> u'c936802c-42f3-4ff3-9eb2-dd003517a8ef', jobinstancetype : u'Volume',
> accountid : u'36a29ade-ef83-11e3-a86b-00163e0af42c'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === JobId:2249fb73-7560-4d22-a7f9-dba0507b096e is Still Processing,
> Will TimeOut in:3595
> test_09_delete_detached_volume (i
[jira] [Created] (CLOUDSTACK-6880) cloudstack-usage: invalid installation instructions
Pierre-Luc Dion created CLOUDSTACK-6880: --- Summary: cloudstack-usage: invalid installation instructions Key: CLOUDSTACK-6880 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6880 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Environment: RTD Reporter: Pierre-Luc Dion Assignee: Pierre-Luc Dion Priority: Trivial http://cloudstack-installation.readthedocs.org/en/latest/optional_installation.html#installing-the-usage-server-optional Invalid installation instruction of cloudstack-usage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6691) NPE while assigning a VM nic primary/secondaryip to internal lb rule.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-6691:
Assignee: manasaveloori (was: Jessica Wang)
Manasa,
Please provide your database dump, then assign this bug back to me.
thank you.
Jessica
> NPE while assigning a VM nic primary/secondaryip to internal lb rule.
> -
>
> Key: CLOUDSTACK-6691
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6691
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.4.0
>Reporter: manasaveloori
>Assignee: manasaveloori
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> 1.Create VPC.
> 2. Create a tier network using the network offering supporting the internal
> lb.
> 3. Deploy a VM using this tier network.Acquire secondary ip to the VM nic.
> 4. Go to VPC->configure->tier->internal LB->configure the internal LB.
> 5. Now assign vm in that tier to that internal Lb rule.
> Failing with NPE:
> 2014-05-16 06:29:00,509 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-23:job-114) Executing AsyncJobVO {id:114, userId: 2,
> accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd,
> cmdInfo:
> {"":"","cmdEventType":"LB.ASSIGN.TO.RULE","ctxUserId":"2","signatureversion":"3","httpmethod":"GET","vmidipmap[0].vmip":"","apikey":"71KC57DrfcKrtoky1fx8-1drvYkZhxt2h1qhXig8LMlvnnppryePDI6ZZbyQ9uSHwawJcIA7xPzOV6zKoQEwDw","id":"","10.0.2.250":"","response":"json","ctxDetails":"{\"LoadBalancer\":\"\"}","expires":"2014-05-16T10:39:00+","5":"","uuid":"","ctxAccountId":"2","vmidipmap[0].vmid":"f91de9de-508a-4b84-8939-1c9173caa316","ctxStartEventId":"284","signature":"+ufhrzwBGdylmvZEV/6P+YmsLv0\u003d"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7672522866886, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-16 06:29:00,523 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-23:job-114 ctx-1d33bb54) Received unknown parameters for
> command assignToLoadBalancerRule. Unknown parameters : signatureversion
> ctxdetails 10.0.2.250 expires 5
> 2014-05-16 06:29:00,524 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-23:job-114) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd
> java.lang.NullPointerException
> at
> org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd.getSyncObjId(AssignToLoadBalancerRuleCmd.java:190)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:92)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> 2014-05-16 06:29:00,526 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-23:job-114) Complete async job-114, jobStatus: FAILED,
> resultCode: 530, result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530}
> 2014-05-16 06:29:00,550 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-23:job-114) Done executing
> org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd
> for job-114
> Attaching the logs
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6852) UI - improve modules functionalities.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025514#comment-14025514 ] ASF subversion and git services commented on CLOUDSTACK-6852: - Commit 1641b280544e1982f155f82b17d56d0f6ec82e6a in cloudstack's branch refs/heads/4.4-forward from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1641b28 ] CLOUDSTACK-6852: UI - modules - add DR fields to volume detailView, network detailView, zone detailView. > UI - improve modules functionalities. > - > > Key: CLOUDSTACK-6852 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6852 > 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.2#6252)
[jira] [Commented] (CLOUDSTACK-6852) UI - improve modules functionalities.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025515#comment-14025515 ] ASF subversion and git services commented on CLOUDSTACK-6852: - Commit 044c5e0eeef3211a4418c1251f23f1e91499316e in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=044c5e0 ] CLOUDSTACK-6852: UI - modules - add DR fields to volume detailView, network detailView, zone detailView. > UI - improve modules functionalities. > - > > Key: CLOUDSTACK-6852 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6852 > 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.2#6252)
[jira] [Created] (CLOUDSTACK-6881) MS:IPv6: Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity
Parth Jagirdar created CLOUDSTACK-6881: -- Summary: MS:IPv6: Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity Key: CLOUDSTACK-6881 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6881 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Reporter: Parth Jagirdar We need a mechanism to remove 0's followed by a number in IPv4 addressing. To reproduce, deploy a VM with static IPv4 where there is a single digit number followed by a 0. Example, 10.2.2.02 Refer to following.. 2014-06-09 11:44:47,608 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-SystemCapability from cache: true 2014-06-09 11:44:47,608 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Root Access granted to Acct[298be2e2-df9d-11e3-98fe-ced18bec4952-admin] by RoleBasedEntityAccessChecker 2014-06-09 11:44:47,609 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainCapability from cache: false 2014-06-09 11:44:47,610 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainResourceCapability from cache: false 2014-06-09 11:44:47,611 DEBUG [c.c.n.NetworkModelImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Service SecurityGroup is not supported in the network id=222 2014-06-09 11:44:47,626 DEBUG [c.c.v.UserVmManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating in the DB for vm 2014-06-09 11:44:47,636 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating entries for VM: VM[User|i-2-143-VM] 2014-06-09 11:44:47,637 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nics for VM[User|i-2-143-VM] 2014-06-09 11:44:47,638 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nic for vm VM[User|i-2-143-VM] in network Ntwk[6c04eff1-972d-4119-bd97-e26c39d2bc0c|Guest|7] with requested profile NicProfile[0-0-null-null-null 2014-06-09 11:44:47,640 WARN [c.c.n.IpAddressManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Unable to get ip adress in zone id=1, vlanId id=[1, 21], network id=222: requested ip 10.2.2.09 is not available 2014-06-09 11:44:47,641 DEBUG [c.c.u.d.T.Transaction] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Rolling back the transaction: Time = 21 Name = catalina-exec-7; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:661-IpAddressManagerImpl.assignPublicIpAddress:648-IpAddressManagerImpl$11.doInTransactionWithoutResult:1853-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-IpAddressManagerImpl.allocateDirectIp:1831-DirectNetworkGuru$1.doInTransactionWithoutResult:246 2014-06-09 11:44:47,650 INFO [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 2014-06-09 11:44:47,650 TRACE [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Insufficient address capacity com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:750) at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:661) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:661) at com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:648) at com.cloud.network.IpAddressManagerImpl$11.doInTransactionWithoutResult(IpAddressManagerImpl.java:1853) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.allocateDirectIp(IpAddressManagerImpl.java:1831) at com.cloud.network.guru.DirectNetworkGuru$1.doInTransactionWithoutResult(DirectNetworkGuru.java:246) at com.cloud.utils.db.Transactio
[jira] [Updated] (CLOUDSTACK-6881) MS:IPv6: Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6881: --- Description: We need a mechanism to remove 0's followed by a number in IPv4 addressing. To reproduce, deploy a VM with static IPv4 where there is a single digit number followed by a 0. Example, 10.2.2.02 Refer to following.. Observed in dual stack. 2014-06-09 11:44:47,608 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-SystemCapability from cache: true 2014-06-09 11:44:47,608 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Root Access granted to Acct[298be2e2-df9d-11e3-98fe-ced18bec4952-admin] by RoleBasedEntityAccessChecker 2014-06-09 11:44:47,609 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainCapability from cache: false 2014-06-09 11:44:47,610 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainResourceCapability from cache: false 2014-06-09 11:44:47,611 DEBUG [c.c.n.NetworkModelImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Service SecurityGroup is not supported in the network id=222 2014-06-09 11:44:47,626 DEBUG [c.c.v.UserVmManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating in the DB for vm 2014-06-09 11:44:47,636 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating entries for VM: VM[User|i-2-143-VM] 2014-06-09 11:44:47,637 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nics for VM[User|i-2-143-VM] 2014-06-09 11:44:47,638 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nic for vm VM[User|i-2-143-VM] in network Ntwk[6c04eff1-972d-4119-bd97-e26c39d2bc0c|Guest|7] with requested profile NicProfile[0-0-null-null-null 2014-06-09 11:44:47,640 WARN [c.c.n.IpAddressManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Unable to get ip adress in zone id=1, vlanId id=[1, 21], network id=222: requested ip 10.2.2.09 is not available 2014-06-09 11:44:47,641 DEBUG [c.c.u.d.T.Transaction] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Rolling back the transaction: Time = 21 Name = catalina-exec-7; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:661-IpAddressManagerImpl.assignPublicIpAddress:648-IpAddressManagerImpl$11.doInTransactionWithoutResult:1853-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-IpAddressManagerImpl.allocateDirectIp:1831-DirectNetworkGuru$1.doInTransactionWithoutResult:246 2014-06-09 11:44:47,650 INFO [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 2014-06-09 11:44:47,650 TRACE [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Insufficient address capacity com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:750) at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:661) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:661) at com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:648) at com.cloud.network.IpAddressManagerImpl$11.doInTransactionWithoutResult(IpAddressManagerImpl.java:1853) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.allocateDirectIp(IpAddressManagerImpl.java:1831) at com.cloud.network.guru.DirectNetworkGuru$1.doInTransactionWithoutResult(DirectNetworkGuru.java:246) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
[jira] [Updated] (CLOUDSTACK-6881) MS:IPv4 Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6881: --- Summary: MS:IPv4 Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity (was: MS:IPv6: Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity) > MS:IPv4 Incorrect IPv4 address as iptonetworklist param raises insufficient > address capacity > > > Key: CLOUDSTACK-6881 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6881 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 >Reporter: Parth Jagirdar > > We need a mechanism to remove 0's followed by a number in IPv4 addressing. > To reproduce, deploy a VM with static IPv4 where there is a single digit > number followed by a 0. > Example, 10.2.2.02 > Refer to following.. Observed in dual stack. > 2014-06-09 11:44:47,608 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for > 2-null-null-SystemCapability from cache: true > 2014-06-09 11:44:47,608 DEBUG [c.c.u.AccountManagerImpl] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Root Access granted to > Acct[298be2e2-df9d-11e3-98fe-ced18bec4952-admin] by > RoleBasedEntityAccessChecker > 2014-06-09 11:44:47,609 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for > 2-null-null-DomainCapability from cache: false > 2014-06-09 11:44:47,610 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for > 2-null-null-DomainResourceCapability from cache: false > 2014-06-09 11:44:47,611 DEBUG [c.c.n.NetworkModelImpl] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Service SecurityGroup is not > supported in the network id=222 > 2014-06-09 11:44:47,626 DEBUG [c.c.v.UserVmManagerImpl] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating in the DB for vm > 2014-06-09 11:44:47,636 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating entries for VM: > VM[User|i-2-143-VM] > 2014-06-09 11:44:47,637 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nics for > VM[User|i-2-143-VM] > 2014-06-09 11:44:47,638 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nic for vm > VM[User|i-2-143-VM] in network > Ntwk[6c04eff1-972d-4119-bd97-e26c39d2bc0c|Guest|7] with requested profile > NicProfile[0-0-null-null-null > 2014-06-09 11:44:47,640 WARN [c.c.n.IpAddressManagerImpl] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Unable to get ip adress in zone > id=1, vlanId id=[1, 21], network id=222: requested ip 10.2.2.09 is not > available > 2014-06-09 11:44:47,641 DEBUG [c.c.u.d.T.Transaction] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Rolling back the transaction: > Time = 21 Name = catalina-exec-7; called by > -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:661-IpAddressManagerImpl.assignPublicIpAddress:648-IpAddressManagerImpl$11.doInTransactionWithoutResult:1853-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-IpAddressManagerImpl.allocateDirectIp:1831-DirectNetworkGuru$1.doInTransactionWithoutResult:246 > 2014-06-09 11:44:47,650 INFO [o.a.c.a.c.u.v.DeployVMCmd] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) > com.cloud.exception.InsufficientAddressCapacityException: Insufficient > address capacityScope=interface com.cloud.dc.DataCenter; id=1 > 2014-06-09 11:44:47,650 TRACE [o.a.c.a.c.u.v.DeployVMCmd] > (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Insufficient address capacity > com.cloud.exception.InsufficientAddressCapacityException: Insufficient > address capacityScope=interface com.cloud.dc.DataCenter; id=1 > at > com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:750) > at > com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:661) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at > com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:661) > at > com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:648) > at > com.cloud.network.IpAddressManagerImpl$11.doInTransactionWithoutResult(IpAddressManagerImpl.java:1853) > at > com.cloud.u
[jira] [Created] (CLOUDSTACK-6882) Doc generator should be generate doc for plugins
Rayees Namathponnan created CLOUDSTACK-6882: --- Summary: Doc generator should be generate doc for plugins Key: CLOUDSTACK-6882 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6882 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, Doc Reporter: Rayees Namathponnan Priority: Critical -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6882) Doc generator should be generate doc for plugins
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6882: Fix Version/s: 4.4.0 > Doc generator should be generate doc for plugins > - > > Key: CLOUDSTACK-6882 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6882 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Doc >Reporter: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6881) MS:IPv4 Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6881: --- Description: We need a mechanism to validate 0's followed by a number in IPv4 addressing. To reproduce, deploy a VM with static IPv4 where there is a single digit number followed by a 0. Example, 10.2.2.02 API should return an appropriate error, Alternatively this validation can be performed using JS. Refer to following.. Observed in dual stack. 2014-06-09 11:44:47,608 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-SystemCapability from cache: true 2014-06-09 11:44:47,608 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Root Access granted to Acct[298be2e2-df9d-11e3-98fe-ced18bec4952-admin] by RoleBasedEntityAccessChecker 2014-06-09 11:44:47,609 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainCapability from cache: false 2014-06-09 11:44:47,610 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainResourceCapability from cache: false 2014-06-09 11:44:47,611 DEBUG [c.c.n.NetworkModelImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Service SecurityGroup is not supported in the network id=222 2014-06-09 11:44:47,626 DEBUG [c.c.v.UserVmManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating in the DB for vm 2014-06-09 11:44:47,636 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating entries for VM: VM[User|i-2-143-VM] 2014-06-09 11:44:47,637 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nics for VM[User|i-2-143-VM] 2014-06-09 11:44:47,638 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nic for vm VM[User|i-2-143-VM] in network Ntwk[6c04eff1-972d-4119-bd97-e26c39d2bc0c|Guest|7] with requested profile NicProfile[0-0-null-null-null 2014-06-09 11:44:47,640 WARN [c.c.n.IpAddressManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Unable to get ip adress in zone id=1, vlanId id=[1, 21], network id=222: requested ip 10.2.2.09 is not available 2014-06-09 11:44:47,641 DEBUG [c.c.u.d.T.Transaction] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Rolling back the transaction: Time = 21 Name = catalina-exec-7; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:661-IpAddressManagerImpl.assignPublicIpAddress:648-IpAddressManagerImpl$11.doInTransactionWithoutResult:1853-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-IpAddressManagerImpl.allocateDirectIp:1831-DirectNetworkGuru$1.doInTransactionWithoutResult:246 2014-06-09 11:44:47,650 INFO [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 2014-06-09 11:44:47,650 TRACE [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Insufficient address capacity com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:750) at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:661) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:661) at com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:648) at com.cloud.network.IpAddressManagerImpl$11.doInTransactionWithoutResult(IpAddressManagerImpl.java:1853) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.allocateDirectIp(IpAddressManagerImpl.java:1831) at com.cloud.network.guru.DirectNetworkGuru$1.doInTransactionWithoutResult(DirectNetworkGuru.java:246) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWi
[jira] [Updated] (CLOUDSTACK-6881) MS:IPv4 Incorrect IPv4 address as iptonetworklist param raises insufficient address capacity
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6881: --- Description: We need a mechanism to validate 0's followed by a number in IPv4 addressing. To reproduce, deploy a VM with static IPv4 where there is a single digit number followed by a 0. Example, 10.2.2.02 API should return an appropriate error, This validation can be performed using JS as a preventive method. Refer to following.. Observed in dual stack. 2014-06-09 11:44:47,608 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-SystemCapability from cache: true 2014-06-09 11:44:47,608 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Root Access granted to Acct[298be2e2-df9d-11e3-98fe-ced18bec4952-admin] by RoleBasedEntityAccessChecker 2014-06-09 11:44:47,609 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainCapability from cache: false 2014-06-09 11:44:47,610 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) IAM access check for 2-null-null-DomainResourceCapability from cache: false 2014-06-09 11:44:47,611 DEBUG [c.c.n.NetworkModelImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Service SecurityGroup is not supported in the network id=222 2014-06-09 11:44:47,626 DEBUG [c.c.v.UserVmManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating in the DB for vm 2014-06-09 11:44:47,636 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating entries for VM: VM[User|i-2-143-VM] 2014-06-09 11:44:47,637 DEBUG [c.c.v.VirtualMachineManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nics for VM[User|i-2-143-VM] 2014-06-09 11:44:47,638 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Allocating nic for vm VM[User|i-2-143-VM] in network Ntwk[6c04eff1-972d-4119-bd97-e26c39d2bc0c|Guest|7] with requested profile NicProfile[0-0-null-null-null 2014-06-09 11:44:47,640 WARN [c.c.n.IpAddressManagerImpl] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Unable to get ip adress in zone id=1, vlanId id=[1, 21], network id=222: requested ip 10.2.2.09 is not available 2014-06-09 11:44:47,641 DEBUG [c.c.u.d.T.Transaction] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Rolling back the transaction: Time = 21 Name = catalina-exec-7; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:661-IpAddressManagerImpl.assignPublicIpAddress:648-IpAddressManagerImpl$11.doInTransactionWithoutResult:1853-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-IpAddressManagerImpl.allocateDirectIp:1831-DirectNetworkGuru$1.doInTransactionWithoutResult:246 2014-06-09 11:44:47,650 INFO [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 2014-06-09 11:44:47,650 TRACE [o.a.c.a.c.u.v.DeployVMCmd] (catalina-exec-7:ctx-8d87d71b ctx-fc6ae1da) Insufficient address capacity com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:750) at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:661) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:661) at com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:648) at com.cloud.network.IpAddressManagerImpl$11.doInTransactionWithoutResult(IpAddressManagerImpl.java:1853) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.IpAddressManagerImpl.allocateDirectIp(IpAddressManagerImpl.java:1831) at com.cloud.network.guru.DirectNetworkGuru$1.doInTransactionWithoutResult(DirectNetworkGuru.java:246) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionC
[jira] [Commented] (CLOUDSTACK-6882) Doc generator should be generate doc for plugins
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025590#comment-14025590
]
Rayees Namathponnan commented on CLOUDSTACK-6882:
-
As part below implementation, cloudstack can automatically load plugin
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plug-ins%2C+Modules%2C+and+Extensions
There is no option to create doc for plugin, there are hardcode package
values in server/src/com/cloud/api/doc/ApiXmlDocWriter.java,
Currently you need to update this manually with you package name to create doc,
instead of manually modifying this, we should get the packages from loaded
plugins
101 public static void main(String[] args) {
102
103 Set> cmdClasses =
ReflectUtil.getClassesWithAnnotation(APICommand.class, new String[]
{"org.apache.cloudstack.api", "com.cloud.api"});
104
105 for (Class cmdClass : cmdClasses) {
106 String apiName =
cmdClass.getAnnotation(APICommand.class).name();
107 if (s_apiNameCmdClassMap.containsKey(apiName)) {
108 // handle API cmd separation into admin cmd and user cmd
with the common api name
109 Class curCmd = s_apiNameCmdClassMap.get(apiName);
110 if (curCmd.isAssignableFrom(cmdClass)) {
111 // api_cmd map always keep the admin cmd class to get
full response and parameters
> Doc generator should be generate doc for plugins
> -
>
> Key: CLOUDSTACK-6882
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6882
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Doc
>Reporter: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.4.0
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025695#comment-14025695
]
Animesh Chaturvedi commented on CLOUDSTACK-6710:
Amogh is there any update on this issue?
> [Automation] VM snapshot failing with NPE in vmware
> ---
>
> Key: CLOUDSTACK-6710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
> Environment: Vmware 5.0
> 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Amogh Vasekar
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Execute BVT
> integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
> This test case creating VM snapshot in VMware; this is failing with below NPE
> 2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-130:job-390/job-391) Run VM work job:
> com.cloud.vm.snapshot.VmWorkCreateVMSn
> apshot for VM 62, job origin: 390
> 2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job:
> com.cloud.vm.snapsh
> ot.VmWorkCreateVMSnapshot{"vmSnapshotId":1,"quiesceVm":false,"userId":2,"accountId":2,"vmId":62,"handlerName":"VMSnapshotManagerImpl"}
> 2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm
> snapshot: 1
> java.lang.NullPointerException
> at
> org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> 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.$Proxy182.handleVmWorkJob(Unknown Source)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurr
[jira] [Commented] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025699#comment-14025699
]
Amogh Vasekar commented on CLOUDSTACK-6710:
---
Setting up VMware to test the fix.
Thanks,
Amogh
> [Automation] VM snapshot failing with NPE in vmware
> ---
>
> Key: CLOUDSTACK-6710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
> Environment: Vmware 5.0
> 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Amogh Vasekar
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Execute BVT
> integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
> This test case creating VM snapshot in VMware; this is failing with below NPE
> 2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-130:job-390/job-391) Run VM work job:
> com.cloud.vm.snapshot.VmWorkCreateVMSn
> apshot for VM 62, job origin: 390
> 2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job:
> com.cloud.vm.snapsh
> ot.VmWorkCreateVMSnapshot{"vmSnapshotId":1,"quiesceVm":false,"userId":2,"accountId":2,"vmId":62,"handlerName":"VMSnapshotManagerImpl"}
> 2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm
> snapshot: 1
> java.lang.NullPointerException
> at
> org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> 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.$Proxy182.handleVmWorkJob(Unknown Source)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurre
[jira] [Updated] (CLOUDSTACK-6623) Register template does not work as expected, when deploying simulator and xen zones simultaneously on a single management server.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] edison su updated CLOUDSTACK-6623: -- Priority: Major (was: Blocker) > Register template does not work as expected, when deploying simulator and xen > zones simultaneously on a single management server. > - > > Key: CLOUDSTACK-6623 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6623 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Bharat Kumar >Assignee: edison su > Fix For: 4.4.0 > > > when we setup simulator and xenserver both in separate zones on a single > management server, The register template always behaves as if it is executing > on the simulator. i.e. register template is always successful and it dose not > initiate the actual download when calling the register template API against > xen-zone. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6674) [Automation] [DB lock] When KVM agent is alert state, agent never trying to connect back
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025769#comment-14025769 ] edison su commented on CLOUDSTACK-6674: --- KVM agent won't reconnect back, is because their are jobs running on kvm host, the current logic is that, unless all the jobs finished, kvm agent won't connect back to mgt server. Why there are jobs not finished, maybe due to storage error, such as hanging on access primary/secondary storage etc. But there is a DB deadlock exception in the log, may need DB expert to take a look it. > [Automation] [DB lock] When KVM agent is alert state, agent never trying to > connect back > - > > Key: CLOUDSTACK-6674 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6674 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.4.0 > Environment: KVM (RHEL 6.3) > 4.4-forward >Reporter: Rayees Namathponnan >Assignee: edison su >Priority: Critical > Fix For: 4.4.0 > > > This issue observed in automation run, when KVM agent is alert state, it > never tries to connect back, also observed SQL DB lock in MS log for > AgentConnectTaskPool > You need to restart agent manually to connect it back > Here is agent log > 2014-05-13 23:59:38,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining > commands... > 2014-05-13 23:59:38,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 5 commands in progre > ss. > 2014-05-13 23:59:43,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining > commands... > 2014-05-13 23:59:43,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 5 commands in progre > ss. > 2014-05-13 23:59:48,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining > commands... > 2014-05-13 23:59:48,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 5 commands in progre > ss. > 2014-05-13 23:59:53,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining > commands... > 2014-05-13 23:59:53,878 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 5 commands in progre > ss. > 2014-05-13 23:59:58,878 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining > commands... > 2014-05-13 23:59:58,878 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 5 commands in progress. > ~ > MS log, please see the attached log for more info > 2014-05-13 20:07:50,170 DEBUG [c.c.v.VirtualMachineManagerImpl] > (API-Job-Executor-93:job-2240 ctx-f6efb16a) Destroying vm > VM[User|i-137-304-QA] > 2014-05-13 20:07:50,171 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-65:job-2223 ctx-a60be5ae) Rolling back the transaction: > Time = 291 Name = API-Job-Ex > ecutor-65; called by > -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-Ref > lectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:204-$Proxy97.markA > sUnavailable:-1-IpAddressManagerImpl$10.doInTransaction:1639-IpAddressManagerImpl$10.doInTransaction:1620-Transaction$2.doInTransaction:49 > 2014-05-13 20:07:50,173 WARN [c.c.u.AccountManagerImpl] > (API-Job-Executor-65:job-2223 ctx-a60be5ae) Failed to cleanup account > Acct[20c063c7-9913-496d-983f-e > fe18a92a9dc-test-account-TestScaleVmDynamicServiceOffering-test_change_so_running_vm_dynamic_to_dynamic_1_ADMIN] > due to > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.PreparedStatement@76384607: UPDATE user_ip_address SET > user_ip_address.state > ='Releasing' WHERE user_ip_address.id = 15 > at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:851) > at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:1327) > at > com.cloud.network.dao.IPAddressDaoImpl.markAsUnavailable(IPAddressDaoImpl.java:323) > at sun.reflect.GeneratedMethodAccessor536.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
[jira] [Commented] (CLOUDSTACK-6623) Register template does not work as expected, when deploying simulator and xen zones simultaneously on a single management server.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025777#comment-14025777 ] edison su commented on CLOUDSTACK-6623: --- Not a blocker, as it's not a normal deployment. > Register template does not work as expected, when deploying simulator and xen > zones simultaneously on a single management server. > - > > Key: CLOUDSTACK-6623 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6623 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Bharat Kumar >Assignee: edison su > Fix For: 4.4.0 > > > when we setup simulator and xenserver both in separate zones on a single > management server, The register template always behaves as if it is executing > on the simulator. i.e. register template is always successful and it dose not > initiate the actual download when calling the register template API against > xen-zone. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5582) kvm - HA is not triggered when host is powered down since the host gets into "Disconnected" state.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025799#comment-14025799
]
edison su commented on CLOUDSTACK-5582:
---
Jakob, currently, there is no way to change the host state from "DIsconnected"
to "Down" manually, unless you change DB.
"Disconnected" state is a temporary state, it should be changed to either
"Alert" or "Down". If it's in "Alert" state, mgt server will start investigate
the host's state by sending command(ping the host's ip address) to other hosts
in the same cluster as the host, if the investigation failed, then host will
remain in "Alert" state, or the state will be changed to "Down".
> kvm - HA is not triggered when host is powered down since the host gets into
> "Disconnected" state.
> ---
>
> Key: CLOUDSTACK-5582
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5582
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: Build from 4.3
>Reporter: Sangeetha Hariharan
>Assignee: edison su
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: kvmhost-down-up.rar, kvmhost-down-up.rar
>
>
> kvm - HA is not triggered when host is powered down since the host gets into
> "Disconnected" state.
> Advanced zone with 2 KVM (RHEL 6.3) hosts.
> Steps to reproduce the problem:
> Deploy few Vms in each of the hosts .
> Power down one of the hosts ( using IPMI).
> We see that the host gets into "Disconnected" state.
> All the Vms that are running in this host continue to be in "Up" state.
> This happens because of management server receiving a explicit shutdown
> request from the agent:
> 2013-12-19 21:06:37,262 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) SeqA 2--1: Processing Seq 2--1: { Cmd ,
> MgmtId: -1, via: 2, Ver: v1, Flags: 111,
> [{"com.cloud.agent.api.ShutdownCommand":{"reason":"sig.kill","wait":0}}] }
> 2013-12-19 21:06:37,263 INFO [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) Host 2 has informed us that it is shutting
> down with reason sig.kill and detail null
> 2013-12-19 21:06:37,263 INFO [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) Host 2 is disconnecting with event
> ShutdownRequested
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) The next status of agent 2is Disconnected,
> current status is Up
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) Deregistering link for 2 with state
> Disconnected
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) Remove Agent : 2
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.ConnectedAgentAttache]
> (AgentTaskPool-1:ctx-a32ed8e2) Processing Disconnect.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5582) kvm - HA is not triggered when host is powered down since the host gets into "Disconnected" state.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-5582.
---
Resolution: Fixed
It should be fixed by the fix: e51892abd5d11ee1f11cf3d21233133c9ecc54a4
I made long time ago.
> kvm - HA is not triggered when host is powered down since the host gets into
> "Disconnected" state.
> ---
>
> Key: CLOUDSTACK-5582
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5582
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: Build from 4.3
>Reporter: Sangeetha Hariharan
>Assignee: edison su
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: kvmhost-down-up.rar, kvmhost-down-up.rar
>
>
> kvm - HA is not triggered when host is powered down since the host gets into
> "Disconnected" state.
> Advanced zone with 2 KVM (RHEL 6.3) hosts.
> Steps to reproduce the problem:
> Deploy few Vms in each of the hosts .
> Power down one of the hosts ( using IPMI).
> We see that the host gets into "Disconnected" state.
> All the Vms that are running in this host continue to be in "Up" state.
> This happens because of management server receiving a explicit shutdown
> request from the agent:
> 2013-12-19 21:06:37,262 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) SeqA 2--1: Processing Seq 2--1: { Cmd ,
> MgmtId: -1, via: 2, Ver: v1, Flags: 111,
> [{"com.cloud.agent.api.ShutdownCommand":{"reason":"sig.kill","wait":0}}] }
> 2013-12-19 21:06:37,263 INFO [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) Host 2 has informed us that it is shutting
> down with reason sig.kill and detail null
> 2013-12-19 21:06:37,263 INFO [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) Host 2 is disconnecting with event
> ShutdownRequested
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) The next status of agent 2is Disconnected,
> current status is Up
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) Deregistering link for 2 with state
> Disconnected
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-a32ed8e2) Remove Agent : 2
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.ConnectedAgentAttache]
> (AgentTaskPool-1:ctx-a32ed8e2) Processing Disconnect.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5429) KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue of primary store being down hangs.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025813#comment-14025813 ] edison su commented on CLOUDSTACK-5429: --- It's the default behavior on RHEL: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-gracefully-shut-down-guests-libvirt.html One can change the behavior to shutdown vm, instead of suspend vm, during host shutdown, by modify libvirt-guests, but I think it should be configured by admin, not in cloudstack. > KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue of > primary store being down hangs. > - > > Key: CLOUDSTACK-5429 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5429 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: 4.4.0 > > Attachments: kvm-networkshutdown.png, kvmhostreboot.png, psdown.rar > > > KVM - Primary store down - Hosts attempt to reboot becasue of primary store > being down hangs. > Set up: > Advanced zone with KVM (RHEL 6.3) hosts. > Steps to reproduce the problem: > 1. Deploy few Vms in each of the hosts with 10 GB ROOT volume size , so we > start with 10 Vms. > 2. Create snaposhot for ROOT volumes. > 3. When snapshot is still in progress , Make the primary storage unavailable > for 10 mts. > This results in the KVM hosts to reboot. > But reboot of KVM host is not successful. > It is stuck at trying to unmount nfs mount points. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5429) KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue of primary store being down hangs.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] edison su resolved CLOUDSTACK-5429. --- Resolution: Fixed KVM configuration issue, should be down by admin > KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue of > primary store being down hangs. > - > > Key: CLOUDSTACK-5429 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5429 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: 4.4.0 > > Attachments: kvm-networkshutdown.png, kvmhostreboot.png, psdown.rar > > > KVM - Primary store down - Hosts attempt to reboot becasue of primary store > being down hangs. > Set up: > Advanced zone with KVM (RHEL 6.3) hosts. > Steps to reproduce the problem: > 1. Deploy few Vms in each of the hosts with 10 GB ROOT volume size , so we > start with 10 Vms. > 2. Create snaposhot for ROOT volumes. > 3. When snapshot is still in progress , Make the primary storage unavailable > for 10 mts. > This results in the KVM hosts to reboot. > But reboot of KVM host is not successful. > It is stuck at trying to unmount nfs mount points. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5452) KVM - Agent is not able to connect back if management server was restarted when there are pending tasks to this host.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025877#comment-14025877 ] Kal Torak commented on CLOUDSTACK-5452: --- And if you restarted the agent and still doesn't work ? I've restarted the agent, the management, the both hosts, disable iptables, running in circles and crying like a cow and STILL DOESN'T WORK, Then my workaround was, drop the database, and restart the process then it works ( I should tell you was in front my teachers, in our test) > KVM - Agent is not able to connect back if management server was restarted > when there are pending tasks to this host. > - > > Key: CLOUDSTACK-5452 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5452 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: Future > > > KVM - Agent is not able to connect back if management server was restarted > when there are pending tasks to this host. > Steps to reproduce the problem: > Set up - Advanced zone with 2 KVM ( RHEL 6.3) hosts. > Deployed few Vms. > Started snapshot for ROOT volume of the VMs. > When the snapshot processes are still in progress , restart management > server. > When the management sever started , the KVM hosts remain in disconnected > state. > Attempt to stop Vms /start Vms fails because of having no connection to the > host. > Following is seen in agent logs: > 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:56:51,641 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:51,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:56:56,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:56,643 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:06,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:06,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:11,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:11,646 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:26,649 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:26,675 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:31,676 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:31,677 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:36,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:36,678 INFO [cloud.agent.Agent]
[jira] [Commented] (CLOUDSTACK-5452) KVM - Agent is not able to connect back if management server was restarted when there are pending tasks to this host.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025892#comment-14025892 ] edison su commented on CLOUDSTACK-5452: --- If you restart agent, then agent should connect back to mgt server immediately. If it doesn't work, then must be something else is wrong. Such as, the configuration file (/etc/cloudstack/agent/agent.properties)on the kvm host is out-of-date. Anyway, if you have both mgt server log and agent log, when the tragedy happened, I can take a look at it. > KVM - Agent is not able to connect back if management server was restarted > when there are pending tasks to this host. > - > > Key: CLOUDSTACK-5452 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5452 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: Future > > > KVM - Agent is not able to connect back if management server was restarted > when there are pending tasks to this host. > Steps to reproduce the problem: > Set up - Advanced zone with 2 KVM ( RHEL 6.3) hosts. > Deployed few Vms. > Started snapshot for ROOT volume of the VMs. > When the snapshot processes are still in progress , restart management > server. > When the management sever started , the KVM hosts remain in disconnected > state. > Attempt to stop Vms /start Vms fails because of having no connection to the > host. > Following is seen in agent logs: > 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:56:51,641 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:51,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:56:56,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:56,643 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:06,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:06,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:11,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:11,646 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:26,649 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:26,675 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:31,676 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:31,677 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:36,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:36,678 INFO [cloud
[jira] [Closed] (CLOUDSTACK-6818) Create recipe to pull in systemvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Duffy closed CLOUDSTACK-6818. - Resolution: Done Done, result can be seen over at https://github.com/imduffy15/cookbook_cloudstack > Create recipe to pull in systemvm > - > > Key: CLOUDSTACK-6818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6818 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Ian Duffy >Assignee: Ian Duffy > > The system vms must be pre-downloaded onto the NFS box. > In order to do this I plan to write a recipe that will allow the user to > specify the URL of the system vm to be downloaded. > On execution the recipe will download the system vm and install it using the > cloud-install-sys-tmplt script. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025917#comment-14025917
]
ASF subversion and git services commented on CLOUDSTACK-6710:
-
Commit fae148d39606f25d814a45c273c9fc2fa9138d52 in cloudstack's branch
refs/heads/amoghs_44_commit from [~amogh.vasekar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fae148d ]
CLOUDSTACK-6710: Add missing OS mappings
> [Automation] VM snapshot failing with NPE in vmware
> ---
>
> Key: CLOUDSTACK-6710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
> Environment: Vmware 5.0
> 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Amogh Vasekar
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Execute BVT
> integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
> This test case creating VM snapshot in VMware; this is failing with below NPE
> 2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-130:job-390/job-391) Run VM work job:
> com.cloud.vm.snapshot.VmWorkCreateVMSn
> apshot for VM 62, job origin: 390
> 2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job:
> com.cloud.vm.snapsh
> ot.VmWorkCreateVMSnapshot{"vmSnapshotId":1,"quiesceVm":false,"userId":2,"accountId":2,"vmId":62,"handlerName":"VMSnapshotManagerImpl"}
> 2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm
> snapshot: 1
> java.lang.NullPointerException
> at
> org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> 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.$Proxy182.handleVmWorkJob(Unknown Source)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(
[jira] [Commented] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025924#comment-14025924
]
ASF subversion and git services commented on CLOUDSTACK-6710:
-
Commit ac92b3690304ff224e7e2530ea7d8e39f28a05c3 in cloudstack's branch
refs/heads/4.4-forward from [~amogh.vasekar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ac92b36 ]
CLOUDSTACK-6710: Add missing OS mappings
> [Automation] VM snapshot failing with NPE in vmware
> ---
>
> Key: CLOUDSTACK-6710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
> Environment: Vmware 5.0
> 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Amogh Vasekar
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Execute BVT
> integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
> This test case creating VM snapshot in VMware; this is failing with below NPE
> 2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-130:job-390/job-391) Run VM work job:
> com.cloud.vm.snapshot.VmWorkCreateVMSn
> apshot for VM 62, job origin: 390
> 2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job:
> com.cloud.vm.snapsh
> ot.VmWorkCreateVMSnapshot{"vmSnapshotId":1,"quiesceVm":false,"userId":2,"accountId":2,"vmId":62,"handlerName":"VMSnapshotManagerImpl"}
> 2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm
> snapshot: 1
> java.lang.NullPointerException
> at
> org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> 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.$Proxy182.handleVmWorkJob(Unknown Source)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(Async
[jira] [Commented] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025958#comment-14025958 ] ASF subversion and git services commented on CLOUDSTACK-6358: - Commit a4b401f29f83f2f0b467a9d05b509f951b5a3bca in cloudstack's branch refs/heads/4.4-forward from [~amogh.vasekar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a4b401f ] CLOUDSTACK-6358: Remove hardcoded VMware mappings, handle snapshots > Remove hardcoded guest OS mappings > -- > > Key: CLOUDSTACK-6358 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: Amogh Vasekar >Assignee: Amogh Vasekar >Priority: Critical > Fix For: 4.4.0 > > > The guest OS to platform emulator mappings are hardcoded in the codebase. > This needs to be removed so as to support dynamic addition of guest OS type -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6603) [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-6603. Resolution: Fixed > [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to > 4.4 > > > Key: CLOUDSTACK-6603 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6603 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.4.0 >Reporter: manasaveloori >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar, mysqldump43.dmp, mysqldump44.dmp > > > 1. Deploy CS 4.3 with 2 zones using xen 6.1 and KVM hypervisor. > 2. Configured LB rules,firewall rules. > 3. Registered the template for 4.4 (using the naming convention > systemvm-xenserver-4.4,systemvm-kvm-4.4) > 4. Upgraded to 4.4 > Start the management server: > Below are the observations: > 2014-05-05 05:05:13,567 DEBUG [c.c.s.StatsCollector] > (StatsCollector-4:ctx-e36f20e1) AutoScaling Monitor is running... > 2014-05-05 05:05:13,577 ERROR [c.c.s.StatsCollector] > (StatsCollector-4:ctx-e36f20e1) Error trying to monitor autoscaling > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@5b140551: SELECT autoscale_vmgroups.id, > autoscale_vmgroups.uuid, autoscale_vmgroups.zone_id, > autoscale_vmgroups.domain_id, autoscale_vmgroups.account_id, > autoscale_vmgroups.load_balancer_id, autoscale_vmgroups.min_members, > autoscale_vmgroups.max_members, autoscale_vmgroups.member_port, > autoscale_vmgroups.interval, autoscale_vmgroups.last_interval, > autoscale_vmgroups.profile_id, autoscale_vmgroups.removed, > autoscale_vmgroups.created, autoscale_vmgroups.state, > autoscale_vmgroups.display FROM autoscale_vmgroups WHERE > autoscale_vmgroups.removed IS NULL > at com.cloud.utils.db.GenericDaoBase.executeList(GenericDaoBase.java:1127) > at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1150) > at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1136) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at com.sun.proxy.$Proxy220.listAll(Unknown Source) > at > com.cloud.server.StatsCollector$AutoScaleMonitor.runInContext(StatsCollector.java:673) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown > c
[jira] [Resolved] (CLOUDSTACK-6831) [Hyper-V] Improve the logging for VM snapshot failures as it is not supported. Right now it is throwing NPEs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-6831. Resolution: Fixed > [Hyper-V] Improve the logging for VM snapshot failures as it is not > supported. Right now it is throwing NPEs > > > Key: CLOUDSTACK-6831 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6831 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 > Environment: HyperV >Reporter: Abhinav Roy >Assignee: Rajesh Battala > Fix For: 4.4.0 > > > Steps : > > 1. Deploy a advanced zone hyperv setup. > 2. Create a VM v1. > 3. Create a VM snapshot on v1 > Expected behavior : > > Since VM snapshot is not supported in 4.4.0 for HyperV, the operation should > fail gracefully with appropriate error message. > Observed behavior : > === > VM snapshot operation fails with a NPE > 2014-06-03 15:21:25,150 DEBUG [c.c.a.ApiServlet] > (catalina-exec-7:ctx-8ce4a754) ===START=== 10.144.7.13 -- GET > command=createVMSnapshot&virtualmachineid=fb624f96-c70f-4e25-94a0-65f9daf145aa&snapshotmemory=false&quiescevm=false&name=ss&response=json&sessionkey=o%2F8Vw1YoKZS4JAca7rkI3sCMSDs%3D&_=1401788814498 > 2014-06-03 15:21:25,168 ERROR [c.c.a.ApiServer] (catalina-exec-7:ctx-8ce4a754 > ctx-ce4443a6) unhandled exception executing api command: > [Ljava.lang.String;@7cfb6b51 > java.lang.NullPointerException > at > com.cloud.hypervisor.dao.HypervisorCapabilitiesDaoImpl.isVmSnapshotEnabled(HypervisorCapabilitiesDaoImpl.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy179.isVmSnapshotEnabled(Unknown Source) > at > com.cloud.vm.snapshot.VMSnapshotManagerImpl.allocVMSnapshot(VMSnapshotManagerImpl.java:265) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy182.allocVMSnapshot(Unknown Source) > at > org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd.create(CreateVMSnapshotCmd.java:92) > at > com.cloud.api.dispatch.CommandCreationWorker.handle(CommandCreationWorker.java:47) > at > com.cloud.api.dispatch.DispatchChain.dispatch(DispatchChain.java:37) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:79) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:614) > at com.cloud.api.ApiServe
[jira] [Resolved] (CLOUDSTACK-6833) [Hyper-V] Volume snapshot creation returns success even though snapshots are not supported for Hyper-V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-6833. Resolution: Fixed > [Hyper-V] Volume snapshot creation returns success even though snapshots are > not supported for Hyper-V > -- > > Key: CLOUDSTACK-6833 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6833 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Snapshot >Affects Versions: 4.4.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Assignee: Rajesh Battala > Fix For: 4.4.0 > > > Steps : > > 1. Deploy an advanced zone CS setup with hyperv . > 2. Create a VM. > 3. Goto the ROOT volume of the VM created in above step and take a snapshot. > Expected behavior : > > Since snapshots are not supported for Hyper-V in Felton, the operation should > error out with a valid exception/error and the job should fail. > Observed behaviour : > === > Exception is thrown in MS but the async job succeeds. In the UI also job > succeeds but snapshots are in error state. > 2014-06-03 15:31:30,360 DEBUG [o.a.c.s.s.SnapshotServiceImpl] > (Work-Job-Executor-40:ctx-9b7ff57b job-145/job-146 ctx-079ae456) create > snapshot stag4_ROOT-23_20140603100128 failed: > org.apache.cloudstack.storage.command.CreateObjectCommand failed on > exception, Object reference not set to an instance of an object. > 2014-06-03 15:31:30,382 DEBUG [o.a.c.s.s.XenserverSnapshotStrategy] > (Work-Job-Executor-40:ctx-9b7ff57b job-145/job-146 ctx-079ae456) Failed to > take snapshot: org.apache.cloudstack.storage.command.CreateObjectCommand > failed on exception, Object reference not set to an instance of an object. > 2014-06-03 15:31:30,398 DEBUG [c.c.s.s.SnapshotManagerImpl] > (Work-Job-Executor-40:ctx-9b7ff57b job-145/job-146 ctx-079ae456) Failed to > create snapshot > com.cloud.utils.exception.CloudRuntimeException: > org.apache.cloudstack.storage.command.CreateObjectCommand failed on > exception, Object reference not set to an instance of an object. > at > org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:287) > at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:922) > 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 $Proxy177.takeSnapshot(Unknown Source) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1503) > at > com.cloud.storage.VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(VolumeApiServiceImpl.java:1769) > at > com.cloud.storage.VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(VolumeApiServiceImpl.java:2504) > 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 > com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > at > com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2512) > 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) >
[jira] [Created] (CLOUDSTACK-6883) Golden Primary Storage
Hieu LE created CLOUDSTACK-6883: --- Summary: Golden Primary Storage Key: CLOUDSTACK-6883 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6883 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.5.0 Reporter: Hieu LE Assignee: Hieu LE Fix For: 4.5.0 Currently all VMs in CloudStack have not been guaranteed IOPS from the primary storage, especially shared storage. In some cases (such as deploying a large number of VMs), this could lead to slow performance and high boot-time of VM. In CloudStack 4.3, all VMs deployed in XenServer always have a child image VHD stay on the same storage repository with parent image (master image or golden image). Thus, this page describe a new approach in order to increase VM performance by decrease total IOPS in primary storage. The method is simply move the parent image to a new high-IOPS primary storage, similar with XenServer Intellicache feature. This method can reduce storage cost by 30-40%, compare to 80% of Intellicache. -- This message was sent by Atlassian JIRA (v6.2#6252)
