[jira] [Created] (CLOUDSTACK-6661) deployvm failed with NPE
Jayapal Reddy created CLOUDSTACK-6661:
-
Summary: deployvm failed with NPE
Key: CLOUDSTACK-6661
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6661
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: XenServer
Affects Versions: 4.4.0
Reporter: Jayapal Reddy
Priority: Critical
Fix For: 4.4.0
While deploying vm observed the NPE
java.lang.NullPointerException
at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:96)
=
2014-05-14 11:58:59,398 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(867392383@qtp-1655170479-7:ctx-2fd5e67f ctx-20936702) submit async job-178,
details: AsyncJobVO {id:178, userId: 2, accountId: 2, instanceType:
VirtualMachine, instanceId: 26, cmd:
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
{serviceofferingid:baa62f3e-9f44-46ad-a137-7275bcaf8c99,sessionkey:Li3x1YB3+DUERGcuaZ9plLrGSZc\u003d,cmdEventType:VM.CREATE,ctxUserId:2,zoneid:e7d72675-2bf3-4bab-b673-d9d92a735603,httpmethod:GET,templateid:79f647d6-da5c-11e3-80cb-b51f7904a635,response:json,id:26,ctxDetails:{\com.cloud.template.VirtualMachineTemplate\:5,\com.cloud.vm.VirtualMachine\:26,\com.cloud.dc.DataCenter\:1,\VirtualMachine\:\ed6a3bef-8e60-4001-8fc9-d0bd1ad15312\,\com.cloud.offering.ServiceOffering\:1},hypervisor:XenServer,iptonetworklist[0].networkid:4bcc4888-3a5d-4736-8b3e-ad8204606dcd,_:1400048939193,uuid:ed6a3bef-8e60-4001-8fc9-d0bd1ad15312,ctxAccountId:2,ctxStartEventId:197},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled: null,
created: null}
2014-05-14 11:58:59,399 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-7:job-178) Add job-178 into job monitoring
2014-05-14 11:58:59,399 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-7:job-178) Executing AsyncJobVO {id:178, userId: 2,
accountId: 2, instanceType: VirtualMachine, instanceId: 26, cmd:
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
{serviceofferingid:baa62f3e-9f44-46ad-a137-7275bcaf8c99,sessionkey:Li3x1YB3+DUERGcuaZ9plLrGSZc\u003d,cmdEventType:VM.CREATE,ctxUserId:2,zoneid:e7d72675-2bf3-4bab-b673-d9d92a735603,httpmethod:GET,templateid:79f647d6-da5c-11e3-80cb-b51f7904a635,response:json,id:26,ctxDetails:{\com.cloud.template.VirtualMachineTemplate\:5,\com.cloud.vm.VirtualMachine\:26,\com.cloud.dc.DataCenter\:1,\VirtualMachine\:\ed6a3bef-8e60-4001-8fc9-d0bd1ad15312\,\com.cloud.offering.ServiceOffering\:1},hypervisor:XenServer,iptonetworklist[0].networkid:4bcc4888-3a5d-4736-8b3e-ad8204606dcd,_:1400048939193,uuid:ed6a3bef-8e60-4001-8fc9-d0bd1ad15312,ctxAccountId:2,ctxStartEventId:197},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled: null,
created: null}
2014-05-14 11:58:59,400 DEBUG [c.c.a.ApiServlet]
(867392383@qtp-1655170479-7:ctx-2fd5e67f ctx-20936702) ===END=== 10.252.192.19
-- GET
command=deployVirtualMachineresponse=jsonsessionkey=Li3x1YB3%2BDUERGcuaZ9plLrGSZc%3Dzoneid=e7d72675-2bf3-4bab-b673-d9d92a735603templateid=79f647d6-da5c-11e3-80cb-b51f7904a635hypervisor=XenServerserviceofferingid=baa62f3e-9f44-46ad-a137-7275bcaf8c99iptonetworklist%5B0%5D.networkid=4bcc4888-3a5d-4736-8b3e-ad8204606dcd_=1400048939193
2014-05-14 11:58:59,407 DEBUG [c.c.a.d.ParamProcessWorker]
(API-Job-Executor-7:job-178 ctx-836ec730) Access granted to
Acct[7aa84a4e-da5c-11e3-80cb-b51f7904a635-admin] to service offering:1 by
RoleBasedEntityAccessChecker
2014-05-14 11:58:59,409 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
2-null-null-SystemCapability from cache: true
2014-05-14 11:58:59,409 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-7:job-178 ctx-836ec730) Root Access granted to
Acct[7aa84a4e-da5c-11e3-80cb-b51f7904a635-admin] by RoleBasedEntityAccessChecker
2014-05-14 11:58:59,411 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
2-null-null-DomainCapability from cache: false
2014-05-14 11:58:59,413 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
2-null-null-DomainResourceCapability from cache: false
2014-05-14 11:58:59,414 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
2-VirtualMachineTemplate5-UseEntry-deployVirtualMachine from cache: true
2014-05-14 11:58:59,414 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-7:job-178 ctx-836ec730) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[7aa84a4e-da5c-11e3-80cb-b51f7904a635-admin] by RoleBasedEntityAccessChecker
2014-05-14 11:58:59,414
[jira] [Created] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
Sanjay Tripathi created CLOUDSTACK-6650: --- Summary: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment Key: CLOUDSTACK-6650 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6650 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Fix For: 4.4.0 If CS environment has GPU cards then for non-GPU enabled VM deployments, deployment planner should check the non-GPU hosts first and if they are out of capacity then deploy in GPU enabled hosts. For now, this restriction is imposed at cluster level not at zone level, so to protect GPU resources, CS should give lower priority to clusters which has GPU enabled host and high priority to clusters which contains non-GPU enabled hosts. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6662) New XenServer host is not activated due to no agent connection
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6662: -- Affects Version/s: 4.4.0 New XenServer host is not activated due to no agent connection -- Key: CLOUDSTACK-6662 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6662 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Daan Hoogland Priority: Blocker A new xenserver 6.0.2 or devcloud2 with xcp 4.1 or the newer one with xcp 4.4 won't become active after adding because of the ssh command erroneously failing a remote execution of 'mkdir -p /opt/cloud/bin /var/log/cloud'. The command executes succesfully but an exceptions is logged: 2014-05-12 15:52:50,395 DEBUG [c.c.u.s.SSHCmdHelper] (DirectAgent-1:ctx-704cd231) Executing cmd: mkdir -p /opt/cloud/bin /var/log/cloud 2014-05-12 15:52:51,409 DEBUG [c.c.u.s.SSHCmdHelper] (DirectAgent-1:ctx-704cd231) Ssh executed failed java.lang.NullPointerException at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShotWithExitCode(SSHCmdHelper.java:159) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShot(SSHCmdHelper.java:170) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmd(SSHCmdHelper.java:66) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmd(SSHCmdHelper.java:91) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4845) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:4674) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:490) at com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOssResource.java:176) 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) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error Can only support create Private VLAN network with IPv4!
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994997#comment-13994997
]
Santhosh Kumar Edukulla commented on CLOUDSTACK-6627:
-
Looking at this bug, I didn't see any issue in the CS code for this.
1. Here we are verifying to create a ipv6 network with isolated pvlan support,
and product is appropriately reporting that creating pvlan with ipv6 is not
supported under NetworkServiceImpl.java( line 1201)
if (isolatedPvlan != null ipv6) {
throw new InvalidParameterValueException(Can only support create
Private VLAN network with IPv4!);
}
2. The issue is with test case, we should verify for exception from CS. Here,
at below line, it need to be verified for exception instead of return status
(line 85) under test_pvlan.py.
self.assertEqual(createNetworkResponse, FAILED, Creating PVLAN with IPv6
should fail).
3. Fixed TC and tested, It now works.
[Automation] createNetwork API failing with error Can only support create
Private VLAN network with IPv4!
---
Key: CLOUDSTACK-6627
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6627
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.4.0
Environment: KVM and vmware
build 4.4-forward
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.rar
integration.smoke.test_pvlan.TestPVLAN.test_create_pvlan_network failing
latest run
2014-05-09 14:37:36,948 DEBUG [c.c.a.ApiServlet]
(catalina-exec-11:ctx-80f69f30) ===START=== 10.223.240.194 -- GET
apiKey=PqBwvR5XGUP5UMkcchdzGW9QtWAexG7mh
0JjGFlcpg7Vf6Xazb9RhhL4j7RAY-bGWpqt_IjM2W3Oy0ukiFF_3Qstartipv6=fc00%3A1234%3A%3A10zoneid=8ec43c1f-ee32-4b1e-90d2-fce40313aafcisolatedpvlan=567displaytext
=pvlan+networkip6gateway=fc00%3A1234%3A%3A1gateway=10.10.10.20endipv6=fc00%3A1234%3A%3A20networkofferingid=7vlan=1234netmask=255.255.255.0response=jso
nname=pvlan+networkstartip=10.10.10.10ip6cidr=fc00%3A1234%3A%3A%2F64command=createNetworksignature=mHKCVFL1AM4NkVrEr%2FiW%2FdIj2NE%3D
API failing with error Can only support create Private VLAN network with
IPv4!
2014-05-09 14:37:36,971 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) IAM access check
for 2-null-nu
ll-SystemCapability from cache: false
2014-05-09 14:37:36,971 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Root Access granted
to Acct[e853580a-d7ae-
11e3-a7c8-1a6f7bb0d0a8-admin] by AffinityGroupAccessChecker
2014-05-09 14:37:37,011 INFO [c.c.a.ApiServer]
(catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Can only support
create Private VLAN network with IPv4!
2014
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6614) systemvm template build failed since src iso link is broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997350#comment-13997350 ] ASF subversion and git services commented on CLOUDSTACK-6614: - Commit 866e73df66ab6a3cf6a172c9d726d5d1f18cf51e in cloudstack's branch refs/heads/4.4 from [~ynojima] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=866e73d ] CLOUDSTACK-6614 bugfix: systemvm template build failed because of src iso link is broken systemvm template build failed since src iso link is broken --- Key: CLOUDSTACK-6614 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6614 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: Future, 4.4.0 Reporter: Yoshikazu Nojima Labels: systemvm Fix For: Future, 4.4.0 at least master is affected. build log: == We did not find an isofile here : /var/lib/jenkins/workspace/cloudstack-master-systemvm64/tools/appliance/iso/debian-7.4.0-amd64-netinst.iso. The definition provided the following download information: - Download url: http://ftp.acc.umu.se/mirror/cdimage/release/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso - Md5 Checksum: e7e9433973f082a297793c3c5010b2c5 Checking if isofile debian-7.4.0-amd64-netinst.iso already exists. Full path: /var/lib/jenkins/workspace/cloudstack-master-systemvm64/tools/appliance/iso/debian-7.4.0-amd64-netinst.iso There was an error downloading http://ftp.acc.umu.se/mirror/cdimage/release/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso: 404 Not Found There was an error downloading http://ftp.acc.umu.se/mirror/cdimage/release/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso: 404 Not Found -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6662) New XenServer host is not activated due to no agent connection
Daan Hoogland created CLOUDSTACK-6662: - Summary: New XenServer host is not activated due to no agent connection Key: CLOUDSTACK-6662 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6662 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Daan Hoogland Priority: Blocker A new xenserver 6.0.2 or devcloud2 with xcp 4.1 or the newer one with xcp 4.4 won't become active after adding because of the ssh command erroneously failing a remote execution of 'mkdir -p /opt/cloud/bin /var/log/cloud'. The command executes succesfully but an exceptions is logged: 2014-05-12 15:52:50,395 DEBUG [c.c.u.s.SSHCmdHelper] (DirectAgent-1:ctx-704cd231) Executing cmd: mkdir -p /opt/cloud/bin /var/log/cloud 2014-05-12 15:52:51,409 DEBUG [c.c.u.s.SSHCmdHelper] (DirectAgent-1:ctx-704cd231) Ssh executed failed java.lang.NullPointerException at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShotWithExitCode(SSHCmdHelper.java:159) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShot(SSHCmdHelper.java:170) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmd(SSHCmdHelper.java:66) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmd(SSHCmdHelper.java:91) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4845) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:4674) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:490) at com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOssResource.java:176) 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) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6663) [Hyper-V] Agent fails to start on some setups if last nic on host in nic list doesn't contain unicast address
Anshul Gangwar created CLOUDSTACK-6663: -- Summary: [Hyper-V] Agent fails to start on some setups if last nic on host in nic list doesn't contain unicast address Key: CLOUDSTACK-6663 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6663 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Anshul Gangwar Priority: Critical Before starting Hyper-V agent we initialize HypervResourceController. We try to initialize it with IP address 0.0.0.0. We try to get nic info of 0.0.0.0. To get nic info we iterate through all nics and return the last NIC in the list if it doesn't match with any IP address. So in case last NIC doesn't have unicastAddress, Hyper-V agent will fail to start. We don't need IP address during initialization. It get initialized with startupcommand later -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5501) Unable to create more than one vpnConnection per vpn customer gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996189#comment-13996189 ] ASF subversion and git services commented on CLOUDSTACK-5501: - Commit ed7bd0022e23352c8ec57bdd832b49451db88e73 in cloudstack's branch refs/heads/4.4 from [~yasker] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ed7bd00 ] CLOUDSTACK-5501: Allow one vpn customer gateway with multiple connections This restriction was purposely avoid confusion of VPN setup, but later found too strictly and cause troubles for deployment. Removed after testing one customer gateway with multiple connections. Unable to create more than one vpnConnection per vpn customer gateway - Key: CLOUDSTACK-5501 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5501 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: Alena Prokharchyk Assignee: Sheng Yang Priority: Critical Fix For: 4.4.0 There is currently a limitation in the CS code when you can't create more than one vpn connection per customer gateway. There are no technical reasons for this kind of limitation, so we should remove it as the customers might want to use his customer gateway cross zones if he owns VPCs in diff zones. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6548) [Automation] createPrivateNetwork API failed with NullPointer exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6548: -- Assignee: Rayees Namathponnan (was: Daan Hoogland) [Automation] createPrivateNetwork API failed with NullPointer exception Key: CLOUDSTACK-6548 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6548 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Environment: Xen 6.2 build 4.4-forward Reporter: Rayees Namathponnan Assignee: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Attachments: management-server.log.2014-04-30.gz This issue observed with BVT, test cases integration.smoke.test_privategw_acl.TestPrivateGwACL.test_privategw_acl failed with BVT, observed below NPE in ms log 2014-04-30 21:38:37,417 DEBUG [c.c.n.NetworkServiceImpl] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) Created private network Nt wk[cf4d60e1-9d4a-46de-85bc-910a6ea44024|Guest|5] 2014-04-30 21:38:37,433 DEBUG [c.c.u.d.T.Transaction] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) Rolling back the transaction: Time = 209 Name = catalina-exec-17; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670- Transaction.execute:41-NetworkServiceImpl.createPrivateNetwork:3964-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:-1-De legatingMethodAccessorImpl.invoke:-1-Method.invoke:-1-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint: 183-ReflectiveMethodInvocation.proceed:150 2014-04-30 21:38:37,452 ERROR [c.c.a.ApiServer] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) unhandled exception executing api c ommand: [Ljava.lang.String;@1925edc3 java.lang.NullPointerException at com.cloud.network.NetworkServiceImpl$11.doInTransaction(NetworkServiceImpl.java:3987) at com.cloud.network.NetworkServiceImpl$11.doInTransaction(NetworkServiceImpl.java:3964) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.NetworkServiceImpl.createPrivateNetwork(NetworkServiceImpl.java:3964) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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.$Proxy154.createPrivateNetwork(Unknown Source) at com.cloud.network.vpc.VpcManagerImpl$6.doInTransaction(VpcManagerImpl.java:1594) at com.cloud.network.vpc.VpcManagerImpl$6.doInTransaction(VpcManagerImpl.java:1578) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.vpc.VpcManagerImpl.createVpcPrivateGateway(VpcManagerImpl.java:1578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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
[jira] [Commented] (CLOUDSTACK-5046) [Automation] Vmware- System's StartCommand failed with NumberFormatException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996677#comment-13996677
]
Chip Childers commented on CLOUDSTACK-5046:
---
http://cloudstack.apache.org/mailing-lists.html
[Automation] Vmware- System's StartCommand failed with
NumberFormatException
---
Key: CLOUDSTACK-5046
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5046
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, VMware
Affects Versions: 4.3.0
Environment: vmware ; 5.0
branch : master (4.3)
Reporter: Rayees Namathponnan
Assignee: Min Chen
Priority: Blocker
Fix For: 4.3.0
Attachments: CLOUDSTACK-5046.rar
Create build from master branch; deploy advance zone in vmware setup
system vms are not getting created, observed NumberFormatException in ms log
2013-11-05 11:03:50,915 INFO [c.c.h.v.r.VmwareResource]
(DirectAgent-45:ctx-a29b989d 10.223.250.130) Prepare NIC device based on
NicTO:
{deviceId:2,networkRateMbps:-1,defaultNic:true,uuid:6f144332-f9e1-4ff6-9c15-d628272c2645,ip:10.223.243.2,netmask:255.255.255.192,gateway:10.223.243.1,mac:06:61:3a:00:00:3b,dns1:8.8.8.8,broadcastType:Vlan,type:Public,broadcastUri:vlan://510,isolationUri:vlan://510,isSecurityGroupEnabled:false}
2013-11-05 11:03:50,930 INFO [c.c.h.v.r.VmwareResource]
(DirectAgent-45:ctx-a29b989d 10.223.250.130) Prepare network on vmwaresvs
P[vSwitch0:untagged] with name prefix: cloud.public
2013-11-05 11:03:50,970 WARN [c.c.h.v.r.VmwareResource]
(DirectAgent-45:ctx-a29b989d 10.223.250.130) StartCommand failed due to
Exception: java.lang.NumberFormatException
Message: null
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:454)
at java.lang.Integer.parseInt(Integer.java:527)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:940)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3533)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2880)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:519)
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)
2013-11-05 11:03:50,973 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-45:ctx-a29b989d) Seq 2-1387069469: Cancelling because one of the
answers is false and it is stop on error.
2013-11-05 11:03:50,973 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-45:ctx-a29b989d) Seq 2-1387069469: Response Received:
2013-11-05 11:03:50,975 DEBUG [c.c.a.t.Request] (DirectAgent-45:ctx-a29b989d)
Seq 2-1387069469: Processing: { Ans: , MgmtId: 90928106758026, via: 2, Ver:
v1, Flags: 10,
[{com.cloud.agent.api.StartAnswer:{vm:{id:1,name:v-1-VM,bootloader:HVM,type:ConsoleProxy,cpus:1,minSpeed:500,maxSpeed:500,minRam:1073741824,maxRam:1073741824,hostName:v-1-VM,arch:i686,os:Debian
GNU/Linux 5.0 (32:
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-6664) support Docker as a new hypervisor
tuna created CLOUDSTACK-6664: Summary: support Docker as a new hypervisor Key: CLOUDSTACK-6664 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6664 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: Future Reporter: tuna Fix For: Future Supporting Docker as a new hypervisor, which can spawn containers from Dockerfile, Docker image or Docker tar file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6662) New XenServer host is not activated due to no agent connection
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997439#comment-13997439 ] Jayapal Reddy commented on CLOUDSTACK-6662: --- KVM host add also failing: 014-05-14 15:00:39,485 DEBUG [c.c.u.s.SSHCmdHelper] (831269712@qtp-798103901-9:ctx-9799e99d ctx-a4d1e0cf) Executing cmd: lsmod|grep kvm 2014-05-14 15:00:40,679 DEBUG [c.c.u.s.SSHCmdHelper] (831269712@qtp-798103901-9:ctx-9799e99d ctx-a4d1e0cf) Ssh executed failed java.lang.NullPointerException at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShotWithExitCode(SSHCmdHelper.java:159) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShot(SSHCmdHelper.java:170) at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmd(SSHCmdHelper.java:66) at com.cloud.hypervisor.kvm.discoverer.LibvirtServerDiscoverer.find(LibvirtServerDiscoverer.java:161) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:735) 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.$Proxy148.discoverHosts(Unknown Source) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:119) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:683) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:506) 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:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) 2014-05-14 15:00:40,680 DEBUG [c.c.u.s.SSHCmdHelper] (831269712@qtp-798103901-9:ctx-9799e99d ctx-a4d1e0cf) Executing cmd: lsmod|grep kvm 2014-05-14 15:00:41,884 DEBUG
[jira] [Commented] (CLOUDSTACK-6204) HTTP support for CPVM, as part of realhostip changes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997363#comment-13997363 ] ASF subversion and git services commented on CLOUDSTACK-6204: - Commit 156bd9b88589897f7a3c102104fc7cbe29354251 in cloudstack's branch refs/heads/4.3-forward from [~jlkinsel] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=156bd9b ] Applying missed patch from CLOUDSTACK-6204 Was brought to my attention that when I manually applied the CLOUDSTACK-6204 patch to 4.3-forward, somehow the changes for ConsoleProxyInof.java were missed. Fixing that here. BUG-ID: CLOUDSTACK-6204 Bugfix-for: 4.3 (exists in 0e57b75 on master) Signed-off-by: John Kinsella j...@stratosec.co 1400052371 -0700 HTTP support for CPVM, as part of realhostip changes Key: CLOUDSTACK-6204 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6204 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Critical Fix For: Future Details can be found here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4770) Management server fails to start with Unable to get the management server node due to downed interface with no MAC address
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997456#comment-13997456 ] Milamber commented on CLOUDSTACK-4770: -- Please note: before the restard of CS management service, a lot of these messages appear in logs: 2014-05-14 11:01:31,177 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-8284b79e) Management node 1 is detected inactive by timestamp but is pingable 2014-05-14 11:01:32,681 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-c7f636db) Trying to connect to 10.7.1.21 After the restart, these messages disappeared. Management server fails to start with Unable to get the management server node due to downed interface with no MAC address - Key: CLOUDSTACK-4770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4770 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1, 4.2.0, 4.4.0 Environment: CentOS 6.4, Ubuntu 14.04 Reporter: Richard Chatterton Priority: Minor Installing CloudStack 4.1.1 today, the management server failed to start with the following errors: 2013-09-30 14:43:43,436 INFO [utils.component.ComponentContext] (Timer-2:null) Running SystemIntegrityChecker managementServerNode 2013-09-30 14:43:43,438 ERROR [utils.component.ComponentContext] (Timer-2:null) System integrity check failed. Refuse to startup Due to CLOUDSTACK-4170, there wasn't any useful information provided, so I attempted to reinstall with CloudStack 4.2.0. This produced the following error messages: 2013-09-30 14:43:43,436 INFO [utils.component.ComponentContext] (Timer-2:null) Running SystemIntegrityChecker managementServerNode 2013-09-30 14:43:43,438 ERROR [utils.component.ComponentContext] (Timer-2:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: Unable to get the management server node id at com.cloud.cluster.ManagementServerNode.check(ManagementServerNode.java:46) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484) I found a mailing list post which mentioned that this might be due to missing MAC address, and recommended testing by running the class directly. This produced the following output for me: $ java -classpath /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-utils-4.2.0.jar com.cloud.utils.net.MacAddress addr in integer is 0 addr in bytes is 0 0 0 0 0 0 addr in char is 00:00:00:00:00:00 This was odd to me, as the output of ifconfig didn't have any MAC addresses that were 00:00:00:00:00:00. Looking into the code for that module, I found that what it appears to be doing is parsing ifconfig -a and returning the first string that looks like a MAC address. Reviewing the ifconfig -a output on the server, there was a downed bond interface with a MAC address of 00:00:00:00:00:00. When this interface is up, it automatically gets a MAC address from one of its slave physical interfaces. After assigning a dummy IP address to that interface and upping it, it received a MAC address and I was able to start the management server normally. I expect that there may be a better way to determine what the node id for the management server should be, or logic could be implemented to look for another MAC address if the first once it receives is invalid. Alternatively, if this behavior is expected, logging/debugging resources should be provided to help the user correct the problem. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6551) [Automation] Failed to revert vm snapshot in xen
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992696#comment-13992696
]
ASF subversion and git services commented on CLOUDSTACK-6551:
-
Commit 3f26eeb6eda6741a8b3ca2659317e12b216543c6 in cloudstack's branch
refs/heads/master from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3f26eeb ]
CLOUDSTACK-6551: [Automation] Failed to revert vm snapshot in xen
[Automation] Failed to revert vm snapshot in xen
-
Key: CLOUDSTACK-6551
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6551
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Snapshot, XenServer
Affects Versions: 4.4.0
Environment: Xen 6.2
build 4.4-forward
Reporter: Rayees Namathponnan
Assignee: Harikrishna Patnala
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.rar
Steps to reproduce
Step 1) Create advanced zone on xen
Step 2) Deploy a vm
Step 3) create vm snapshot without memory
step 4) revert the snapshot
Result
Revert snapshot failed with below exception
2014-05-01 06:22:19,439 DEBUG [c.c.n.NetworkModelImpl]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Service SecurityGroup is
not supported in the network id=241
2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq
2-5867345889533626796: Sending { Cmd , MgmtId: 6631563722783, via:
2(Rack1Pod1Host15), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.RevertToVMSnapshotCommand:{reloadVm:false,volumeTOs:[{uuid:ee4093bf-e6f0-49e3-be37-3b5c05fd6845,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cb8c6c62-71ea-3269-94b9-b1c0a4055d45,id:3,poolType:NetworkFilesystem,host:10.147.28.8,path:/vol/dgVol/automation/adv/pri_3,port:2049,url:NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=PrimarySTOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45}},name:ROOT-77,size:21474836480,path:75f283c8-db97-4b95-96c2-72d981bc7f0c,volumeId:83,vmName:i-2-77-VM,accountId:2,format:VHD,id:83,deviceId:0,hypervisorType:XenServer}],target:{id:3,snapshotName:i-2-77-VM_VS_20140501005100,type:Disk,createTime:139890546,current:true,description:Test
,quiescevm:true},vmName:i-2-77-VM,guestOSType:CentOS 5.6
(64-bit),wait:0}}] }
2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq
2-5867345889533626796: Executing: { Cmd , MgmtId: 6631563722783, via:
2(Rack1Pod1Host15), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.RevertToVMSnapshotCommand:{reloadVm:false,volumeTOs:[{uuid:ee4093bf-e6f0-49e3-be37-3b5c05fd6845,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cb8c6c62-71ea-3269-94b9-b1c0a4055d45,id:3,poolType:NetworkFilesystem,host:10.147.28.8,path:/vol/dgVol/automation/adv/pri_3,port:2049,url:NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=PrimarySTOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45}},name:ROOT-77,size:21474836480,path:75f283c8-db97-4b95-96c2-72d981bc7f0c,volumeId:83,vmName:i-2-77-VM,accountId:2,format:VHD,id:83,deviceId:0,hypervisorType:XenServer}],target:{id:3,snapshotName:i-2-77-VM_VS_20140501005100,type:Disk,createTime:139890546,current:true,description:Test
,quiescevm:true},vmName:i-2-77-VM,guestOSType:CentOS 5.6
(64-bit),wait:0}}] }
2014-05-01 06:22:19,465 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-233:ctx-acc9e792) Seq 2-5867345889533626796: Executing request
2014-05-01 06:22:20,084 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 8-4288: Processing Seq 8-4288: { Cmd ,
MgmtId: -1, via: 8, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:3,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-05-01 06:22:20,089 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 8-4288: Sending Seq 8-4288: { Ans: ,
MgmtId: 6631563722783, via: 8, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-05-01 06:22:20,524 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-233:ctx-acc9e792) Task failed! Task record:
uuid: 1affb5ba-5bcf-4e86-f866-c3cbba89dff8
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Wed Apr 30 20:08:59 IST 2014
finished: Wed Apr 30 20:08:59 IST 2014
status: failure
residentOn: com.xensource.xenapi.Host@e88e6ba5
progress: 1.0
type: none/
[jira] [Comment Edited] (CLOUDSTACK-6665) DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997453#comment-13997453
]
Remi Bergsma edited comment on CLOUDSTACK-6665 at 5/14/14 10:35 AM:
Review 21431 has been created to address this issue.
https://reviews.apache.org/r/21431/
was (Author: remibergsma):
Review 21431 has been created to address this issue.
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
-
Key: CLOUDSTACK-6665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0, 4.4.0
Reporter: Remi Bergsma
Priority: Critical
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
How to reproduce:
- create vpc network with small prefix
- create as many vm’s until all ip address space is consumed
- delete one vm
- now create a vm again: there should be an ip address freed
- it does not work though. Error on router:
/var/log/dnsmasq.log:May 13 12:53:16 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:00:0d:00:b6 no address available
How to reproduce #2:
- create a vm with static ip
- destroy it
- create vm with same static ip: this ip should be free again
This does not work either:
/var/log/dnsmasq.log:May 13 13:59:41 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:69:06:00:c1 no address available
Cause:
edithosts.sh is supposed to clean up addresses.
edithosts.sh line 101:
dhcp_release eth0 $ipv4 $(grep $ipv4 $DHCP_LEASES | awk '{print $2}')
/dev/null 21
But it doesn’t work, because eth0 is the link local address on VPC routers.
We should make the interface variable on VPC routers.
It does work fine on redundant routers, for example. Because eth0 is the
actual guest network.
CloudStack reports to the user: Insufficient capacity.
Manual work-around:
Run on the router:
dhcp_release eth3 02:00:69:06:00:c1 10.75.16.8
Replace eth3 with the correct interface.
It logs:
/var/log/messages-20140419:May 13 13:38:29 r-4197-VM cloud: edithosts:
released 10.75.16.8
It now works!
This an annoying bug for users that use static ip’s in their networks. Also
users that deploy a lot of test vm’s in the same network are impacted. Let’s
fix it :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6668) OVS distributed routing: ensure bridge is deleted when last VM from the VPC is deleted on a host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997464#comment-13997464 ] ASF subversion and git services commented on CLOUDSTACK-6668: - Commit 4c01d81d80ef8541ba0976c3beee9d7180da883b in cloudstack's branch refs/heads/4.4-forward from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4c01d81 ] CLOUDSTACK-6668: OVS distributed routing: ensure bridge is deleted when last VM from the VPC is deleted on a host OVS distributed routing: ensure bridge is deleted when last VM from the VPC is deleted on a host. This fix ensures that bridge is destroyed. OVS distributed routing: ensure bridge is deleted when last VM from the VPC is deleted on a host Key: CLOUDSTACK-6668 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6668 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.4.0 When last VM from a VPC in destroyed on host, then host is no longer is part of VPC topology. Currently bridge is not destroyed. This bug is to ensure that bridge is destroyed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6668) OVS distributed routing: ensure bridge is deleted when last VM from the VPC is deleted on a host
Murali Reddy created CLOUDSTACK-6668: Summary: OVS distributed routing: ensure bridge is deleted when last VM from the VPC is deleted on a host Key: CLOUDSTACK-6668 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6668 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.4.0 When last VM from a VPC in destroyed on host, then host is no longer is part of VPC topology. Currently bridge is not destroyed. This bug is to ensure that bridge is destroyed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (CLOUDSTACK-6617) [Automation] detach / resize volume test cases failing with permission error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Clark updated CLOUDSTACK-6617:
---
Comment: was deleted
(was: Full test output available here:
http://jenkins-ccp.citrix.com/view/XenRT/job/xenrt-bvt-basic-xs/lastCompletedBuild/testReport/integration.smoke.test_volumes/TestVolumes/test_06_download_detached_volume/
MS logs available here:
http://xenrt.hq.xensource.com/share/control/logs/job/692214/Logs/CCPLogs/browse)
[Automation] detach / resize volume test cases failing with permission error
--
Key: CLOUDSTACK-6617
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6617
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes, Xen
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Min Chen
Fix For: 4.4.0
Attachments: management-server.log
This issue is observed in 4.4-forward automation in Xen, test case
integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume
failing with permission error
integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
Execute cmd: attachvolume failed, due to: errorCode: 531,
errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
begin captured stdout -
=== TestName: test_06_download_detached_volume | Status : EXCEPTION ===
- end captured stdout --
begin captured logging
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: STARTED :
TC: test_06_download_detached_volume :::
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Extract detached Volume
ID: 885ac921-4728-4903-9621-b07c5353e9bc
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Payload: {'apiKey':
u'WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ',
'virtualmachineid': u'2e1ef913-b207-4688-bbaa-408797810d3a', 'id':
u'885ac921-4728-4903-9621-b07c5353e9bc', 'command': 'attachVolume',
'signature': 'hnLR1wCmFp5EtwMZRaS1e3J75S8=', 'response': 'json'}
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Sending GET Cmd
: attachVolume===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.76.63
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQvirtualmachineid=2e1ef913-b207-4688-bbaa-408797810d3aid=885ac921-4728-4903-9621-b07c5353e9bccommand=attachVolumesignature=hnLR1wCmFp5EtwMZRaS1e3J75S8%3Dresponse=json
HTTP/1.1 531 212
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): ERROR: Exception:['Traceback
(most recent call last):\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse\nresponse_cls)\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj\nraise
cloudstackException.CloudstackAPIException(respname, errMsg)\n',
'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources\n']
Traceback (most recent call last):
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse
response_cls)
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj
raise cloudstackException.CloudstackAPIException(respname, errMsg)
CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): ERROR: marvinRequest : CmdName:
marvin.cloudstackAPI.attachVolume.attachVolumeCmd object at 0x36ccf90
Exception: ['Traceback (most recent call last):\n', ' File
[jira] [Commented] (CLOUDSTACK-6649) CS is not giving the system-wide capacity for GPU reosurce.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997427#comment-13997427 ] ASF subversion and git services commented on CLOUDSTACK-6649: - Commit e7e1ae254af8588a90bee56f5dcd1175c64ffd5e in cloudstack's branch refs/heads/4.4-forward from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e7e1ae2 ] CLOUDSTACK-6649: CS is not giving the system-wide capacity for GPU reosurce. CS is not giving the system-wide capacity for GPU reosurce. --- Key: CLOUDSTACK-6649 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6649 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP! Reporter: Sanjay Tripathi Priority: Critical Fix For: 4.4.0 CloudStack is not displaying system-wide capacity for GPU resource because of this admin is not able to see how much of GPU resource is used and how much is available. Like other resources, CS should give capacity details of GPU resource in listCapacity API call response and display that in CS dashboard. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6649) CS is not giving the system-wide capacity for GPU reosurce.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997496#comment-13997496 ] ASF subversion and git services commented on CLOUDSTACK-6649: - Commit 13ba59c5f0b5e5007981c1705110d4e9387aca4f in cloudstack's branch refs/heads/4.4 from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=13ba59c ] CLOUDSTACK-6649: CS is not giving the system-wide capacity for GPU reosurce. CS is not giving the system-wide capacity for GPU reosurce. --- Key: CLOUDSTACK-6649 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6649 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP! Reporter: Sanjay Tripathi Priority: Critical Fix For: 4.4.0 CloudStack is not displaying system-wide capacity for GPU resource because of this admin is not able to see how much of GPU resource is used and how much is available. Like other resources, CS should give capacity details of GPU resource in listCapacity API call response and display that in CS dashboard. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6617) [Automation] detach / resize volume test cases failing with permission error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993555#comment-13993555
]
Doug Clark commented on CLOUDSTACK-6617:
Full test output available here:
http://jenkins-ccp.citrix.com/view/XenRT/job/xenrt-bvt-basic-xs/lastCompletedBuild/testReport/integration.smoke.test_volumes/TestVolumes/test_06_download_detached_volume/
MS logs available here:
http://xenrt.hq.xensource.com/share/control/logs/job/692214/Logs/CCPLogs/browse
[Automation] detach / resize volume test cases failing with permission error
--
Key: CLOUDSTACK-6617
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6617
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes, Xen
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Fix For: 4.4.0
Attachments: management-server.log
This issue is observed in 4.4-forward automation in Xen, test case
integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume
failing with permission error
integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
Execute cmd: attachvolume failed, due to: errorCode: 531,
errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
begin captured stdout -
=== TestName: test_06_download_detached_volume | Status : EXCEPTION ===
- end captured stdout --
begin captured logging
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: STARTED :
TC: test_06_download_detached_volume :::
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Extract detached Volume
ID: 885ac921-4728-4903-9621-b07c5353e9bc
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Payload: {'apiKey':
u'WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ',
'virtualmachineid': u'2e1ef913-b207-4688-bbaa-408797810d3a', 'id':
u'885ac921-4728-4903-9621-b07c5353e9bc', 'command': 'attachVolume',
'signature': 'hnLR1wCmFp5EtwMZRaS1e3J75S8=', 'response': 'json'}
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Sending GET Cmd
: attachVolume===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.76.63
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQvirtualmachineid=2e1ef913-b207-4688-bbaa-408797810d3aid=885ac921-4728-4903-9621-b07c5353e9bccommand=attachVolumesignature=hnLR1wCmFp5EtwMZRaS1e3J75S8%3Dresponse=json
HTTP/1.1 531 212
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): ERROR: Exception:['Traceback
(most recent call last):\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse\nresponse_cls)\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj\nraise
cloudstackException.CloudstackAPIException(respname, errMsg)\n',
'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources\n']
Traceback (most recent call last):
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse
response_cls)
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj
raise cloudstackException.CloudstackAPIException(respname, errMsg)
CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): ERROR: marvinRequest : CmdName:
marvin.cloudstackAPI.attachVolume.attachVolumeCmd object at 0x36ccf90
Exception: ['Traceback (most recent call last):\n', ' File
[jira] [Commented] (CLOUDSTACK-6606) create network offering dailog box has greyed out (not selectable) providers for the connectivity service.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996196#comment-13996196 ] ASF subversion and git services commented on CLOUDSTACK-6606: - Commit 7bd0b92ea060be978ce1b9a69cfc45b4a673a342 in cloudstack's branch refs/heads/4.4 from [~gabora] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7bd0b92 ] CLOUDSTACK-6606: Fixed: create network offering dailog box has greyed out (not selectable) providers for the connectivity service. create network offering dailog box has greyed out (not selectable) providers for the connectivity service. -- Key: CLOUDSTACK-6606 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6606 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Murali Reddy Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Attachments: Screen Shot 2014-05-07 at 3.05.09 PM.png create network offering dailog box has greyed out (not selectable) providers for the connectivity service. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6648) [Automation]: vm ha cases were failing in 4.4-forward
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-6648: --- Assignee: Santhosh Kumar Edukulla [Automation]: vm ha cases were failing in 4.4-forward - Key: CLOUDSTACK-6648 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6648 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla vm_ha.py cases were failing because of proper zone was not getting picked up. Fixed them now, moved the test data out of test cases to get proper test data. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-2697) cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 // podId:: 1 // clusterId:: null }
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Girish Chaudhari resolved CLOUDSTACK-2697.
--
Resolution: Fixed
cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 //
podId:: 1 // clusterId:: null }
-
Key: CLOUDSTACK-2697
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2697
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
Assignee: Girish Chaudhari
Priority: Minor
Fix For: 4.4.0
Attachments: logs.rar
Cluster id should not be null in Alert message.
Snippet of log
2013-05-27 13:13:19,879 WARN [apache.cloudstack.alerts]
(CapacityChecker:null) alertType:: 1 // dataCenterId:: 1 // podId:: 1 //
clusterId:: null // message:: System Alert: Low Unallocated CPU in cluster
cluster pod pod of availability zone pod
2013-05-27 13:13:19,890 DEBUG [cloud.alert.AlertManagerImpl]
(CapacityChecker:null) Have already sent: 1 emails for alert type '1' --
skipping send email
2013-05-27 13:13:19,954 DEBUG [cloud.alert.AlertManagerImpl]
(CapacityChecker:null) System Alert: Low Unallocated CPU in cluster cluster2
pod pod of availability zone pod
2013-05-27 13:13:19,954 DEBUG [cloud.alert.AlertManagerImpl]
(CapacityChecker:null) Unallocated CPU is low, total: 9576 Mhz, used: 2000
Mhz (20.89%)
2013-05-27 13:13:19,955 WARN [apache.cloudstack.alerts]
(CapacityChecker:null) alertType:: 1 // dataCenterId:: 1 // podId:: 1 //
clusterId:: null // message:: System Alert: Low Unallocated CPU in cluster
cluster2 pod pod of availability zone pod
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6473) Debian 7 Virtual Router ip_conntrack_max not set at boot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997280#comment-13997280 ] Keerthiraja commented on CLOUDSTACK-6473: - is this will be fixed in 4.3.1 Debian 7 Virtual Router ip_conntrack_max not set at boot Key: CLOUDSTACK-6473 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6473 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Virtual Router Affects Versions: 4.3.0 Environment: XenServer 6.2 CloudStack 4.3.0 Debian 7 SystemVM/Virtual Router Reporter: Logan B Fix For: 4.3.1 The Problem: The Debian 7 Virtual Router VMs for XenServer experiences intermittent connectivity problems. This affects all VMs behind the virtual router in various ways: SSH failures, Apache connections fail, etc. This issue also affects various function within CloudStack that attempt to connect to the Virtual Router (updating firewall rules, NAT, etc.) The Cause: It appears that the issues is being caused by a low default limit for the net.ipv4.netfilter.ip_conntrack_max sysctl. The issue can be easily diagnosed in /var/log/messages: Apr 22 15:45:34 r-5602-VM kernel: [ 1085.117498] nf_conntrack: table full, dropping packet. Apr 22 15:45:34 r-5602-VM kernel: [ 1085.133095] nf_conntrack: table full, dropping packet. Apr 22 15:45:34 r-5602-VM kernel: [ 1085.145440] nf_conntrack: table full, dropping packet. The default setting for ip_conntrack_max is '3796': # sysctl net.ipv4.netfilter.ip_conntrack_max net.ipv4.netfilter.ip_conntrack_max = 3796 As per /etc/sysctl.conf this setting should be '100': net.ipv4.netfilter.ip_conntrack_max=100 It would appear that this setting is not being correctly applied when the virtual router boots. The Solution: - A temporary workaround is to manually set the ip_conntrack_max sysctl to the correct value: # sysctl -w net.ipv4.netfilter.ip_conntrack_max=100 It's likely that this sysctl is being run at boot before the module is loaded, so it doesn't take effect. There are various solutions suggested around the web, any of which should work fine. To resolve this problem a new System VM template should be created. I'm assuming this can be done in between CloudStack releases. I know there is supposed to be a new template released to fix the HeartBleed vulnerability, so this would be a good fix to include with that updated template. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6666) UI search for vm's in port forward rules field does not work
Remi Bergsma created CLOUDSTACK-: Summary: UI search for vm's in port forward rules field does not work Key: CLOUDSTACK- URL: https://issues.apache.org/jira/browse/CLOUDSTACK- 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: Remi Bergsma Priority: Minor How to reproduce: Click: - network - vpc from drop down - select a vpc network - configure - router :: public ip addresses - click ip address - configuration tab - port forwarding :: view all - add vm the search above this screen does not work this because the ‘keyword’ parameter is not parsed to the listVirtualMachines call. API call made: account some name command listVirtualMachines domainid69d000c7-a8f8-0009-0a8a-949172fe2bda listAll true page1 pageSize20 responsejson sessionkey bla Please add filter so the search will work. Especially with large amounts of vm's this is annoying. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6645) UI:MS: Unable to create a user type Admin under a domain; No API being fired
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995726#comment-13995726 ] Jessica Wang commented on CLOUDSTACK-6645: -- https://issues.apache.org/jira/i#browse/CLOUDSTACK-6379 UI:MS: Unable to create a user type Admin under a domain; No API being fired Key: CLOUDSTACK-6645 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6645 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6565) [UI] New Zones tab for Templates and ISOs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995437#comment-13995437 ] ASF subversion and git services commented on CLOUDSTACK-6565: - Commit c20acc6a4451dd0f3eba1beeb52e215f000b59d9 in cloudstack's branch refs/heads/4.4-forward from [~gabora] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c20acc6 ] CLOUDSTACK-6565: [UI] New Zones tab for Templates and ISOs [UI] New Zones tab for Templates and ISOs - Key: CLOUDSTACK-6565 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6565 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Display templates and ISOs only once, even if they are for multiple zones. Instead of showing redundant list, one item for each zone, show zone list in a new tab. (Current UI shows templates and ISOs as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show the per-zone related user actions in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. This feature does not need API changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6594) [Automation] Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997574#comment-13997574 ] Milamber commented on CLOUDSTACK-6594: -- Also with CS 4.4.0 snapshot 20140513 (fresh install) Full log in attachment. 2014-05-14 15:09:13,266 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert 2014-05-14 15:09:13,271 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key i_alert__last_sent on table alert 2014-05-14 15:09:13,542 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_nsp_id on table baremetal_dhcp_devices 2014-05-14 15:09:13,665 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_host_id on table baremetal_dhcp_devices 2014-05-14 15:09:13,765 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_pod_id on table baremetal_dhcp_devices 2014-05-14 15:09:13,854 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_physical_network_id on table baremetal_dhcp_devices 2014-05-14 15:09:13,977 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_nsp_id on table baremetal_pxe_devices 2014-05-14 15:09:14,066 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_host_id on table baremetal_pxe_devices 2014-05-14 15:09:14,167 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_pod_id on table baremetal_pxe_devices 2014-05-14 15:09:14,268 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_physical_network_id on table baremetal_pxe_devices 2014-05-14 15:09:14,369 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_nsp_id on table baremetal_pxe_devices 2014-05-14 15:09:14,469 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_host_id on table baremetal_pxe_devices 2014-05-14 15:09:14,569 WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_physical_network_id on table baremetal_pxe_devices [Automation] Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists Key: CLOUDSTACK-6594 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6594 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: RHEL 6.3, Build - 4.4-forward, Also Ubuntu 14.04, CS 4.4.0-snapshot 20140513 Reporter: Rayees Namathponnan Assignee: Nitin Mehta Fix For: 4.4.0 Attachments: CLOUDSTACK-6594.rar, management-server.log Below exception observed while staring MS INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) Loading module context [system] from URL [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-core-4.4.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml] INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false INFO [c.c.u.d.Merovingian2] (main:null) Cleaning up locks for 29066118877352 INFO [c.c.u.d.Merovingian2] (main:null) Released 0 locks for 29066118877352 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@883ca2e INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for database upgrade. INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.0.0 Code Version = 4.4.0-SNAPSHOT INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 4.0.0 to 4.4.0-SNAPSHOT WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'last_sent'; check that column/key exists at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
[jira] [Commented] (CLOUDSTACK-6659) Change updatePublicIpAddress API command name to updateIpAddress
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996913#comment-13996913 ] ASF subversion and git services commented on CLOUDSTACK-6659: - Commit c94158f0fdb5a742a80a3a9177809d9a1840af18 in cloudstack's branch refs/heads/4.4 from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c94158f ] CLOUDSTACK-6659: fixed the name for the updateIpAddress API command Change updatePublicIpAddress API command name to updateIpAddress Key: CLOUDSTACK-6659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6659 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Priority: Critical Fix For: 4.4.0 The command updatePublicIpAddress was introduced in 4.4 release. We have to change its name to updateIpAddress to be consistent with the rest of public ip address commands - associateipaddress/disassociateipaddress -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6659) Change updatePublicIpAddress API command name to updateIpAddress
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996903#comment-13996903 ] ASF subversion and git services commented on CLOUDSTACK-6659: - Commit 2334d9a1f3bd5ecc51cdeeff0512e95c93b7ead1 in cloudstack's branch refs/heads/4.4-forward from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2334d9a ] CLOUDSTACK-6659: fixed the name for the updateIpAddress API command Change updatePublicIpAddress API command name to updateIpAddress Key: CLOUDSTACK-6659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6659 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Priority: Critical Fix For: 4.4.0 The command updatePublicIpAddress was introduced in 4.4 release. We have to change its name to updateIpAddress to be consistent with the rest of public ip address commands - associateipaddress/disassociateipaddress -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6594) [Automation] Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milamber updated CLOUDSTACK-6594: - Environment: RHEL 6.3, Build - 4.4-forward, Also Ubuntu 14.04, CS 4.4.0-snapshot 20140513 was: RHEL 6.3 Build - 4.4-forward [Automation] Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists Key: CLOUDSTACK-6594 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6594 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: RHEL 6.3, Build - 4.4-forward, Also Ubuntu 14.04, CS 4.4.0-snapshot 20140513 Reporter: Rayees Namathponnan Assignee: Nitin Mehta Fix For: 4.4.0 Attachments: CLOUDSTACK-6594.rar Below exception observed while staring MS INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) Loading module context [system] from URL [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-core-4.4.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml] INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false INFO [c.c.u.d.Merovingian2] (main:null) Cleaning up locks for 29066118877352 INFO [c.c.u.d.Merovingian2] (main:null) Released 0 locks for 29066118877352 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@883ca2e INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for database upgrade. INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.0.0 Code Version = 4.4.0-SNAPSHOT INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 4.0.0 to 4.4.0-SNAPSHOT WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'last_sent'; check that column/key exists at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.upgrade.dao.DatabaseAccessObject.dropKey(DatabaseAccessObject.java:37) at com.cloud.upgrade.dao.DbUpgradeUtils.dropKeysIfExist(DbUpgradeUtils.java:28) at com.cloud.upgrade.dao.Upgrade410to420.addIndexForAlert(Upgrade410to420.java:543) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:98) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:310) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:432) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at
[jira] [Closed] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error Can only support create Private VLAN network with IPv4!
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6627. --- [Automation] createNetwork API failing with error Can only support create Private VLAN network with IPv4! --- Key: CLOUDSTACK-6627 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6627 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.4.0 Environment: KVM and vmware build 4.4-forward Reporter: Rayees Namathponnan Assignee: Santhosh Kumar Edukulla Priority: Blocker Fix For: 4.4.0 Attachments: management-server.rar integration.smoke.test_pvlan.TestPVLAN.test_create_pvlan_network failing latest run 2014-05-09 14:37:36,948 DEBUG [c.c.a.ApiServlet] (catalina-exec-11:ctx-80f69f30) ===START=== 10.223.240.194 -- GET apiKey=PqBwvR5XGUP5UMkcchdzGW9QtWAexG7mh 0JjGFlcpg7Vf6Xazb9RhhL4j7RAY-bGWpqt_IjM2W3Oy0ukiFF_3Qstartipv6=fc00%3A1234%3A%3A10zoneid=8ec43c1f-ee32-4b1e-90d2-fce40313aafcisolatedpvlan=567displaytext =pvlan+networkip6gateway=fc00%3A1234%3A%3A1gateway=10.10.10.20endipv6=fc00%3A1234%3A%3A20networkofferingid=7vlan=1234netmask=255.255.255.0response=jso nname=pvlan+networkstartip=10.10.10.10ip6cidr=fc00%3A1234%3A%3A%2F64command=createNetworksignature=mHKCVFL1AM4NkVrEr%2FiW%2FdIj2NE%3D API failing with error Can only support create Private VLAN network with IPv4! 2014-05-09 14:37:36,971 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) IAM access check for 2-null-nu ll-SystemCapability from cache: false 2014-05-09 14:37:36,971 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Root Access granted to Acct[e853580a-d7ae- 11e3-a7c8-1a6f7bb0d0a8-admin] by AffinityGroupAccessChecker 2014-05-09 14:37:37,011 INFO [c.c.a.ApiServer] (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Can only support create Private VLAN network with IPv4! 2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6674) [Automation] [DB lock] When KVM agent is alert state, agent never trying to connect back
Rayees Namathponnan created CLOUDSTACK-6674: --- Summary: [Automation] [DB lock] When KVM agent is alert state, agent never trying to connect back Key: CLOUDSTACK-6674 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6674 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Environment: KVM (RHEL 6.3) 4.4-forward Reporter: Rayees Namathponnan Assignee: edison su Priority: Blocker Fix For: 4.4.0 This issue observed in automation run, when KVM agent is alert state, it never tries to connect back, also observed SQL DB lock in MS log for AgentConnectTaskPool You need to restart agent manually to connect it back Here is agent log 2014-05-13 23:59:38,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands... 2014-05-13 23:59:38,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 5 commands in progre ss. 2014-05-13 23:59:43,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands... 2014-05-13 23:59:43,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 5 commands in progre ss. 2014-05-13 23:59:48,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands... 2014-05-13 23:59:48,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 5 commands in progre ss. 2014-05-13 23:59:53,877 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands... 2014-05-13 23:59:53,878 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 5 commands in progre ss. 2014-05-13 23:59:58,878 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands... 2014-05-13 23:59:58,878 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 5 commands in progress. ~ MS log 2014-05-13 20:07:50,170 DEBUG [c.c.v.VirtualMachineManagerImpl] (API-Job-Executor-93:job-2240 ctx-f6efb16a) Destroying vm VM[User|i-137-304-QA] 2014-05-13 20:07:50,171 DEBUG [c.c.u.d.T.Transaction] (API-Job-Executor-65:job-2223 ctx-a60be5ae) Rolling back the transaction: Time = 291 Name = API-Job-Ex ecutor-65; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-Ref lectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:204-$Proxy97.markA sUnavailable:-1-IpAddressManagerImpl$10.doInTransaction:1639-IpAddressManagerImpl$10.doInTransaction:1620-Transaction$2.doInTransaction:49 2014-05-13 20:07:50,173 WARN [c.c.u.AccountManagerImpl] (API-Job-Executor-65:job-2223 ctx-a60be5ae) Failed to cleanup account Acct[20c063c7-9913-496d-983f-e fe18a92a9dc-test-account-TestScaleVmDynamicServiceOffering-test_change_so_running_vm_dynamic_to_dynamic_1_ADMIN] due to com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.PreparedStatement@76384607: UPDATE user_ip_address SET user_ip_address.state ='Releasing' WHERE user_ip_address.id = 15 at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:851) at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:1327) at com.cloud.network.dao.IPAddressDaoImpl.markAsUnavailable(IPAddressDaoImpl.java:323) at sun.reflect.GeneratedMethodAccessor536.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
[jira] [Commented] (CLOUDSTACK-6604) [Upgrade]Failed to find any private zone for Resource domain admin message when admin logs in after upgrading from 4.3 to 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994117#comment-13994117 ] Min Chen commented on CLOUDSTACK-6604: -- Prachi is working on IAM upgrade, so assign this to her to take a look. [Upgrade]Failed to find any private zone for Resource domain admin message when admin logs in after upgrading from 4.3 to 4.4 Key: CLOUDSTACK-6604 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6604 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.4.0 Reporter: manasaveloori Assignee: Min Chen Priority: Blocker Fix For: 4.4.0 Attachments: management-server.rar, mysqldump43.dmp, mysqldump44.dmp 1. Deploy CS 4.3 with 2 zones using xen 6.1 and KVM hypervisor. 2. Configured LB rules,firewall rules. 3. Registered the template for 4.4 (using the naming convention systemvm-xenserver-4.4,systemvm-kvm-4.4) 4. Upgraded to 4.4 Start the management server: Below are the observations: Login the UI Found below exception: 2014-05-05 05:10:27,789 ERROR [c.c.a.ApiServer] (catalina-exec-19:ctx-738d7732 ctx-f31c0a20) unhandled exception executing api command: [Ljava.lang.String;@4cc0a048 com.cloud.utils.exception.CloudRuntimeException: Failed to find any private zone for Resource domain admin. at com.cloud.user.AccountManagerImpl.getZoneIdForAccount(AccountManagerImpl.java:599) at com.cloud.user.AccountManagerImpl.checkAccessAndSpecifyAuthority(AccountManagerImpl.java:581) 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.$Proxy100.checkAccessAndSpecifyAuthority(Unknown Source) at com.cloud.server.ManagementServerImpl.searchForAlerts(ManagementServerImpl.java:2333) 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.$Proxy234.searchForAlerts(Unknown Source) at org.apache.cloudstack.api.command.admin.resource.ListAlertsCmd.execute(ListAlertsCmd.java:81) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:119) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:591) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:414) 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.doGet(ApiServlet.java:77) at
[jira] [Commented] (CLOUDSTACK-6562) [Automation] [XenServer] Secondary Storage count for account shows double the value of the desired count
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996299#comment-13996299 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6562: - Hello Ashutosh, Looking at the bug, i didnt see the issue. Where exactly we see the size to double for account when template is downloaded? Did we mean on dashboard, secondary storage allocated value for a given zone ? https://issues.apache.org/jira/browse/CLOUDSTACK-6562 Please add some steps to reproduce as well snapshot explaining the issue. Let me know. Santhosh [Automation] [XenServer] Secondary Storage count for account shows double the value of the desired count Key: CLOUDSTACK-6562 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6562 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Storage Controller, Template Affects Versions: 4.4.0 Environment: XenServer No problem on KVM and VMware Reporter: Ashutosk Kelkar Assignee: Santhosh Kumar Edukulla Labels: automation Fix For: 4.4.0 Create an account. Register a template and download it. if the template size is X, then the secondarystoragetotal for the account shows it as 2X. Desired value is X. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6575) Deploy VM failed with NPE while using custom compute offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992500#comment-13992500
]
Saksham Srivastava commented on CLOUDSTACK-6575:
Available for review at: https://reviews.apache.org/r/21156/
Deploy VM failed with NPE while using custom compute offering
--
Key: CLOUDSTACK-6575
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6575
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.4.0
Attachments: logs.zip
Steps:
1. Install and configure Adv zone using Xen 6.2.5 Hypervisor
2. Create Compute offering with Custom option enabled
3. Deploy VM using Default Cent OS template using Customer option enabled
Compute offering with CPU=1, Memory=2000 , Speed = 500
Observation:
Deploy VM failed with NPE while using custom compute offering
API call:
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to service offering:13 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to disk offering:4 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,335 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,373 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Ntwk[91973ed0-97f6-47bf-94ea-25751da81ae9|Guest|8]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,412 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,437 ERROR [c.c.a.ApiServer]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) unhandled exception executing
api command: [Ljava.lang.String;@763f4779
java.lang.NullPointerException
at
[jira] [Updated] (CLOUDSTACK-6575) Deploy VM failed with NPE while using custom compute offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-6575:
---
Assignee: Saksham Srivastava
Deploy VM failed with NPE while using custom compute offering
--
Key: CLOUDSTACK-6575
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6575
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Assignee: Saksham Srivastava
Priority: Critical
Fix For: 4.4.0
Attachments: logs.zip
Steps:
1. Install and configure Adv zone using Xen 6.2.5 Hypervisor
2. Create Compute offering with Custom option enabled
3. Deploy VM using Default Cent OS template using Customer option enabled
Compute offering with CPU=1, Memory=2000 , Speed = 500
Observation:
Deploy VM failed with NPE while using custom compute offering
API call:
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to service offering:13 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to disk offering:4 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,335 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,373 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Ntwk[91973ed0-97f6-47bf-94ea-25751da81ae9|Guest|8]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,412 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,437 ERROR [c.c.a.ApiServer]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) unhandled exception executing
api command: [Ljava.lang.String;@763f4779
java.lang.NullPointerException
at
com.cloud.service.ServiceOfferingVO.init(ServiceOfferingVO.java:167)
at
[jira] [Commented] (CLOUDSTACK-6575) Deploy VM failed with NPE while using custom compute offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992552#comment-13992552
]
ASF subversion and git services commented on CLOUDSTACK-6575:
-
Commit b8adb96ae1d1ce0066ce8c937fa0e15434c4acc4 in cloudstack's branch
refs/heads/master from [~saksham]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b8adb96 ]
CLOUDSTACK-6575: Deploy VM failed with NPE while using custom compute offering
Deploy VM failed with NPE while using custom compute offering
--
Key: CLOUDSTACK-6575
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6575
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.4.0
Attachments: logs.zip
Steps:
1. Install and configure Adv zone using Xen 6.2.5 Hypervisor
2. Create Compute offering with Custom option enabled
3. Deploy VM using Default Cent OS template using Customer option enabled
Compute offering with CPU=1, Memory=2000 , Speed = 500
Observation:
Deploy VM failed with NPE while using custom compute offering
API call:
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to service offering:13 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to disk offering:4 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,335 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,373 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Ntwk[91973ed0-97f6-47bf-94ea-25751da81ae9|Guest|8]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,412 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,437 ERROR
[jira] [Updated] (CLOUDSTACK-5485) Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5485: --- Assignee: Kelven Yang Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time. --- Key: CLOUDSTACK-5485 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5485 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: Build from 4.3 Reporter: Sangeetha Hariharan Assignee: Kelven Yang Priority: Critical Fix For: 4.4.0 Attachments: vmware.rar Vmware - When 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time. Set up : Advanced Zone with 2 5.1 ESXI hosts. Steps to reproduce the problem: 1. Deploy 5 Vms in each of the hosts , so we start with 10 Vms. 2. Start concurrent snapshots for ROOT volumes of all the Vms. Noticed that on the Vsphere client , only 5 of these snapshots gets executed in parallel.Rest of them get picked up when the current snapshot jobs complete. Why cant we do more than 5 parallel tasks ? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6608) OVS distributed firewall: default ACL rule is not getting applied when a tier in VPC is created.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992662#comment-13992662 ] ASF subversion and git services commented on CLOUDSTACK-6608: - Commit 2a175a2b02aa39e2fccaabdb263e8eb45078ec33 in cloudstack's branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2a175a2 ] CLOUDSTACK-6608:OVS distributed firewall: default ACL rule is not getting applied when a tier in VPC is created. fix ensures, VpcRoutingPolicyUpdate is send when network rules are programmed when network tier in VPC is created OVS distributed firewall: default ACL rule is not getting applied when a tier in VPC is created. Key: CLOUDSTACK-6608 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6608 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.4.0 OVS distributed firewall: default ACL rule is not getting applied when a tier in VPC is created. Current logic in OVS tunnel manager is updating ACL table on the host only when ACL is replace, but not for the default ACL that gets applied when network is created. Fix should ensure OvsVpcRoutingPolicyConfigCommand update is send to the hosts on which VPC spans when tier is created. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6607) Create VPC is failing.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996190#comment-13996190
]
ASF subversion and git services commented on CLOUDSTACK-6607:
-
Commit 169c2be11acfe3af86f8e1f8061f24846cc34e47 in cloudstack's branch
refs/heads/4.4 from [~yasker]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=169c2be ]
CLOUDSTACK-6607: Correct the result of VpcNetworkUsage
Blank or not shouldn't be used to indicate command is failure or not.
Create VPC is failing.
--
Key: CLOUDSTACK-6607
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6607
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.4.0
Reporter: manasaveloori
Assignee: Sheng Yang
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.log
Deploy CS using Xenserver 6.2.
Create a VPC.
Observed that VPC creation is failing with below exception:
2014-05-08 04:29:48,225 WARN [c.c.h.x.r.XenServer56Resource]
(DirectAgent-95:ctx-70fed5e6) Failed to get network usage stats due to
java.lang.Exception: vpc network usage plugin call failed
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.VPCNetworkUsage(XenServer56Resource.java:183)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.execute(XenServer56Resource.java:194)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:58)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93)
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-05-08 04:29:48,229 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-95:ctx-70fed5e6) Seq 1-126100789566377982: Response Received:
2014-05-08 04:29:48,231 DEBUG [c.c.a.t.Request] (DirectAgent-95:ctx-70fed5e6)
Seq 1-126100789566377982: Processing: { Ans: , MgmtId: 7672522866886, via:
1, Ver: v1, Flags: 110,
[{com.cloud.agent.api.StartAnswer:{vm:{id:10,name:r-10-VM,bootloader:PyGrub,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,arch:x86_64,os:Debian
GNU/Linux 7(32-bit),bootArgs: vpccidr=10.0.0.0/16
domain=cs2cloud.internal dns1=10.140.50.6 template=domP name=r-10-VM
eth0ip=169.254.1.131 eth0mask=255.255.0.0 type=vpcrouter
[jira] [Updated] (CLOUDSTACK-6617) [Automation] detach / resize volume test cases failing with permission error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6617:
Description:
This issue is observed in 4.4-forward automation in Xen, test case
integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume
failing with permission error
integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
Execute cmd: attachvolume failed, due to: errorCode: 531,
errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
begin captured stdout -
=== TestName: test_06_download_detached_volume | Status : EXCEPTION ===
- end captured stdout --
begin captured logging
test_06_download_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: STARTED : TC: test_06_download_detached_volume :::
test_06_download_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Extract detached Volume ID: 885ac921-4728-4903-9621-b07c5353e9bc
test_06_download_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Payload: {'apiKey':
u'WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ',
'virtualmachineid': u'2e1ef913-b207-4688-bbaa-408797810d3a', 'id':
u'885ac921-4728-4903-9621-b07c5353e9bc', 'command': 'attachVolume',
'signature': 'hnLR1wCmFp5EtwMZRaS1e3J75S8=', 'response': 'json'}
test_06_download_detached_volume (integration.smoke.test_volumes.TestVolumes):
DEBUG: Sending GET Cmd : attachVolume===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.76.63
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQvirtualmachineid=2e1ef913-b207-4688-bbaa-408797810d3aid=885ac921-4728-4903-9621-b07c5353e9bccommand=attachVolumesignature=hnLR1wCmFp5EtwMZRaS1e3J75S8%3Dresponse=json
HTTP/1.1 531 212
test_06_download_detached_volume (integration.smoke.test_volumes.TestVolumes):
ERROR: Exception:['Traceback (most recent call last):\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse\nresponse_cls)\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj\nraise
cloudstackException.CloudstackAPIException(respname, errMsg)\n',
'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources\n']
Traceback (most recent call last):
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse
response_cls)
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj
raise cloudstackException.CloudstackAPIException(respname, errMsg)
CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
test_06_download_detached_volume (integration.smoke.test_volumes.TestVolumes):
ERROR: marvinRequest : CmdName:
marvin.cloudstackAPI.attachVolume.attachVolumeCmd object at 0x36ccf90
Exception: ['Traceback (most recent call last):\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 380, in marvinRequest\nraise self.__lastError\n',
'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources\n']
Traceback (most recent call last):
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 380, in marvinRequest
raise self.__lastError
CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
test_06_download_detached_volume (integration.smoke.test_volumes.TestVolumes):
CRITICAL: EXCEPTION: test_06_download_detached_volume: ['Traceback (most recent
call last):\n', ' File /usr/lib/python2.7/unittest/case.py, line 332, in
run\ntestMethod()\n', '
[jira] [Updated] (CLOUDSTACK-6576) No Error Handling while deploying GPU unsupported instances on a GPU enabled host (Ex: Cent OS instance)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-6576:
---
Assignee: Saksham Srivastava
No Error Handling while deploying GPU unsupported instances on a GPU enabled
host (Ex: Cent OS instance)
Key: CLOUDSTACK-6576
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6576
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Assignee: Saksham Srivastava
Priority: Minor
Fix For: 4.4.0
Attachments: logs1.zip
Steps:
1. Install and configure Adv zone with GPU enabled XenServer 6.2.5
2. Try to deploy default Cent OS instance using GPU enabled offering( K2 -
200 profile)
Observation:
1. Xenserver does not support vGPU with Linux instances.
2. Cloudstack throws deployment failure after throwing lot of exceptions by
XenServer.
Expected Results:
CloudStack should parse the failure provided by XS and provide proper
deployment failure as unsupported deployment.
2014-05-05 16:38:50,730 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Sending { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:1439f05b06e154d2,params:{},uuid:00069b3f-abf0-4f0d-a12c-6ae9d1a3ea81,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:e92dcd30-3775-4762-bb83-b6c9d901644b,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:e8ccf63a-577b-3378-9741-16ce76631992,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/goletagpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/goletagpups1/?ROLE=PrimarySTOREUUID=e8ccf63a-577b-3378-9741-16ce76631992}},name:ROOT-9,size:21474836480,path:8d273d72-877c-4776-b4b5-9e52072ea45f,volumeId:11,vmName:i-3-9-VM,accountId:3,format:VHD,id:11,deviceId:0,hypervisorType:XenServer}},diskSeq:0,path:8d273d72-877c-4776-b4b5-9e52072ea45f,type:ROOT,_details:{managed:false,storagePort:2049,storageHost:10.102.192.101,volumeSize:21474836480}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:91973ed0-97f6-47bf-94ea-25751da81ae9,ip:10.1.1.220,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:03:4b:00:07,dns1:10.140.50.5,broadcastType:Vlan,type:Guest,broadcastUri:vlan://770,isolationUri:vlan://770,isSecurityGroupEnabled:false}],gpuDevice:{gpuGroup:Group
of NVIDIA Corporation GK104GL [GRID K2] GPUs,vgpuType:GRID
K200}},hostIp:10.102.192.66,executeInSequence:false,wait:0}}] }
2014-05-05 16:38:50,732 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
[jira] [Assigned] (CLOUDSTACK-6617) [Automation] detach / resize volume test cases failing with permission error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Min Chen reassigned CLOUDSTACK-6617:
Assignee: Min Chen
[Automation] detach / resize volume test cases failing with permission error
--
Key: CLOUDSTACK-6617
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6617
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes, Xen
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Min Chen
Fix For: 4.4.0
Attachments: management-server.log
This issue is observed in 4.4-forward automation in Xen, test case
integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume
failing with permission error
integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
Execute cmd: attachvolume failed, due to: errorCode: 531,
errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
begin captured stdout -
=== TestName: test_06_download_detached_volume | Status : EXCEPTION ===
- end captured stdout --
begin captured logging
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: STARTED :
TC: test_06_download_detached_volume :::
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Extract detached Volume
ID: 885ac921-4728-4903-9621-b07c5353e9bc
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Payload: {'apiKey':
u'WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ',
'virtualmachineid': u'2e1ef913-b207-4688-bbaa-408797810d3a', 'id':
u'885ac921-4728-4903-9621-b07c5353e9bc', 'command': 'attachVolume',
'signature': 'hnLR1wCmFp5EtwMZRaS1e3J75S8=', 'response': 'json'}
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): DEBUG: Sending GET Cmd
: attachVolume===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.76.63
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQvirtualmachineid=2e1ef913-b207-4688-bbaa-408797810d3aid=885ac921-4728-4903-9621-b07c5353e9bccommand=attachVolumesignature=hnLR1wCmFp5EtwMZRaS1e3J75S8%3Dresponse=json
HTTP/1.1 531 212
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): ERROR: Exception:['Traceback
(most recent call last):\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse\nresponse_cls)\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj\nraise
cloudstackException.CloudstackAPIException(respname, errMsg)\n',
'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources\n']
Traceback (most recent call last):
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 313, in __parseAndGetResponse
response_cls)
File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
line 151, in getResultObj
raise cloudstackException.CloudstackAPIException(respname, errMsg)
CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources
test_06_download_detached_volume
(integration.smoke.test_volumes.TestVolumes): ERROR: marvinRequest : CmdName:
marvin.cloudstackAPI.attachVolume.attachVolumeCmd object at 0x36ccf90
Exception: ['Traceback (most recent call last):\n', ' File
/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 380, in marvinRequest\nraise self.__lastError\n',
'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode:
531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have
permission to perform this operation on these resources\n']
Traceback
[jira] [Resolved] (CLOUDSTACK-6611) [Automation] Dynamic_compute_offering :DeployVM Failed with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-6611. - Resolution: Fixed Deployvm is working fine now. NPE got fixed with Commit 3943e0ba1c6fc343ac928980bb7309c7256b4e8e in cloudstack's branch refs/heads/4.4 [Automation] Dynamic_compute_offering :DeployVM Failed with NPE Key: CLOUDSTACK-6611 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6611 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Affects Versions: 4.4.0 Environment: KVM (RHEL 6.3) Build 4.4-forward Reporter: Rayees Namathponnan Assignee: Bharat Kumar Priority: Blocker Fix For: 4.4.0 Dynamic compute offering test case integration.component.test_dynamic_compute_offering.TestAccountLimits.test_max_account_cpus_scale_VM_1_ADMIN_ACCOUNT 2014-05-07 16:58:04,108 DEBUG [c.c.n.g.GuestNetworkGuru] (catalina-exec-12:ctx-71d3090d ctx-a9cdac4c ctx-5b2113e8) Empty physical isolation type for physical network 38e39e12-7458-451b-b408-07a0243c6590 2014-05-07 16:58:04,110 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-12:ctx-71d3090d ctx-a9cdac4c ctx-5b2113e8) Releasing lock for Acct[a1b7e396-44ab -4f03-bd62-a292770aa3a0-test-account-TestScaleVmDynamicServiceOffering-test_max_account_cpus_scale_VM_1_ADMIN_ACCOUNT-WCTVP] 2014-05-07 16:58:04,148 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-12:ctx-71d3090d ctx-a9cdac4c ctx-5b2113e8) Root Access granted to Acct[b1d58e04-d616- 11e3-a7c8-1a6f7bb0d0a8-admin] by RoleBasedEntityAccessChecker 2014-05-07 16:58:04,209 ERROR [c.c.a.ApiServer] (catalina-exec-12:ctx-71d3090d ctx-a9cdac4c ctx-5b2113e8) unhandled exception executing api command: [Ljava.l ang.String;@50561a0c java.lang.NullPointerException at com.cloud.service.ServiceOfferingVO.init(ServiceOfferingVO.java:167) at com.cloud.service.dao.ServiceOfferingDaoImpl.getcomputeOffering(ServiceOfferingDaoImpl.java:227) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy58.getcomputeOffering(Unknown Source) at com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:2576) at com.cloud.vm.UserVmManagerImpl.createAdvancedVirtualMachine(UserVmManagerImpl.java:2520) at sun.reflect.GeneratedMethodAccessor473.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.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
