[jira] [Created] (CLOUDSTACK-8136) [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed.
Likitha Shetty created CLOUDSTACK-8136: -- Summary: [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. Key: CLOUDSTACK-8136 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8136 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: Future +Steps to reproduce+ 1. Deploy a VM. 2. Take a failed VM snapshot. - Stop the VM. - Migrate VM's ROOT disk to another primary storage. - Try to take a VM snapshot - Expected failure (fails because CS expects the VM to be started after it has been cold migration before performing any further operations on the VM). 3. Start the VM. 4. Immediately take another VM snapshot - Fails. 5. Try taking a snapshot after 10 mins when the VMs 'Recent Tasks' in vCenter are all cleared - Succeeds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8136) [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14260934#comment-14260934 ] ASF subversion and git services commented on CLOUDSTACK-8136: - Commit 25a4f0dc530951e87fe357313dc983cb75aa8972 in cloudstack's branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=25a4f0d ] CLOUDSTACK-8136. [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. While looking for an ongoing VM snapshot task, check the task status to identify if the task is still running. [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. Key: CLOUDSTACK-8136 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8136 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: Future +Steps to reproduce+ 1. Deploy a VM. 2. Take a failed VM snapshot. - Stop the VM. - Migrate VM's ROOT disk to another primary storage. - Try to take a VM snapshot - Expected failure (fails because CS expects the VM to be started after it has been cold migration before performing any further operations on the VM). 3. Start the VM. 4. Immediately take another VM snapshot - Fails. 5. Try taking a snapshot after 10 mins when the VMs 'Recent Tasks' in vCenter are all cleared - Succeeds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8136) [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8136. Resolution: Fixed [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. Key: CLOUDSTACK-8136 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8136 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: Future +Steps to reproduce+ 1. Deploy a VM. 2. Take a failed VM snapshot. - Stop the VM. - Migrate VM's ROOT disk to another primary storage. - Try to take a VM snapshot - Expected failure (fails because CS expects the VM to be started after it has been cold migration before performing any further operations on the VM). 3. Start the VM. 4. Immediately take another VM snapshot - Fails. 5. Try taking a snapshot after 10 mins when the VMs 'Recent Tasks' in vCenter are all cleared - Succeeds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8137) component.test_escalations_instances.TestInstances.test_23_deploy_vm_multiple_securitygroups fails in clenaup operation
Ashutosk Kelkar created CLOUDSTACK-8137: --- Summary: component.test_escalations_instances.TestInstances.test_23_deploy_vm_multiple_securitygroups fails in clenaup operation Key: CLOUDSTACK-8137 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8137 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Ashutosk Kelkar Assignee: Ashutosk Kelkar Fix For: 4.5.0 The test case failed while deleting the security groups in cleanup operation because those were deleted as part of account cleanup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (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 ] manasaveloori closed CLOUDSTACK-7642. - Verified .Working fine. [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] [Closed] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori closed CLOUDSTACK-6481. - closing as not an issue Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS. - Key: CLOUDSTACK-6481 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, XenServer Affects Versions: 4.4.0 Environment: Xenserver6.2 added to CS 4.4 Reporter: manasaveloori Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.4.0 Attachments: management-server.log PXE booted the Xenserver. Added it to CS 4.4. observed that system vms fails to deploy with Exception: 2014-04-23 04:23:46,875 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-3:ctx-cf6a380b) Catch Exception com.cloud.utils.exception.CloudRuntimeException for template + due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) 2014-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received: Checked in xenserver the vhd-util file is missing under /opt/cloud/bin. As work around copied the vhd-util to /opt/cloud/bin. Attaching the log files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6690) [UI] ListView while assigning VM to internal LB rule in VPC is not valid.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori closed CLOUDSTACK-6690.
-
Verified on 4.5 .Working fine
[UI] ListView while assigning VM to internal LB rule in VPC is not valid.
--
Key: CLOUDSTACK-6690
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6690
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: UI
Affects Versions: 4.3.0, 4.4.0
Reporter: manasaveloori
Assignee: Jessica Wang
Fix For: 4.5.0
Attachments: Listview.jpg, jessica-2014-11-04.PNG
1. Create VPC.
2. Create a tier network with network offering having support for internal LB.
3. Deploy a VM under this tier network.
3. VPC-tier-internal LBCon figure internal LB.
4. Now assign the VM to internal LB.
While assigning we are haviing 2 options to select the VM.
Listview on left hand side is not valid.
Assigning the VM by using the Listview does not configure the lb rule:
Logs
2014-05-16 16:00:58,946 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-12:job-444) Executing AsyncJobVO {id:444, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd,
cmdInfo:
{response:json,id:c2ca8600-0cf9-44a0-8443-da5c743cbd49,sessionkey:e9nTmi2e/Ci2Oy/hkABO5FRlkI8\u003d,cmdEventType:LB.ASSIGN.TO.RULE,virtualmachineids:,ctxUserId:2,httpmethod:GET,_:1400236258357,ctxAccountId:2,ctxStartEventId:541},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7322717913215, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-16 16:00:59,016 WARN [c.c.n.l.LoadBalancingRulesManagerImpl]
(API-Job-Executor-12:job-444 ctx-723e9aab) List of vms to assign to the lb,
is empty
2014-05-16 16:00:59,029 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-12:job-444) Complete async job-444, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
to assign load balancer rule}
2014-05-16 16:00:59,042 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-12:job-444) Done executing
org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd
for job-444
Attaching the screen shot for the same.
Able to assign VM to internal LB uisng the select button on right hand side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6590) No option in UI to acquire secondary IP for VM nic
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori closed CLOUDSTACK-6590. - Verified in 4.5 . No option in UI to acquire secondary IP for VM nic -- Key: CLOUDSTACK-6590 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6590 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, UI Affects Versions: 4.4.0 Reporter: manasaveloori Assignee: Brian Federle Priority: Critical Fix For: 4.4.0 Deploy a user Vm. Go to Nics Observed that there is no option to acquire a secondary ip for the VM nic. This a regression issue... Able to acquire the secondary IP using API. Build commit id: [root@RHEL63test secondaryxen]# cloudstack-sccs ed088c72c461c08a061881f78cceae7f74794b9c -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8024) use barematel instance to stop or start Physical Machine failed。
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14260997#comment-14260997
]
ChunFeng commented on CLOUDSTACK-8024:
--
after review code and confirm to this bug submitter , lanplus code had already
removed from cloudstack version 4.3.2 above , so this issue already resolved.
I will close this issue now .
use barematel instance to stop or start Physical Machine failed。
Key: CLOUDSTACK-8024
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8024
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Baremetal
Affects Versions: 4.4.1
Environment: Latest build from ACS 4.4.1-SNAPSHOT branch
Cluster: KVM
barematel instance OS:centos6.2.x86_64
Physical Machine:DELL PowerEdge M610
Reporter: luzhhk
Assignee: ChunFeng
Priority: Trivial
when use barematel to create instance,the instance Automatic finish OS
Installation and restart the system normally,but stop or reinstall OS get
problem 。
Following is the log snippet:
=
2, accountId: 2, instanceType: VirtualMachine, instanceId: 7, cmd:
org.apache.cloudstack.api.command.admin.vm.StopVMCmdByAdmin, cmdInfo:
{response:json,id:51c44437-b22d-4cde-ac32-b7ee5ea96521,sessionkey:qpV/kzaFZJjyjLW0IdAh8B4jpF4\u003d,ctxDetails:{\com.cloud.vm.VirtualMachine\:
\51c44437-b22d-4cde-ac32-b7ee5ea96521\},cmdEventType:VM.STOP,ctxUserId:2,httpmethod:GET,_:1417678580312,uuid:51c44437-b22d-4cde-ac32-
b7ee5ea96521,ctxAccountId:2,ctxStartEventId:150,forced:false},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null,
b22d-4cde-ac32-b7ee5ea96521forced=falseresponse=jsonsessionkey=qpV%2FkzaFZJjyjLW0IdAh8B4jpF4%3D_=1417678580312
instanceType: VirtualMachine, instanceId: 7, cmd:
org.apache.cloudstack.api.command.admin.vm.StopVMCmdByAdmin, cmdInfo:
{response:json,id:51c44437-b22d-4cde-
ac32-b7ee5ea96521,sessionkey:qpV/kzaFZJjyjLW0IdAh8B4jpF4\u003d,ctxDetails:{\com.cloud.vm.VirtualMachine\:\51c44437-b22d-4cde-ac32-
b7ee5ea96521\},cmdEventType:VM.STOP,ctxUserId:2,httpmethod:GET,_:1417678580312,uuid:51c44437-b22d-4cde-ac32-
b7ee5ea96521,ctxAccountId:2,ctxStartEventId:150,forced:false},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null,
initMsid: 345051498404, completeMsid: null, lastUpdated: null, lastPolled:
null, created: null}
2014-12-04 15:36:11,026 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-41:ctx-54077a56 job-73 ctx-045d0389) Sync job-74 execution
on object VmWorkJobQueue.7
2014-12-04 15:36:11,030 WARN [c.c.u.d.Merovingian2]
(API-Job-Executor-41:ctx-54077a56 job-73 ctx-045d0389) Was unable to find
lock for the key vm_instance7 and thread
instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkStop,
resultCode: 0, result: null, initMsid: 345051498404, completeMsid: null,
lastUpdated: null, lastPolled: null, created: Thu Dec 04 15:36:11 CST 2014}
2014-12-04 15:36:11,552 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74) Run VM work job:
com.cloud.vm.VmWorkStop for VM 7, job
com.cloud.vm.VmWorkStop{cleanup:false,userId:2,accountId:2,vmId:7,handlerName:VirtualMachineManagerImpl}
2014-12-04 15:36:11,563 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74 ctx-a631e9b0) VM state
transitted from :Running to Stopping
with event: StopRequestedvm's original host id: 7 new host id: 7 host id
before state transition: 7
2014-12-04 15:36:11,568 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74 ctx-a631e9b0) Seq
7-3745306040111988838: Sending { Cmd , MgmtId:
345051498404, via: 7(192.168.100.24), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StopCommand:
{isProxy:false,executeInSequence:false,checkBeforeCleanup:false,vmName:i-2-7-VM,wait:0}}]
}
2014-12-04 15:36:11,568 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74 ctx-a631e9b0) Seq
7-3745306040111988838: Executing: { Cmd , MgmtId:
345051498404, via: 7(192.168.100.24), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StopCommand:
{isProxy:false,executeInSequence:false,checkBeforeCleanup:false,vmName:i-2-7-VM,wait:0}}]
}
2014-12-04 15:36:11,568 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-4:ctx-e14edce9) Seq 7-3745306040111988838: Executing request
2014-12-04 15:36:11,569 DEBUG [c.c.b.n.BareMetalResourceBase]
(DirectAgent-4:ctx-e14edce9) Executing: /usr/bin/python
/usr/share/cloudstack-common/scripts/util/ipmi.py
power interface=default hostname=192.168.100.24 usrname=root **
action=soft
2014-12-04
[jira] [Resolved] (CLOUDSTACK-8024) use barematel instance to stop or start Physical Machine failed。
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChunFeng resolved CLOUDSTACK-8024.
--
Resolution: Fixed
Fix Version/s: 4.3.2
ipmi script about lanplus had already remove , this issue no longer exist.
so , closed it .
use barematel instance to stop or start Physical Machine failed。
Key: CLOUDSTACK-8024
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8024
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Baremetal
Affects Versions: 4.4.1
Environment: Latest build from ACS 4.4.1-SNAPSHOT branch
Cluster: KVM
barematel instance OS:centos6.2.x86_64
Physical Machine:DELL PowerEdge M610
Reporter: luzhhk
Assignee: ChunFeng
Priority: Trivial
Fix For: 4.3.2
when use barematel to create instance,the instance Automatic finish OS
Installation and restart the system normally,but stop or reinstall OS get
problem 。
Following is the log snippet:
=
2, accountId: 2, instanceType: VirtualMachine, instanceId: 7, cmd:
org.apache.cloudstack.api.command.admin.vm.StopVMCmdByAdmin, cmdInfo:
{response:json,id:51c44437-b22d-4cde-ac32-b7ee5ea96521,sessionkey:qpV/kzaFZJjyjLW0IdAh8B4jpF4\u003d,ctxDetails:{\com.cloud.vm.VirtualMachine\:
\51c44437-b22d-4cde-ac32-b7ee5ea96521\},cmdEventType:VM.STOP,ctxUserId:2,httpmethod:GET,_:1417678580312,uuid:51c44437-b22d-4cde-ac32-
b7ee5ea96521,ctxAccountId:2,ctxStartEventId:150,forced:false},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null,
b22d-4cde-ac32-b7ee5ea96521forced=falseresponse=jsonsessionkey=qpV%2FkzaFZJjyjLW0IdAh8B4jpF4%3D_=1417678580312
instanceType: VirtualMachine, instanceId: 7, cmd:
org.apache.cloudstack.api.command.admin.vm.StopVMCmdByAdmin, cmdInfo:
{response:json,id:51c44437-b22d-4cde-
ac32-b7ee5ea96521,sessionkey:qpV/kzaFZJjyjLW0IdAh8B4jpF4\u003d,ctxDetails:{\com.cloud.vm.VirtualMachine\:\51c44437-b22d-4cde-ac32-
b7ee5ea96521\},cmdEventType:VM.STOP,ctxUserId:2,httpmethod:GET,_:1417678580312,uuid:51c44437-b22d-4cde-ac32-
b7ee5ea96521,ctxAccountId:2,ctxStartEventId:150,forced:false},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null,
initMsid: 345051498404, completeMsid: null, lastUpdated: null, lastPolled:
null, created: null}
2014-12-04 15:36:11,026 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-41:ctx-54077a56 job-73 ctx-045d0389) Sync job-74 execution
on object VmWorkJobQueue.7
2014-12-04 15:36:11,030 WARN [c.c.u.d.Merovingian2]
(API-Job-Executor-41:ctx-54077a56 job-73 ctx-045d0389) Was unable to find
lock for the key vm_instance7 and thread
instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkStop,
resultCode: 0, result: null, initMsid: 345051498404, completeMsid: null,
lastUpdated: null, lastPolled: null, created: Thu Dec 04 15:36:11 CST 2014}
2014-12-04 15:36:11,552 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74) Run VM work job:
com.cloud.vm.VmWorkStop for VM 7, job
com.cloud.vm.VmWorkStop{cleanup:false,userId:2,accountId:2,vmId:7,handlerName:VirtualMachineManagerImpl}
2014-12-04 15:36:11,563 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74 ctx-a631e9b0) VM state
transitted from :Running to Stopping
with event: StopRequestedvm's original host id: 7 new host id: 7 host id
before state transition: 7
2014-12-04 15:36:11,568 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74 ctx-a631e9b0) Seq
7-3745306040111988838: Sending { Cmd , MgmtId:
345051498404, via: 7(192.168.100.24), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StopCommand:
{isProxy:false,executeInSequence:false,checkBeforeCleanup:false,vmName:i-2-7-VM,wait:0}}]
}
2014-12-04 15:36:11,568 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-29:ctx-261b052e job-73/job-74 ctx-a631e9b0) Seq
7-3745306040111988838: Executing: { Cmd , MgmtId:
345051498404, via: 7(192.168.100.24), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StopCommand:
{isProxy:false,executeInSequence:false,checkBeforeCleanup:false,vmName:i-2-7-VM,wait:0}}]
}
2014-12-04 15:36:11,568 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-4:ctx-e14edce9) Seq 7-3745306040111988838: Executing request
2014-12-04 15:36:11,569 DEBUG [c.c.b.n.BareMetalResourceBase]
(DirectAgent-4:ctx-e14edce9) Executing: /usr/bin/python
/usr/share/cloudstack-common/scripts/util/ipmi.py
power interface=default hostname=192.168.100.24 usrname=root **
action=soft
2014-12-04 15:36:11,674 DEBUG [c.c.b.n.BareMetalResourceBase]
(DirectAgent-4:ctx-e14edce9)
[jira] [Closed] (CLOUDSTACK-3095) [UI][API]Able to add multiple tier networks to a deployed VM using “Add network” option.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori closed CLOUDSTACK-3095. - Verified .Working fine [UI][API]Able to add multiple tier networks to a deployed VM using “Add network” option. Key: CLOUDSTACK-3095 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3095 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: manasaveloori Assignee: Saksham Srivastava Fix For: 4.4.3 Steps: 1.Have a CS with advanced zone. 2.Create 2 VPCs and tier network under each VPC.(say VPC1-tier1 and VPC2-tier2). 3.Create a instance under VPC1 using tier1. 4.Now go to that created Vm-Nics-Add network-select tier2 from drop down.Add a network. Observation: As expected the network addition fails with exception. But the UI and API is listing all the networks under NICs for a VM. That is UI and API are listing multiple tiers to a VM. Ifconfig –a in Vm is not displaying the failed NICs. Also User should not be allowed to add VPC2 tier network to a VM belong to one VPC1. API passed: http://10.147.38.154:8096/client/api?command=listVirtualMachinesdetails=nicsid=c1024642-b4ba-4228-ace3-cf3cca587745 API response: listvirtualmachinesresponse cloud-stack-version=4.2.0-SNAPSHOTcount1/countvirtualmachineidc1024642-b4ba-4228-ace3-cf3cca587745/idnamec1024642-b4ba-4228-ace3-cf3cca587745/nameaccountadmin/accountdomainid58f45860-d73e-11e2-8845-06307824/domainiddomainROOT/domaincreated2013-06-20T21:53:15+0530/createdstateRunning/statehaenablefalse/haenablezoneid0f17ac3e-9499-4486-b7ab-5928cc97c98f/zoneidzonenamezoneVMw/zonenamezonetypeAdvanced/zonetypehostid1d17a148-9a60-4e2b-88fd-50187f4aeb21/hostidhostname10.147.40.29/hostnameguestosid590a7c3a-d73e-11e2-8845-06307824/guestosidnicid600b7332-e285-4d36-9696-9435dbee4563/idnetworkida311c39a-cabd-4fa5-9f96-8716a7145a4e/networkidnetworknametierVMw/networknamenetmask255.255.255.0/netmaskgateway172.16.1.1/gatewayipaddress172.16.1.180/ipaddressisolationurivlan://971/isolationuribroadcasturivlan://971/broadcasturitraffictypeGuest/traffictypetypeIsolated/typeisdefaulttrue/isdefaultmacaddress02:00:1d:a8:00:03/macaddress/nicnicid595d0ea1-fdc8-4138-8880-e201edeb8d96/idnetworkid178d6d12-e7d3-41df-b6cf-22db48b88db4/networkidnetworknametier1/networknamenetmask255.255.255.0/netmaskgateway10.0.1.1/gatewayipaddress10.0.1.61/ipaddressisolationurivlan://970/isolationuribroadcasturivlan://970/broadcasturitraffictypeGuest/traffictypetypeIsolated/typeisdefaultfalse/isdefaultmacaddress02:00:40:94:00:08/macaddress/nicnicid232420cc-6eec-432f-9679-9751e1ce0d47/idnetworkiddff16b9f-0484-477d-a16e-887db1d7a7d2/networkidnetworknamesh/networknamenetmask255.255.255.0/netmaskgateway10.147.55.1/gatewayipaddress10.147.55.102/ipaddressisolationurivlan://55/isolationuribroadcasturivlan://55/broadcasturitraffictypeGuest/traffictypetypeShared/typeisdefaultfalse/isdefaultmacaddress06:cb:1a:00:00:83/macaddress/nichypervisorVMware/hypervisorpublicipida90c4f5a-6ad5-4a7c-a425-36d227255ff7/publicipidpublicip10.147.47.9/publicipinstancenamei-2-25-VM/instancenamedisplayvmtrue/displayvm/virtualmachine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6417) Adding the KVM host to management server is failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori closed CLOUDSTACK-6417. - no longer an issue Adding the KVM host to management server is failing --- Key: CLOUDSTACK-6417 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6417 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: 4.4.0 Reporter: manasaveloori Assignee: Kishan Kavala Fix For: 4.4.0 Attachments: management-server.rar Updated java version to 1.7 in both MS and KVM host before installing the CS packages. When KVM agent is installed ,the agent package is installing java 1.6 Installing : 1:java-1.6.0-openjdk-1.6.0.0-1.45.1.11.1.el6.x86_64 Now java -verison was pointing to 1.6 Adding the host to CS is failing with following exception: 2014-04-15 06:33:43,505 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Timeout, to wait for the host connecting to mgt svr, assuming it is failed 2014-04-15 06:33:43,511 WARN [c.c.r.ResourceManagerImpl] (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Unable to find the server resources at http://10.147.40.29 2014-04-15 06:33:43,513 INFO [c.c.u.e.CSExceptionErrorCode] (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2014-04-15 06:33:43,514 WARN [o.a.c.a.c.a.h.AddHostCmd] (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy145.discoverHosts(Unknown Source) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:134) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:593) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330) at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at
[jira] [Created] (CLOUDSTACK-8138) [Automation] test_15_revert_vm_to_snapshot
Rayees Namathponnan created CLOUDSTACK-8138: --- Summary: [Automation] test_15_revert_vm_to_snapshot Key: CLOUDSTACK-8138 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8138 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Reporter: Rayees Namathponnan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8138) [Automation] test_15_revert_vm_to_snapshot : VM state should be stopped before revert
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-8138: Summary: [Automation] test_15_revert_vm_to_snapshot : VM state should be stopped before revert (was: [Automation] test_15_revert_vm_to_snapshot ) [Automation] test_15_revert_vm_to_snapshot : VM state should be stopped before revert - Key: CLOUDSTACK-8138 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8138 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rayees Namathponnan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8138) [Automation] test_15_revert_vm_to_snapshot : VM state should be stopped before revert
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-8138:
Description:
In test case
integration.component.test_escalations_instances.TestInstances.test_15_revert_vm_to_snapshot
, we should check VM state is stopped before VM revert
# Stop Virtual machine befor reverting VM to a snapshot taken without memory
vm_created.stop(self.userapiclient)
# Reverting the VM to Snapshot 1
VmSnapshot.revertToSnapshot(
self.userapiclient,
snapshot1.id
)
# L
Currently test cases failing with below error
File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
File
/root/cloudstack/test/integration/component/test_escalations_instances.py,
line 2632, in test_15_revert_vm_to_snapshot
snapshot1.id
File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line 4337,
in revertToSnapshot
return apiclient.revertToVMSnapshot(cmd)
File
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
line 2846, in revertToVMSnapshot
response = self.connection.marvinRequest(command, response_type=response,
method=method)
File /usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py,
line 379, in marvinRequest
raise e
'Job failed: {jobprocstatus : 0, created : u\'2014-12-25T07:29:06+\', cmd :
u\'org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd\',
userid : u\'212c570b-9e91-4d14-8198-051a46ae7181\', jobstatus : 2, jobid :
u\'6d31ff1b-bba0-43b6-bdbd-a0c93bee1110\', jobresultcode : 530, jobresulttype :
u\'object\', jobresult : {errorcode : 431, errortext : u\'VM Snapshot revert
not allowed. This will result in VM state change. You can revert running VM to
disk and memory type snapshot and stopped VM to disk type snapshot\'},
accountid : u\'ceda5a6d-9ab1-4029-ab0c-5ad80b3d8cba\'}\n
[Automation] test_15_revert_vm_to_snapshot : VM state should be stopped
before revert
-
Key: CLOUDSTACK-8138
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8138
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Reporter: Rayees Namathponnan
In test case
integration.component.test_escalations_instances.TestInstances.test_15_revert_vm_to_snapshot
, we should check VM state is stopped before VM revert
# Stop Virtual machine befor reverting VM to a snapshot taken without
memory
vm_created.stop(self.userapiclient)
# Reverting the VM to Snapshot 1
VmSnapshot.revertToSnapshot(
self.userapiclient,
snapshot1.id
)
# L
Currently test cases failing with below error
File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
File
/root/cloudstack/test/integration/component/test_escalations_instances.py,
line 2632, in test_15_revert_vm_to_snapshot
snapshot1.id
File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line
4337, in revertToSnapshot
return apiclient.revertToVMSnapshot(cmd)
File
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
line 2846, in revertToVMSnapshot
response = self.connection.marvinRequest(command, response_type=response,
method=method)
File
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, line
379, in marvinRequest
raise e
'Job failed: {jobprocstatus : 0, created : u\'2014-12-25T07:29:06+\', cmd
:
u\'org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd\',
userid : u\'212c570b-9e91-4d14-8198-051a46ae7181\', jobstatus : 2, jobid :
u\'6d31ff1b-bba0-43b6-bdbd-a0c93bee1110\', jobresultcode : 530, jobresulttype
: u\'object\', jobresult : {errorcode : 431, errortext : u\'VM Snapshot
revert not allowed. This will result in VM state change. You can revert
running VM to disk and memory type snapshot and stopped VM to disk type
snapshot\'}, accountid : u\'ceda5a6d-9ab1-4029-ab0c-5ad80b3d8cba\'}\n
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8138) [Automation] test_15_revert_vm_to_snapshot : VM state should be stopped before revert
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-8138:
Assignee: Gaurav Aradhye
[Automation] test_15_revert_vm_to_snapshot : VM state should be stopped
before revert
-
Key: CLOUDSTACK-8138
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8138
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
In test case
integration.component.test_escalations_instances.TestInstances.test_15_revert_vm_to_snapshot
, we should check VM state is stopped before VM revert
# Stop Virtual machine befor reverting VM to a snapshot taken without
memory
vm_created.stop(self.userapiclient)
# Reverting the VM to Snapshot 1
VmSnapshot.revertToSnapshot(
self.userapiclient,
snapshot1.id
)
# L
Currently test cases failing with below error
File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
File
/root/cloudstack/test/integration/component/test_escalations_instances.py,
line 2632, in test_15_revert_vm_to_snapshot
snapshot1.id
File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line
4337, in revertToSnapshot
return apiclient.revertToVMSnapshot(cmd)
File
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
line 2846, in revertToVMSnapshot
response = self.connection.marvinRequest(command, response_type=response,
method=method)
File
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, line
379, in marvinRequest
raise e
'Job failed: {jobprocstatus : 0, created : u\'2014-12-25T07:29:06+\', cmd
:
u\'org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd\',
userid : u\'212c570b-9e91-4d14-8198-051a46ae7181\', jobstatus : 2, jobid :
u\'6d31ff1b-bba0-43b6-bdbd-a0c93bee1110\', jobresultcode : 530, jobresulttype
: u\'object\', jobresult : {errorcode : 431, errortext : u\'VM Snapshot
revert not allowed. This will result in VM state change. You can revert
running VM to disk and memory type snapshot and stopped VM to disk type
snapshot\'}, accountid : u\'ceda5a6d-9ab1-4029-ab0c-5ad80b3d8cba\'}\n
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
