[jira] [Created] (CLOUDSTACK-8687) Update prepare template api to seed/prepare a template only on a give primary storage
Devdeep Singh created CLOUDSTACK-8687: - Summary: Update prepare template api to seed/prepare a template only on a give primary storage Key: CLOUDSTACK-8687 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8687 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh Currently, the prepare template api will seed/prepare a given template on all the primary storage pools in a zone. If however, a user wishes to prepare a template only a particular storage pool, it isn't possible. The prepare template api should be updated to allow seedng/preparing a template only on a given primary storage pool. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8687) Update prepare template api to seed/prepare a template only on a give primary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-8687: -- Status: Reviewable (was: In Progress) Update prepare template api to seed/prepare a template only on a give primary storage - Key: CLOUDSTACK-8687 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8687 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh Original Estimate: 2h Remaining Estimate: 2h Currently, the prepare template api will seed/prepare a given template on all the primary storage pools in a zone. If however, a user wishes to prepare a template only a particular storage pool, it isn't possible. The prepare template api should be updated to allow seedng/preparing a template only on a given primary storage pool. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8479) Disabling storage pool for provisioning of volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550069#comment-14550069 ] Devdeep Singh commented on CLOUDSTACK-8479: --- Pull request created for this feature here https://github.com/apache/cloudstack/pull/257 Disabling storage pool for provisioning of volumes -- Key: CLOUDSTACK-8479 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8479 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Devdeep Singh Assignee: Devdeep Singh This feature would allow an administrator to disable a storage pool from being used for provisioning of new volumes. Instances with volumes on a disabled pool will continue to run; however, no new volumes will get placed on the storage pool. This feature has been asked for in the community http://markmail.org/message/5jouqvojuhgnlzxt?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+Disable+primary+storage FS for this feature can also be looked up here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disabling+Storage+Pool+for+Provisioning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8479) Disabling storage pool for provisioning of volumes
Devdeep Singh created CLOUDSTACK-8479: - Summary: Disabling storage pool for provisioning of volumes Key: CLOUDSTACK-8479 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8479 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Reporter: Devdeep Singh Assignee: Devdeep Singh This feature would allow an administrator to disable a storage pool from being used for provisioning of new volumes. Instances with volumes on a disabled pool will continue to run; however, no new volumes will get placed on the storage pool. This feature has been asked for in the community http://markmail.org/message/5jouqvojuhgnlzxt?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+Disable+primary+storage FS for this feature can also be looked up here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disabling+Storage+Pool+for+Provisioning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8479) Disabling storage pool for provisioning of volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550206#comment-14550206 ] Devdeep Singh commented on CLOUDSTACK-8479: --- Merged to master in commit a99c9d0e68b42725a9f174d94f8d91c8a05398f3 and bab4e3a6af5ff5f8c20063d8ba82ac1dd021493f. Disabling storage pool for provisioning of volumes -- Key: CLOUDSTACK-8479 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8479 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Devdeep Singh Assignee: Devdeep Singh This feature would allow an administrator to disable a storage pool from being used for provisioning of new volumes. Instances with volumes on a disabled pool will continue to run; however, no new volumes will get placed on the storage pool. This feature has been asked for in the community http://markmail.org/message/5jouqvojuhgnlzxt?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+Disable+primary+storage FS for this feature can also be looked up here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disabling+Storage+Pool+for+Provisioning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8479) Disabling storage pool for provisioning of volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-8479. --- Resolution: Fixed Disabling storage pool for provisioning of volumes -- Key: CLOUDSTACK-8479 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8479 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Devdeep Singh Assignee: Devdeep Singh This feature would allow an administrator to disable a storage pool from being used for provisioning of new volumes. Instances with volumes on a disabled pool will continue to run; however, no new volumes will get placed on the storage pool. This feature has been asked for in the community http://markmail.org/message/5jouqvojuhgnlzxt?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+Disable+primary+storage FS for this feature can also be looked up here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disabling+Storage+Pool+for+Provisioning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6144) HA for guest VMs running Hyper-V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6144: -- Fix Version/s: (was: 4.5.0) Future HA for guest VMs running Hyper-V Key: CLOUDSTACK-6144 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6144 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.4.0 Reporter: Rajesh Battala Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6109) Support of iSCSI as primary store in Hyper-V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6109: -- Fix Version/s: (was: 4.5.0) Future Support of iSCSI as primary store in Hyper-V Key: CLOUDSTACK-6109 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6109 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.4.0 Reporter: Rajesh Battala Assignee: Devdeep Singh Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6109) Support of iSCSI as primary store in Hyper-V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230974#comment-14230974 ] Devdeep Singh commented on CLOUDSTACK-6109: --- I'll try to bring it in 4.6 release. Support of iSCSI as primary store in Hyper-V Key: CLOUDSTACK-6109 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6109 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.4.0 Reporter: Rajesh Battala Assignee: Devdeep Singh Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7642) [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7642. --- Resolution: Fixed [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV. -- Key: CLOUDSTACK-7642 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7642 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.5.0 Environment: upgrade from 4.3.0 to 4.5 using Xen server 6.2 Reporter: manasaveloori Assignee: Devdeep Singh Priority: Blocker Fix For: 4.5.0 Attachments: management-server.rar, mysqldump4.5.rar, mysqldumpBeforeUp.rar 1. Deployed 4.3.0 CS with 1zone,1 pod,1cluster,2 Xen 6.2 HVs using 4.3.0 build. 2. Registered the 4.5 template as systemvm-xenserver-4.5 3. Upgraded to 4.5 and started the MS. Observation: Observed the following exception in MS logs .Hosts went into disconnected stated. 2014-09-29 13:45:26,849 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Loading directly connected host 1(Rack1Pod1Host29) 2014-09-29 13:45:26,851 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to find class com.cloud.hypervisor.xen.resource.XenServer620Resource java.lang.ClassNotFoundException: com.cloud.hypervisor.xen.resource.XenServer620Resource at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:89) at com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:150) at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:680) at com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:219) at com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:185) at com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:99) at com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.runInContext(ClusteredAgentManagerImpl.java:235) at org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30) 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.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2014-09-29 13:45:26,852 WARN [c.c.a.m.AgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to load the resource: 1 2014-09-29 13:45:26,853 DEBUG [c.c.h.Status] (ClusteredAgentManager Timer:ctx-7b268e53) Transition:[Resource state = Enabled, Agent event = AgentDisconnected, Host id = 1, name = Rack1Pod1Host29] Attaching the dumps and logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6924) Exceptions are thrown when a data disk on local storage is attached/migrated to a clusterwide primary storage, zonewide primary storage or to local storage on anothe
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-6924:
--
Fix Version/s: (was: 4.4.0)
Exceptions are thrown when a data disk on local storage is attached/migrated
to a clusterwide primary storage, zonewide primary storage or to local
storage on another host
---
Key: CLOUDSTACK-6924
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6924
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 Setup with local storage, cluster wide primary
storage and zone wide primary storage
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Fix For: 4.5.0
Steps :
1. Deploy a hyperv Setup with multiple clusters having local storage, cluster
wide primary storage and zone wide primary storage.
2. Deploy VMs with datadisk
v1 on local storage on host1, v2 on cwps and v3 on zwps, v4 on local
storage on host2
3. Detach the data disk from v1 and attach to v2 or v3 or v4
Expected behavior :
=
Since the migration of a data disk on local storage to cpws , zwps or local
storage on another host is not supported, we should error out the operation
with appropriate error msg and should not throw any exception.
Observed behavior :
=
Expecptions are thrown during these operations :
MS logs when with conflicting Host and Cluster scope :
---
2014-06-17 15:11:47,303 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520) ===START=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,348 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) submit async job-93, details:
AsyncJobVO {id:93, userId: 2, accountId: 2, instanceType: Volume, instanceId:
23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,349 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) ===END=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,354 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-60:ctx-daa38c1b job-93) Add job-93 into job monitoring
2014-06-17 15:11:47,354 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93) Executing AsyncJobVO {id:93,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,372 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) Sync job-94 execution
on object VmWorkJobQueue.12
2014-06-17 15:11:47,375 DEBUG [c.c.s.VolumeApiServiceImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) New job 94, result
field: null
2014-06-17 15:11:47,375 WARN [c.c.u.d.Merovingian2]
(API-Job-Executor-60:ctx-daa38c1b job-93
[jira] [Resolved] (CLOUDSTACK-6924) Exceptions are thrown when a data disk on local storage is attached/migrated to a clusterwide primary storage, zonewide primary storage or to local storage on anoth
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-6924.
---
Resolution: Fixed
Exceptions are thrown when a data disk on local storage is attached/migrated
to a clusterwide primary storage, zonewide primary storage or to local
storage on another host
---
Key: CLOUDSTACK-6924
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6924
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 Setup with local storage, cluster wide primary
storage and zone wide primary storage
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Fix For: 4.5.0
Steps :
1. Deploy a hyperv Setup with multiple clusters having local storage, cluster
wide primary storage and zone wide primary storage.
2. Deploy VMs with datadisk
v1 on local storage on host1, v2 on cwps and v3 on zwps, v4 on local
storage on host2
3. Detach the data disk from v1 and attach to v2 or v3 or v4
Expected behavior :
=
Since the migration of a data disk on local storage to cpws , zwps or local
storage on another host is not supported, we should error out the operation
with appropriate error msg and should not throw any exception.
Observed behavior :
=
Expecptions are thrown during these operations :
MS logs when with conflicting Host and Cluster scope :
---
2014-06-17 15:11:47,303 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520) ===START=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,348 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) submit async job-93, details:
AsyncJobVO {id:93, userId: 2, accountId: 2, instanceType: Volume, instanceId:
23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,349 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) ===END=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,354 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-60:ctx-daa38c1b job-93) Add job-93 into job monitoring
2014-06-17 15:11:47,354 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93) Executing AsyncJobVO {id:93,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,372 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) Sync job-94 execution
on object VmWorkJobQueue.12
2014-06-17 15:11:47,375 DEBUG [c.c.s.VolumeApiServiceImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) New job 94, result
field: null
2014-06-17 15:11:47,375 WARN [c.c.u.d.Merovingian2]
(API-Job-Executor-60:ctx-daa38c1b job-93
[jira] [Updated] (CLOUDSTACK-6924) Exceptions are thrown when a data disk on local storage is attached/migrated to a clusterwide primary storage, zonewide primary storage or to local storage on anothe
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-6924:
--
Fix Version/s: (was: 4.5.0)
4.6.0
Exceptions are thrown when a data disk on local storage is attached/migrated
to a clusterwide primary storage, zonewide primary storage or to local
storage on another host
---
Key: CLOUDSTACK-6924
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6924
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 Setup with local storage, cluster wide primary
storage and zone wide primary storage
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Fix For: 4.6.0
Steps :
1. Deploy a hyperv Setup with multiple clusters having local storage, cluster
wide primary storage and zone wide primary storage.
2. Deploy VMs with datadisk
v1 on local storage on host1, v2 on cwps and v3 on zwps, v4 on local
storage on host2
3. Detach the data disk from v1 and attach to v2 or v3 or v4
Expected behavior :
=
Since the migration of a data disk on local storage to cpws , zwps or local
storage on another host is not supported, we should error out the operation
with appropriate error msg and should not throw any exception.
Observed behavior :
=
Expecptions are thrown during these operations :
MS logs when with conflicting Host and Cluster scope :
---
2014-06-17 15:11:47,303 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520) ===START=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,348 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) submit async job-93, details:
AsyncJobVO {id:93, userId: 2, accountId: 2, instanceType: Volume, instanceId:
23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,349 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) ===END=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,354 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-60:ctx-daa38c1b job-93) Add job-93 into job monitoring
2014-06-17 15:11:47,354 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93) Executing AsyncJobVO {id:93,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,372 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) Sync job-94 execution
on object VmWorkJobQueue.12
2014-06-17 15:11:47,375 DEBUG [c.c.s.VolumeApiServiceImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) New job 94, result
field: null
2014-06-17 15:11:47,375 WARN [c.c.u.d.Merovingian2]
[jira] [Closed] (CLOUDSTACK-7724) [Automation][HyperV] Unable to migrate VM due to JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh closed CLOUDSTACK-7724.
-
[Automation][HyperV] Unable to migrate VM due to JsonParseException: The
JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
-
Key: CLOUDSTACK-7724
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7724
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
=
JsonParseException: The JsonDeserializer EnumTypeAdapter failed to
deserialize json object Running
=
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Sending { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Executing: { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Executing request
2014-10-14 19:34:47,984 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST request to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
with contents
{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:47,990 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) Sending cmd to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
cmd
data:{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:48,099 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST response is
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{result:true,details:null,state:Running,contextMap:{}}}]
2014-10-14 19:34:48,148 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Throwable caught
while executing command
com.google.gson.JsonParseException: The JsonDeserializer EnumTypeAdapter
failed to deserialize json object Running given the type class
com.cloud.vm.VirtualMachine$PowerState
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:76)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:54)
at com.google.gson.Gson.fromJson(Gson.java:551)
at com.google.gson.Gson.fromJson(Gson.java:521)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:80)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:40)
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
at com.google.gson.Gson.fromJson(Gson.java:551)
at com.google.gson.Gson.fromJson(Gson.java:498)
at
[jira] [Updated] (CLOUDSTACK-7716) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-7716: -- Fix Version/s: (was: 4.5.0) 4.6.0 Triage and fix Coverity defects --- Key: CLOUDSTACK-7716 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7716 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Devdeep Singh Fix For: 4.6.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7716) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206569#comment-14206569 ] Devdeep Singh commented on CLOUDSTACK-7716: --- Moving the fix version to 4.6 Triage and fix Coverity defects --- Key: CLOUDSTACK-7716 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7716 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Devdeep Singh Fix For: 4.6.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7725) [Automation][HyperV] After sometime System VM 'agents' get disconnected due to Ping Issues and get shut down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7725. --- Resolution: Cannot Reproduce I did a fresh setup with the latest build for Hyper-V. I have left the system vms running for more than an hour now and I don't see them getting disconnected. Neither are they getting shutdown by the management server. Resolving the bug. Kindly reopen it if you see the problem in your setup. [Automation][HyperV] After sometime System VM 'agents' get disconnected due to Ping Issues and get shut down Key: CLOUDSTACK-7725 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7725 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip There is something still wrong with the Agents in System VMs on HyperV Setup. The System VM agents got disconnected due to Ping Issues and VMs got shut down. I found this observation when I noticed that all the SSVM Test cases failed. Someone has to look at what is happening between management server and agents communication. I don’t think it is anything wrong with the Setup based on the success of other test suites. === Disconnection Information Log is as shown below: === 2014-10-14 19:21:50,378 INFO [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Found the following agents behind on ping: [3, 4] 2014-10-14 19:21:50,380 WARN [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Disconnect agent for CPVM/SSVM due to physical connection close. host: 3 2014-10-14 19:21:50,381 INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Host 3 is disconnecting with event PingTimeout 2014-10-14 19:21:50,382 WARN [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Disconnect agent for CPVM/SSVM due to physical connection close. host: 4 2014-10-14 19:21:50,383 INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Host 4 is disconnecting with event PingTimeout 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) The next status of agent 3 is Alert, current status is Up 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Deregistering link for 3 with state Alert 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Remove Agent : 3 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.ConnectedAgentAttache] (AgentTaskPool-5:ctx-693d2497) Processing Disconnect. 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.hyperv.discoverer.HypervServerDiscoverer 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.storage.secondary.SecondaryStorageListener 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) The next status of agent 4 is Alert, current status is Up 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Deregistering link for 4 with state Alert 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Remove Agent : 4 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.ConnectedAgentAttache] (AgentTaskPool-6:ctx-f560f275) Processing Disconnect. 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.vm.ClusteredVirtualMachineManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: org.apache.cloudstack.engine.orchestration.NetworkOrchestrator 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.storage.listener.StoragePoolMonitor 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.vmware.manager.VmwareManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener:
[jira] [Resolved] (CLOUDSTACK-7721) [Automation] [Hyper-V] System VMs fail to deploy due to NPE: InvocationTargetException when invoking RPC callback for command: copyBaseImageCallback
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7721. --- Resolution: Fixed [Automation] [Hyper-V] System VMs fail to deploy due to NPE: InvocationTargetException when invoking RPC callback for command: copyBaseImageCallback Key: CLOUDSTACK-7721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7721 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 = NullPointerException: = 2014-10-14 15:40:28,113 DEBUG [o.a.c.s.i.s.TemplateObject] (Work-Job-Executor-2:ctx-8958a812 job-17/job-19 ctx-d2c645ce) failed to process event and answer java.lang.NullPointerException at org.apache.cloudstack.storage.image.store.TemplateObject.processEvent(TemplateObject.java:194) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyBaseImageCallback(VolumeServiceImpl.java:568) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:449) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:68) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:73) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:502) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:748) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1227) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1297) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:972) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4593) 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.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4749) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:513) 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:470) 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
[jira] [Resolved] (CLOUDSTACK-7310) XenServer does not support shrink data disk. CloudStack should prevent such an operation on XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7310. --- Resolution: Fixed This issue was fixed in commit 3773ff060e994d665b3b6d37f79df40c19a74c26 and commit f8031008139978abb6831a1d7cb240c993fbf8f5 where we capture and log a better message when the operation is carried out. User sees the message that a resize operation isn't supported for a data disk attached to a running vm. XenServer does not support shrink data disk. CloudStack should prevent such an operation on XenServer - Key: CLOUDSTACK-7310 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7310 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Volumes, XenServer Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 XenServer does not allowing shrinking of disks currently. Please add code on Cloudstack to prevent such an operation (similar to VMWare case). Failing to prevent such an operation on XenServer leads to https://issues.apache.org/jira/browse/CLOUDSTACK-7228 . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7724) [Automation][HyperV] Unable to migrate VM due to JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176732#comment-14176732
]
Devdeep Singh commented on CLOUDSTACK-7724:
---
I had already fixed this issue in commit
5350e61187d5b2f9fdc997dcc9fea34ff68148f7 on 19th September. The issue was fixed
against bug CLOUDSTACK-7494. The fix was in hyper-v agent. Hyper-v hosts are
probably running an older agent. This is the reason they are returning the
wrong state of the VM instead of the power state.
If you build and install the latest hyper-v agent, migration should be
successful. I tried it on a fresh setup and it was successful.
[Automation][HyperV] Unable to migrate VM due to JsonParseException: The
JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
-
Key: CLOUDSTACK-7724
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7724
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
=
JsonParseException: The JsonDeserializer EnumTypeAdapter failed to
deserialize json object Running
=
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Sending { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Executing: { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Executing request
2014-10-14 19:34:47,984 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST request to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
with contents
{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:47,990 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) Sending cmd to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
cmd
data:{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:48,099 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST response is
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{result:true,details:null,state:Running,contextMap:{}}}]
2014-10-14 19:34:48,148 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Throwable caught
while executing command
com.google.gson.JsonParseException: The JsonDeserializer EnumTypeAdapter
failed to deserialize json object Running given the type class
com.cloud.vm.VirtualMachine$PowerState
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:76)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:54)
at com.google.gson.Gson.fromJson(Gson.java:551)
at com.google.gson.Gson.fromJson(Gson.java:521)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:80)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:40)
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
[jira] [Resolved] (CLOUDSTACK-7724) [Automation][HyperV] Unable to migrate VM due to JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-7724.
---
Resolution: Duplicate
[Automation][HyperV] Unable to migrate VM due to JsonParseException: The
JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
-
Key: CLOUDSTACK-7724
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7724
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
=
JsonParseException: The JsonDeserializer EnumTypeAdapter failed to
deserialize json object Running
=
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Sending { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Executing: { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Executing request
2014-10-14 19:34:47,984 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST request to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
with contents
{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:47,990 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) Sending cmd to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
cmd
data:{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:48,099 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST response is
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{result:true,details:null,state:Running,contextMap:{}}}]
2014-10-14 19:34:48,148 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Throwable caught
while executing command
com.google.gson.JsonParseException: The JsonDeserializer EnumTypeAdapter
failed to deserialize json object Running given the type class
com.cloud.vm.VirtualMachine$PowerState
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:76)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:54)
at com.google.gson.Gson.fromJson(Gson.java:551)
at com.google.gson.Gson.fromJson(Gson.java:521)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:80)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:40)
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
at com.google.gson.Gson.fromJson(Gson.java:551)
at
[jira] [Resolved] (CLOUDSTACK-7737) [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7737. --- Resolution: Not a Problem [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering -- Key: CLOUDSTACK-7737 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7737 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 Deployed VM has the following memory configuration on the VM: [root@Atoms-VM-2 ~]# cat /proc/meminfo | grep Mem MemTotal: 363416 kB MemFree: 81864 kB [root@Atoms-VM-2 ~]# Which is around 354.8984375 MB But the Service Offering specified specifies 512 MB as shown below: mysql select id,name,instance_name,state,service_offering_id from vm_instance where id=59 \G id: 59 name: Atoms-VM-2 instance_name: i-36-59-VM state: Running service_offering_id: 1 1 row in set (0.00 sec) mysql select * from service_offering where id=1 \G id: 1 cpu: 1 speed: 500 ram_size: 512 nw_rate: NULL mc_rate: NULL ha_enabled: 0 limit_cpu_use: 0 host_tag: NULL default_use: 0 vm_type: NULL sort_key: 0 is_volatile: 0 deployment_planner: NULL 1 row in set (0.00 sec) mysql -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7737) [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176740#comment-14176740 ] Devdeep Singh commented on CLOUDSTACK-7737: --- I spoke to Chandan and had a look at his setup. Hyper-v agent is assigning the right memory to the vm. Even running a powershell command is reporting the expected memory PS C:\Users\Administrator.XSQA Get-VMMemory i-36-59-VM VMName DynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M) -- -- -- -- i-36-59-VM False512512512 PS C:\Users\Administrator.XSQA Get-VMMemory i-2-60-VM VMNameDynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M) -- -- -- -- i-2-60-VM False1024 1024 1024 Here the first VM is the one created by automation run and the second one is the one I created with a Medium service offering. The default CentOS template created for hyper-v is enabled with GUI. Maybe the memory is being used by video ram. On my local setup I created an instance with GUI and reported of 494 MB for a Small service offering when I checked in /proc/meminfo inside the VM. So I don’t think it is an issue here. [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering -- Key: CLOUDSTACK-7737 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7737 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 Deployed VM has the following memory configuration on the VM: [root@Atoms-VM-2 ~]# cat /proc/meminfo | grep Mem MemTotal: 363416 kB MemFree: 81864 kB [root@Atoms-VM-2 ~]# Which is around 354.8984375 MB But the Service Offering specified specifies 512 MB as shown below: mysql select id,name,instance_name,state,service_offering_id from vm_instance where id=59 \G id: 59 name: Atoms-VM-2 instance_name: i-36-59-VM state: Running service_offering_id: 1 1 row in set (0.00 sec) mysql select * from service_offering where id=1 \G id: 1 cpu: 1 speed: 500 ram_size: 512 nw_rate: NULL mc_rate: NULL ha_enabled: 0 limit_cpu_use: 0 host_tag: NULL default_use: 0 vm_type: NULL sort_key: 0 is_volatile: 0 deployment_planner: NULL 1 row in set (0.00 sec) mysql -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7724) [Automation][HyperV] Unable to migrate VM due to JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-7724:
-
Assignee: Devdeep Singh
[Automation][HyperV] Unable to migrate VM due to JsonParseException: The
JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
-
Key: CLOUDSTACK-7724
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7724
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
=
JsonParseException: The JsonDeserializer EnumTypeAdapter failed to
deserialize json object Running
=
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Sending { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Executing: { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Executing request
2014-10-14 19:34:47,984 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST request to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
with contents
{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:47,990 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) Sending cmd to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
cmd
data:{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:48,099 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST response is
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{result:true,details:null,state:Running,contextMap:{}}}]
2014-10-14 19:34:48,148 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Throwable caught
while executing command
com.google.gson.JsonParseException: The JsonDeserializer EnumTypeAdapter
failed to deserialize json object Running given the type class
com.cloud.vm.VirtualMachine$PowerState
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:76)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:54)
at com.google.gson.Gson.fromJson(Gson.java:551)
at com.google.gson.Gson.fromJson(Gson.java:521)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:80)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:40)
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
at com.google.gson.Gson.fromJson(Gson.java:551)
at
[jira] [Resolved] (CLOUDSTACK-7495) [Automation][HyperV] Stack trace along with error message - CloudStack currently only supports volumes marked as the KVM, VMware, or XenServer hypervisor type for r
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-7495.
---
Resolution: Fixed
[Automation][HyperV] Stack trace along with error message - CloudStack
currently only supports volumes marked as the KVM, VMware, or XenServer
hypervisor type for resize.
--
Key: CLOUDSTACK-7495
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7495
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
{code}
2014-09-03 17:55:32,084 DEBUG [c.c.a.ApiServlet]
(catalina-exec-11:ctx-5e814549 ctx-6724d865 ctx-56a27ef7) ===END===
10.220.135.217 -- GET
jobid=3f397629-d004-4020-a97d-8aa277ea2c61apiKey=hCPmYiAF1lm_sBLrhXIEWXCJt0vYbxzkeFfv7E1ZhyPPL_TF6BvI8cVOm2AqLlzWwa2w9dO0eFQu6SafM_st3gcommand=queryAsyncJobResultresponse=jsonsignature=6X9pGZqTxQTAxWy4N73kVno%2B62s%3D
2014-09-03 17:55:32,091 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-123:ctx-0a86f6fa job-255) Unexpected exception while
executing
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin
com.cloud.exception.InvalidParameterValueException: CloudStack currently only
supports volumes marked as the KVM, VMware, or XenServer hypervisor type for
resize.
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:725)
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:150)
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 $Proxy184.resizeVolume(Unknown Source)
at
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin.execute(ResizeVolumeCmdByAdmin.java:37)
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)
[jira] [Assigned] (CLOUDSTACK-7598) Cloudstack VM State is not in sync with state from Hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-7598: - Assignee: Devdeep Singh Cloudstack VM State is not in sync with state from Hypervisor - Key: CLOUDSTACK-7598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Devdeep Singh Priority: Blocker Fix For: 4.5.0 Attachments: vmsynclogs.rar Steps: 1. Install and configure Adv zone using XS 6.5 Hypervisor 2. Deploy Linux VM , Windows VM 3. After VM is up and running login to the VM and shutdown the instance 4. It moved to Shutdown state in the hypervisor 5. But this state is not synced to cloudstack and it remained in running state in cloudstack Observation: Cloudstack VM State is not in sync with state from Hypervisor Ob -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-7598) Cloudstack VM State is not in sync with state from Hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146216#comment-14146216 ] Devdeep Singh edited comment on CLOUDSTACK-7598 at 9/24/14 11:22 AM: - As part of commit 7f440854f7bcd41a1bd6581c0239cde2e98261b7, the directagentattache was updated to retry PingCommand to deal with network glitches. However, there is a minor bug in the logic because of which the agent attache is never sending the PingCommand. The vm state is retrieved as part of this ping command. So if a vm is stopped on the hypervisor, cloudstack will never update the state of the vms in its db. The retry logic needs to be fixed to make sure the command is send atleast once. was (Author: devdeep): As part of commit 7f440854f7bcd41a1bd6581c0239cde2e98261b7, the directagentattache was updated to retry PingCommand to deal with network glitches. However, there is a minor bug in the logic because of which the agent attache is never sending the PingCommand. The vm state is retrieved as part of this ping command. So if a vm is stopped on the hypervisor, cloudstack will never update the state of the vms in its db. The retyr logic needs to be fixed to make sure the command is send atleast once. Cloudstack VM State is not in sync with state from Hypervisor - Key: CLOUDSTACK-7598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Devdeep Singh Priority: Blocker Fix For: 4.5.0 Attachments: vmsynclogs.rar Steps: 1. Install and configure Adv zone using XS 6.5 Hypervisor 2. Deploy Linux VM , Windows VM 3. After VM is up and running login to the VM and shutdown the instance 4. It moved to Shutdown state in the hypervisor 5. But this state is not synced to cloudstack and it remained in running state in cloudstack Observation: Cloudstack VM State is not in sync with state from Hypervisor Ob -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7598) Cloudstack VM State is not in sync with state from Hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146216#comment-14146216 ] Devdeep Singh commented on CLOUDSTACK-7598: --- As part of commit 7f440854f7bcd41a1bd6581c0239cde2e98261b7, the directagentattache was updated to retry PingCommand to deal with network glitches. However, there is a minor bug in the logic because of which the agent attache is never sending the PingCommand. The vm state is retrieved as part of this ping command. So if a vm is stopped on the hypervisor, cloudstack will never update the state of the vms in its db. The retyr logic needs to be fixed to make sure the command is send atleast once. Cloudstack VM State is not in sync with state from Hypervisor - Key: CLOUDSTACK-7598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Devdeep Singh Priority: Blocker Fix For: 4.5.0 Attachments: vmsynclogs.rar Steps: 1. Install and configure Adv zone using XS 6.5 Hypervisor 2. Deploy Linux VM , Windows VM 3. After VM is up and running login to the VM and shutdown the instance 4. It moved to Shutdown state in the hypervisor 5. But this state is not synced to cloudstack and it remained in running state in cloudstack Observation: Cloudstack VM State is not in sync with state from Hypervisor Ob -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7494) [Automation][HyperV] Unable to Migrate VM - Error Message mentions that the operation is not supported
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-7494.
---
Resolution: Fixed
[Automation][HyperV] Unable to Migrate VM - Error Message mentions that the
operation is not supported
--
Key: CLOUDSTACK-7494
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7494
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
==
Test Client Code:
==
{code}
@attr(tags = [advanced, advancedns, smoke, basic, sg,
multihost], required_hardware=false)
def test_08_migrate_vm(self):
Test migrate VM
# Validate the following
# 1. Environment has enough hosts for migration
# 2. DeployVM on suitable host (with another host in the cluster)
# 3. Migrate the VM and assert migration successful
suitable_hosts = None
hosts = Host.list(
self.apiclient,
zoneid=self.zone.id,
type='Routing'
)
self.assertEqual(validateList(hosts)[0], PASS, hosts list validation
failed)
if len(hosts) 2:
self.skipTest(At least two hosts should be present in the zone
for migration)
hypervisor = str(get_hypervisor_type(self.apiclient)).lower()
# For KVM, two hosts used for migration should be present in same
cluster
# For XenServer and VMware, migration is possible between hosts
belonging to different clusters
# with the help of XenMotion and Vmotion respectively.
if hypervisor.lower() in [kvm,simulator]:
#identify suitable host
clusters = [h.clusterid for h in hosts]
#find hosts withe same clusterid
clusters = [cluster for index, cluster in enumerate(clusters) if
clusters.count(cluster) 1]
if len(clusters) = 1:
self.skipTest(In + hypervisor.lower() + Live Migration
needs two hosts within same cluster)
suitable_hosts = [host for host in hosts if host.clusterid ==
clusters[0]]
else:
suitable_hosts = hosts
target_host = suitable_hosts[0]
migrate_host = suitable_hosts[1]
#deploy VM on target host
self.vm_to_migrate = VirtualMachine.create(
self.apiclient,
self.services[small],
accountid=self.account.name,
domainid=self.account.domainid,
serviceofferingid=self.small_offering.id,
mode=self.services[mode],
hostid=target_host.id
)
self.debug(Migrating VM-ID: %s to Host: %s % (
self.vm_to_migrate.id,
migrate_host.id
))
self.vm_to_migrate.migrate(self.apiclient, migrate_host.id)
retries_cnt = 3
while retries_cnt =0:
list_vm_response = VirtualMachine.list(self.apiclient,
id=self.vm_to_migrate.id)
self.assertNotEqual(
list_vm_response,
None,
Check virtual machine is listed
)
vm_response = list_vm_response[0]
self.assertEqual(vm_response.id,self.vm_to_migrate.id,Check
virtual machine ID of migrated VM)
self.assertEqual(vm_response.hostid,migrate_host.id,Check
destination hostID of migrated VM)
retries_cnt = retries_cnt - 1
return
{code}
==
*Error message reported in the management log:*
==
{code}
2014-09-03 17:52:56,853 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-64:ctx-b2276c7f job-223/job-224 ctx-43ef9330) Invocation
exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Unable
to migrate due to com.cloud.agent.api.MigrateCommand failed due to Failed
migrating VM i-15-35-VM (GUID AA19CC47-04E5-498F-BC20-574262279F68) due to
NotSupported
2014-09-03 17:52:56,853 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-64:ctx-b2276c7f job-223/job-224 ctx-43ef9330) Rethrow
exception com.cloud.utils.exception.CloudRuntimeException: Unable to migrate
due to com.cloud.agent.api.MigrateCommand failed due to Failed migrating VM
i-15-35-VM (GUID
[jira] [Resolved] (CLOUDSTACK-7495) [Automation][HyperV] Stack trace along with error message - CloudStack currently only supports volumes marked as the KVM, VMware, or XenServer hypervisor type for r
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-7495.
---
Resolution: Not a Problem
This is a resize volume operation which is not supported for Hyper-V. The test
should be disabled for Hyper-V. Resolving the bug as not a problem.
[Automation][HyperV] Stack trace along with error message - CloudStack
currently only supports volumes marked as the KVM, VMware, or XenServer
hypervisor type for resize.
--
Key: CLOUDSTACK-7495
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7495
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
{code}
2014-09-03 17:55:32,084 DEBUG [c.c.a.ApiServlet]
(catalina-exec-11:ctx-5e814549 ctx-6724d865 ctx-56a27ef7) ===END===
10.220.135.217 -- GET
jobid=3f397629-d004-4020-a97d-8aa277ea2c61apiKey=hCPmYiAF1lm_sBLrhXIEWXCJt0vYbxzkeFfv7E1ZhyPPL_TF6BvI8cVOm2AqLlzWwa2w9dO0eFQu6SafM_st3gcommand=queryAsyncJobResultresponse=jsonsignature=6X9pGZqTxQTAxWy4N73kVno%2B62s%3D
2014-09-03 17:55:32,091 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-123:ctx-0a86f6fa job-255) Unexpected exception while
executing
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin
com.cloud.exception.InvalidParameterValueException: CloudStack currently only
supports volumes marked as the KVM, VMware, or XenServer hypervisor type for
resize.
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:725)
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:150)
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 $Proxy184.resizeVolume(Unknown Source)
at
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin.execute(ResizeVolumeCmdByAdmin.java:37)
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
[jira] [Resolved] (CLOUDSTACK-7359) Volume migration between pools times out on cloudstack, but the migration completes on Xenserver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7359. --- Resolution: Fixed Volume migration between pools times out on cloudstack, but the migration completes on Xenserver Key: CLOUDSTACK-7359 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7359 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical When a volume is live migrated from one storage pool to another, cloudstack sends a migratecommand to the resource. The agent waits for wait*3 seconds for the command to complete. Whereas the resource waits for migratewait seconds for the migration to complete. If volume migration doesn't complete within migratewait interval the operation is cancelled. (wait and migratewait for global configurable parameters). If wait parameter is much less than migratewait; the agent assumes the operation hasn't completed and moves ahead. On the resource side the operation would go ahead and complete at a later point in time. This leads to the volume being moved to a different storage pool, but the location isn't updated on the db. Subsequent operation on the vm/volume like stop start etc. will fail. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7359) Volume migration between pools times out on cloudstack, but the migration completes on Xenserver
Devdeep Singh created CLOUDSTACK-7359: - Summary: Volume migration between pools times out on cloudstack, but the migration completes on Xenserver Key: CLOUDSTACK-7359 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7359 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical When a volume is live migrated from one storage pool to another, cloudstack sends a migratecommand to the resource. The agent waits for wait*3 seconds for the command to complete. Whereas the resource waits for migratewait seconds for the migration to complete. If volume migration doesn't complete within migratewait interval the operation is cancelled. (wait and migratewait for global configurable parameters). If wait parameter is much less than migratewait; the agent assumes the operation hasn't completed and moves ahead. On the resource side the operation would go ahead and complete at a later point in time. This leads to the volume being moved to a different storage pool, but the location isn't updated on the db. Subsequent operation on the vm/volume like stop start etc. will fail. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7227) [Automation] Failed to generate certificate, sudo:keytool not found
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7227. --- Resolution: Cannot Reproduce The issue seems to be that keytool isn't available in the environment. Please verify that the tool is present. Resolving the bug. Kindly reopen the issue if the problem is not related to missing keytool [Automation] Failed to generate certificate, sudo:keytool not found --- Key: CLOUDSTACK-7227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7227 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Raja Pullela Assignee: Devdeep Singh Priority: Critical Following exception is seen the CI Automation Xen runs: 2014-07-31 20:11:51,236 INFO [c.c.s.ConfigurationServerImpl] (main:null) Processing updateSSLKeyStore 2014-07-31 20:11:51,239 INFO [c.c.s.ConfigurationServerImpl] (main:null) SSL keystore located at /automation/cloudstack/client/target/generated-webapp/WEB-INF/classes/cloud.keystore 2014-07-31 20:11:51,242 DEBUG [c.c.u.s.Script] (main:null) Executing: sudo keytool -genkey -keystore /automation/cloudstack/client/target/generated-webapp/WEB-INF/classes/cloud.keystore -storepass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn=Cloudstack User,ou=automation.hyd.com,o=automation.hyd.com,c=Unknown 2014-07-31 20:11:51,382 DEBUG [c.c.u.s.Script] (main:null) Exit value is 1 2014-07-31 20:11:51,383 DEBUG [c.c.u.s.Script] (main:null) sudo: keytool: command not found 2014-07-31 20:11:51,383 WARN [c.c.s.ConfigurationServerImpl] (main:null) Would use fail-safe keystore to continue. java.io.IOException: Fail to generate certificate!: sudo: keytool: command not found at com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:604) at com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:632) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:301) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:166) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79) at
[jira] [Assigned] (CLOUDSTACK-6924) Exceptions are thrown when a data disk on local storage is attached/migrated to a clusterwide primary storage, zonewide primary storage or to local storage on anoth
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-6924:
-
Assignee: Devdeep Singh
Exceptions are thrown when a data disk on local storage is attached/migrated
to a clusterwide primary storage, zonewide primary storage or to local
storage on another host
---
Key: CLOUDSTACK-6924
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6924
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 Setup with local storage, cluster wide primary
storage and zone wide primary storage
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Fix For: 4.4.0
Steps :
1. Deploy a hyperv Setup with multiple clusters having local storage, cluster
wide primary storage and zone wide primary storage.
2. Deploy VMs with datadisk
v1 on local storage on host1, v2 on cwps and v3 on zwps, v4 on local
storage on host2
3. Detach the data disk from v1 and attach to v2 or v3 or v4
Expected behavior :
=
Since the migration of a data disk on local storage to cpws , zwps or local
storage on another host is not supported, we should error out the operation
with appropriate error msg and should not throw any exception.
Observed behavior :
=
Expecptions are thrown during these operations :
MS logs when with conflicting Host and Cluster scope :
---
2014-06-17 15:11:47,303 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520) ===START=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,348 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) submit async job-93, details:
AsyncJobVO {id:93, userId: 2, accountId: 2, instanceType: Volume, instanceId:
23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,349 DEBUG [c.c.a.ApiServlet]
(catalina-exec-18:ctx-fb917520 ctx-0622857b) ===END=== 10.144.6.9 -- GET
command=attachVolumeid=8fcefeed-9606-45a0-a482-48a52554ecd1virtualMachineId=89612a65-8398-4a61-92b4-2431b9adbe52response=jsonsessionkey=usW3Wz8dQ4fHD24kCe9r5A27Tbc%3D_=1402997805674
2014-06-17 15:11:47,354 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-60:ctx-daa38c1b job-93) Add job-93 into job monitoring
2014-06-17 15:11:47,354 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93) Executing AsyncJobVO {id:93,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 23, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{response:json,id:8fcefeed-9606-45a0-a482-48a52554ecd1,sessionkey:usW3Wz8dQ4fHD24kCe9r5A27Tbc\u003d,ctxDetails:{\com.cloud.storage.Volume\:\8fcefeed-9606-45a0-a482-48a52554ecd1\,\com.cloud.vm.VirtualMachine\:\89612a65-8398-4a61-92b4-2431b9adbe52\},cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:89612a65-8398-4a61-92b4-2431b9adbe52,httpmethod:GET,_:1402997805674,uuid:8fcefeed-9606-45a0-a482-48a52554ecd1,ctxAccountId:2,ctxStartEventId:189},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-06-17 15:11:47,372 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) Sync job-94 execution
on object VmWorkJobQueue.12
2014-06-17 15:11:47,375 DEBUG [c.c.s.VolumeApiServiceImpl]
(API-Job-Executor-60:ctx-daa38c1b job-93 ctx-9c523ebe) New job 94, result
field: null
2014-06-17 15:11:47,375 WARN [c.c.u.d.Merovingian2]
(API-Job-Executor-60:ctx-daa38c1b job-93
[jira] [Created] (CLOUDSTACK-7244) 'Hyperv' doesn't get added to hypervisor list on upgrade
Devdeep Singh created CLOUDSTACK-7244: - Summary: 'Hyperv' doesn't get added to hypervisor list on upgrade Key: CLOUDSTACK-7244 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7244 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh On an upgrade from 4.2; 'Hyperv' doesn't get added to the hypervisor.list in the global configuration. Because of this; Hyperv option isn't available while creating a zone. User can manually edit the global parameter to add the 'Hyperv' hypervisor type. However, the issue needs to fixed so that the option is available by default. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7244) 'Hyperv' doesn't get added to hypervisor list on upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7244. --- Resolution: Fixed 'Hyperv' doesn't get added to hypervisor list on upgrade Key: CLOUDSTACK-7244 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7244 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh On an upgrade from 4.2; 'Hyperv' doesn't get added to the hypervisor.list in the global configuration. Because of this; Hyperv option isn't available while creating a zone. User can manually edit the global parameter to add the 'Hyperv' hypervisor type. However, the issue needs to fixed so that the option is available by default. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7201) migrate volume with live migrate = true allows migration across cluster or fails with NPE
Devdeep Singh created CLOUDSTACK-7201: - Summary: migrate volume with live migrate = true allows migration across cluster or fails with NPE Key: CLOUDSTACK-7201 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7201 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical migrate volume with livemigrate=true allows migrating the volume across clusters in case of Hyper-V. In case of XS, we are throwing an NPE although the migration correctly fails. Steps: = 0. Create a set up with at least 2 clusters 1. Deploy a VM with data disk 2. As admin, while VM is running migrate volume to another shared pool in another cluster (cloudmonkey) migrate volume livemigrate=true storageid=id of pool in another cluster volumeid=id of ROOT or DATA disk Expected Result: This shouldn't be allowed, we should fail the API with proper error message, allowing us to migrate volume only to storage pool within the same cluster, unless it is a zone wide storage pool. (If we want to achieve across cluster migration, we should use migrateVitualMachine with storage live migration) Result in Hyper-V = We end up with the volume migrated to another cluster storage pool while the VM is running off the original cluster storage pool. We should not allow this to happen. Result in XS 6.2 Migration correctly fails with error message but we also throw an NPE. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7201) migrate volume with live migrate = true allows migration across cluster or fails with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7201. --- Resolution: Fixed migrate volume with live migrate = true allows migration across cluster or fails with NPE - Key: CLOUDSTACK-7201 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7201 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical migrate volume with livemigrate=true allows migrating the volume across clusters in case of Hyper-V. In case of XS, we are throwing an NPE although the migration correctly fails. Steps: = 0. Create a set up with at least 2 clusters 1. Deploy a VM with data disk 2. As admin, while VM is running migrate volume to another shared pool in another cluster (cloudmonkey) migrate volume livemigrate=true storageid=id of pool in another cluster volumeid=id of ROOT or DATA disk Expected Result: This shouldn't be allowed, we should fail the API with proper error message, allowing us to migrate volume only to storage pool within the same cluster, unless it is a zone wide storage pool. (If we want to achieve across cluster migration, we should use migrateVitualMachine with storage live migration) Result in Hyper-V = We end up with the volume migrated to another cluster storage pool while the VM is running off the original cluster storage pool. We should not allow this to happen. Result in XS 6.2 Migration correctly fails with error message but we also throw an NPE. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7136) [Automation] NPE thrown during listing Hosts For Migration Of VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14079051#comment-14079051 ] Devdeep Singh commented on CLOUDSTACK-7136: --- The issue seems to be related to custom disk offering. For a custom disk offering the cpu and memory values are null and the user specifies them while creating an instance. In the allocator, these values are expected to be present in the offering object. This causes a null pointer exception. [Automation] NPE thrown during listing Hosts For Migration Of VM Key: CLOUDSTACK-7136 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7136 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 = NullPointer Exception: = 2014-07-11 15:38:49,980 DEBUG [c.c.a.ApiServlet] (catalina-exec-8:ctx-fe756f7e) ===START=== 10.220.64.12 -- GET signature=b5ug4%2FGZ2j39PwVI1etwVopiE7o%3DapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=queryAsyncJobResultresponse=jsonjobid=6a85f3b5-98fa-407d-90b6-16ed1b6d3ff5 2014-07-11 15:38:49,999 DEBUG [c.c.a.ApiServlet] (catalina-exec-8:ctx-fe756f7e ctx-305f25b6 ctx-957b41d0) ===END=== 10.220.64.12 -- GET signature=b5ug4%2FGZ2j39PwVI1etwVopiE7o%3DapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=queryAsyncJobResultresponse=jsonjobid=6a85f3b5-98fa-407d-90b6-16ed1b6d3ff5 2014-07-11 15:38:50,003 DEBUG [c.c.a.ApiServlet] (catalina-exec-5:ctx-0b26583d) ===START=== 10.220.64.12 -- GET apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAvirtualmachineid=64f87891-2ae6-486e-9ce0-c02a14bc38eccommand=listHostssignature=EiTYc1Um98AA34LKUSsqan2vRPA%3Dresponse=json 2014-07-11 15:38:50,027 DEBUG [o.a.c.a.HostAntiAffinityProcessor] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) Processing affinity group aff_grp_E3U2D3 for VM Id: 44 2014-07-11 15:38:50,031 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) FirstFitAllocator has 1 hosts to check for allocation: [Host[-2-Routing]] 2014-07-11 15:38:50,035 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) Found 1 hosts for allocation after prioritization: [Host[-2-Routing]] 2014-07-11 15:38:50,036 ERROR [c.c.a.ApiServer] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) unhandled exception executing api command: [Ljava.lang.String;@37e5f2d9 java.lang.NullPointerException at com.cloud.agent.manager.allocator.impl.FirstFitAllocator.allocateTo(FirstFitAllocator.java:253) at com.cloud.agent.manager.allocator.impl.FirstFitAllocator.allocateTo(FirstFitAllocator.java:225) at com.cloud.server.ManagementServerImpl.listHostsForMigrationOfVM(ManagementServerImpl.java:1226) 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 $Proxy236.listHostsForMigrationOfVM(Unknown Source) at org.apache.cloudstack.api.command.admin.host.ListHostsCmd.execute(ListHostsCmd.java:189) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) at
[jira] [Resolved] (CLOUDSTACK-7136) [Automation] NPE thrown during listing Hosts For Migration Of VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-7136. --- Resolution: Fixed [Automation] NPE thrown during listing Hosts For Migration Of VM Key: CLOUDSTACK-7136 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7136 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 = NullPointer Exception: = 2014-07-11 15:38:49,980 DEBUG [c.c.a.ApiServlet] (catalina-exec-8:ctx-fe756f7e) ===START=== 10.220.64.12 -- GET signature=b5ug4%2FGZ2j39PwVI1etwVopiE7o%3DapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=queryAsyncJobResultresponse=jsonjobid=6a85f3b5-98fa-407d-90b6-16ed1b6d3ff5 2014-07-11 15:38:49,999 DEBUG [c.c.a.ApiServlet] (catalina-exec-8:ctx-fe756f7e ctx-305f25b6 ctx-957b41d0) ===END=== 10.220.64.12 -- GET signature=b5ug4%2FGZ2j39PwVI1etwVopiE7o%3DapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=queryAsyncJobResultresponse=jsonjobid=6a85f3b5-98fa-407d-90b6-16ed1b6d3ff5 2014-07-11 15:38:50,003 DEBUG [c.c.a.ApiServlet] (catalina-exec-5:ctx-0b26583d) ===START=== 10.220.64.12 -- GET apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAvirtualmachineid=64f87891-2ae6-486e-9ce0-c02a14bc38eccommand=listHostssignature=EiTYc1Um98AA34LKUSsqan2vRPA%3Dresponse=json 2014-07-11 15:38:50,027 DEBUG [o.a.c.a.HostAntiAffinityProcessor] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) Processing affinity group aff_grp_E3U2D3 for VM Id: 44 2014-07-11 15:38:50,031 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) FirstFitAllocator has 1 hosts to check for allocation: [Host[-2-Routing]] 2014-07-11 15:38:50,035 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) Found 1 hosts for allocation after prioritization: [Host[-2-Routing]] 2014-07-11 15:38:50,036 ERROR [c.c.a.ApiServer] (catalina-exec-5:ctx-0b26583d ctx-c01743fd ctx-f1ba4ab8) unhandled exception executing api command: [Ljava.lang.String;@37e5f2d9 java.lang.NullPointerException at com.cloud.agent.manager.allocator.impl.FirstFitAllocator.allocateTo(FirstFitAllocator.java:253) at com.cloud.agent.manager.allocator.impl.FirstFitAllocator.allocateTo(FirstFitAllocator.java:225) at com.cloud.server.ManagementServerImpl.listHostsForMigrationOfVM(ManagementServerImpl.java:1226) 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 $Proxy236.listHostsForMigrationOfVM(Unknown Source) at org.apache.cloudstack.api.command.admin.host.ListHostsCmd.execute(ListHostsCmd.java:189) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
[jira] [Resolved] (CLOUDSTACK-6809) listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-6809. --- Resolution: Not a Problem We do not allow live storage motion of a volume from cluster wide to zone wide primary storage. That is why the findStoragePoolsForMigration api lists only zone wide pools for a volume on zone wide storage and cluster wide pools for a volume on cluster wide storage. This is the expected behavior. listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps -- Key: CLOUDSTACK-6809 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6809 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: HyperV Advanced zone setup with cluster wide, zone wide and local storages. Reporter: Abhinav Roy Assignee: Devdeep Singh Priority: Critical Labels: S1 Fix For: 4.4.0 Steps : == 1. Deploy a advanced zone hyperv setup with 2 clusters. 2. Have 2 primary storages in each of the clusters and 2 zone wide primary storages. 3. Deploy a VM v1 on cluster wide primary storage in cluster1/2 4. Deply a VM v2 on zone wide primary storage in cluster1/2. 5. Now do a listStoragePoolsForMigration for ROOT volumes of v1 and v2 Expected behavior : = All zone wide primary storage and cluster wide primary storages available should be listed Observed behavior : = 1. list for v1 doesn't show any zone wide primary storage. monkey# find storagepoolsformigration id=31 count = 1 storagepool: name = p2 id = b3fcb49c-b870-33e6-86f2-bb1eb72cceef clusterid = 5e649bb3-b2a8-49f9-9db0-ab50546d306a clustername = cluster1 created = 2014-05-26T11:27:01+0530 disksizeallocated = 1073741824 disksizetotal = 998772830208 disksizeused = 157359783936 ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps2?user=abhinavroydomain=BLR podid = f36ada26-ecf2-4869-ba4f-d844ec23531a podname = hyperv scope = CLUSTER state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv 2. list for v2 doesn't show any cluster wide primary storage monkey# find storagepoolsformigration id=30 count = 1 storagepool: name = zwps id = 3f754d4f-365c-3bd1-93d1-c3c9947fb3cc created = 2014-05-30T11:57:02+0530 disksizeallocated = 0 disksizetotal = 998772830208 hypervisor = Hyperv ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps6?user=abhinavroydomain=BLR scope = ZONE state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv NOTE : Even though the pools are not listed, if the migration is attempted using the API and passing these storage pool ids, migration succeeds from zwps to cwps and vice-versa -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6053) While adding smb as primary or secondary the password should be uri encoded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6053: -- Labels: S1 (was: ) While adding smb as primary or secondary the password should be uri encoded --- Key: CLOUDSTACK-6053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6053 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh Labels: S1 Fix For: 4.4.0 When a smb share is added as a primary or secondary the user, password and domain are passed in the url. If the password has special characters (like ) added the share fails as the server isn't able to parse the uri. User, password and details should be passed as details parameters in the api and the server side should be updated to understand it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6053) While adding smb as primary or secondary the password should be uri encoded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-6053. --- Resolution: Fixed Was already fixed. Resolving the bug While adding smb as primary or secondary the password should be uri encoded --- Key: CLOUDSTACK-6053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6053 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh Labels: S1 Fix For: 4.4.0 When a smb share is added as a primary or secondary the user, password and domain are passed in the url. If the password has special characters (like ) added the share fails as the server isn't able to parse the uri. User, password and details should be passed as details parameters in the api and the server side should be updated to understand it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6809) listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6809: -- Labels: S1 (was: ) listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps -- Key: CLOUDSTACK-6809 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6809 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: HyperV Advanced zone setup with cluster wide, zone wide and local storages. Reporter: Abhinav Roy Assignee: Devdeep Singh Priority: Critical Labels: S1 Fix For: 4.4.0 Steps : == 1. Deploy a advanced zone hyperv setup with 2 clusters. 2. Have 2 primary storages in each of the clusters and 2 zone wide primary storages. 3. Deploy a VM v1 on cluster wide primary storage in cluster1/2 4. Deply a VM v2 on zone wide primary storage in cluster1/2. 5. Now do a listStoragePoolsForMigration for ROOT volumes of v1 and v2 Expected behavior : = All zone wide primary storage and cluster wide primary storages available should be listed Observed behavior : = 1. list for v1 doesn't show any zone wide primary storage. monkey# find storagepoolsformigration id=31 count = 1 storagepool: name = p2 id = b3fcb49c-b870-33e6-86f2-bb1eb72cceef clusterid = 5e649bb3-b2a8-49f9-9db0-ab50546d306a clustername = cluster1 created = 2014-05-26T11:27:01+0530 disksizeallocated = 1073741824 disksizetotal = 998772830208 disksizeused = 157359783936 ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps2?user=abhinavroydomain=BLR podid = f36ada26-ecf2-4869-ba4f-d844ec23531a podname = hyperv scope = CLUSTER state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv 2. list for v2 doesn't show any cluster wide primary storage monkey# find storagepoolsformigration id=30 count = 1 storagepool: name = zwps id = 3f754d4f-365c-3bd1-93d1-c3c9947fb3cc created = 2014-05-30T11:57:02+0530 disksizeallocated = 0 disksizetotal = 998772830208 hypervisor = Hyperv ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps6?user=abhinavroydomain=BLR scope = ZONE state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv NOTE : Even though the pools are not listed, if the migration is attempted using the API and passing these storage pool ids, migration succeeds from zwps to cwps and vice-versa -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5746) Can't access vm console from IE browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5746: -- Summary: Can't access vm console from IE browser (was: [HyperV]Can't access vm console from IE browser) Can't access vm console from IE browser --- Key: CLOUDSTACK-5746 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5746 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Environment: Latest build from 4.3 branch with commit: 95b6a7b96dab1c77e25987d6fe6003b4447281f1 Reporter: Sanjeev N Assignee: Devdeep Singh Priority: Critical Fix For: 4.4.0 Attachments: console3.PNG [Hyper-v] Can't access vm console vm from IE browser Steps to reproduce: 1.Bring up CS in advanced zone with Hyper-v host 2.Deploy couple of guest vms using default cent os template 3.Try to access any of the vms (System/guest) using Internet Explorer Result: == Blank screen is displayed in IE browser. Observations: MS generates URL with secure token and opens console session in new browser. However browser displays blank white screen. 2014-01-03 12:14:53,651 DEBUG [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) Port info instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B 2014-01-03 12:14:53,651 INFO [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) Parse host info returned from executing GetVNCPortCommand. host info: instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) Compose console url: https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mwguest=windows 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) the console url is :: htmltitlewin7/titleframesetframe src=https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mwguest=windows;/frame/frameset/html Tried this with enabling/disabling compatablity view available on IE IE version 9 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5746) Can't access vm console from IE browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064759#comment-14064759 ] Devdeep Singh commented on CLOUDSTACK-5746: --- Issue isn't specific to Hyper-V. It is console proxy specific. Should be seen on IE8 and 9 against all hypervisors. Removing the Hyper-V name from the bug summary. Can't access vm console from IE browser --- Key: CLOUDSTACK-5746 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5746 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Environment: Latest build from 4.3 branch with commit: 95b6a7b96dab1c77e25987d6fe6003b4447281f1 Reporter: Sanjeev N Assignee: Devdeep Singh Priority: Critical Fix For: 4.4.0 Attachments: console3.PNG [Hyper-v] Can't access vm console vm from IE browser Steps to reproduce: 1.Bring up CS in advanced zone with Hyper-v host 2.Deploy couple of guest vms using default cent os template 3.Try to access any of the vms (System/guest) using Internet Explorer Result: == Blank screen is displayed in IE browser. Observations: MS generates URL with secure token and opens console session in new browser. However browser displays blank white screen. 2014-01-03 12:14:53,651 DEBUG [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) Port info instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B 2014-01-03 12:14:53,651 INFO [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) Parse host info returned from executing GetVNCPortCommand. host info: instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) Compose console url: https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mwguest=windows 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] (catalina-exec-20:null) the console url is :: htmltitlewin7/titleframesetframe src=https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mwguest=windows;/frame/frameset/html Tried this with enabling/disabling compatablity view available on IE IE version 9 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6810) Migration of a VM with volumes in local storage to another host in the same cluster is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-6810:
-
Assignee: Devdeep Singh
Migration of a VM with volumes in local storage to another host in the same
cluster is failing
--
Key: CLOUDSTACK-6810
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6810
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 advanced zone setup having 2 clusters and local
storage enabled
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Blocker
Fix For: 4.4.0
Steps :
==
1. Deploy an advanced zone Hyper-V setup having 2 clusters and local storage
enabled
2. Cluster1 has 2 hosts h1h2 and cluster 2 has 1 host h3
3. Create a VM v1 on h1 with its volume on local storage.
4. now migrate v1 to h2
Expected behavior :
===
Migration of v1 to h2 with storage should succeed.
Observed behavior :
===
1. Migration fails with :
2014-05-30 12:11:15,815 DEBUG [c.c.a.ApiServlet]
(catalina-exec-17:ctx-974c06fb ctx-97ad77c9) ===END=== 10.144.7.13 -- GET
command=migrateVirtualMachineWithVolumehostid=a8159199-7d97-4452-8e72-a7a2192bc00avirtualmachineid=f5c72950-100c-40b7-8a4c-42a10f1e1394response=jsonsessionkey=iBUNgVHSPfj%2F0RJrH4y0VHXcdWY%3D_=1401431807938
2014-05-30 12:11:15,816 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-37:ctx-cdc57df1 job-113) Add job-113 into job monitoring
2014-05-30 12:11:15,816 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-37:ctx-cdc57df1 job-113) Executing AsyncJobVO {id:113,
userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd,
cmdInfo:
{response:json,sessionkey:iBUNgVHSPfj/0RJrH4y0VHXcdWY\u003d,ctxDetails:{\com.cloud.vm.VirtualMachine\:20,\com.cloud.host.Host\:2},virtualmachineid:f5c72950-100c-40b7-8a4c-42a10f1e1394,cmdEventType:VM.MIGRATE,hostid:a8159199-7d97-4452-8e72-a7a2192bc00a,ctxUserId:2,httpmethod:GET,_:1401431807938,ctxAccountId:2,ctxStartEventId:200},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-30 12:11:15,824 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-37:ctx-cdc57df1 job-113 ctx-c34467bb) Received unknown
parameters for command migrateVirtualMachineWithVolume. Unknown parameters :
ctxdetails
2014-05-30 12:11:15,862 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-37:ctx-cdc57df1 job-113 ctx-c34467bb) Sync job-114
execution on object VmWorkJobQueue.20
2014-05-30 12:11:15,864 WARN [c.c.u.d.Merovingian2]
(API-Job-Executor-37:ctx-cdc57df1 job-113 ctx-c34467bb) Was unable to find
lock for the key vm_instance20 and thread id 1502122810
2014-05-30 12:11:16,455 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-79593829) Execute sync-queue item:
SyncQueueItemVO {id:49, queueId: 47, contentType: AsyncJob, contentId: 114,
lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null,
created: Fri May 30 12:11:15 IST 2014}
2014-05-30 12:11:16,457 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-79593829) Schedule queued job-114
2014-05-30 12:11:16,482 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-4:null) SeqA 3-75336: Processing Seq 3-75336: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-05-30 12:11:16,486 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Work-Job-Executor-41:ctx-18c2968f job-113/job-114) Add job-114 into job
monitoring
2014-05-30 12:11:16,486 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-41:ctx-18c2968f job-113/job-114) Executing AsyncJobVO
{id:114, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyACVjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZVdpdGhTdG9yYWdlsew9z6UxtXMCAANKAApkZXN0SG9zdElkSgAJc3JjSG9zdElkTAAMdm9sdW1lVG9Qb29sdAAPTGphdmEvdXRpbC9NYXA7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAUdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbAACAAFzcgARamF2YS51dGlsLkhhc2hNYXAFB9rBwxZg0QMAAkYACmxvYWRGYWN0b3JJAAl0aHJlc2hvbGR4cD9MdwgQAHg,
cmdVersion: 0,
[jira] [Resolved] (CLOUDSTACK-6810) Migration of a VM with volumes in local storage to another host in the same cluster is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-6810.
---
Resolution: Fixed
Migration of a VM with volumes in local storage to another host in the same
cluster is failing
--
Key: CLOUDSTACK-6810
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6810
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 advanced zone setup having 2 clusters and local
storage enabled
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Blocker
Fix For: 4.4.0
Steps :
==
1. Deploy an advanced zone Hyper-V setup having 2 clusters and local storage
enabled
2. Cluster1 has 2 hosts h1h2 and cluster 2 has 1 host h3
3. Create a VM v1 on h1 with its volume on local storage.
4. now migrate v1 to h2
Expected behavior :
===
Migration of v1 to h2 with storage should succeed.
Observed behavior :
===
1. Migration fails with :
2014-05-30 12:11:15,815 DEBUG [c.c.a.ApiServlet]
(catalina-exec-17:ctx-974c06fb ctx-97ad77c9) ===END=== 10.144.7.13 -- GET
command=migrateVirtualMachineWithVolumehostid=a8159199-7d97-4452-8e72-a7a2192bc00avirtualmachineid=f5c72950-100c-40b7-8a4c-42a10f1e1394response=jsonsessionkey=iBUNgVHSPfj%2F0RJrH4y0VHXcdWY%3D_=1401431807938
2014-05-30 12:11:15,816 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-37:ctx-cdc57df1 job-113) Add job-113 into job monitoring
2014-05-30 12:11:15,816 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-37:ctx-cdc57df1 job-113) Executing AsyncJobVO {id:113,
userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd,
cmdInfo:
{response:json,sessionkey:iBUNgVHSPfj/0RJrH4y0VHXcdWY\u003d,ctxDetails:{\com.cloud.vm.VirtualMachine\:20,\com.cloud.host.Host\:2},virtualmachineid:f5c72950-100c-40b7-8a4c-42a10f1e1394,cmdEventType:VM.MIGRATE,hostid:a8159199-7d97-4452-8e72-a7a2192bc00a,ctxUserId:2,httpmethod:GET,_:1401431807938,ctxAccountId:2,ctxStartEventId:200},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-30 12:11:15,824 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-37:ctx-cdc57df1 job-113 ctx-c34467bb) Received unknown
parameters for command migrateVirtualMachineWithVolume. Unknown parameters :
ctxdetails
2014-05-30 12:11:15,862 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-37:ctx-cdc57df1 job-113 ctx-c34467bb) Sync job-114
execution on object VmWorkJobQueue.20
2014-05-30 12:11:15,864 WARN [c.c.u.d.Merovingian2]
(API-Job-Executor-37:ctx-cdc57df1 job-113 ctx-c34467bb) Was unable to find
lock for the key vm_instance20 and thread id 1502122810
2014-05-30 12:11:16,455 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-79593829) Execute sync-queue item:
SyncQueueItemVO {id:49, queueId: 47, contentType: AsyncJob, contentId: 114,
lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null,
created: Fri May 30 12:11:15 IST 2014}
2014-05-30 12:11:16,457 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-79593829) Schedule queued job-114
2014-05-30 12:11:16,482 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-4:null) SeqA 3-75336: Processing Seq 3-75336: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-05-30 12:11:16,486 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Work-Job-Executor-41:ctx-18c2968f job-113/job-114) Add job-114 into job
monitoring
2014-05-30 12:11:16,486 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-41:ctx-18c2968f job-113/job-114) Executing AsyncJobVO
{id:114, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyACVjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZVdpdGhTdG9yYWdlsew9z6UxtXMCAANKAApkZXN0SG9zdElkSgAJc3JjSG9zdElkTAAMdm9sdW1lVG9Qb29sdAAPTGphdmEvdXRpbC9NYXA7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAUdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbAACAAFzcgARamF2YS51dGlsLkhhc2hNYXAFB9rBwxZg0QMAAkYACmxvYWRGYWN0b3JJAAl0aHJlc2hvbGR4cD9MdwgQAHg,
cmdVersion: 0, status:
[jira] [Assigned] (CLOUDSTACK-6802) [HyperV] Attaching a data disk created on local storage to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-6802:
-
Assignee: Devdeep Singh
[HyperV] Attaching a data disk created on local storage to a VM is failing
--
Key: CLOUDSTACK-6802
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
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
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.4.0
Steps :
=
1. Deploy a CS advanced zone setup with both local storage and shared storage
enabled.
2. Deploy VMs. ( both on shared and local storage)
3. create a disk offering with local storage
4. Create a data disk with local storage disk offering.
5. attach the datadisk created on step 4 to VM created on step 2
Expected result :
===
Volume should be attached successfully.
Observed result :
==
volume attach fails with following error.
2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
command=createVolumeresponse=jsonsessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3Dname=data-local2zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24_=1401348494217
2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
18, cmd:
org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
cmdInfo:
{id:18,response:json,sessionkey:YYidBdJcBJV64kdZ8c+KOeSqY14\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\,\com.cloud.dc.DataCenter\:1,\com.cloud.offering.DiskOffering\:14},cmdEventType:VOLUME.CREATE,ctxUserId:2,name:data-local2,diskOfferingId:8cf4d614-08b8-455c-a99f-814f4b109d24,httpmethod:GET,_:1401348494217,uuid:dd5d8d32-03b4-4afd-80ca-58586c7c9e8d,ctxAccountId:2,ctxStartEventId:125,zoneId:242c701a-43e8-4790-84f3-9112ca0b5db7},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
command=createVolumeresponse=jsonsessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3Dname=data-local2zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24_=1401348494217
2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
cmdInfo:
{id:18,response:json,sessionkey:YYidBdJcBJV64kdZ8c+KOeSqY14\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\,\com.cloud.dc.DataCenter\:1,\com.cloud.offering.DiskOffering\:14},cmdEventType:VOLUME.CREATE,ctxUserId:2,name:data-local2,diskOfferingId:8cf4d614-08b8-455c-a99f-814f4b109d24,httpmethod:GET,_:1401348494217,uuid:dd5d8d32-03b4-4afd-80ca-58586c7c9e8d,ctxAccountId:2,ctxStartEventId:125,zoneId:242c701a-43e8-4790-84f3-9112ca0b5db7},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
parameters for command createVolume. Unknown parameters : ctxdetails
2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
jobStatus: SUCCEEDED, resultCode: 0, result:
[jira] [Updated] (CLOUDSTACK-6802) Attaching a data disk created on local storage to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-6802:
--
Summary: Attaching a data disk created on local storage to a VM is failing
(was: [HyperV] Attaching a data disk created on local storage to a VM is
failing)
Attaching a data disk created on local storage to a VM is failing
-
Key: CLOUDSTACK-6802
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
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
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.4.0
Steps :
=
1. Deploy a CS advanced zone setup with both local storage and shared storage
enabled.
2. Deploy VMs. ( both on shared and local storage)
3. create a disk offering with local storage
4. Create a data disk with local storage disk offering.
5. attach the datadisk created on step 4 to VM created on step 2
Expected result :
===
Volume should be attached successfully.
Observed result :
==
volume attach fails with following error.
2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
command=createVolumeresponse=jsonsessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3Dname=data-local2zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24_=1401348494217
2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
18, cmd:
org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
cmdInfo:
{id:18,response:json,sessionkey:YYidBdJcBJV64kdZ8c+KOeSqY14\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\,\com.cloud.dc.DataCenter\:1,\com.cloud.offering.DiskOffering\:14},cmdEventType:VOLUME.CREATE,ctxUserId:2,name:data-local2,diskOfferingId:8cf4d614-08b8-455c-a99f-814f4b109d24,httpmethod:GET,_:1401348494217,uuid:dd5d8d32-03b4-4afd-80ca-58586c7c9e8d,ctxAccountId:2,ctxStartEventId:125,zoneId:242c701a-43e8-4790-84f3-9112ca0b5db7},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
command=createVolumeresponse=jsonsessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3Dname=data-local2zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24_=1401348494217
2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
cmdInfo:
{id:18,response:json,sessionkey:YYidBdJcBJV64kdZ8c+KOeSqY14\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\,\com.cloud.dc.DataCenter\:1,\com.cloud.offering.DiskOffering\:14},cmdEventType:VOLUME.CREATE,ctxUserId:2,name:data-local2,diskOfferingId:8cf4d614-08b8-455c-a99f-814f4b109d24,httpmethod:GET,_:1401348494217,uuid:dd5d8d32-03b4-4afd-80ca-58586c7c9e8d,ctxAccountId:2,ctxStartEventId:125,zoneId:242c701a-43e8-4790-84f3-9112ca0b5db7},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
parameters for command createVolume. Unknown parameters : ctxdetails
2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
jobStatus: SUCCEEDED, resultCode: 0, result:
[jira] [Commented] (CLOUDSTACK-6802) Attaching a data disk created on local storage to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012302#comment-14012302
]
Devdeep Singh commented on CLOUDSTACK-6802:
---
Issue is with the local storage pool allocators. They way it is listing pools
needs to be fixed. The query does a join on the details table even when no tags
are present which ends up returning an empty list.
Attaching a data disk created on local storage to a VM is failing
-
Key: CLOUDSTACK-6802
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
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
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.4.0
Steps :
=
1. Deploy a CS advanced zone setup with both local storage and shared storage
enabled.
2. Deploy VMs. ( both on shared and local storage)
3. create a disk offering with local storage
4. Create a data disk with local storage disk offering.
5. attach the datadisk created on step 4 to VM created on step 2
Expected result :
===
Volume should be attached successfully.
Observed result :
==
volume attach fails with following error.
2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
command=createVolumeresponse=jsonsessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3Dname=data-local2zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24_=1401348494217
2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
18, cmd:
org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
cmdInfo:
{id:18,response:json,sessionkey:YYidBdJcBJV64kdZ8c+KOeSqY14\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\,\com.cloud.dc.DataCenter\:1,\com.cloud.offering.DiskOffering\:14},cmdEventType:VOLUME.CREATE,ctxUserId:2,name:data-local2,diskOfferingId:8cf4d614-08b8-455c-a99f-814f4b109d24,httpmethod:GET,_:1401348494217,uuid:dd5d8d32-03b4-4afd-80ca-58586c7c9e8d,ctxAccountId:2,ctxStartEventId:125,zoneId:242c701a-43e8-4790-84f3-9112ca0b5db7},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
command=createVolumeresponse=jsonsessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3Dname=data-local2zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24_=1401348494217
2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64,
userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
cmdInfo:
{id:18,response:json,sessionkey:YYidBdJcBJV64kdZ8c+KOeSqY14\u003d,ctxDetails:{\com.cloud.storage.Volume\:18,\Volume\:\dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\,\com.cloud.dc.DataCenter\:1,\com.cloud.offering.DiskOffering\:14},cmdEventType:VOLUME.CREATE,ctxUserId:2,name:data-local2,diskOfferingId:8cf4d614-08b8-455c-a99f-814f4b109d24,httpmethod:GET,_:1401348494217,uuid:dd5d8d32-03b4-4afd-80ca-58586c7c9e8d,ctxAccountId:2,ctxStartEventId:125,zoneId:242c701a-43e8-4790-84f3-9112ca0b5db7},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
parameters for command createVolume. Unknown parameters : ctxdetails
2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
jobStatus: SUCCEEDED, resultCode: 0, result:
[jira] [Resolved] (CLOUDSTACK-6622) [Hyper-V] After storage migration the folder path in DB contains SMB credentials.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-6622. --- Resolution: Fixed [Hyper-V] After storage migration the folder path in DB contains SMB credentials. - Key: CLOUDSTACK-6622 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6622 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Devdeep Singh Priority: Critical Fix For: 4.4.0 On a Hyper-V setup, deploy an instance in a cluster with multiple storage pools. Live migrate (storage motion) a volume of a virtual machine from one storage pool to another. After migration the destination storage SMB credentials are visible in the folder column (volumes table) in the db. Same behavior is observed when a virtual machine is live migrated from one host to another and the volumes of the vm also get migrated to a different storage pool (storage motion). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6510) java.lang.IllegalStateException: circular reference error during live migration of VM.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-6510.
---
Resolution: Fixed
java.lang.IllegalStateException: circular reference error during live
migration of VM.
--
Key: CLOUDSTACK-6510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.4.0
Environment: MS 4.4
XS 6.2.0
Reporter: Sanjay Tripathi
Assignee: Devdeep Singh
Fix For: 4.4.0
Getting the following exception during live migration of VM, though this is
not affecting live migration functionality:
2014-04-25 13:59:27,699 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-2:job-71/job-72 ctx-1920db32) Seq 4-3947968023343661101:
Executing: { Cmd , MgmtId: 116698015432997, via: 4(xen20.cloud.com), Ver:
v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-2-9-VM,wait:20}}]
}
2014-04-25 13:59:27,700 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-36:ctx-a412b1b1) Seq 4-3947968023343661101: Executing request
2014-04-25 13:59:27,718 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-36:ctx-a412b1b1) 3. The VM i-2-9-VM is in Running state
2014-04-25 13:59:27,719 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-36:ctx-a412b1b1) Seq 4-3947968023343661101: Response Received:
2014-04-25 13:59:27,719 DEBUG [c.c.a.t.Request] (DirectAgent-36:ctx-a412b1b1)
Seq 4-3947968023343661101: Processing: { Ans: , MgmtId: 116698015432997,
via: 4, Ver: v1, Flags: 10,
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{state:Running,result:true,wait:0}}]
}
2014-04-25 13:59:27,721 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-2:job-71/job-72 ctx-1920db32) Seq 4-3947968023343661101:
Received: { Ans: , MgmtId: 116698015432997, via: 4, Ver: v1, Flags: 10, {
CheckVirtualMachineAnswer } }
2014-04-25 13:59:27,735 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-59:ctx-3603e975) Seq 1-2562829662950522954: Response Received:
2014-04-25 13:59:27,736 DEBUG [c.c.a.t.Request]
(StatsCollector-1:ctx-8f878bfd) Seq 1-2562829662950522954: Received: { Ans:
, MgmtId: 116698015432997, via: 1, Ver: v1, Flags: 10, { GetGPUStatsAnswer } }
2014-04-25 13:59:27,807 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-2:job-71/job-72) Done with run of VM work job:
com.cloud.vm.VmWorkMigrate for VM 9, job origin: 71
2014-04-25 13:59:27,807 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-2:job-71/job-72) Unable to complete AsyncJobVO {id:72,
userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyACVjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZVdpdGhTdG9yYWdlsew9z6UxtXMCAANKAApkZXN0SG9zdElkSgAJc3JjSG9zdElkTAAMdm9sdW1lVG9Qb29sdAAPTGphdmEvdXRpbC9NYXA7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAJdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbAAEAAVzcgARamF2YS51dGlsLkhhc2hNYXAFB9rBwxZg0QMAAkYACmxvYWRGYWN0b3JJAAl0aHJlc2hvbGR4cD9MdwgQAHg,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 116698015432997, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Fri Apr 25 13:55:58 IST 2014}, job origin:71
java.lang.IllegalStateException: circular reference error
Offending field: field
Offending object: preserveType: false, type: class java.lang.reflect.Field,
obj: private long org.apache.cloudstack.storage.datastore.db.StoragePoolVO.id
at
com.google.gson.CircularReferenceException.createDetailedException(CircularReferenceException.java:43)
at
com.google.gson.JsonSerializationVisitor.visitObjectField(JsonSerializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:69)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonSerializationVisitor.getJsonElementForChild(JsonSerializationVisitor.java:147)
at
com.google.gson.JsonSerializationVisitor.addAsChildOfObject(JsonSerializationVisitor.java:127)
at
com.google.gson.JsonSerializationVisitor.visitObjectField(JsonSerializationVisitor.java:114)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:69)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonSerializationVisitor.getJsonElementForChild(JsonSerializationVisitor.java:147)
at
[jira] [Created] (CLOUDSTACK-6622) [Hyper-V] After storage migration the folder path in DB contains SMB credentials.
Devdeep Singh created CLOUDSTACK-6622: - Summary: [Hyper-V] After storage migration the folder path in DB contains SMB credentials. Key: CLOUDSTACK-6622 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6622 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Devdeep Singh Priority: Critical Fix For: 4.4.0 On a Hyper-V setup, deploy an instance in a cluster with multiple storage pools. Live migrate (storage motion) a volume of a virtual machine from one storage pool to another. After migration the destination storage SMB credentials are visible in the folder column (volumes table) in the db. Same behavior is observed when a virtual machine is live migrated from one host to another and the volumes of the vm also get migrated to a different storage pool (storage motion). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5463) Hyper-V does not report stopped VMs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5463.
---
Resolution: Fixed
It was fixed in commit d45ee3ef21fd55c8a1cf1373225cab81389ad8c7 and
3ec7497e1ebcaa65a8cbd24c27326356355ac8cc; as part of vmsync changes. When a vm
is stopped outside cloudstack; say by Hyper-V manager; the state of the vm is
updated to stopped in cloudstack db too.
Hyper-V does not report stopped VMs
---
Key: CLOUDSTACK-5463
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5463
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Donal Lafferty
Assignee: Devdeep Singh
Labels: Hyper-V
Fix For: 4.4.0
The Hyper-V agent is never asked whether a VM is running. E.g. it is only
asked the VmStats:
2013-12-11 06:28:08,544 [32] INFO HypervResource.HypervResourceController
[7bbebc6a-400a-4d9f-832a-06924b823ba4] -
com.cloud.agent.api.GetVmStatsCommand{
vmNames: [
i-2-3-VM
],
hostGuid: 700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource,
hostName: 10.70.176.29,
contextMap: {},
wait: 0
}
2013-12-11 06:28:08,716 [32] DEBUG HypervResource.WmiCallsV2
[7bbebc6a-400a-4d9f-832a-06924b823ba4] - VM
20E0665F-4EE0-42A5-AC94-03DC9D3B5E8C(elementName i-2-3-VM) has 1 CPUs, and
load of 0
2013-12-11 06:28:08,717 [32] INFO HypervResource.HypervResourceController
[7bbebc6a-400a-4d9f-832a-06924b823ba4] - {
com.cloud.agent.api.GetVmStatsAnswer: {
vmStatsMap: {
i-2-3-VM: {
cpuUtilization: 0.0,
networkReadKBs: 1.0,
networkWriteKBs: 1.0,
numCPUs: 1,
entityType: vm
}
},
result: true,
contextMap: {}
}
}
Therefore, if the VM shut itself down, the management server thinks it is
still running.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6510) java.lang.IllegalStateException: circular reference error during live migration of VM.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-6510:
-
Assignee: Devdeep Singh
java.lang.IllegalStateException: circular reference error during live
migration of VM.
--
Key: CLOUDSTACK-6510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.4.0
Environment: MS 4.4
XS 6.2.0
Reporter: Sanjay Tripathi
Assignee: Devdeep Singh
Fix For: 4.4.0
Getting the following exception during live migration of VM, though this is
not affecting live migration functionality:
2014-04-25 13:59:27,699 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-2:job-71/job-72 ctx-1920db32) Seq 4-3947968023343661101:
Executing: { Cmd , MgmtId: 116698015432997, via: 4(xen20.cloud.com), Ver:
v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-2-9-VM,wait:20}}]
}
2014-04-25 13:59:27,700 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-36:ctx-a412b1b1) Seq 4-3947968023343661101: Executing request
2014-04-25 13:59:27,718 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-36:ctx-a412b1b1) 3. The VM i-2-9-VM is in Running state
2014-04-25 13:59:27,719 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-36:ctx-a412b1b1) Seq 4-3947968023343661101: Response Received:
2014-04-25 13:59:27,719 DEBUG [c.c.a.t.Request] (DirectAgent-36:ctx-a412b1b1)
Seq 4-3947968023343661101: Processing: { Ans: , MgmtId: 116698015432997,
via: 4, Ver: v1, Flags: 10,
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{state:Running,result:true,wait:0}}]
}
2014-04-25 13:59:27,721 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-2:job-71/job-72 ctx-1920db32) Seq 4-3947968023343661101:
Received: { Ans: , MgmtId: 116698015432997, via: 4, Ver: v1, Flags: 10, {
CheckVirtualMachineAnswer } }
2014-04-25 13:59:27,735 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-59:ctx-3603e975) Seq 1-2562829662950522954: Response Received:
2014-04-25 13:59:27,736 DEBUG [c.c.a.t.Request]
(StatsCollector-1:ctx-8f878bfd) Seq 1-2562829662950522954: Received: { Ans:
, MgmtId: 116698015432997, via: 1, Ver: v1, Flags: 10, { GetGPUStatsAnswer } }
2014-04-25 13:59:27,807 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-2:job-71/job-72) Done with run of VM work job:
com.cloud.vm.VmWorkMigrate for VM 9, job origin: 71
2014-04-25 13:59:27,807 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-2:job-71/job-72) Unable to complete AsyncJobVO {id:72,
userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyACVjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZVdpdGhTdG9yYWdlsew9z6UxtXMCAANKAApkZXN0SG9zdElkSgAJc3JjSG9zdElkTAAMdm9sdW1lVG9Qb29sdAAPTGphdmEvdXRpbC9NYXA7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAJdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbAAEAAVzcgARamF2YS51dGlsLkhhc2hNYXAFB9rBwxZg0QMAAkYACmxvYWRGYWN0b3JJAAl0aHJlc2hvbGR4cD9MdwgQAHg,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 116698015432997, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Fri Apr 25 13:55:58 IST 2014}, job origin:71
java.lang.IllegalStateException: circular reference error
Offending field: field
Offending object: preserveType: false, type: class java.lang.reflect.Field,
obj: private long org.apache.cloudstack.storage.datastore.db.StoragePoolVO.id
at
com.google.gson.CircularReferenceException.createDetailedException(CircularReferenceException.java:43)
at
com.google.gson.JsonSerializationVisitor.visitObjectField(JsonSerializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:69)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonSerializationVisitor.getJsonElementForChild(JsonSerializationVisitor.java:147)
at
com.google.gson.JsonSerializationVisitor.addAsChildOfObject(JsonSerializationVisitor.java:127)
at
com.google.gson.JsonSerializationVisitor.visitObjectField(JsonSerializationVisitor.java:114)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:69)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonSerializationVisitor.getJsonElementForChild(JsonSerializationVisitor.java:147)
at
[jira] [Resolved] (CLOUDSTACK-5743) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5743. --- Resolution: Fixed Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server - Key: CLOUDSTACK-5743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: 4.3, Hyper-V, Vmware Reporter: Abhinav Roy Assignee: Devdeep Singh Fix For: 4.3.0 Steps : 1. Create an advanced zone setup with hyper-v as the host hypervisor type and shared CIFS storage for primary storage 2. Deploy a VM 3. stop the VM 4. Goto the ROOT/Data volume of the VM and try to download it. Expected behaviour : = The volume should be successfully downloaded . Observed behaviour : = ROOT volume download fails with the following message in the UI : Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server There is nothing in the MS log or Agent logs. NOTE : The operation is failing for all hypervisors. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-5743) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5743: - Assignee: Devdeep Singh Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server - Key: CLOUDSTACK-5743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: 4.3, Hyper-V, Vmware Reporter: Abhinav Roy Assignee: Devdeep Singh Fix For: 4.3.0 Steps : 1. Create an advanced zone setup with hyper-v as the host hypervisor type and shared CIFS storage for primary storage 2. Deploy a VM 3. stop the VM 4. Goto the ROOT/Data volume of the VM and try to download it. Expected behaviour : = The volume should be successfully downloaded . Observed behaviour : = ROOT volume download fails with the following message in the UI : Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server There is nothing in the MS log or Agent logs. NOTE : The operation is failing for all hypervisors. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6053) While adding smb as primary or secondary the password should be uri encoded
Devdeep Singh created CLOUDSTACK-6053: - Summary: While adding smb as primary or secondary the password should be uri encoded Key: CLOUDSTACK-6053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6053 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh When a smb share is added as a primary or secondary the user, password and domain are passed in the url. If the password has special characters (like ) added the share fails as the server isn't able to parse the uri. User, password and details should be passed as details parameters in the api and the server side should be updated to understand it. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-6053) While adding smb as primary or secondary the password should be uri encoded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6053: -- Fix Version/s: 4.3.0 While adding smb as primary or secondary the password should be uri encoded --- Key: CLOUDSTACK-6053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6053 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh Fix For: 4.3.0 When a smb share is added as a primary or secondary the user, password and domain are passed in the url. If the password has special characters (like ) added the share fails as the server isn't able to parse the uri. User, password and details should be passed as details parameters in the api and the server side should be updated to understand it. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-6030) smb user password is stored in clear text in the db
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6030: -- Fix Version/s: 4.3.0 smb user password is stored in clear text in the db --- Key: CLOUDSTACK-6030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6030 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: Devdeep Singh Assignee: Devdeep Singh Priority: Critical Fix For: 4.3.0 When a smb primary or secondary storage is added to a setup, the user password gets stored in clear text in the db. It should be encrypted and stored. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6030) smb usern password is stored in clear text in the db
Devdeep Singh created CLOUDSTACK-6030: - Summary: smb usern password is stored in clear text in the db Key: CLOUDSTACK-6030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6030 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: Devdeep Singh Assignee: Devdeep Singh Priority: Critical When a smb primary or secondary storage is added to a setup, the user password gets stored in clear text in the db. It should be encrypted and stored. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-6030) smb user password is stored in clear text in the db
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-6030: -- Summary: smb user password is stored in clear text in the db (was: smb usern password is stored in clear text in the db) smb user password is stored in clear text in the db --- Key: CLOUDSTACK-6030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6030 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: Devdeep Singh Assignee: Devdeep Singh Priority: Critical When a smb primary or secondary storage is added to a setup, the user password gets stored in clear text in the db. It should be encrypted and stored. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-6030) smb user password is stored in clear text in the db
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-6030. --- Resolution: Fixed smb user password is stored in clear text in the db --- Key: CLOUDSTACK-6030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6030 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: Devdeep Singh Assignee: Devdeep Singh Priority: Critical When a smb primary or secondary storage is added to a setup, the user password gets stored in clear text in the db. It should be encrypted and stored. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5942) Hyperv agent shouldn't log the password
Devdeep Singh created CLOUDSTACK-5942: - Summary: Hyperv agent shouldn't log the password Key: CLOUDSTACK-5942 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5942 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical The agent at places logs the password of the domain user. It should cleanup the log message before writing to the log to mask the password. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5942) Hyperv agent shouldn't log the password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5942. --- Resolution: Fixed Hyperv agent shouldn't log the password --- Key: CLOUDSTACK-5942 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5942 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical The agent at places logs the password of the domain user. It should cleanup the log message before writing to the log to mask the password. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5936) Hyper-V agent should log to windows event viewer
Devdeep Singh created CLOUDSTACK-5936: - Summary: Hyper-V agent should log to windows event viewer Key: CLOUDSTACK-5936 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5936 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh CloudStack hyper-v agent currently logs to the file. It should leverage the windows event framework and log to the event log. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5936) Hyper-V agent should log to windows event viewer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13879803#comment-13879803 ] Devdeep Singh commented on CLOUDSTACK-5936: --- The commit was already pushed to master in commit id 538092b73e3fc3a87087c2d0e1890c2bea379519. Hyper-V agent should log to windows event viewer Key: CLOUDSTACK-5936 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5936 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh CloudStack hyper-v agent currently logs to the file. It should leverage the windows event framework and log to the event log. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5936) Hyper-V agent should log to windows event viewer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5936. --- Resolution: Fixed Hyper-V agent should log to windows event viewer Key: CLOUDSTACK-5936 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5936 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh CloudStack hyper-v agent currently logs to the file. It should leverage the windows event framework and log to the event log. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5743) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5743: -- Assignee: (was: Devdeep Singh) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server - Key: CLOUDSTACK-5743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: 4.3, Hyper-V Reporter: Abhinav Roy Fix For: 4.3.0 Steps : 1. Create an advanced zone setup with hyper-v as the host hypervisor type and shared CIFS storage for primary storage 2. Deploy a VM 3. stop the VM 4. Goto the ROOT/Data volume of the VM and try to download it. Expected behaviour : = The volume should be successfully downloaded . Observed behaviour : = ROOT volume download fails with the following message in the UI : Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server There is nothing in the MS log or Agent logs. NOTE : The operation is failing for all hypervisors. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5743) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5743: -- Environment: 4.3, Hyper-V, Vmware (was: 4.3, Hyper-V) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server - Key: CLOUDSTACK-5743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: 4.3, Hyper-V, Vmware Reporter: Abhinav Roy Fix For: 4.3.0 Steps : 1. Create an advanced zone setup with hyper-v as the host hypervisor type and shared CIFS storage for primary storage 2. Deploy a VM 3. stop the VM 4. Goto the ROOT/Data volume of the VM and try to download it. Expected behaviour : = The volume should be successfully downloaded . Observed behaviour : = ROOT volume download fails with the following message in the UI : Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server There is nothing in the MS log or Agent logs. NOTE : The operation is failing for all hypervisors. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5660) Migrate vm live migration succeeds but throws error as Failed to migrate the system vm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5660:
--
Priority: Critical (was: Major)
Migrate vm live migration succeeds but throws error as Failed to migrate
the system vm
--
Key: CLOUDSTACK-5660
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5660
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Environment: Latest build from 4.3 branch with commit:
bf7601e9b86b7ea66026ac3ac94cd145e9912864
Reporter: Sanjeev N
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.4.0
[Hyper-v] Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm
Steps to Reproduce:
1.Bring up CS in advanced zone with at-least two hyper-v hosts in the cluster.
2.Deploy one guest vm with default cent os template
3.Live Migrate any vm (system /guest ) to another host.
Result:
==
VM Migration to another host succeeds but the migrate job retuns failure as
follows :2013-12-27 19:19:49,143 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Complete async job-19, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
to migrate the system vm}
2013-12-27 19:19:49,208 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Done executing
org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd for
job-19
Does not throw any exception but throws error in UI and MS log . This might
confuse the user.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5660) Migrate vm live migration succeeds but throws error as Failed to migrate the system vm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5660:
--
Fix Version/s: (was: 4.3.0)
4.4.0
Migrate vm live migration succeeds but throws error as Failed to migrate
the system vm
--
Key: CLOUDSTACK-5660
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5660
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Environment: Latest build from 4.3 branch with commit:
bf7601e9b86b7ea66026ac3ac94cd145e9912864
Reporter: Sanjeev N
Assignee: Devdeep Singh
Fix For: 4.4.0
[Hyper-v] Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm
Steps to Reproduce:
1.Bring up CS in advanced zone with at-least two hyper-v hosts in the cluster.
2.Deploy one guest vm with default cent os template
3.Live Migrate any vm (system /guest ) to another host.
Result:
==
VM Migration to another host succeeds but the migrate job retuns failure as
follows :2013-12-27 19:19:49,143 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Complete async job-19, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
to migrate the system vm}
2013-12-27 19:19:49,208 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Done executing
org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd for
job-19
Does not throw any exception but throws error in UI and MS log . This might
confuse the user.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5660) [Hyper-v] Migrate vm live migration succeeds but throws error as Failed to migrate the system vm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5660:
--
Labels: (was: hyper-V, hyper-v hyperv)
[Hyper-v] Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm
Key: CLOUDSTACK-5660
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5660
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Environment: Latest build from 4.3 branch with commit:
bf7601e9b86b7ea66026ac3ac94cd145e9912864
Reporter: Sanjeev N
Assignee: Devdeep Singh
Fix For: 4.3.0
[Hyper-v] Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm
Steps to Reproduce:
1.Bring up CS in advanced zone with at-least two hyper-v hosts in the cluster.
2.Deploy one guest vm with default cent os template
3.Live Migrate any vm (system /guest ) to another host.
Result:
==
VM Migration to another host succeeds but the migrate job retuns failure as
follows :2013-12-27 19:19:49,143 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Complete async job-19, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
to migrate the system vm}
2013-12-27 19:19:49,208 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Done executing
org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd for
job-19
Does not throw any exception but throws error in UI and MS log . This might
confuse the user.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5660) [Hyper-v] Migrate vm live migration succeeds but throws error as Failed to migrate the system vm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13877305#comment-13877305
]
Devdeep Singh commented on CLOUDSTACK-5660:
---
The issue is not hyper-v specific. The UserVmManager::migrateVirtualMachine
function is called by migrate system vm cmd. After migration is successful it
looks up for the vm entry in uservmdao table and fails. System vm entries are
only in vm_instance table and not user_vm table. Probably this change
introduced the issue e99a1ef1d947ae2161cd64f97a089ef6f042a59e.
We cannot change the look from uservmdao to vminstancedao because migrate vm
cmd (not migrate system vm cmd) expects a uservmvo to be returned by
UserVmManager::migrateVirtualMachine function.
Removing the Hyper-v tag and updated the bug description.
[Hyper-v] Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm
Key: CLOUDSTACK-5660
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5660
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Environment: Latest build from 4.3 branch with commit:
bf7601e9b86b7ea66026ac3ac94cd145e9912864
Reporter: Sanjeev N
Assignee: Devdeep Singh
Fix For: 4.3.0
[Hyper-v] Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm
Steps to Reproduce:
1.Bring up CS in advanced zone with at-least two hyper-v hosts in the cluster.
2.Deploy one guest vm with default cent os template
3.Live Migrate any vm (system /guest ) to another host.
Result:
==
VM Migration to another host succeeds but the migrate job retuns failure as
follows :2013-12-27 19:19:49,143 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Complete async job-19, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
to migrate the system vm}
2013-12-27 19:19:49,208 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Done executing
org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd for
job-19
Does not throw any exception but throws error in UI and MS log . This might
confuse the user.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5660) Migrate vm live migration succeeds but throws error as Failed to migrate the system vm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5660:
--
Summary: Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm (was: [Hyper-v] Migrate vm live migration succeeds but
throws error as Failed to migrate the system vm)
Migrate vm live migration succeeds but throws error as Failed to migrate
the system vm
--
Key: CLOUDSTACK-5660
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5660
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Environment: Latest build from 4.3 branch with commit:
bf7601e9b86b7ea66026ac3ac94cd145e9912864
Reporter: Sanjeev N
Assignee: Devdeep Singh
Fix For: 4.3.0
[Hyper-v] Migrate vm live migration succeeds but throws error as Failed to
migrate the system vm
Steps to Reproduce:
1.Bring up CS in advanced zone with at-least two hyper-v hosts in the cluster.
2.Deploy one guest vm with default cent os template
3.Live Migrate any vm (system /guest ) to another host.
Result:
==
VM Migration to another host succeeds but the migrate job retuns failure as
follows :2013-12-27 19:19:49,143 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Complete async job-19, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
to migrate the system vm}
2013-12-27 19:19:49,208 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-15:ctx-9065306c) Done executing
org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd for
job-19
Does not throw any exception but throws error in UI and MS log . This might
confuse the user.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5894) Create a Template from volume, restart management server. The template entry vanishes from cloud.template_store_ref table and template is no longer usable.
Devdeep Singh created CLOUDSTACK-5894: - Summary: Create a Template from volume, restart management server. The template entry vanishes from cloud.template_store_ref table and template is no longer usable. Key: CLOUDSTACK-5894 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5894 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical Fix For: 4.3.0 Steps : === 1. Deploy an advanced zone setup of CS 4.3 with Hyper-V as the hypervisor type. 2. Create a VM. 3. Stop the VM and create a Template from it's ROOT volume. When the template is created, we can see in our secondary storage that the template.properties file gets created. 4. Now Deploy a VM from the template created in step 3 . VM deployment goes fine. 5. Now restart the management server. After management server restart we find that the DB entry for that template in template_store_ref is gone. The template cannot be used for deploying an instance. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5894) Create a Template from volume, restart management server. The template entry vanishes from cloud.template_store_ref table and template is no longer usable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5894. --- Resolution: Fixed Create a Template from volume, restart management server. The template entry vanishes from cloud.template_store_ref table and template is no longer usable. --- Key: CLOUDSTACK-5894 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5894 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical Labels: Hyper-V, hyper-V,, hyper-v Fix For: 4.3.0 Steps : === 1. Deploy an advanced zone setup of CS 4.3 with Hyper-V as the hypervisor type. 2. Create a VM. 3. Stop the VM and create a Template from it's ROOT volume. When the template is created, we can see in our secondary storage that the template.properties file gets created. 4. Now Deploy a VM from the template created in step 3 . VM deployment goes fine. 5. Now restart the management server. After management server restart we find that the DB entry for that template in template_store_ref is gone. The template cannot be used for deploying an instance. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5880) Communication between management server and hyper-v agent should be secure
Devdeep Singh created CLOUDSTACK-5880: - Summary: Communication between management server and hyper-v agent should be secure Key: CLOUDSTACK-5880 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5880 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Reporter: Devdeep Singh Priority: Critical Fix For: 4.3.0 Currently the hyper-v agent and management server talk over http. Communication between mgmt server and HyperV Agent running in hyperv host should be secured using say SSL. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5880) Communication between management server and hyper-v agent should be secure
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5880: -- Affects Version/s: 4.3.0 Communication between management server and hyper-v agent should be secure -- Key: CLOUDSTACK-5880 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5880 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: Devdeep Singh Assignee: Anshul Gangwar Priority: Critical Fix For: 4.3.0 Currently the hyper-v agent and management server talk over http. Communication between mgmt server and HyperV Agent running in hyperv host should be secured using say SSL. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5869) [Hyper-V] VM creation on local storage is failing
Devdeep Singh created CLOUDSTACK-5869:
-
Summary: [Hyper-V] VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (DirectAgent-162:ctx-59574cc6)
Seq 5-374407591: Processing: { Ans: , MgmtId: 280320865129348, via: 5, Ver: v1,
Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348, via:
5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no need
to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed on
exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed on
exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Summary: [Hyper-V] System VM creation on local storage is failing (was:
[Hyper-V] VM creation on local storage is failing)
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Resolved] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5869.
---
Resolution: Fixed
Fixed in commits
Commit 5bf5d3669d22d48f4b2db01c76647c977fad7468 in branch refs/heads/4.3 from
Devdeep Singh
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5bf5d36 ]
CLOUDSTACK-5689: System vm creation on local storage fails for hyper-v. A
null pointer exception was getting generated when a VolumeTO object was
serialized to create an answer object. If a local storage is used the uri
field will be null. Added null checks for the same.
ASF subversion and git services added a comment - a minute ago
Commit f58d77c8d1fd9eb2bee927f7d92e50ba1553c7b6 in branch refs/heads/master
from Devdeep Singh
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f58d77c ]
CLOUDSTACK-5689: System vm creation on local storage fails for hyper-v. A
null pointer exception was getting generated when a VolumeTO object was
serialized to create an answer object. If a local storage is used the uri
field will be null. Added null checks for the same.
I gave the wrong bug id in the commit message.
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Labels: hyper-V, (was: )
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
Labels: hyper-V,
Fix For: 4.3.0
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Affects Version/s: 4.3.0
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
Labels: hyper-V,
Fix For: 4.3.0
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Fix Version/s: 4.3.0
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
Labels: hyper-V,
Fix For: 4.3.0
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Resolved] (CLOUDSTACK-5639) [Hyper-v] cold storage migration does not work in hyperv
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5639.
---
Resolution: Fixed
[Hyper-v] cold storage migration does not work in hyperv
Key: CLOUDSTACK-5639
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5639
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: Latest build from 4.3 branch with
commit:4b2b6544255ee7fe12b4b4732cacd08e4ee6a1b7
Storage: SMB for both primary and secondary
Hypervisor: Hyper-v
Reporter: Sanjeev N
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0
Attachments: cloudstack-agent.rar, management-server.rar,
management-server.rar
[Hyper-v] cold storage does not work in hyperv
Steps to Reproduce:
1.Bring up CS in advanced zone with 2 hosts in a hyper-v cluster using CIFS
for both primary and secondary storage
2.Deploy one or two guest vms using default cent os template.
3.Add one more primary storage (say primary2) to the cluster
4.Stop one of the vms deployed at step2
5.Migrate the storage from source primary to new primary storage primary2
Expected Result:
=
Storage migration should succeed when the vm is in stopped state
Actual Result:
===
Storage migration failed with the error Failed to migration:
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:7] is
unreachable
Observations:
Log snippet from the MS log:
2013-12-24 19:11:55,475 DEBUG [c.c.a.ApiServlet]
(catalina-exec-11:ctx-717ba369) ===START=== 10.146.0.134 -- GET
command=migrateVirtualMachinestorageid=fe97ca45-5cba-329a-ae79-fa02649421c1virtualmachineid=3a1b4f23-7a43-4806-8fd5-43a9c1130872response=jsonsessionkey=uHhzduF1EppEHm%2Bibsj2%2Bqf%2Fzto%3D_=1387892514178
2013-12-24 19:11:55,661 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-11:ctx-717ba369 ctx-d805adb4) submit async job-33, details:
AsyncJobVO {id:33, userId: 2, accountId: 2, instanceType: None, instanceId:
null, cmd: org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:uHhzduF1EppEHm+ibsj2+qf/zto\u003d,virtualmachineid:3a1b4f23-7a43-4806-8fd5-43a9c1130872,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:fe97ca45-5cba-329a-ae79-fa02649421c1,httpmethod:GET,_:1387892514178,ctxAccountId:2,ctxStartEventId:99},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 132129494109518, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2013-12-24 19:11:55,663 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-29:ctx-893d8661) Add job-33 into job monitoring
2013-12-24 19:11:55,663 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-29:ctx-893d8661) Executing AsyncJobVO {id:33, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:uHhzduF1EppEHm+ibsj2+qf/zto\u003d,virtualmachineid:3a1b4f23-7a43-4806-8fd5-43a9c1130872,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:fe97ca45-5cba-329a-ae79-fa02649421c1,httpmethod:GET,_:1387892514178,ctxAccountId:2,ctxStartEventId:99},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 132129494109518, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2013-12-24 19:11:55,663 DEBUG [c.c.a.ApiServlet]
(catalina-exec-11:ctx-717ba369 ctx-d805adb4) ===END=== 10.146.0.134 -- GET
command=migrateVirtualMachinestorageid=fe97ca45-5cba-329a-ae79-fa02649421c1virtualmachineid=3a1b4f23-7a43-4806-8fd5-43a9c1130872response=jsonsessionkey=uHhzduF1EppEHm%2Bibsj2%2Bqf%2Fzto%3D_=1387892514178
2013-12-24 19:11:55,794 DEBUG [c.c.c.CapacityManagerImpl]
(Job-Executor-29:ctx-893d8661 ctx-d805adb4) VM state transitted from :Stopped
to Migrating with event: StorageMigrationRequestedvm's original host id: 4
new host id: null host id before state transition: null
2013-12-24 19:11:56,026 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Job-Executor-29:ctx-893d8661 ctx-d805adb4) copyAsync inspecting src type
VOLUME copyAsync inspecting dest type VOLUME
2013-12-24 19:11:56,199 DEBUG [c.c.a.t.Request] (Job-Executor-29:ctx-893d8661
ctx-d805adb4) Seq 1-1652228440: Sending { Cmd , MgmtId: 132129494109518,
via: 1(10.147.40.14), Ver: v1, Flags: 100011,
[jira] [Updated] (CLOUDSTACK-5743) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5743: -- Assignee: (was: Devdeep Singh) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server - Key: CLOUDSTACK-5743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: 4.3, Hyper-V Reporter: Abhinav Roy Priority: Critical Fix For: 4.3.0 Steps : 1. Create an advanced zone setup with hyper-v as the host hypervisor type and shared CIFS storage for primary storage 2. Deploy a VM 3. stop the VM 4. Goto the ROOT/Data volume of the VM and try to download it. Expected behaviour : = The volume should be successfully downloaded . Observed behaviour : = ROOT volume download fails with the following message in the UI : Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server There is nothing in the MS log or Agent logs. NOTE : The operation is failing for all hypervisors. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5743) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867637#comment-13867637 ] Devdeep Singh commented on CLOUDSTACK-5743: --- The issue isn't specific to hyper-v. It is generic and is seen on other hypervisors too. The volume gets uploaded correctly, but the link that is shown to download the volume gives a permission denied error. Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server - Key: CLOUDSTACK-5743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: 4.3, Hyper-V Reporter: Abhinav Roy Assignee: Devdeep Singh Priority: Critical Fix For: 4.3.0 Steps : 1. Create an advanced zone setup with hyper-v as the host hypervisor type and shared CIFS storage for primary storage 2. Deploy a VM 3. stop the VM 4. Goto the ROOT/Data volume of the VM and try to download it. Expected behaviour : = The volume should be successfully downloaded . Observed behaviour : = ROOT volume download fails with the following message in the UI : Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server There is nothing in the MS log or Agent logs. NOTE : The operation is failing for all hypervisors. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-5743) Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867637#comment-13867637 ] Devdeep Singh edited comment on CLOUDSTACK-5743 at 1/10/14 9:01 AM: The issue isn't specific to hyper-v. It is generic and is seen on other hypervisors too. The volume gets uploaded correctly, but the link that is shown to download the volume gives a permission denied error. Unassigning, so that someone else can take a look. was (Author: devdeep): The issue isn't specific to hyper-v. It is generic and is seen on other hypervisors too. The volume gets uploaded correctly, but the link that is shown to download the volume gives a permission denied error. Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server - Key: CLOUDSTACK-5743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: 4.3, Hyper-V Reporter: Abhinav Roy Assignee: Devdeep Singh Priority: Critical Fix For: 4.3.0 Steps : 1. Create an advanced zone setup with hyper-v as the host hypervisor type and shared CIFS storage for primary storage 2. Deploy a VM 3. stop the VM 4. Goto the ROOT/Data volume of the VM and try to download it. Expected behaviour : = The volume should be successfully downloaded . Observed behaviour : = ROOT volume download fails with the following message in the UI : Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server There is nothing in the MS log or Agent logs. NOTE : The operation is failing for all hypervisors. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5657) [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5657. --- Resolution: Fixed Made changes to install and run the service as an account on the host. The account needs to be part of the Hyper-V Administrators group and Local Administrators group on the host. To install the service with the account privileges run the following command AgentShell.exe --install -u domain\user1 -p password Where -u is the domain user who is part of Hyper-V Administrators on the host and -p is the users password. [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On - Key: CLOUDSTACK-5657 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5657 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Environment: latest build from 4.3 Hypervisor: Hyperv Storage: SMB for both primary and secondary Reporter: Sanjeev N Assignee: Devdeep Singh Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: 4.3.0 [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On CloudStack to communicate with Hyper-v server we run CloudStack-Hyperv Agent as a service in Windows2012R2 (Hyperv) Server. By default this service would run with Local System Log On. However vm live migration fails with authentication issues if this service runs with Local System Log on. So we need to stop this service and change the Log On account to domain user and start the service for the live migration to work. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5818) [Hyper-v]Agent status of the System VMs is not updated during Host disconnect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5818: -- Fix Version/s: (was: 4.3.0) Future [Hyper-v]Agent status of the System VMs is not updated during Host disconnect - Key: CLOUDSTACK-5818 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5818 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Environment: Latest build from 4.3branch with commit:6f309b8a87d3376950a60234d399c6e3749ad1c7 Reporter: Sanjeev N Assignee: Devdeep Singh Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: Future Attachments: management-server.rar [Hyper-v]Agent status of the System VMs is not updated during Host disconnect. Steps to Reproduce: 1.Bring up CS in advanced zone with hyper-v cluster and with SMB for both primary and secondary 2.Wait for the system vms to come up 3.Simulate host disconnect by unplugging the network cable. 4.I see host status changing to Down but the agent status of the system vms remained Up Impact: == All the operations involving SSVM and CPVM are failing since the host is down. So user is blocked to perform following things: 1.Download/Register/copy template 2.Upload/Download volume 3.Console access -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5795) [Hyper-V] When a Template is created from volume the template.properties file is not created, due to which when we restart management server, The DB entry for that
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5795. --- Resolution: Fixed [Hyper-V] When a Template is created from volume the template.properties file is not created, due to which when we restart management server, The DB entry for that Template is deleted from template_store_ref table and template becomes inaccessible Key: CLOUDSTACK-5795 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5795 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.3.0 Environment: Hyperv , 4.3 Reporter: Abhinav Roy Assignee: Devdeep Singh Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: 4.3.0 Attachments: CS-5795.jpg, CS-5795.zip Steps : === 1. Deploy an advanced zone setup of CS 4.3 with Hyper-V as the hypervisor type. 2. Create a VM. 3. Stop the VM and create a Template from it's ROOT volume. But when the template is created, we can see in our secondary storage that the template.properties file doesn't get created 4. Now Deploy a VM from the template created in step 3 . VM deployment goes fine. 5. Now restart the management server. After management server restart we find that the DB entry for that template in template_store_ref is gone. Attaching management server logs , snapshot and DB dump. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5657) [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5657: -- Status: Ready To Review (was: In Progress) [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On - Key: CLOUDSTACK-5657 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5657 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Hypervisor Controller Affects Versions: 4.3.0 Environment: latest build from 4.3 Hypervisor: Hyperv Storage: SMB for both primary and secondary Reporter: Sanjeev N Assignee: Devdeep Singh Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: 4.3.0 [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On CloudStack to communicate with Hyper-v server we run CloudStack-Hyperv Agent as a service in Windows2012R2 (Hyperv) Server. By default this service would run with Local System Log On. However vm live migration fails with authentication issues if this service runs with Local System Log on. So we need to stop this service and change the Log On account to domain user and start the service for the live migration to work. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5657) [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5657: -- Component/s: (was: Doc) [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On - Key: CLOUDSTACK-5657 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5657 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Environment: latest build from 4.3 Hypervisor: Hyperv Storage: SMB for both primary and secondary Reporter: Sanjeev N Assignee: Devdeep Singh Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: 4.3.0 [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On CloudStack to communicate with Hyper-v server we run CloudStack-Hyperv Agent as a service in Windows2012R2 (Hyperv) Server. By default this service would run with Local System Log On. However vm live migration fails with authentication issues if this service runs with Local System Log on. So we need to stop this service and change the Log On account to domain user and start the service for the live migration to work. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5610) [Hyper-v] Host does not go into Alert state even though it is power-off hence vm deployment fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5610.
---
Resolution: Fixed
This is expected. To check if a host is disconnected we need to send a command
to another host in the cluster. If the second host is in maintenance mode,
there are no hosts available to send the command too. So cloudstack cannot
determine the state and leave the host state as is.
[Hyper-v] Host does not go into Alert state even though it is power-off hence
vm deployment fails
-
Key: CLOUDSTACK-5610
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5610
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: Latest build from 4.3 with commit
:d462db4ae5c30e677d5810111f9ea5ca6812bce2
Storage: SMB for both primary and secondary
Hypervisor: Hyper-v
Reporter: Sanjeev N
Assignee: Devdeep Singh
Priority: Blocker
Labels: hyper-V,
Fix For: 4.3.0
Attachments: cloud.dmp, management-server.rar, management-server.rar
[Hyper-v] Host does not go into Alert state even though it is power-off hence
vm deployment fails
Steps to Reproduce:
=
1.Bring up CS in advanced zone with with 2 or more Hyper-v hosts using SMB
for both primary and secondary
2.Enable the zone and deploy few vms. Make sure that vms are distributed
across all the hosts
3.Power off one of the hosts(Power off the hosts where vms are running)
Expected Result:
==
Host should go into Alert state and all the vms running on it should be
stopped
Actual Result:
Host remains in Up state and all the vms state show as running.
I could see the ping commands to Hypervsior aget, system vm agents in the MS
log. Even though the agents are behind ping, agent status remains in UP state.
At this state , I have tried to deploy a vm and deployment planner chose the
host which was powered off . Hence the vm deployment failed.
Also CPVM was running on the powered off host. That also remained in running
state. Since cpvm agent is not reachable from CS it should have been stopped
and started on another Host in the cluster.
2013-12-23 18:19:25,334 ERROR [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-331:ctx-831c60e9) org.apache.http.conn.HttpHostConnectException:
Connection to http://10.147.40.31:8250 refused
2013-12-23 18:19:25,334 INFO [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-331:ctx-831c60e9) Cannot ping host 10.147.40.31 (IP
10.147.40.31), pingAns (blank means null)
is:com.cloud.agent.api.UnsupportedAnswer
2013-12-23 18:19:25,334 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-331:ctx-831c60e9) Unable to get current status on 5(10.147.40.31)
2013-12-23 18:19:25,336 INFO [c.c.a.m.AgentManagerImpl]
(AgentTaskPool-16:ctx-be3804c7) Investigating why host 5 has disconnected
with event AgentDisconnected
2013-12-23 18:19:25,336 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentTaskPool-16:ctx-be3804c7) checking if agent (5) is alive
2013-12-23 18:19:25,339 DEBUG [c.c.a.t.Request]
(AgentTaskPool-16:ctx-be3804c7) Seq 5-1482556239: Sending { Cmd , MgmtId:
132129494109518, via: 5(10.147.40.31), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckHealthCommand:{wait:50}}] }
2013-12-23 18:19:25,339 DEBUG [c.c.a.t.Request]
(AgentTaskPool-16:ctx-be3804c7) Seq 5-1482556239: Executing: { Cmd , MgmtId:
132129494109518, via: 5(10.147.40.31), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckHealthCommand:{wait:50}}] }
2013-12-23 18:19:25,339 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-325:ctx-39f5ed39) Seq 5-1482556239: Executing request
2013-12-23 18:19:25,339 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-325:ctx-39f5ed39) POST request
tohttp://10.147.40.31:8250/api/HypervResource/com.cloud.agent.api.CheckHealthCommand
with contents{contextMap:{},wait:50}
2013-12-23 18:19:25,340 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-325:ctx-39f5ed39) Sending cmd to
http://10.147.40.31:8250/api/HypervResource/com.cloud.agent.api.CheckHealthCommand
cmd data:{contextMap:{},wait:50}
2013-12-23 18:19:46,345 DEBUG [c.c.h.UserVmDomRInvestigator]
(AgentTaskPool-16:ctx-be3804c7) checking if agent (5) is alive
2013-12-23 18:19:46,347 DEBUG [c.c.h.UserVmDomRInvestigator]
(AgentTaskPool-16:ctx-be3804c7) sending ping from (1) to agent's host ip
address (10.147.40.31)
2013-12-23 18:19:46,349 DEBUG [c.c.a.t.Request]
(AgentTaskPool-16:ctx-be3804c7) Seq 1-790364876: Sending { Cmd , MgmtId:
[jira] [Assigned] (CLOUDSTACK-5789) [Hyper-V] Download ROOT Volume when the VM is in stopped state is failing because copyCommand fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-5789:
-
Assignee: Devdeep Singh
[Hyper-V] Download ROOT Volume when the VM is in stopped state is failing
because copyCommand fails
---
Key: CLOUDSTACK-5789
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5789
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0
Steps :
1. Create an advanced zone setup with hyper-v as the host hypervisor type and
shared CIFS storage for primary storage
2. Deploy a VM
3. stop the VM
4. Goto the ROOT volume of the VM and try to download it.
Expected behaviour :
=
The volume should be successfully downloaded .
Observed behaviour :
=
ROOT volume download fails with :
MS logs
---
2014-01-06 11:08:03,797 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-204:ctx-47365a36) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,newData:null,contextMap:{}}}]
2014-01-06 11:08:03,798 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-204:ctx-47365a36) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027FullFileName\u0027 on
\u0027HypervResource.VolumeObjectTO\u0027.,contextMap:{},wait:0}}]
2014-01-06 11:08:03,798 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-204:ctx-47365a36) Seq 5-2015625318: Response Received:
2014-01-06 11:08:03,798 DEBUG [c.c.a.t.Request]
(DirectAgent-204:ctx-47365a36) Seq 5-2015625318: Processing: { Ans: ,
MgmtId: 280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,wait:0}}] }
2014-01-06 11:08:03,798 DEBUG [c.c.a.t.Request] (Job-Executor-42:ctx-f12094f2
ctx-6ab0db09) Seq 5-2015625318: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2014-01-06 11:08:03,802 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-42:ctx-f12094f2 ctx-6ab0db09) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@476a261c), no
need to delete from object in store ref table
2014-01-06 11:08:03,831 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-42:ctx-f12094f2) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume
from the source primary storage pool to secondary storage.
at
com.cloud.storage.VolumeApiServiceImpl.extractVolume(VolumeApiServiceImpl.java:1856)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
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
[jira] [Assigned] (CLOUDSTACK-5788) [Hyper-V] Attaching an uploaded volume to a VM is failing because copyCommand fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-5788:
-
Assignee: Devdeep Singh
[Hyper-V] Attaching an uploaded volume to a VM is failing because copyCommand
fails
---
Key: CLOUDSTACK-5788
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5788
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: hyperv,4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0
Steps :
=
1. Deploy an advanced zone setup with hyperv.
2. Create a VM.
3. upload a volume.
4. Attach the volume uploaded in step 3 to the VM created in step 2.
Expected behaviour:
=
Attach volume should succeed.
Observed behaviour:
=
Attach volume fails with :
MS logs :
--
2014-01-06 11:53:37,402 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-380:ctx-674d76cf) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,newData:null,contextMap:{}}}]
2014-01-06 11:53:37,403 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-380:ctx-674d76cf) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027FullFileName\u0027 on
\u0027HypervResource.VolumeObjectTO\u0027.,contextMap:{},wait:0}}]
2014-01-06 11:53:37,403 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-380:ctx-674d76cf) Seq 1-849871246: Response Received:
2014-01-06 11:53:37,403 DEBUG [c.c.a.t.Request]
(DirectAgent-380:ctx-674d76cf) Seq 1-849871246: Processing: { Ans: , MgmtId:
280320865129348, via: 1, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,wait:0}}] }
2014-01-06 11:53:37,403 DEBUG [c.c.a.t.Request]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) Seq 1-849871246: Received: {
Ans: , MgmtId: 280320865129348, via: 1, Ver: v1, Flags: 10, { CopyCmdAnswer }
}
2014-01-06 11:53:37,421 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) copy volume failed:
java.lang.NullPointerException
2014-01-06 11:53:37,421 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) Invocation exception, caused by:
com.cloud.utils.exception.CloudRuntimeException: copy volume failed:
java.lang.NullPointerException
2014-01-06 11:53:37,421 ERROR [c.c.v.VmWorkJobDispatcher]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) Unable to complete AsyncJobVO
{id:142, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.storage.VmWorkAttachVolume, cmdInfo:
rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAAp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwABM,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Mon Jan 06 11:53:27 IST 2014}
com.cloud.utils.exception.CloudRuntimeException: copy volume failed:
java.lang.NullPointerException
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.copyVolumeFromSecToPrimary(VolumeOrchestrator.java:412)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.copyVolume(VolumeOrchestrator.java:718)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:747)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1249)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1127)
at
[jira] [Resolved] (CLOUDSTACK-5788) [Hyper-V] Attaching an uploaded volume to a VM is failing because copyCommand fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5788.
---
Resolution: Fixed
[Hyper-V] Attaching an uploaded volume to a VM is failing because copyCommand
fails
---
Key: CLOUDSTACK-5788
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5788
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: hyperv,4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0
Steps :
=
1. Deploy an advanced zone setup with hyperv.
2. Create a VM.
3. upload a volume.
4. Attach the volume uploaded in step 3 to the VM created in step 2.
Expected behaviour:
=
Attach volume should succeed.
Observed behaviour:
=
Attach volume fails with :
MS logs :
--
2014-01-06 11:53:37,402 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-380:ctx-674d76cf) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,newData:null,contextMap:{}}}]
2014-01-06 11:53:37,403 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-380:ctx-674d76cf) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027FullFileName\u0027 on
\u0027HypervResource.VolumeObjectTO\u0027.,contextMap:{},wait:0}}]
2014-01-06 11:53:37,403 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-380:ctx-674d76cf) Seq 1-849871246: Response Received:
2014-01-06 11:53:37,403 DEBUG [c.c.a.t.Request]
(DirectAgent-380:ctx-674d76cf) Seq 1-849871246: Processing: { Ans: , MgmtId:
280320865129348, via: 1, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,wait:0}}] }
2014-01-06 11:53:37,403 DEBUG [c.c.a.t.Request]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) Seq 1-849871246: Received: {
Ans: , MgmtId: 280320865129348, via: 1, Ver: v1, Flags: 10, { CopyCmdAnswer }
}
2014-01-06 11:53:37,421 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) copy volume failed:
java.lang.NullPointerException
2014-01-06 11:53:37,421 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) Invocation exception, caused by:
com.cloud.utils.exception.CloudRuntimeException: copy volume failed:
java.lang.NullPointerException
2014-01-06 11:53:37,421 ERROR [c.c.v.VmWorkJobDispatcher]
(Job-Executor-115:ctx-46b175df ctx-9f2ec3a6) Unable to complete AsyncJobVO
{id:142, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.storage.VmWorkAttachVolume, cmdInfo:
rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAAp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwABM,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Mon Jan 06 11:53:27 IST 2014}
com.cloud.utils.exception.CloudRuntimeException: copy volume failed:
java.lang.NullPointerException
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.copyVolumeFromSecToPrimary(VolumeOrchestrator.java:412)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.copyVolume(VolumeOrchestrator.java:718)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:747)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1249)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1127)
at
[jira] [Resolved] (CLOUDSTACK-5789) [Hyper-V] Download ROOT Volume when the VM is in stopped state is failing because copyCommand fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5789.
---
Resolution: Fixed
[Hyper-V] Download ROOT Volume when the VM is in stopped state is failing
because copyCommand fails
---
Key: CLOUDSTACK-5789
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5789
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0
Steps :
1. Create an advanced zone setup with hyper-v as the host hypervisor type and
shared CIFS storage for primary storage
2. Deploy a VM
3. stop the VM
4. Goto the ROOT volume of the VM and try to download it.
Expected behaviour :
=
The volume should be successfully downloaded .
Observed behaviour :
=
ROOT volume download fails with :
MS logs
---
2014-01-06 11:08:03,797 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-204:ctx-47365a36) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,newData:null,contextMap:{}}}]
2014-01-06 11:08:03,798 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-204:ctx-47365a36) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027FullFileName\u0027 on
\u0027HypervResource.VolumeObjectTO\u0027.,contextMap:{},wait:0}}]
2014-01-06 11:08:03,798 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-204:ctx-47365a36) Seq 5-2015625318: Response Received:
2014-01-06 11:08:03,798 DEBUG [c.c.a.t.Request]
(DirectAgent-204:ctx-47365a36) Seq 5-2015625318: Processing: { Ans: ,
MgmtId: 280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'FullFileName' on
'HypervResource.VolumeObjectTO'.,wait:0}}] }
2014-01-06 11:08:03,798 DEBUG [c.c.a.t.Request] (Job-Executor-42:ctx-f12094f2
ctx-6ab0db09) Seq 5-2015625318: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2014-01-06 11:08:03,802 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-42:ctx-f12094f2 ctx-6ab0db09) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@476a261c), no
need to delete from object in store ref table
2014-01-06 11:08:03,831 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-42:ctx-f12094f2) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume
from the source primary storage pool to secondary storage.
at
com.cloud.storage.VolumeApiServiceImpl.extractVolume(VolumeApiServiceImpl.java:1856)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
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
