[jira] [Commented] (CLOUDSTACK-6699) listResouceDetails - enhance it to list by (key,value) pair
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001411#comment-14001411 ] ASF subversion and git services commented on CLOUDSTACK-6699: - Commit d5425e1a4a8ed4cadc2f9b97f82f6f608e9a51de in cloudstack's branch refs/heads/4.4-forward from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d5425e1 ] CLOUDSTACK-6699: listResouceDetails - enhance it to list by (key,value) pair - allowed to Admin only. listResouceDetails - enhance it to list by (key,value) pair --- Key: CLOUDSTACK-6699 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6699 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta listResouceDetails - enhance it to list by (key,value) pair. Currently allowing this to only Admin user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6699) listResouceDetails - enhance it to list by (key,value) pair
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001412#comment-14001412 ] ASF subversion and git services commented on CLOUDSTACK-6699: - Commit 667c8e7905a9c7b5c261969c55b71066125740eb in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=667c8e7 ] CLOUDSTACK-6699: listResouceDetails - enhance it to list by (key,value) pair - allowed to Admin only. listResouceDetails - enhance it to list by (key,value) pair --- Key: CLOUDSTACK-6699 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6699 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta listResouceDetails - enhance it to list by (key,value) pair. Currently allowing this to only Admin user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001323#comment-14001323
]
Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/19/14 7:05 AM:
---
Thank you for your support.
I have three zones. I tested on each zone with Small Disk, 5GB disk offering ,
but the same results.
Additional info; when I create an instance(ROOT DISK) and a volume(DATA DISK)
simultaneously, the volume(DATA DISK) is created correctly. And I can attach
and detach the volume to any instance.
was (Author: itokaz):
Thank you for your support.
I have three zones. I tested on each zone with Small Disk, 5GB disk offering ,
but the same results.
unable to attach new Volume to VM
-
Key: CLOUDSTACK-6631
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.1
Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
Reporter: Kazuhiro Ito
1. I added new volume.
2. I tried to attach the volume to a VM on UI.
3. It failed and the following log appeared.
2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
(http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
command=attachVolumeid=ac7099fb-ac66-4c63-bf1e-ed0e1429f412virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74response=jsonsessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D_=1399861774316
2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
(http-6443-exec-116:null) submit async job-4916 = [
dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:ac7099fb-ac66-4c63-bf1e-ed0e1429f412,sessionkey:TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d,cmdEventType:VOLUME.ATTACH,ctxUserId:3,virtualMachineId:ecdc2c1d-e21e-4c04-962a-4efac1a69a74,httpmethod:GET,_:1399861774316,ctxAccountId:3,ctxStartEventId:34276},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
(http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
command=attachVolumeid=ac7099fb-ac66-4c63-bf1e-ed0e1429f412virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74response=jsonsessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D_=1399861774316
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to VM[User|TEST-A2-VM01] granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
LocalStoragePoolAllocator trying to find storage pool to fit the vm
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
ClusterScopeStoragePoolAllocator looking for storage pool
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
2014-05-12 11:29:47,216 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
storage pools available for shared volume allocation, returning
2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
SUM(IF(vol.state='Ready' AND
[jira] [Commented] (CLOUDSTACK-6687) [Automation] test_ip_reservation.py test cases are failing with 'TestFailureScnarios' object has no attribute 'isolated_persistent_network'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001475#comment-14001475
]
ASF subversion and git services commented on CLOUDSTACK-6687:
-
Commit de9909403eaaa01d5b6fb6df631aceb4651a5422 in cloudstack's branch
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=de99094 ]
CLOUDSTACK-6687: Fixed IP reservation test case failures with code re-factoring
[Automation] test_ip_reservation.py test cases are failing with
'TestFailureScnarios' object has no attribute 'isolated_persistent_network'
-
Key: CLOUDSTACK-6687
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6687
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Environment: All hypervisors
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
Labels: automation
Fix For: 4.4.0
'TestFailureScnarios' object has no attribute 'isolated_persistent_network'
begin captured stdout -
=== TestName: test_reservation_after_router_restart | Status : EXCEPTION ===
- end captured stdout --
begin captured logging
test_reservation_after_router_restart
(integration.component.test_ip_reservation.TestFailureScnarios): DEBUG:
STARTED : TC: test_reservation_after_router_restart :::
test_reservation_after_router_restart
(integration.component.test_ip_reservation.TestFailureScnarios): DEBUG:
Payload: {'username':
'test-account-TestUpdateIPReservation-test_reservation_after_router_restart-U4445S',
'domainid': u'4ae80f5a-d616-11e3-a7c8-1a6f7bb0d0a8', 'firstname': 'test',
'lastname': 'test', 'response': 'json', 'apiKey':
u'TKG3-LFUFTPhT_OQ9MPrEdI_UpDMgvR07w8NZCUhWlsIKeSPIrnKBNcn0UgWIPIQLhwcTYMD5jyVpJ7oMdc9GA',
'command': 'createAccount', 'accounttype': 0, 'signature':
'oH50KwLjbHRHq4rd4RAuZlte0Oo=', 'password': 'password', 'email':
'test-acco...@test.com'}
test_reservation_after_router_restart
(integration.component.test_ip_reservation.TestFailureScnarios): DEBUG:
Sending GET Cmd : createAccount===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.49.195
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?username=test-account-TestUpdateIPReservation-test_reservation_after_router_restart-U4445Sdomainid=4ae80f5a-d616-11e3-a7c8-1a6f7bb0d0a8firstname=testlastname=testresponse=jsonapiKey=TKG3-LFUFTPhT_OQ9MPrEdI_UpDMgvR07w8NZCUhWlsIKeSPIrnKBNcn0UgWIPIQLhwcTYMD5jyVpJ7oMdc9GAcommand=createAccountaccounttype=0signature=oH50KwLjbHRHq4rd4RAuZlte0Oo%3Dpassword=passwordemail=test-account%40test.com
HTTP/1.1 200 1812
test_reservation_after_router_restart
(integration.component.test_ip_reservation.TestFailureScnarios): DEBUG:
Response : {primarystorageavailable : u'Unlimited', domain : u'ROOT',
domainid : u'4ae80f5a-d616-11e3-a7c8-1a6f7bb0d0a8', vpclimit : u'Unlimited',
iplimit : u'Unlimited', volumelimit : u'Unlimited', memorytotal : 0,
secondarystorageavailable : u'Unlimited', vmtotal : 0, cputotal : 0, vpctotal
: 0, id : u'7836228d-2283-4bed-ae30-2511bfe37302', cpuavailable :
u'Unlimited', snapshotlimit : u'Unlimited', networklimit : u'Unlimited',
iptotal : 0, volumetotal : 0, projectlimit : u'Unlimited', state :
u'enabled', networktotal : 0, accounttype : 0, networkavailable :
u'Unlimited', primarystoragetotal : 0, templatelimit : u'Unlimited',
snapshottotal : 0, templateavailable : u'Unlimited', vmlimit : u'Unlimited',
vpcavailable : u'Unlimited', memoryavailable : u'Unlimited',
secondarystoragetotal : 0, templatetotal : 0, projecttotal : 0, user :
[{username :
u'test-account-TestUpdateIPReservation-test_reservation_after_router_restart-U4445S',
account :
u'test-account-TestUpdateIPReservation-test_reservation_after_router_restart-U4445S',
domainid : u'4ae80f5a-d616-11e3-a7c8-1a6f7bb0d0a8', firstname : u'test',
created : u'2014-05-07T19:22:49-0700', lastname : u'test', domain : u'ROOT',
id : u'3287f1f5-b3ca-4264-a578-b4a5f7a09fc9', iscallerchilddomain : False,
state : u'enabled', accounttype : 0, email : u'test-acco...@test.com',
isdefault : False, accountid : u'7836228d-2283-4bed-ae30-2511bfe37302'}],
groups : [u'NORMAL', u'DomainGrp-4ae80f5a-d616-11e3-a7c8-1a6f7bb0d0a8'],
projectavailable : u'Unlimited', isdefault : False, primarystoragelimit :
u'Unlimited', secondarystoragelimit :
[jira] [Commented] (CLOUDSTACK-6672) [Automation] NPE observed while listing system vms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001512#comment-14001512 ] ASF subversion and git services commented on CLOUDSTACK-6672: - Commit 840938504b9ed5931785070c70234d36b5ed577e in cloudstack's branch refs/heads/4.4 from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8409385 ] CLOUDSTACK-6672: [Automation] NPE observed while listing system vms fixing NPE [Automation] NPE observed while listing system vms -- Key: CLOUDSTACK-6672 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6672 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.4.0 Environment: EIP/ELB Reporter: Rayees Namathponnan Assignee: Murali Reddy Fix For: 4.4.0 Attachments: management-server.rar This issue is observed in EIP/ELB setup Steps to reproduce 1) Create EIP/ELB setup 2) delete ssvm 3) while creating new SSVM, call list system vm API. listsystem vm api returns NPE 2014-05-14 07:45:53,227 DEBUG [c.c.a.ApiServlet] (catalina-exec-14:ctx-3a43fc0b) ===START=== 10.216.51.142 -- GET command=listSystemsresponse=jsonsessionkey=xiNXdhTMhQghYSan%2Bsj60Au015s%3DlistAll=truepage=1pagesize=1_=1400079830040 2014-05-14 07:45:53,236 WARN [c.c.a.d.ParamGenericValidationWorker] (catalina-exec-14:ctx-3a43fc0b ctx-0ec73e61) Received unknown pameters for command listSystemVms. Unknown parameters : listall 2014-05-14 07:45:53,237 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] (catalina-exec-14:ctx-3a43fc0b ctx-0ec73e61) IAM access check fo2-null-null-DomainResourceCapability from cache: false 2014-05-14 07:45:53,265 ERROR [c.c.a.ApiServer] (catalina-exec-14:ctx-3a43fc0b ctx-0ec73e61) unhandled exception executing api comman [Ljava.lang.String;@2329f184 java.lang.NullPointerException at com.cloud.api.ApiResponseHelper.createSystemVmResponse(ApiResponseHelper.java:1210) at org.apache.cloudstack.api.command.admin.systemvm.ListSystemVMsCmd.execute(ListSystemVMsCmd.java:136) 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.doGet(ApiServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) 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-14 07:45:53,267 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
[jira] [Assigned] (CLOUDSTACK-6624) Unable to create new Network Offerings via UI with Specify VLAN option set
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Hitchins reassigned CLOUDSTACK-6624: - Assignee: Alex Hitchins Unable to create new Network Offerings via UI with Specify VLAN option set -- Key: CLOUDSTACK-6624 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6624 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Geoff Higgibottom Assignee: Alex Hitchins Priority: Critical Labels: UI When creating a new network offering with the Specify VLAN option set, the Specify IP Option should also be set automatically. The UI is no longer sending this parameter in the API string so the Network Offering has an invalid configuration. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6705) [SDN] VNI range is not allowing more than 2147483647 as a maximum vnet range
Sanjeev N created CLOUDSTACK-6705: - Summary: [SDN] VNI range is not allowing more than 2147483647 as a maximum vnet range Key: CLOUDSTACK-6705 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6705 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Network Controller Affects Versions: 4.4.0 Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Fix For: 4.4.0 [SDN] VNI range is not allowing more than 2147483647 as a maximum vnet range 1.Bring up CS in advanced zone 2.Create physical network with GRE isolation 3.In guest network creation give vnet/vni range as 1-4294967295 Result: == Failed to add above vnet range. 2014-05-19 10:37:40,383 WARN [c.c.n.NetworkServiceImpl] (API-Job-Executor-27:job-31 ctx-ff496cfb) Unable to parse vnet range: java.lang.NumberFormatException: For input string: 4294967100 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:495) at java.lang.Integer.parseInt(Integer.java:527) at com.cloud.network.NetworkServiceImpl.validateVlanRange(NetworkServiceImpl.java:2749) at com.cloud.network.NetworkServiceImpl.addOrRemoveVnets(NetworkServiceImpl.java:2640) at com.cloud.network.NetworkServiceImpl.updatePhysicalNetwork(NetworkServiceImpl.java:2622) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at 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.$Proxy154.updatePhysicalNetwork(Unknown Source) at org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd.execute(UpdatePhysicalNetworkCmd.java:99) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:119) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453) at java.util.concurrent.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-19 10:37:40,394 ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-27:job-31) Unexpected exception while executing org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd com.cloud.exception.InvalidParameterValueException: Please provide valid vnet range. The vnet range should be a coma seperated list example 2001-2012,3000-3005. between 0 and 4294967295 at com.cloud.network.NetworkServiceImpl.validateVlanRange(NetworkServiceImpl.java:2753) at
[jira] [Created] (CLOUDSTACK-6706) Not able to update network offering because :Invalid network domain. Total length shouldn't exceed 190 chars. Each domain label must be between 1 and 63 characters..
prashant kumar mishra created CLOUDSTACK-6706:
-
Summary: Not able to update network offering because :Invalid
network domain. Total length shouldn't exceed 190 chars. Each domain label must
be between 1 and 63 characters...
Key: CLOUDSTACK-6706
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6706
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: prashant kumar mishra
Priority: Critical
Fix For: 4.4.0
steps to reproduce
===
1-prepare a CS setup and create a network offering and create a network(without
any network domain)
2-deploy a vm using network created in step 1
3-try to update network to new new network offering
Exception:
2014-05-19 05:41:19,915 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-21:ctx-2ea42397 ctx-c0d5d6b7) submit async job-175, details:
AsyncJobVO {id:175, userId: 2, accountId: 2, instanceType: None, instanceId:
null, cmd:
org.apache.cloudstack.api.command.admin.network.UpdateNetworkCmdByAdmin,
cmdInfo:
{changecidr:false,sessionkey:hQuvq/8XCHOm2Yt5N5gPNmpB4HQ\u003d,cmdEventType:NETWORK.UPDATE,ctxUserId:2,networkdomain:,networkofferingid:a8e65b9d-de21-46a3-9976-8fed23a4369e,httpmethod:GET,id:9a303408-5c88-4879-8fdd-8205eb540d2b,response:json,ctxDetails:{\Network\:\9a303408-5c88-4879-8fdd-8205eb540d2b\,\com.cloud.offering.NetworkOffering\:19,\com.cloud.network.Network\:213},name:newtest2,displaytext:newtest2,_:1400492460588,uuid:9a303408-5c88-4879-8fdd-8205eb540d2b,ctxAccountId:2,ctxStartEventId:387},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7672522866886, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-19 05:41:19,916 DEBUG [c.c.a.ApiServlet] (catalina-exec-21:ctx-2ea42397
ctx-c0d5d6b7) ===END=== 10.252.192.60 -- GET
command=updateNetworkresponse=jsonsessionkey=hQuvq%2F8XCHOm2Yt5N5gPNmpB4HQ%3Did=9a303408-5c88-4879-8fdd-8205eb540d2bname=newtest2displaytext=newtest2networkdomain=networkofferingid=a8e65b9d-de21-46a3-9976-8fed23a4369echangecidr=false_=1400492460588
2014-05-19 05:41:19,917 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-13:job-175) Add job-175 into job monitoring
2014-05-19 05:41:19,917 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-13:job-175) Executing AsyncJobVO {id:175, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.network.UpdateNetworkCmdByAdmin,
cmdInfo:
{changecidr:false,sessionkey:hQuvq/8XCHOm2Yt5N5gPNmpB4HQ\u003d,cmdEventType:NETWORK.UPDATE,ctxUserId:2,networkdomain:,networkofferingid:a8e65b9d-de21-46a3-9976-8fed23a4369e,httpmethod:GET,id:9a303408-5c88-4879-8fdd-8205eb540d2b,response:json,ctxDetails:{\Network\:\9a303408-5c88-4879-8fdd-8205eb540d2b\,\com.cloud.offering.NetworkOffering\:19,\com.cloud.network.Network\:213},name:newtest2,displaytext:newtest2,_:1400492460588,uuid:9a303408-5c88-4879-8fdd-8205eb540d2b,ctxAccountId:2,ctxStartEventId:387},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7672522866886, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-19 05:41:19,925 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-null-null-SystemCapability from cache: true
2014-05-19 05:41:19,925 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-13:job-175 ctx-7943d027) Root Access granted to
Acct[66c18f4a-da84-11e3-a5a0-06fa66c6-admin] by RoleBasedEntityAccessChecker
2014-05-19 05:41:19,926 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-null-null-DomainCapability from cache: false
2014-05-19 05:41:19,927 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-null-null-DomainResourceCapability from cache: false
2014-05-19 05:41:19,927 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-Network213-OperateEntry-updateNetwork from cache: true
2014-05-19 05:41:19,927 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-13:job-175 ctx-7943d027) Access to
{Ntwk[9a303408-5c88-4879-8fdd-8205eb540d2b|Guest|18]} granted to
Acct[66c18f4a-da84-11e3-a5a0-06fa66c6-admin] by RoleBasedEntityAccessChecker
2014-05-19 05:41:19,927 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-13:job-175 ctx-7943d027) Received unknown parameters for
command updateNetwork. Unknown parameters : ctxdetails
2014-05-19 05:41:19,940 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
[jira] [Updated] (CLOUDSTACK-6706) Not able to update network offering because :Invalid network domain. Total length shouldn't exceed 190 chars. Each domain label must be between 1 and 63 characters..
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-6706:
--
Attachment: db_Log.rar
Not able to update network offering because :Invalid network domain. Total
length shouldn't exceed 190 chars. Each domain label must be between 1 and 63
characters...
--
Key: CLOUDSTACK-6706
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6706
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: prashant kumar mishra
Priority: Critical
Fix For: 4.4.0
Attachments: db_Log.rar
steps to reproduce
===
1-prepare a CS setup and create a network offering and create a
network(without any network domain)
2-deploy a vm using network created in step 1
3-try to update network to new new network offering
Exception:
2014-05-19 05:41:19,915 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-21:ctx-2ea42397 ctx-c0d5d6b7) submit async job-175, details:
AsyncJobVO {id:175, userId: 2, accountId: 2, instanceType: None, instanceId:
null, cmd:
org.apache.cloudstack.api.command.admin.network.UpdateNetworkCmdByAdmin,
cmdInfo:
{changecidr:false,sessionkey:hQuvq/8XCHOm2Yt5N5gPNmpB4HQ\u003d,cmdEventType:NETWORK.UPDATE,ctxUserId:2,networkdomain:,networkofferingid:a8e65b9d-de21-46a3-9976-8fed23a4369e,httpmethod:GET,id:9a303408-5c88-4879-8fdd-8205eb540d2b,response:json,ctxDetails:{\Network\:\9a303408-5c88-4879-8fdd-8205eb540d2b\,\com.cloud.offering.NetworkOffering\:19,\com.cloud.network.Network\:213},name:newtest2,displaytext:newtest2,_:1400492460588,uuid:9a303408-5c88-4879-8fdd-8205eb540d2b,ctxAccountId:2,ctxStartEventId:387},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7672522866886, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-19 05:41:19,916 DEBUG [c.c.a.ApiServlet]
(catalina-exec-21:ctx-2ea42397 ctx-c0d5d6b7) ===END=== 10.252.192.60 -- GET
command=updateNetworkresponse=jsonsessionkey=hQuvq%2F8XCHOm2Yt5N5gPNmpB4HQ%3Did=9a303408-5c88-4879-8fdd-8205eb540d2bname=newtest2displaytext=newtest2networkdomain=networkofferingid=a8e65b9d-de21-46a3-9976-8fed23a4369echangecidr=false_=1400492460588
2014-05-19 05:41:19,917 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-13:job-175) Add job-175 into job monitoring
2014-05-19 05:41:19,917 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-13:job-175) Executing AsyncJobVO {id:175, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.network.UpdateNetworkCmdByAdmin,
cmdInfo:
{changecidr:false,sessionkey:hQuvq/8XCHOm2Yt5N5gPNmpB4HQ\u003d,cmdEventType:NETWORK.UPDATE,ctxUserId:2,networkdomain:,networkofferingid:a8e65b9d-de21-46a3-9976-8fed23a4369e,httpmethod:GET,id:9a303408-5c88-4879-8fdd-8205eb540d2b,response:json,ctxDetails:{\Network\:\9a303408-5c88-4879-8fdd-8205eb540d2b\,\com.cloud.offering.NetworkOffering\:19,\com.cloud.network.Network\:213},name:newtest2,displaytext:newtest2,_:1400492460588,uuid:9a303408-5c88-4879-8fdd-8205eb540d2b,ctxAccountId:2,ctxStartEventId:387},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7672522866886, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-19 05:41:19,925 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-null-null-SystemCapability from cache: true
2014-05-19 05:41:19,925 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-13:job-175 ctx-7943d027) Root Access granted to
Acct[66c18f4a-da84-11e3-a5a0-06fa66c6-admin] by
RoleBasedEntityAccessChecker
2014-05-19 05:41:19,926 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-null-null-DomainCapability from cache: false
2014-05-19 05:41:19,927 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-null-null-DomainResourceCapability from cache: false
2014-05-19 05:41:19,927 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-13:job-175 ctx-7943d027) IAM access check for
2-Network213-OperateEntry-updateNetwork from cache: true
2014-05-19 05:41:19,927 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-13:job-175 ctx-7943d027) Access to
{Ntwk[9a303408-5c88-4879-8fdd-8205eb540d2b|Guest|18]} granted to
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001547#comment-14001547 ] ASF subversion and git services commented on CLOUDSTACK-4757: - Commit fa0897f902dbb941bb18a0bf63fe1b182f535c86 in cloudstack's branch refs/heads/multiple-disk-ova from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fa0897f ] CLOUDSTACK-4757. More updates to Datadisk template creation - update ROOT disk OVA once all the datadisks have been created Support OVA files with multiple disks for templates --- Key: CLOUDSTACK-4757 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4757 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.3.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.4.0 CloudStack volumes and templates are one single virtual disk in case of XenServer/XCP and KVM hypervisors since the files used for templates and volumes are virtual disks (VHD, QCOW2). However, VMware volumes and templates are in OVA format, which are archives that can contain a complete VM including multiple VMDKs and other files such as ISOs. And currently, Cloudstack only supports Template creation based on OVA files containing a single disk. If a user creates a template from a OVA file containing more than 1 disk and launches an instance using this template, only the first disk is attached to the new instance and other disks are ignored. Similarly with uploaded volumes, attaching an uploaded volume that contains multiple disks to a VM will result in only one VMDK to being attached to the VM. This behavior needs to be improved in VMWare to support OVA files with multiple disks for both uploaded volumes and templates. i.e. If a user creates a template from a OVA file containing more than 1 disk and launches an instance using this template, the first disk should be attached to the new instance as the ROOT disk and volumes should be created based on other VMDK disks in the OVA file and should be attached to the instance. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6636) [Windows] Can not create Template from ROOT snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T reassigned CLOUDSTACK-6636: --- Assignee: Damodar Reddy T [Windows] Can not create Template from ROOT snapshot Key: CLOUDSTACK-6636 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6636 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Steps to reproduce the issue 1. Create a snapshot from ROOT disk 2. Goto the above created snapshot 3. Try to create template out of it. It is failing with the following trace. 014-05-12 04:02:01,813 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-428:ctx-2ece4baa) null due to Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd java.net.URISyntaxException: Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.createVolumeFromSnapshot(XenServerStorageProcessor.java:1617) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:96) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java: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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6707) [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network
Sanjeev N created CLOUDSTACK-6707: - Summary: [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network Key: CLOUDSTACK-6707 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6707 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Network Controller Affects Versions: 4.4.0 Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Priority: Critical Fix For: 4.4.0 [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network Steps to Reproduce: 1.Bring up CS in advanced zone with two hosts in a cluster 2.Create physical network with GRE isolation 3.Create network with Connectivity service and OVS as the provider 4.Deploy couple of vms in the above network. 5.Migrate vms to one host and make sure that all the vms (including vr) are running only on one host 6.Verify tunnel ports on the host where there are no vms running Expected Result: == Tunnel ports and ovs bridge shall be deleted from the host where no vms are running Actual result: === OVS bridge and tunnel ports are still present even after migrating all the vms to another host in the cluster Observations: Following bridge info is from the host on with all system vms and guest vms are running [root@xen-host-13 ~]# ovs-vsctl list-br xapi0 xapi1 xapi2 xenbr0 xenbr1 On the host where only guest vms are running [root@xen-host-14 ~]# ovs-vsctl list-br xapi2 xenbr0 xenbr1 Before migration: == [root@xen-host-13 ~]# ovs-vsctl list-ports xapi2 t997-1-2 vif12.0 vif13.0 [root@xen-host-14 ~]# ovs-vsctl list-ports xapi2 t997-2-1 vif7.0 After migration: = [root@xen-host-13 ~]# ovs-vsctl list-ports xapi2 t997-1-2 vif12.0 vif13.0 vif15.0 [root@xen-host-13 ~]# Following is the target host on which no vms are running: [root@xen-host-14 ~]# ovs-vsctl list-br xapi2 xenbr0 xenbr1 [root@xen-host-14 ~]# ovs-vsctl list-ports xapi2 t997-2-1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6707) [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N updated CLOUDSTACK-6707: -- Attachment: ovstunnel-host14.log ovstunnel-host13.log management-server.rar Attached MS log file and ovstunnel logs from both the hosts. [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network --- Key: CLOUDSTACK-6707 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6707 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Network Controller Affects Versions: 4.4.0 Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Priority: Critical Fix For: 4.4.0 Attachments: management-server.rar, ovstunnel-host13.log, ovstunnel-host14.log [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network Steps to Reproduce: 1.Bring up CS in advanced zone with two hosts in a cluster 2.Create physical network with GRE isolation 3.Create network with Connectivity service and OVS as the provider 4.Deploy couple of vms in the above network. 5.Migrate vms to one host and make sure that all the vms (including vr) are running only on one host 6.Verify tunnel ports on the host where there are no vms running Expected Result: == Tunnel ports and ovs bridge shall be deleted from the host where no vms are running Actual result: === OVS bridge and tunnel ports are still present even after migrating all the vms to another host in the cluster Observations: Following bridge info is from the host on with all system vms and guest vms are running [root@xen-host-13 ~]# ovs-vsctl list-br xapi0 xapi1 xapi2 xenbr0 xenbr1 On the host where only guest vms are running [root@xen-host-14 ~]# ovs-vsctl list-br xapi2 xenbr0 xenbr1 Before migration: == [root@xen-host-13 ~]# ovs-vsctl list-ports xapi2 t997-1-2 vif12.0 vif13.0 [root@xen-host-14 ~]# ovs-vsctl list-ports xapi2 t997-2-1 vif7.0 After migration: = [root@xen-host-13 ~]# ovs-vsctl list-ports xapi2 t997-1-2 vif12.0 vif13.0 vif15.0 [root@xen-host-13 ~]# Following is the target host on which no vms are running: [root@xen-host-14 ~]# ovs-vsctl list-br xapi2 xenbr0 xenbr1 [root@xen-host-14 ~]# ovs-vsctl list-ports xapi2 t997-2-1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6612) [Automation] Test cases failing with db connection error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001616#comment-14001616
]
ASF subversion and git services commented on CLOUDSTACK-6612:
-
Commit f2ebfe019e1ead6172712ec804b241cf0dc5a800 in cloudstack's branch
refs/heads/4.4-forward from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f2ebfe0 ]
CLOUDSTACK-6612: Resolved issue with sshClient.py
[Automation] Test cases failing with db connection error
-
Key: CLOUDSTACK-6612
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6612
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
Fix For: 4.4.0
Test
caseintegration.component.test_egress_fw_rules.TestEgressFWRules.test_04_1_egress_fr4
(from nosetests) failed with below error
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.49.195
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?signature=ylEuPgkfrfJfwrM8fLVEn7SaBNI%3DapiKey=TKG3-LFUFTPhT_OQ9MPrEdI_UpDMgvR07w8NZCUhWlsIKeSPIrnKBNcn0UgWIPIQLhwcTYMD5jyVpJ7oMdc9GAcommand=queryAsyncJobResultresponse=jsonjobid=42c474a9-a4eb-4b5f-8ea0-e46d332e62c5
HTTP/1.1 200 621
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
Response : {jobprocstatus : 0, created : u'2014-05-07T18:10:06-0700', cmd :
u'org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd',
userid : u'b1d59b38-d616-11e3-a7c8-1a6f7bb0d0a8', jobstatus : 1, jobid :
u'42c474a9-a4eb-4b5f-8ea0-e46d332e62c5', jobresultcode : 0, jobresulttype :
u'object', jobresult : {networkid : u'72a5c1d3-4120-4139-bef9-4508268d8539',
protocol : u'icmp', fordisplay : True, cidrlist : u'10.1.1.0/24', tags : [],
icmptype : -1, state : u'Active', icmpcode : -1, id :
u'8b12a8ef-01e6-4dac-b995-1081dceffc2c'}, accountid :
u'b1d58e04-d616-11e3-a7c8-1a6f7bb0d0a8'}
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
===Jobid:42c474a9-a4eb-4b5f-8ea0-e46d332e62c5 ; StartTime:Wed May 7 14:23:16
2014 ; EndTime:Wed May 7 14:23:22 2014 ; TotalTime:-5===
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
Response : {jobprocstatus : 0, created : u'2014-05-07T18:10:06-0700', cmd :
u'org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd',
userid : u'b1d59b38-d616-11e3-a7c8-1a6f7bb0d0a8', jobstatus : 1, jobid :
u'42c474a9-a4eb-4b5f-8ea0-e46d332e62c5', jobresultcode : 0, jobresulttype :
u'object', jobresult : {networkid : u'72a5c1d3-4120-4139-bef9-4508268d8539',
protocol : u'icmp', fordisplay : True, cidrlist : u'10.1.1.0/24', tags : [],
icmptype : -1, state : u'Active', icmpcode : -1, id :
u'8b12a8ef-01e6-4dac-b995-1081dceffc2c'}, accountid :
u'b1d58e04-d616-11e3-a7c8-1a6f7bb0d0a8'}
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
Created rule=8b12a8ef-01e6-4dac-b995-1081dceffc2c
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): CRITICAL:
EXCEPTION: test_04_1_egress_fr4: ['Traceback (most recent call last):\n', '
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run\n
testMethod()\n', ' File
/Repo_30X/ipcl/cloudstack/test/integration/component/test_egress_fw_rules.py,
line 542, in test_04_1_egress_fr4\nqresultset =
self.dbclient.execute(select purpose, traffic_type from firewall_rules where
uuid=\'%s\'; % self.egressruleid)\n', ' File
/usr/local/lib/python2.7/site-packages/marvin/dbConnection.py, line 48, in
execute\ndb=str(self.database))) as conn:\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/__init__.py, line
98, in connect\nreturn MySQLConnection(*args, **kwargs)\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
118, in __init__\nself.connect(**kwargs)\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
382, in connect\nself._open_connection()\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
349, in _open_connection\nself._ssl)\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
176, in _do_auth\nraise errors.get_exception(packet)\n',
ProgrammingError: 1045 (28000): Access denied for user
'root'@'10.223.240.194' (using password: YES)\n]
- end captured
[jira] [Commented] (CLOUDSTACK-6612) [Automation] Test cases failing with db connection error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001620#comment-14001620
]
ASF subversion and git services commented on CLOUDSTACK-6612:
-
Commit 89b041a62d99d07b7c5d5b7b49bda3630f9559dd in cloudstack's branch
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=89b041a ]
CLOUDSTACK-6612: Resolved issue with sshClient.py
[Automation] Test cases failing with db connection error
-
Key: CLOUDSTACK-6612
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6612
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
Fix For: 4.4.0
Test
caseintegration.component.test_egress_fw_rules.TestEgressFWRules.test_04_1_egress_fr4
(from nosetests) failed with below error
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.49.195
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?signature=ylEuPgkfrfJfwrM8fLVEn7SaBNI%3DapiKey=TKG3-LFUFTPhT_OQ9MPrEdI_UpDMgvR07w8NZCUhWlsIKeSPIrnKBNcn0UgWIPIQLhwcTYMD5jyVpJ7oMdc9GAcommand=queryAsyncJobResultresponse=jsonjobid=42c474a9-a4eb-4b5f-8ea0-e46d332e62c5
HTTP/1.1 200 621
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
Response : {jobprocstatus : 0, created : u'2014-05-07T18:10:06-0700', cmd :
u'org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd',
userid : u'b1d59b38-d616-11e3-a7c8-1a6f7bb0d0a8', jobstatus : 1, jobid :
u'42c474a9-a4eb-4b5f-8ea0-e46d332e62c5', jobresultcode : 0, jobresulttype :
u'object', jobresult : {networkid : u'72a5c1d3-4120-4139-bef9-4508268d8539',
protocol : u'icmp', fordisplay : True, cidrlist : u'10.1.1.0/24', tags : [],
icmptype : -1, state : u'Active', icmpcode : -1, id :
u'8b12a8ef-01e6-4dac-b995-1081dceffc2c'}, accountid :
u'b1d58e04-d616-11e3-a7c8-1a6f7bb0d0a8'}
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
===Jobid:42c474a9-a4eb-4b5f-8ea0-e46d332e62c5 ; StartTime:Wed May 7 14:23:16
2014 ; EndTime:Wed May 7 14:23:22 2014 ; TotalTime:-5===
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
Response : {jobprocstatus : 0, created : u'2014-05-07T18:10:06-0700', cmd :
u'org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd',
userid : u'b1d59b38-d616-11e3-a7c8-1a6f7bb0d0a8', jobstatus : 1, jobid :
u'42c474a9-a4eb-4b5f-8ea0-e46d332e62c5', jobresultcode : 0, jobresulttype :
u'object', jobresult : {networkid : u'72a5c1d3-4120-4139-bef9-4508268d8539',
protocol : u'icmp', fordisplay : True, cidrlist : u'10.1.1.0/24', tags : [],
icmptype : -1, state : u'Active', icmpcode : -1, id :
u'8b12a8ef-01e6-4dac-b995-1081dceffc2c'}, accountid :
u'b1d58e04-d616-11e3-a7c8-1a6f7bb0d0a8'}
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): DEBUG:
Created rule=8b12a8ef-01e6-4dac-b995-1081dceffc2c
test_04_1_egress_fr4
(integration.component.test_egress_fw_rules.TestEgressFWRules): CRITICAL:
EXCEPTION: test_04_1_egress_fr4: ['Traceback (most recent call last):\n', '
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run\n
testMethod()\n', ' File
/Repo_30X/ipcl/cloudstack/test/integration/component/test_egress_fw_rules.py,
line 542, in test_04_1_egress_fr4\nqresultset =
self.dbclient.execute(select purpose, traffic_type from firewall_rules where
uuid=\'%s\'; % self.egressruleid)\n', ' File
/usr/local/lib/python2.7/site-packages/marvin/dbConnection.py, line 48, in
execute\ndb=str(self.database))) as conn:\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/__init__.py, line
98, in connect\nreturn MySQLConnection(*args, **kwargs)\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
118, in __init__\nself.connect(**kwargs)\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
382, in connect\nself._open_connection()\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
349, in _open_connection\nself._ssl)\n', ' File
/usr/local/lib/python2.7/site-packages/mysql/connector/connection.py, line
176, in _do_auth\nraise errors.get_exception(packet)\n',
ProgrammingError: 1045 (28000): Access denied for user
'root'@'10.223.240.194' (using password: YES)\n]
- end captured
[jira] [Assigned] (CLOUDSTACK-6688) [Automation] SSVM test cases failing in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye reassigned CLOUDSTACK-6688:
--
Assignee: Gaurav Aradhye (was: Sateesh Chodapuneedi)
[Automation] SSVM test cases failing in vmware
---
Key: CLOUDSTACK-6688
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6688
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: Rayees Namathponnan
Assignee: Gaurav Aradhye
Fix For: 4.4.0
Below test cases failing in vmware
integration.smoke.test_ssvm.TestSSVMs.test_03_ssvm_internals 0.477 6
integration.smoke.test_ssvm.TestSSVMs.test_04_cpvm_internals 0.495 6
integration.smoke.test_ssvm.TestSSVMs.test_05_stop_ssvm 121.115 6
integration.smoke.test_ssvm.TestSSVMs.test_06_stop_cpvm 111.028 6
integration.smoke.test_ssvm.TestSSVMs.test_07_reboot_ssvm 95.884 6
integration.smoke.test_ssvm.TestSSVMs.test_08_reboot_cpvm 95.813 6
integration.smoke.test_ssvm.TestSSVMs.test_09_destroy_ssvm211.072 6
integration.smoke.test_ssvm.TestSSVMs.test_10_destroy_cpvm211.116 6
Test cases failing with error Warning: Identity file //.ssh/id_rsa.cloud not
accessible: No such file or directory.', u'ssh: Could not resolve hostname
None: Name or service not known']}
This issue observed only in vmware
shClient: DEBUG: ===SSH to Host 10.223.250.130 port : 22 SUCCESSFUL===
paramiko.transport: DEBUG: [chan 1] Max packet in: 34816 bytes
paramiko.transport: DEBUG: [chan 1] Max packet out: 32768 bytes
paramiko.transport: INFO: Secsh channel 1 opened.
paramiko.transport: DEBUG: [chan 1] Sesch channel 1 request ok
sshClient: DEBUG: {Cmd: ssh -i ~/.ssh/id_rsa.cloud -ostricthostkeychecking=no
-oUserKnownHostsFile=/dev/null -p 3922 None
/usr/local/cloud/systemvm/ssvm-check.sh |grep -e ERROR -e WARNING -e FAIL via
Host: 10.223.250.130} {returns: [u'Warning: Identity file //.ssh/id_rsa.cloud
not accessible: No such file or directory.', u'ssh: Could not resolve
hostname None: Name or service not known']}
paramiko.transport: DEBUG: [chan 1] EOF received (1)
test_03_ssvm_internals (integration.smoke.test_ssvm.TestSSVMs): DEBUG: SSVM
script output: [u'Warning: Identity file //.ssh/id_rsa.cloud not accessible:
No such file or directory.', u'ssh: Could not resolve hostname None: Name or
service not known']
test_03_ssvm_internals (integration.smoke.test_ssvm.TestSSVMs): CRITICAL:
FAILED: test_03_ssvm_internals: ['Traceback (most recent call last):\n', '
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run\n
testMethod()\n', ' File
/data/Repo2/qa/cloudstack/test/integration/smoke/test_ssvm.py, line 352, in
test_03_ssvm_internals\nCheck for Errors in tests\n', ' File
/usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual\n
assertion_func(first, second, msg=msg)\n', ' File
/usr/local/lib/python2.7/unittest/case.py, line 487, in _baseAssertEqual\n
raise self.failureException(msg)\n', 'AssertionError: Check for Errors in
tests\n']
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
testMethod()
File /data/Repo2/qa/cloudstack/test/integration/smoke/test_ssvm.py, line
352, in test_03_ssvm_internals
Check for Errors in tests
File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual
assertion_func(first, second, msg=msg)
File /usr/local/lib/python2.7/unittest/case.py, line 487, in
_baseAssertEqual
raise self.failureException(msg)
'Check for Errors in tests\n begin captured stdout
-\n=== TestName: test_03_ssvm_internals | Status : FAILED
===\n\n\n- end captured stdout
--\n begin captured logging
\ntest_03_ssvm_internals
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6084) [Automation] Failed to create private gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001629#comment-14001629 ] Jayapal Reddy commented on CLOUDSTACK-6084: --- The commit https://issues.apache.org/jira/browse/CLOUDSTACK-6485 got reverted. So private gateway should get created now. [Automation] Failed to create private gateway - Key: CLOUDSTACK-6084 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6084 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: xenserver 6.2 ,advanced zone Reporter: Srikanteswararao Talluri Assignee: Jayapal Reddy Priority: Critical Fix For: 4.4.0 Steps to reproduce: = # 1) Create VPC self.createVPC() # 2) Create ACl self.createACL() # 3) Create ACl Item self.createACLItem() # 4) Create network with ACL self.createNetwork() # 5) create private gw self.createPvtGw() Logs can be found here : http://jenkins.buildacloud.org/view/cloudstack-qa-master/job/test-matrix-master/3/distro=centos63,hypervisor=xen,profile=xen62/artifact/3.tar.bz2 ===START=== 10.208.8.5 -- GET physicalnetworkid=200vpcid=e1f5910c-1352-4274-9326-f8413f41d4bfsourcenatsupported=trueaclid=bdca388c-c6cf-4757-b72d-c07e22ff9fa5vlan=30response=jsonnetmask=255.255.255.0apiKey=ZVang0oygdXeY5o3XEz4X3i60YHJj5nVE8gN6hR_zlBWzIoxby09FIxK_a-UlWl_jzLen_4I8oXgmQLppn3ikwcommand=createPrivateGatewaysignature=2Z89SOGldeUm9Lfg10R8rcx%2FRZ0%3Dipaddress=10.147.30.200gateway=10.147.30.1 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,779 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-335:ctx-48012a52) Ping from 1(apache-81-3) Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,808 DEBUG [network.vpc.VpcManagerImpl] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Creating Private gateway for VPC [VPC [6-new vpc] Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,808 INFO [network.vpc.VpcManagerImpl] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) creating new network for vpc [VPC [6-new vpc] using broadcast uri: 30 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,834 DEBUG [contrail.management.ContrailGuru] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design this network Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,834 DEBUG [network.guru.MidoNetGuestNetworkGuru] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) design called Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,835 DEBUG [network.guru.MidoNetGuestNetworkGuru] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design this network, the physical isolation type is not MIDO Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,835 DEBUG [network.guru.NiciraNvpGuestNetworkGuru] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design this network Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,840 DEBUG [network.opendaylight.OpendaylightGuestNetworkGuru] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design this network Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,841 DEBUG [network.guru.OvsGuestNetworkGuru] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design this network Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,857 DEBUG [network.guru.SspGuestNetworkGuru] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) SSP not configured to be active Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,858 DEBUG [engine.orchestration.NetworkOrchestrator] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Releasing lock for Acct[bcbb718a-93c7-11e3-af4f-b6c8db337241-system] Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,858 DEBUG [cloud.network.NetworkServiceImpl] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Created private network Ntwk[230|Guest|5] Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,864 DEBUG [cloud.network.NetworkServiceImpl] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Private network Ntwk[230|Guest|5] is created Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,891 DEBUG
[jira] [Created] (CLOUDSTACK-6708) [Automation]: Few suites were failing on simulator run
Santhosh Kumar Edukulla created CLOUDSTACK-6708: --- Summary: [Automation]: Few suites were failing on simulator run Key: CLOUDSTACK-6708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6708 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure integration.smoke.test_hosts.TestHosts.test_01_clusters integration.smoke.test_network.TestDeleteAccount.test_delete_account integration.smoke.test_network.TestPublicIP.test_public_ip_admin_account integration.smoke.test_network.TestReleaseIP.test_releaseIP integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_08_migrate_vm integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001640#comment-14001640 ] ASF subversion and git services commented on CLOUDSTACK-6282: - Commit 2ba6322030dc24e6888407c78a8573f8b0d04bc9 in cloudstack's branch refs/heads/master from [~vinayv] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2ba6322 ] CLOUDSTACK-6282 - Divided test_escalations.py into individual files based on functionality and added automed tests for Public IP Addresses [Automation]: Adding new Testcases -- Key: CLOUDSTACK-6282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Vinay Vegesna Assignee: Santhosh Kumar Edukulla [Automation]: Adding below new Test cases for test_escalations.py test_01_list_volumes_pagination test_02_list_volume_byid test_03_data_volume_resize test_04_custom_volume test_05_volume_snapshot test_06_volume_snapshot_policy test_07_volume_snapshots_pagination test_08_volume_extract test_09_volume_upload -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001642#comment-14001642 ] ASF subversion and git services commented on CLOUDSTACK-6282: - Commit c5634570e25900f2e83a77a2ad20ad267bba8202 in cloudstack's branch refs/heads/4.4-forward from [~vinayv] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c563457 ] CLOUDSTACK-6282 - Divided test_escalations.py into individual files based on functionality and added automed tests for Public IP Addresses [Automation]: Adding new Testcases -- Key: CLOUDSTACK-6282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Vinay Vegesna Assignee: Santhosh Kumar Edukulla [Automation]: Adding below new Test cases for test_escalations.py test_01_list_volumes_pagination test_02_list_volume_byid test_03_data_volume_resize test_04_custom_volume test_05_volume_snapshot test_06_volume_snapshot_policy test_07_volume_snapshots_pagination test_08_volume_extract test_09_volume_upload -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001649#comment-14001649 ] ASF subversion and git services commented on CLOUDSTACK-6282: - Commit d43d28ee84424359d5847fa6e53dabad176f037e in cloudstack's branch refs/heads/4.4-forward from [~gpshilamkar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d43d28e ] Revert CLOUDSTACK-6282 - Divided test_escalations.py into individual files based on functionality and added automed tests for Public IP Addresses This reverts commit c5634570e25900f2e83a77a2ad20ad267bba8202. [Automation]: Adding new Testcases -- Key: CLOUDSTACK-6282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Vinay Vegesna Assignee: Santhosh Kumar Edukulla [Automation]: Adding below new Test cases for test_escalations.py test_01_list_volumes_pagination test_02_list_volume_byid test_03_data_volume_resize test_04_custom_volume test_05_volume_snapshot test_06_volume_snapshot_policy test_07_volume_snapshots_pagination test_08_volume_extract test_09_volume_upload -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001650#comment-14001650 ] ASF subversion and git services commented on CLOUDSTACK-6282: - Commit b4ad709d321b79f532721cd65f9ecf9584d68ee6 in cloudstack's branch refs/heads/master from [~gpshilamkar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b4ad709 ] Revert CLOUDSTACK-6282 - Divided test_escalations.py into individual files based on functionality and added automed tests for Public IP Addresses This reverts commit 2ba6322030dc24e6888407c78a8573f8b0d04bc9. [Automation]: Adding new Testcases -- Key: CLOUDSTACK-6282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Vinay Vegesna Assignee: Santhosh Kumar Edukulla [Automation]: Adding below new Test cases for test_escalations.py test_01_list_volumes_pagination test_02_list_volume_byid test_03_data_volume_resize test_04_custom_volume test_05_volume_snapshot test_06_volume_snapshot_policy test_07_volume_snapshots_pagination test_08_volume_extract test_09_volume_upload -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001656#comment-14001656 ] ASF subversion and git services commented on CLOUDSTACK-6282: - Commit ef2012677c8eb47e083a7220dfc30ac001e91567 in cloudstack's branch refs/heads/master from [~vinayv] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ef20126 ] CLOUDSTACK-6282 - Divided test_escalations.py into individual files based on functionality and added automed tests for Public IP Addresses [Automation]: Adding new Testcases -- Key: CLOUDSTACK-6282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Vinay Vegesna Assignee: Santhosh Kumar Edukulla [Automation]: Adding below new Test cases for test_escalations.py test_01_list_volumes_pagination test_02_list_volume_byid test_03_data_volume_resize test_04_custom_volume test_05_volume_snapshot test_06_volume_snapshot_policy test_07_volume_snapshots_pagination test_08_volume_extract test_09_volume_upload -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001657#comment-14001657 ] ASF subversion and git services commented on CLOUDSTACK-6282: - Commit 378e1da42c235d310df3d39d3d82270ef00546df in cloudstack's branch refs/heads/4.4-forward from [~vinayv] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=378e1da ] CLOUDSTACK-6282 - Divided test_escalations.py into individual files based on functionality and added automed tests for Public IP Addresses [Automation]: Adding new Testcases -- Key: CLOUDSTACK-6282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Vinay Vegesna Assignee: Santhosh Kumar Edukulla [Automation]: Adding below new Test cases for test_escalations.py test_01_list_volumes_pagination test_02_list_volume_byid test_03_data_volume_resize test_04_custom_volume test_05_volume_snapshot test_06_volume_snapshot_policy test_07_volume_snapshots_pagination test_08_volume_extract test_09_volume_upload -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6709) [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor
Sanjeev N created CLOUDSTACK-6709: - Summary: [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor Key: CLOUDSTACK-6709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6709 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Network Controller Affects Versions: 4.4.0 Environment: Latest build from 4.4 with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Priority: Critical Fix For: 4.4.0 [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor Steps to Reproduce: = 1.Bring up CS in advanced zone with two xen hosts in a cluster 2.Add physical network with GRE isolation 3.Create network with connectivity service and ovs as the service provider 4.Deploy few vms in the above network and make sure that vms are spanned across both the hosts 5.Destroy and expunge all the vms in the network and delete the network Expected result: = Network deletion should be successful and all the tunnel ports and brige created for the network should be deleted from both the hosts Actual Result: Network deletion was successful but failed to delete ovs bridge and the tunnel ports. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6709) [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N updated CLOUDSTACK-6709: -- Attachment: ovstunnel-host14.log ovstunnel-host13.log management-server.rar Attached MS log file and ovstunnel log files from both the xenserver hosts. [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor -- Key: CLOUDSTACK-6709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Network Controller Affects Versions: 4.4.0 Environment: Latest build from 4.4 with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Priority: Critical Fix For: 4.4.0 Attachments: management-server.rar, ovstunnel-host13.log, ovstunnel-host14.log [SDN] Deleting network does not delete the tunnel ports and the bridge from the hypervisor Steps to Reproduce: = 1.Bring up CS in advanced zone with two xen hosts in a cluster 2.Add physical network with GRE isolation 3.Create network with connectivity service and ovs as the service provider 4.Deploy few vms in the above network and make sure that vms are spanned across both the hosts 5.Destroy and expunge all the vms in the network and delete the network Expected result: = Network deletion should be successful and all the tunnel ports and brige created for the network should be deleted from both the hosts Actual Result: Network deletion was successful but failed to delete ovs bridge and the tunnel ports. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6656) [Automation] test_deploy_vm_userdata_reg failing with publickey permission error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye reassigned CLOUDSTACK-6656:
--
Assignee: Gaurav Aradhye
[Automation] test_deploy_vm_userdata_reg failing with publickey permission
error
-
Key: CLOUDSTACK-6656
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6656
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Environment:
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
Fix For: 4.4.0
Test case
integration.component.test_deploy_vm_userdata_reg.TestDeployVmWithUserData.test_deployvm_userdata_post
failing with public permssion error.
Observed //.ssh/id_rsa.cloud not accessible: No such file or directory,
error in below log, it should be /root/.ssh/id_rsa.cloud ? is there any
change in test for this failure ? we need to confirm this before fixing
here the stack trace
paramiko.transport: DEBUG: using kex diffie-hellman-group1-sha1; server key
type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local
hmac-sha1, remote hmac-sha1; compression: local none, remote none
paramiko.transport: DEBUG: Switch to new keys ...
paramiko.transport: DEBUG: Adding ssh-rsa host key for 10.223.250.131:
9adbd7958130f6cc11d746cc657ce157
paramiko.transport: DEBUG: Trying discovered key
d73731e045a189d941928d25f66aa458 in /root/.ssh/id_rsa
paramiko.transport: DEBUG: userauth is OK
paramiko.transport: INFO: Auth banner:
paramiko.transport: INFO: Authentication (publickey) failed.
paramiko.transport: DEBUG: userauth is OK
paramiko.transport: DEBUG: Authentication type (password) not permitted.
paramiko.transport: DEBUG: Allowed methods: [u'publickey',
u'keyboard-interactive']
paramiko.transport: DEBUG: userauth is OK
paramiko.transport: INFO: Authentication (keyboard-interactive) successful!
sshClient: DEBUG: ===SSH to Host 10.223.250.131 port : 22 SUCCESSFUL===
paramiko.transport: DEBUG: [chan 1] Max packet in: 34816 bytes
paramiko.transport: DEBUG: [chan 1] Max packet out: 32768 bytes
paramiko.transport: INFO: Secsh channel 1 opened.
paramiko.transport: DEBUG: [chan 1] Sesch channel 1 request ok
paramiko.transport: DEBUG: [chan 1] EOF received (1)
paramiko.transport: DEBUG: [chan 1] EOF sent (1)
sshClient: DEBUG: {Cmd: ssh -i ~/.ssh/id_rsa.cloud -ostricthostkeychecking=no
-oUserKnownHostsFile=/dev/null -p 3922 10.223.250.165 cat
/var/www/html/userdata/10.1.1.89/user-data via Host: 10.223.250.131}
{returns: [u'Warning: Identity file //.ssh/id_rsa.cloud not accessible: No
such file or directory.', uWarning: Permanently added
'[10.223.250.165]:3922' (RSA) to the list of known hosts., u'Permission
denied (publickey).']}
paramiko.transport: DEBUG: EOF in transport thread
test_deployvm_userdata_post
(integration.component.test_deploy_vm_userdata_reg.TestDeployVmWithUserData):
CRITICAL: FAILED: test_deployvm_userdata_post: ['Traceback (most recent call
last):\n', ' File /usr/local/lib/python2.7/unittest/case.py, line 318, in
run\ntestMethod()\n', ' File
/data/Repo2/qa/cloudstack/test/integration/component/test_deploy_vm_userdata_reg.py,
line 212, in test_deployvm_userdata_post\n
self.assertEqual(res.__contains__(self.userdata),True,Userdata Not applied
Check the failures)\n', ' File /usr/local/lib/python2.7/unittest/case.py,
line 494, in assertEqual\nassertion_func(first, second, msg=msg)\n', '
File /usr/local/lib/python2.7/unittest/case.py, line 487, in
_baseAssertEqual\nraise self.failureException(msg)\n', 'AssertionError:
Userdata Not applied Check the failures\n']
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
testMethod()
File
/data/Repo2/qa/cloudstack/test/integration/component/test_deploy_vm_userdata_reg.py,
line 212, in test_deployvm_userdata_post
self.assertEqual(res.__contains__(self.userdata),True,Userdata Not
applied Check the failures)
File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual
assertion_func(first, second, msg=msg)
File /usr/local/lib/python2.7/unittest/case.py, line 487, in
_baseAssertEqual
raise self.failureException(msg)
'Userdata Not applied Check the failures\n begin
captured stdout -\n=== TestName:
test_deployvm_userdata_post | Status : FAILED ===\n\n\n-
end captured stdout --\n
begin captured logging
[jira] [Commented] (CLOUDSTACK-6656) [Automation] test_deploy_vm_userdata_reg failing with publickey permission error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001675#comment-14001675
]
Gaurav Aradhye commented on CLOUDSTACK-6656:
Need to pass hypervisor value while running nosetests.
E.g.
nohup nosetests-2.7 -v --with-marvin --marvin-config=/root/test/run.cfg
--log-folder-path=/root/test/ --tests=/root/test/test_deploy_v
m_userdata_reg.py --hypervisor=VMware
When hypervisor is not passed, it is defaulted to XenServer and wrong script is
executed in the test cases where to be executed script is dependent on the
hypervisor type.
[Automation] test_deploy_vm_userdata_reg failing with publickey permission
error
-
Key: CLOUDSTACK-6656
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6656
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Environment:
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
Fix For: 4.4.0
Test case
integration.component.test_deploy_vm_userdata_reg.TestDeployVmWithUserData.test_deployvm_userdata_post
failing with public permssion error.
Observed //.ssh/id_rsa.cloud not accessible: No such file or directory,
error in below log, it should be /root/.ssh/id_rsa.cloud ? is there any
change in test for this failure ? we need to confirm this before fixing
here the stack trace
paramiko.transport: DEBUG: using kex diffie-hellman-group1-sha1; server key
type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local
hmac-sha1, remote hmac-sha1; compression: local none, remote none
paramiko.transport: DEBUG: Switch to new keys ...
paramiko.transport: DEBUG: Adding ssh-rsa host key for 10.223.250.131:
9adbd7958130f6cc11d746cc657ce157
paramiko.transport: DEBUG: Trying discovered key
d73731e045a189d941928d25f66aa458 in /root/.ssh/id_rsa
paramiko.transport: DEBUG: userauth is OK
paramiko.transport: INFO: Auth banner:
paramiko.transport: INFO: Authentication (publickey) failed.
paramiko.transport: DEBUG: userauth is OK
paramiko.transport: DEBUG: Authentication type (password) not permitted.
paramiko.transport: DEBUG: Allowed methods: [u'publickey',
u'keyboard-interactive']
paramiko.transport: DEBUG: userauth is OK
paramiko.transport: INFO: Authentication (keyboard-interactive) successful!
sshClient: DEBUG: ===SSH to Host 10.223.250.131 port : 22 SUCCESSFUL===
paramiko.transport: DEBUG: [chan 1] Max packet in: 34816 bytes
paramiko.transport: DEBUG: [chan 1] Max packet out: 32768 bytes
paramiko.transport: INFO: Secsh channel 1 opened.
paramiko.transport: DEBUG: [chan 1] Sesch channel 1 request ok
paramiko.transport: DEBUG: [chan 1] EOF received (1)
paramiko.transport: DEBUG: [chan 1] EOF sent (1)
sshClient: DEBUG: {Cmd: ssh -i ~/.ssh/id_rsa.cloud -ostricthostkeychecking=no
-oUserKnownHostsFile=/dev/null -p 3922 10.223.250.165 cat
/var/www/html/userdata/10.1.1.89/user-data via Host: 10.223.250.131}
{returns: [u'Warning: Identity file //.ssh/id_rsa.cloud not accessible: No
such file or directory.', uWarning: Permanently added
'[10.223.250.165]:3922' (RSA) to the list of known hosts., u'Permission
denied (publickey).']}
paramiko.transport: DEBUG: EOF in transport thread
test_deployvm_userdata_post
(integration.component.test_deploy_vm_userdata_reg.TestDeployVmWithUserData):
CRITICAL: FAILED: test_deployvm_userdata_post: ['Traceback (most recent call
last):\n', ' File /usr/local/lib/python2.7/unittest/case.py, line 318, in
run\ntestMethod()\n', ' File
/data/Repo2/qa/cloudstack/test/integration/component/test_deploy_vm_userdata_reg.py,
line 212, in test_deployvm_userdata_post\n
self.assertEqual(res.__contains__(self.userdata),True,Userdata Not applied
Check the failures)\n', ' File /usr/local/lib/python2.7/unittest/case.py,
line 494, in assertEqual\nassertion_func(first, second, msg=msg)\n', '
File /usr/local/lib/python2.7/unittest/case.py, line 487, in
_baseAssertEqual\nraise self.failureException(msg)\n', 'AssertionError:
Userdata Not applied Check the failures\n']
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
testMethod()
File
/data/Repo2/qa/cloudstack/test/integration/component/test_deploy_vm_userdata_reg.py,
line 212, in test_deployvm_userdata_post
self.assertEqual(res.__contains__(self.userdata),True,Userdata Not
applied Check the failures)
File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual
assertion_func(first, second, msg=msg)
File
[jira] [Commented] (CLOUDSTACK-6688) [Automation] SSVM test cases failing in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001676#comment-14001676
]
Gaurav Aradhye commented on CLOUDSTACK-6688:
You need to pass hypervisor value while running nosetests.
E.g.
nohup nosetests-2.7 -v --with-marvin --marvin-config=/root/test/run.cfg
--log-folder-path=/root/test/ --tests=/root/test/test_deploy_v
m_userdata_reg.py --hypervisor=VMware
When hypervisor is not passed, it is defaulted to XenServer and wrong script is
executed in the test cases where to be executed script is dependent on the
hypervisor type.
[Automation] SSVM test cases failing in vmware
---
Key: CLOUDSTACK-6688
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6688
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: Rayees Namathponnan
Assignee: Gaurav Aradhye
Fix For: 4.4.0
Below test cases failing in vmware
integration.smoke.test_ssvm.TestSSVMs.test_03_ssvm_internals 0.477 6
integration.smoke.test_ssvm.TestSSVMs.test_04_cpvm_internals 0.495 6
integration.smoke.test_ssvm.TestSSVMs.test_05_stop_ssvm 121.115 6
integration.smoke.test_ssvm.TestSSVMs.test_06_stop_cpvm 111.028 6
integration.smoke.test_ssvm.TestSSVMs.test_07_reboot_ssvm 95.884 6
integration.smoke.test_ssvm.TestSSVMs.test_08_reboot_cpvm 95.813 6
integration.smoke.test_ssvm.TestSSVMs.test_09_destroy_ssvm211.072 6
integration.smoke.test_ssvm.TestSSVMs.test_10_destroy_cpvm211.116 6
Test cases failing with error Warning: Identity file //.ssh/id_rsa.cloud not
accessible: No such file or directory.', u'ssh: Could not resolve hostname
None: Name or service not known']}
This issue observed only in vmware
shClient: DEBUG: ===SSH to Host 10.223.250.130 port : 22 SUCCESSFUL===
paramiko.transport: DEBUG: [chan 1] Max packet in: 34816 bytes
paramiko.transport: DEBUG: [chan 1] Max packet out: 32768 bytes
paramiko.transport: INFO: Secsh channel 1 opened.
paramiko.transport: DEBUG: [chan 1] Sesch channel 1 request ok
sshClient: DEBUG: {Cmd: ssh -i ~/.ssh/id_rsa.cloud -ostricthostkeychecking=no
-oUserKnownHostsFile=/dev/null -p 3922 None
/usr/local/cloud/systemvm/ssvm-check.sh |grep -e ERROR -e WARNING -e FAIL via
Host: 10.223.250.130} {returns: [u'Warning: Identity file //.ssh/id_rsa.cloud
not accessible: No such file or directory.', u'ssh: Could not resolve
hostname None: Name or service not known']}
paramiko.transport: DEBUG: [chan 1] EOF received (1)
test_03_ssvm_internals (integration.smoke.test_ssvm.TestSSVMs): DEBUG: SSVM
script output: [u'Warning: Identity file //.ssh/id_rsa.cloud not accessible:
No such file or directory.', u'ssh: Could not resolve hostname None: Name or
service not known']
test_03_ssvm_internals (integration.smoke.test_ssvm.TestSSVMs): CRITICAL:
FAILED: test_03_ssvm_internals: ['Traceback (most recent call last):\n', '
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run\n
testMethod()\n', ' File
/data/Repo2/qa/cloudstack/test/integration/smoke/test_ssvm.py, line 352, in
test_03_ssvm_internals\nCheck for Errors in tests\n', ' File
/usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual\n
assertion_func(first, second, msg=msg)\n', ' File
/usr/local/lib/python2.7/unittest/case.py, line 487, in _baseAssertEqual\n
raise self.failureException(msg)\n', 'AssertionError: Check for Errors in
tests\n']
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
testMethod()
File /data/Repo2/qa/cloudstack/test/integration/smoke/test_ssvm.py, line
352, in test_03_ssvm_internals
Check for Errors in tests
File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual
assertion_func(first, second, msg=msg)
File /usr/local/lib/python2.7/unittest/case.py, line 487, in
_baseAssertEqual
raise self.failureException(msg)
'Check for Errors in tests\n begin captured stdout
-\n=== TestName: test_03_ssvm_internals | Status : FAILED
===\n\n\n- end captured stdout
--\n begin captured logging
\ntest_03_ssvm_internals
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6655) Portable IP test cases failing when the ip range in previously executed test cases does not get cleaned up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye resolved CLOUDSTACK-6655. Resolution: Fixed Portable IP test cases failing when the ip range in previously executed test cases does not get cleaned up -- Key: CLOUDSTACK-6655 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6655 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Environment: All hypervisors Reporter: Gaurav Aradhye Assignee: Girish Shilamkar Labels: automation Fix For: 4.4.0 When the range created in the test case does not get cleaned up due to some reason, all next test cases fail with error the portable ip range already exists. Solution: Modify test cases so that proper cleanup takes place. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6655) Portable IP test cases failing when the ip range in previously executed test cases does not get cleaned up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-6655: --- Assignee: Girish Shilamkar Portable IP test cases failing when the ip range in previously executed test cases does not get cleaned up -- Key: CLOUDSTACK-6655 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6655 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Environment: All hypervisors Reporter: Gaurav Aradhye Assignee: Girish Shilamkar Labels: automation Fix For: 4.4.0 When the range created in the test case does not get cleaned up due to some reason, all next test cases fail with error the portable ip range already exists. Solution: Modify test cases so that proper cleanup takes place. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001684#comment-14001684
]
Sam Schmit commented on CLOUDSTACK-6631:
I have a 4.2.1 environment I was able to test on, and had no problem creating a
5GB volume via the UI, then attaching it to a VM that I had just created. I
did this as a user on an account, not as a root admin, but I doubt the results
would be different.
Do any volumes you create via the volumes section of the UI create properly?
Have you tried doing a createVolume API call from outside the UI to see if it
creates properly there? It seems like something isn't functioning quite right
with your volume creation.
unable to attach new Volume to VM
-
Key: CLOUDSTACK-6631
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.1
Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
Reporter: Kazuhiro Ito
1. I added new volume.
2. I tried to attach the volume to a VM on UI.
3. It failed and the following log appeared.
2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
(http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
command=attachVolumeid=ac7099fb-ac66-4c63-bf1e-ed0e1429f412virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74response=jsonsessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D_=1399861774316
2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
(http-6443-exec-116:null) submit async job-4916 = [
dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:ac7099fb-ac66-4c63-bf1e-ed0e1429f412,sessionkey:TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d,cmdEventType:VOLUME.ATTACH,ctxUserId:3,virtualMachineId:ecdc2c1d-e21e-4c04-962a-4efac1a69a74,httpmethod:GET,_:1399861774316,ctxAccountId:3,ctxStartEventId:34276},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
(http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
command=attachVolumeid=ac7099fb-ac66-4c63-bf1e-ed0e1429f412virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74response=jsonsessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D_=1399861774316
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to VM[User|TEST-A2-VM01] granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
LocalStoragePoolAllocator trying to find storage pool to fit the vm
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
ClusterScopeStoragePoolAllocator looking for storage pool
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
2014-05-12 11:29:47,216 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
storage pools available for shared volume allocation, returning
2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
SUM(IF(vol.state='Ready' AND vol.account_id =
[jira] [Updated] (CLOUDSTACK-6616) systemvm template build failed since install dialog prevents automation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoshikazu Nojima updated CLOUDSTACK-6616: - Fix Version/s: 4.4.0 systemvm template build failed since install dialog prevents automation --- Key: CLOUDSTACK-6616 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6616 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: Future Reporter: Yoshikazu Nojima Priority: Blocker Labels: systemvm Fix For: 4.4.0 log: = Executing command: ./base.sh 0% [Working] Hit http://http.us.debian.org wheezy Release.gpg 20% [Waiting for headers] [Waiting for headers] Hit http://security.debian.org wheezy/updates Release.gpg 33% [Waiting for headers] Hit http://http.us.debian.org wheezy-updates Release.gpg 43% [Waiting for headers] Hit http://security.debian.org wheezy/updates Release 43% [Waiting for headers] Hit http://http.us.debian.org wheezy Release 43% [Working] 43% [Release gpgv 102 kB] [Waiting for headers] 40% [Waiting for headers] 40% [Release gpgv 168 kB] [Waiting for headers] [Waiting for headers] 38% [Waiting for headers] [Waiting for headers] Hit http://http.us.debian.org wheezy-updates Release 38% [Waiting for headers] 38% [Release gpgv 124 kB] [Waiting for headers] [Waiting for headers] 38% [Waiting for headers] [Waiting for headers] Hit http://security.debian.org wheezy/updates/main Sources 44% [Waiting for headers] Hit http://http.us.debian.org wheezy/main Sources 50% [Waiting for headers] [Waiting for headers] Hit http://http.us.debian.org wheezy/main amd64 Packages Hit http://security.debian.org wheezy/updates/main amd64 Packages 62% [Waiting for headers] [Waiting for headers] Hit http://http.us.debian.org wheezy/main Translation-en 69% [Waiting for headers] [Waiting for headers] Hit http://security.debian.org wheezy/updates/main Translation-en 75% [Waiting for headers] Hit http://http.us.debian.org wheezy-updates/main Sources 81% [Waiting for headers] Hit http://http.us.debian.org wheezy-updates/main amd64 Packages/DiffIndex 88% [Waiting for headers] Hit http://http.us.debian.org wheezy-updates/main Translation-en/DiffIndex 94% [Working] Reading package lists... 0% Reading package lists... 0% Reading package lists... 1% Reading package lists... 32% Reading package lists... 58% Reading package lists... 58% Reading package lists... 59% Reading package lists... 96% Reading package lists... 96% Reading package lists... 98% Reading package lists... 98% Reading package lists... 99% Reading package lists... 99% Reading package lists... 99% Reading package lists... 99% Reading package lists... 99% Reading package lists... 99% Reading package lists... Done Reading package lists... 0% Reading package lists... 100% Reading package lists... Done Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... 1% Reading state information... Done The following extra packages will be installed: ca-certificates libcurl3 libldap-2.4-2 librtmp0 libsasl2-2 libsasl2-modules libssh2-1 libssl1.0.0 openssl Suggested packages: libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal zip The following NEW packages will be installed: ca-certificates curl libcurl3 libldap-2.4-2 librtmp0 libsasl2-2
[jira] [Resolved] (CLOUDSTACK-6699) listResouceDetails - enhance it to list by (key,value) pair
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-6699. - Resolution: Fixed listResouceDetails - enhance it to list by (key,value) pair --- Key: CLOUDSTACK-6699 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6699 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta listResouceDetails - enhance it to list by (key,value) pair. Currently allowing this to only Admin user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6599) Template/Volume URLs expiration functionality not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002016#comment-14002016 ] Nitin Mehta commented on CLOUDSTACK-6599: - Update - I have made the code changes, will test it soon and push it. Template/Volume URLs expiration functionality not working - Key: CLOUDSTACK-6599 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6599 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta Priority: Blocker Fix For: 4.4.0 Template / Volume Donwload URLs should expire - functionality is missing We have the functionality where we create download urls for volumes and templates for the users. For security reasons we should expire these urls and this functionality existed since 3.0.x. But it doesnt exist in 4.4 and that needs to be implemented. Look at 4.2 for reference. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6644) Unable to attach Volume to a VM as a System User
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-6644:
-
Assignee: edison su
Unable to attach Volume to a VM as a System User
Key: CLOUDSTACK-6644
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6644
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: IAM
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: edison su
Priority: Blocker
Fix For: 4.4.0
As System User, tried to attach a Volume belonging to an account to a VM
belonging to the same account. Failed with the following error.
Acct[4f0e5b12-d6d8-11e3-952f-06098c000757-system] does not have permission
to perform this operation on these resources
mysql select account_id, uuid from vm_instance where uuid like '%56a4%';
++--+
| account_id | uuid |
++--+
| 3 | 56a488ce-9baf-4d99-8e25-002d565f6731 |
++--+
1 row in set (0.00 sec)
mysql select account_id, uuid from volumes where uuid like '%00585b50%';
++--+
| account_id | uuid |
++--+
| 3 | 00585b50-8c65-4e5b-95ee-853489e5499c |
++--+
1 row in set (0.00 sec)
2014-05-12 13:40:48,618 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) submit async
job-190, details: AsyncJobVO {id:190, userId: 1, accountId: 1, instanceType:
Volume, instanceId: 11, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{virtualmachineid:56a488ce-9baf-4d99-8e25-002d565f6731,cmdEventType:VOLUME.ATTACH,ctxUserId:1,httpmethod:GET,deviceid:1,apikey:dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ,id:00585b50-8c65-4e5b-95ee-853489e5499c,response:json,ctxDetails:{\com.cloud.storage.Volume\:11,\Volume\:\00585b50-8c65-4e5b-95ee-853489e5499c\,\com.cloud.vm.VirtualMachine\:8},ctxAccountId:1,uuid:00585b50-8c65-4e5b-95ee-853489e5499c,ctxStartEventId:448,signature:euszCT397/kGpCM1fN+GQhTJCe8\u003d},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-12 13:40:48,619 DEBUG [c.c.a.ApiServlet]
(catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) ===END=== 127.0.0.1
-- GET
apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQcommand=attachVolumedeviceid=1id=00585b50-8c65-4e5b-95ee-853489e5499cresponse=jsonvirtualmachineid=56a488ce-9baf-4d99-8e25-002d565f6731apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQsignature=euszCT397%2FkGpCM1fN%2BGQhTJCe8%3D
2014-05-12 13:40:48,621 DEBUG [c.c.a.ApiServlet]
(catalina-exec-3:ctx-9e956cd7) ===START=== 127.0.0.1 -- GET
apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQcommand=queryAsyncJobResultjobId=2ef19e77-29af-416f-bc16-f27df1b58e7fresponse=jsonapikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQsignature=O1vnDPmstm6Xa2lEazduvETJkXk%3D
2014-05-12 13:40:48,627 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-45:job-190) Add job-190 into job monitoring
2014-05-12 13:40:48,627 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-45:job-190) Executing AsyncJobVO {id:190, userId: 1,
accountId: 1, instanceType: Volume, instanceId: 11, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{virtualmachineid:56a488ce-9baf-4d99-8e25-002d565f6731,cmdEventType:VOLUME.ATTACH,ctxUserId:1,httpmethod:GET,deviceid:1,apikey:dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ,id:00585b50-8c65-4e5b-95ee-853489e5499c,response:json,ctxDetails:{\com.cloud.storage.Volume\:11,\Volume\:\00585b50-8c65-4e5b-95ee-853489e5499c\,\com.cloud.vm.VirtualMachine\:8},ctxAccountId:1,uuid:00585b50-8c65-4e5b-95ee-853489e5499c,ctxStartEventId:448,signature:euszCT397/kGpCM1fN+GQhTJCe8\u003d},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-12 13:40:48,642 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(catalina-exec-3:ctx-9e956cd7 ctx-6c73263d
[jira] [Commented] (CLOUDSTACK-6673) cloudstack-setup-management make a chmod 777 on /root
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002362#comment-14002362 ] Milamber commented on CLOUDSTACK-6673: -- Comment this line seems have no impact on CS 4.4 deployment (KVM installation on Ubuntu 14.04 and Debian7+backports) cloudstack-setup-management make a chmod 777 on /root - Key: CLOUDSTACK-6673 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6673 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.4.0 Environment: Ubuntu 14.04 / KVM CS 4.4.0 snapshot 20140513 Reporter: Milamber Priority: Blocker Labels: security Before run cloudstack-setup-management, /root directory permissions are: drwx-- 4 root root 4096 mai 14 15:05 root After the runs of cloudstack-setup-management, /root directory permissions are: drwxrwxrwx 4 root root 4096 mai 14 15:05 root -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware
Rayees Namathponnan created CLOUDSTACK-6710:
---
Summary: [Automation] VM snapshot failing with NPE in vmware
Key: CLOUDSTACK-6710
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation
Affects Versions: 4.4.0
Environment: Vmware 5.0
4.4-forward
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.rar
Execute BVT
integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
This test case creating VM snapshot in VMware; this is failing with below NPE
2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-130:job-390/job-391) Run VM work job:
com.cloud.vm.snapshot.VmWorkCreateVMSn
apshot for VM 62, job origin: 390
2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job:
com.cloud.vm.snapsh
ot.VmWorkCreateVMSnapshot{vmSnapshotId:1,quiesceVm:false,userId:2,accountId:2,vmId:62,handlerName:VMSnapshotManagerImpl}
2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl]
(Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm
snapshot: 1
java.lang.NullPointerException
at
org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
at
com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
at
com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy182.handleVmWorkJob(Unknown Source)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.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-19 13:12:00,517 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-130:job-390/job-391 ctx-538be870) Invocation exception,
caused by: java.la
ng.NullPointerException
2014-05-19 13:12:00,517 INFO [c.c.v.VmWorkJobHandlerProxy]
[jira] [Updated] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6710:
Attachment: management-server.rar
[Automation] VM snapshot failing with NPE in vmware
---
Key: CLOUDSTACK-6710
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Environment: Vmware 5.0
4.4-forward
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.rar
Execute BVT
integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
This test case creating VM snapshot in VMware; this is failing with below NPE
2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-130:job-390/job-391) Run VM work job:
com.cloud.vm.snapshot.VmWorkCreateVMSn
apshot for VM 62, job origin: 390
2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job:
com.cloud.vm.snapsh
ot.VmWorkCreateVMSnapshot{vmSnapshotId:1,quiesceVm:false,userId:2,accountId:2,vmId:62,handlerName:VMSnapshotManagerImpl}
2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl]
(Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm
snapshot: 1
java.lang.NullPointerException
at
org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
at
com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
at
com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy182.handleVmWorkJob(Unknown Source)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at
[jira] [Assigned] (CLOUDSTACK-6671) Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Vasekar reassigned CLOUDSTACK-6671: - Assignee: Amogh Vasekar Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64) - Key: CLOUDSTACK-6671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6671 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, KVM Affects Versions: 4.4.0 Environment: Ubuntu 14.04 / KVM / CS 4.4.0 snapshot 20140513 / 20140516 Reporter: Milamber Assignee: Amogh Vasekar Priority: Critical Labels: KVM Attachments: extract-management.log Unable to create VM on a fresh CS 4.4.0 installation (branch 4.4). SSVM, Console proxy and first virtual routeur are correctly created and UP. 10 day ago, this issue isn't present. In attachment, full log. 2014-05-14 15:46:33,085 ERROR [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-6:job-25/job-27 ctx-57c7f749) Failed to start instance VM[User|i-2-5-VM] java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.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-6671) Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002614#comment-14002614 ] Amogh Vasekar commented on CLOUDSTACK-6671: --- This issue arises due to a missing Debian mapping in the table. Fixing via https://reviews.apache.org/r/21673/ Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64) - Key: CLOUDSTACK-6671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6671 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, KVM Affects Versions: 4.4.0 Environment: Ubuntu 14.04 / KVM / CS 4.4.0 snapshot 20140513 / 20140516 Reporter: Milamber Assignee: Amogh Vasekar Priority: Critical Labels: KVM Attachments: extract-management.log Unable to create VM on a fresh CS 4.4.0 installation (branch 4.4). SSVM, Console proxy and first virtual routeur are correctly created and UP. 10 day ago, this issue isn't present. In attachment, full log. 2014-05-14 15:46:33,085 ERROR [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-6:job-25/job-27 ctx-57c7f749) Failed to start instance VM[User|i-2-5-VM] java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.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-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002698#comment-14002698
]
Kazuhiro Ito commented on CLOUDSTACK-6631:
--
At first, I tried as both a user and a root admin, the same result.
And I tried via both UI and createVolume API, but the same result.
[root@x01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520
diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242
zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d
SEND URL:
https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolumename=TESTVOL0520diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5dapikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyAsignature=mFAoQ5bAfuIjV07A%2BSP%2FE6AVELg%3D
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
103 207 103 2070 0 1334 0 --:--:-- --:--:-- --:--:-- 2250
?xml version=1.0 encoding=UTF-8?
createvolumeresponse cloud-stack-version=4.2.1
id889fff9b-833d-423d-b295-ae16ed9a10da/id
jobidc5a2a669-98da-4cc6-bad0-d37f63111e86/jobid
/createvolumeresponse
| id | account_id | domain_id | pool_id | last_pool_id | instance_id |
device_id | name| uuid | size
| folder | path |
pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type |
disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable |
created | attached| updated | removed
| state | chain_info | update_count | disk_type |
vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops
|
| 1727 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL0520 | 889fff9b-833d-423d-b295-ae16ed9a10da |
10995116277760 | NULL| NULL
| NULL | 1 | NULL | NULL| DATADISK| NULL
| 29 |NULL | NULL | 0 |
2014-05-20 01:40:58 | NULL| 2014-05-20 01:40:58 | NULL
| Allocated | NULL |0 | NULL |
NULL | NULL | 1 | NULL | NULL | NULL |
unable to attach new Volume to VM
-
Key: CLOUDSTACK-6631
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.1
Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
Reporter: Kazuhiro Ito
1. I added new volume.
2. I tried to attach the volume to a VM on UI.
3. It failed and the following log appeared.
2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
(http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
command=attachVolumeid=ac7099fb-ac66-4c63-bf1e-ed0e1429f412virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74response=jsonsessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D_=1399861774316
2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
(http-6443-exec-116:null) submit async job-4916 = [
dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:ac7099fb-ac66-4c63-bf1e-ed0e1429f412,sessionkey:TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d,cmdEventType:VOLUME.ATTACH,ctxUserId:3,virtualMachineId:ecdc2c1d-e21e-4c04-962a-4efac1a69a74,httpmethod:GET,_:1399861774316,ctxAccountId:3,ctxStartEventId:34276},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
(http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
command=attachVolumeid=ac7099fb-ac66-4c63-bf1e-ed0e1429f412virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74response=jsonsessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D_=1399861774316
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002698#comment-14002698 ] Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/20/14 1:47 AM: --- At first, I tried as both a user and a root admin, the same result. And I tried via both UI and createVolume API, but the same result. pool_id and path is NULL. See the followings. [root@x01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520 diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242 zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d SEND URL: https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolumename=TESTVOL0520diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5dapikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyAsignature=mFAoQ5bAfuIjV07A%2BSP%2FE6AVELg%3D % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 103 207 103 2070 0 1334 0 --:--:-- --:--:-- --:--:-- 2250 ?xml version=1.0 encoding=UTF-8? createvolumeresponse cloud-stack-version=4.2.1 id889fff9b-833d-423d-b295-ae16ed9a10da/id jobidc5a2a669-98da-4cc6-bad0-d37f63111e86/jobid /createvolumeresponse | id | account_id | domain_id | pool_id | last_pool_id | instance_id | device_id | name| uuid | size | folder | path | pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type | disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable | created | attached| updated | removed | state | chain_info | update_count | disk_type | vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops | | 1727 | 2 | 1 |NULL | NULL |NULL | NULL | TESTVOL0520 | 889fff9b-833d-423d-b295-ae16ed9a10da | 10995116277760 | NULL| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL | 29 |NULL | NULL | 0 | 2014-05-20 01:40:58 | NULL| 2014-05-20 01:40:58 | NULL | Allocated | NULL |0 | NULL | NULL | NULL | 1 | NULL | NULL | NULL | was (Author: itokaz): At first, I tried as both a user and a root admin, the same result. And I tried via both UI and createVolume API, but the same result. [root@x01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520 diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242 zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d SEND URL: https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolumename=TESTVOL0520diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5dapikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyAsignature=mFAoQ5bAfuIjV07A%2BSP%2FE6AVELg%3D % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 103 207 103 2070 0 1334 0 --:--:-- --:--:-- --:--:-- 2250 ?xml version=1.0 encoding=UTF-8? createvolumeresponse cloud-stack-version=4.2.1 id889fff9b-833d-423d-b295-ae16ed9a10da/id jobidc5a2a669-98da-4cc6-bad0-d37f63111e86/jobid /createvolumeresponse | id | account_id | domain_id | pool_id | last_pool_id | instance_id | device_id | name| uuid | size | folder | path | pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type | disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable | created | attached| updated | removed | state | chain_info | update_count | disk_type | vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops | | 1727 | 2 | 1 |NULL | NULL |NULL | NULL | TESTVOL0520 | 889fff9b-833d-423d-b295-ae16ed9a10da | 10995116277760 | NULL| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL | 29 |NULL | NULL | 0 | 2014-05-20 01:40:58 | NULL| 2014-05-20 01:40:58 | NULL | Allocated | NULL |0 | NULL | NULL | NULL | 1 | NULL | NULL | NULL | unable to attach new Volume to VM
[jira] [Created] (CLOUDSTACK-6711) unable to set proper domain via createVolume API
Kazuhiro Ito created CLOUDSTACK-6711: Summary: unable to set proper domain via createVolume API Key: CLOUDSTACK-6711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6711 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.1 Environment: CloudStack 4.2.1 + KVM on CentOS 6.4 Reporter: Kazuhiro Ito I tested createVolume API as the followings. [root@01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520-a account=Remote-Users domainid=2 diskofferingid=30 zoneid=1 SEND URL: https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolumename=TESTVOL0520-aaccount=Remote-Usersdomainid=2diskofferingid=30zoneid=1apikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyAsignature=qYanjN9AW7eMF6A%2FVg5iVjfrYU0%3D % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 103 207 103 2070 0949 0 --:--:-- --:--:-- --:--:-- 1370 ?xml version=1.0 encoding=UTF-8? createvolumeresponse cloud-stack-version=4.2.1 id971ead2e-cea5-4d3f-b45a-4270d64d63f2/id jobid89bc3ef4-0146-4cef-a15e-3ccb2ba6d987/jobid /createvolumeresponse domainid 2 is not root domain. but when I check on UI, the volume's domain is ROOT. I tried uuid as domainid, but the same result. createVolume API of 4.2.1 cannot set domain properly? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-796) QA - User Provided hostname to be specified in vCenter instead of CS generated name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-796: Assignee: Kiran Koneti QA - User Provided hostname to be specified in vCenter instead of CS generated name Key: CLOUDSTACK-796 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-796 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: Kiran Koneti Fix For: 4.2.0 QA tasks to include - QA Test plan should be linked to 41 release - Upload Test results done on feature branch - Also make sure to do sanity testing and upload test results for it for ASF 41 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6712) NPE in findJobInstanceUuid() in ApiDBUtils
Murali Reddy created CLOUDSTACK-6712: Summary: NPE in findJobInstanceUuid() in ApiDBUtils Key: CLOUDSTACK-6712 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6712 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 NPE in findJobInstanceUuid() in ApiDBUtils. There is no check that 'job.getInstanceId() == null' before trying to get instance UUID from the job. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6712) NPE in findJobInstanceUuid() in ApiDBUtils
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002803#comment-14002803 ] ASF subversion and git services commented on CLOUDSTACK-6712: - Commit 497f5e53725c30442040805a3ad42a81ee926f50 in cloudstack's branch refs/heads/4.4-forward from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=497f5e5 ] CLOUDSTACK-6712: NPE in findJobInstanceUuid() in ApiDBUtils NPE in findJobInstanceUuid() in ApiDBUtils -- Key: CLOUDSTACK-6712 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6712 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 NPE in findJobInstanceUuid() in ApiDBUtils. There is no check that 'job.getInstanceId() == null' before trying to get instance UUID from the job. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6712) NPE in findJobInstanceUuid() in ApiDBUtils
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002806#comment-14002806 ] ASF subversion and git services commented on CLOUDSTACK-6712: - Commit 965346cad15a03d8cf7ffc12460ffd8ecaf35bf1 in cloudstack's branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=965346c ] CLOUDSTACK-6712: NPE in findJobInstanceUuid() in ApiDBUtils NPE in findJobInstanceUuid() in ApiDBUtils -- Key: CLOUDSTACK-6712 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6712 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 NPE in findJobInstanceUuid() in ApiDBUtils. There is no check that 'job.getInstanceId() == null' before trying to get instance UUID from the job. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6712) NPE in findJobInstanceUuid() in ApiDBUtils
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-6712. -- Resolution: Fixed NPE in findJobInstanceUuid() in ApiDBUtils -- Key: CLOUDSTACK-6712 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6712 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 NPE in findJobInstanceUuid() in ApiDBUtils. There is no check that 'job.getInstanceId() == null' before trying to get instance UUID from the job. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6713) NumberFormatException for NetworkUsage command
Sanjeev N created CLOUDSTACK-6713:
-
Summary: NumberFormatException for NetworkUsage command
Key: CLOUDSTACK-6713
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6713
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, Network Controller
Affects Versions: 4.4.0
Environment: Latest build from 4.4 branch with commit
e6961fd21bb6d793302c234d0f409f66dc498072
Reporter: Sanjeev N
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.rar
NumberFormatException for NetworkUsage command
Steps to reproduce:
===
1.Bringup CS in advanced zone with xen cluster
2.Create an isolated network with default offering
3.Deploy vms in the above created network
4.Verify the MS logs when NetworkUsageCommand gets executed.
Result:
==
Observed follwoing error messages:
2014-05-20 07:06:10,395 DEBUG [c.c.a.m.AgentManagerImpl]
(RouterMonitor-1:ctx-f553d26b) Details from executing class
com.cloud.agent.api.NetworkUsageCommand:
2014-05-20 07:06:10,412 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-39256528) Seq 2-17451448556062862: Executing request
2014-05-20 07:06:10,416 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-39256528) Executing command in VR:
/opt/cloud/bin/router_proxy.sh netusage.sh 169.254.1.119 -g
2014-05-20 07:06:10,830 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-39256528) Seq 2-17451448556062862: Response Received:
2014-05-20 07:06:10,831 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-39256528)
Seq 2-17451448556062862: Processing: { Ans: , MgmtId: 7332683579487, via: 2,
Ver: v1, Flags: 10,
[{com.cloud.agent.api.NetworkUsageAnswer:{routerName:r-9-VM,bytesSent:184390,bytesReceived:3345484,result:true,details:,wait:0}}]
}
2014-05-20 07:06:10,831 DEBUG [c.c.a.t.Request] (RouterMonitor-1:ctx-f553d26b)
Seq 2-17451448556062862: Received: { Ans: , MgmtId: 7332683579487, via: 2,
Ver: v1, Flags: 10, { NetworkUsageAnswer } }
2014-05-20 07:06:10,831 DEBUG [c.c.a.m.AgentManagerImpl]
(RouterMonitor-1:ctx-f553d26b) Details from executing class
com.cloud.agent.api.NetworkUsageCommand:
2014-05-20 07:06:10,967 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-409:ctx-0e46d4d0) Seq 2-17451448556062863: Executing request
2014-05-20 07:06:10,971 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-409:ctx-0e46d4d0) Executing command in VR:
/opt/cloud/bin/router_proxy.sh netusage.sh 169.254.2.24 -g
2014-05-20 07:06:11,379 WARN [c.c.h.x.r.XenServer56Resource]
(DirectAgent-409:ctx-0e46d4d0) Failed to get network usage stats due to
java.lang.NumberFormatException: For input string: iptables
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)
at java.lang.Long.init(Long.java:702)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetworkStats(CitrixResourceBase.java:2228)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.execute(XenServer56Resource.java:214)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
at
com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:65)
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-20 07:06:11,383 DEBUG [c.c.a.m.DirectAgentAttache]
[jira] [Updated] (CLOUDSTACK-6713) NumberFormatException for NetworkUsage command
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-6713:
--
Attachment: management-server.rar
Attached MS log file.
NumberFormatException for NetworkUsage command
--
Key: CLOUDSTACK-6713
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6713
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, Network Controller
Affects Versions: 4.4.0
Environment: Latest build from 4.4 branch with commit
e6961fd21bb6d793302c234d0f409f66dc498072
Reporter: Sanjeev N
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.rar
NumberFormatException for NetworkUsage command
Steps to reproduce:
===
1.Bringup CS in advanced zone with xen cluster
2.Create an isolated network with default offering
3.Deploy vms in the above created network
4.Verify the MS logs when NetworkUsageCommand gets executed.
Result:
==
Observed follwoing error messages:
2014-05-20 07:06:10,395 DEBUG [c.c.a.m.AgentManagerImpl]
(RouterMonitor-1:ctx-f553d26b) Details from executing class
com.cloud.agent.api.NetworkUsageCommand:
2014-05-20 07:06:10,412 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-39256528) Seq 2-17451448556062862: Executing request
2014-05-20 07:06:10,416 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-39256528) Executing command in VR:
/opt/cloud/bin/router_proxy.sh netusage.sh 169.254.1.119 -g
2014-05-20 07:06:10,830 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-39256528) Seq 2-17451448556062862: Response Received:
2014-05-20 07:06:10,831 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-39256528)
Seq 2-17451448556062862: Processing: { Ans: , MgmtId: 7332683579487, via: 2,
Ver: v1, Flags: 10,
[{com.cloud.agent.api.NetworkUsageAnswer:{routerName:r-9-VM,bytesSent:184390,bytesReceived:3345484,result:true,details:,wait:0}}]
}
2014-05-20 07:06:10,831 DEBUG [c.c.a.t.Request]
(RouterMonitor-1:ctx-f553d26b) Seq 2-17451448556062862: Received: { Ans: ,
MgmtId: 7332683579487, via: 2, Ver: v1, Flags: 10, { NetworkUsageAnswer } }
2014-05-20 07:06:10,831 DEBUG [c.c.a.m.AgentManagerImpl]
(RouterMonitor-1:ctx-f553d26b) Details from executing class
com.cloud.agent.api.NetworkUsageCommand:
2014-05-20 07:06:10,967 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-409:ctx-0e46d4d0) Seq 2-17451448556062863: Executing request
2014-05-20 07:06:10,971 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-409:ctx-0e46d4d0) Executing command in VR:
/opt/cloud/bin/router_proxy.sh netusage.sh 169.254.2.24 -g
2014-05-20 07:06:11,379 WARN [c.c.h.x.r.XenServer56Resource]
(DirectAgent-409:ctx-0e46d4d0) Failed to get network usage stats due to
java.lang.NumberFormatException: For input string: iptables
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)
at java.lang.Long.init(Long.java:702)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetworkStats(CitrixResourceBase.java:2228)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.execute(XenServer56Resource.java:214)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
at
com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:65)
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
[jira] [Assigned] (CLOUDSTACK-6629) [Automation] Service offering test cases failing with error Check provisionig type in createServiceOffering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri reassigned CLOUDSTACK-6629:
Assignee: Srikanteswararao Talluri
[Automation] Service offering test cases failing with error Check
provisionig type in createServiceOffering
-
Key: CLOUDSTACK-6629
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6629
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.4.0
Run BVT test integration.smoke.test_disk_offerings suite
Test cases failing with below error
Error Message
Check provisionig type in createServiceOffering
begin captured stdout -
=== TestName: test_04_create_fat_type_disk_offering | Status : FAILED ===
- end captured stdout --
begin captured logging
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
STARTED : TC: test_04_create_fat_type_disk_offering :::
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Payload: {'apiKey':
u'leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA',
'name': 'Fat Type Disk offering', 'command': 'createDiskOffering',
'disksize': 1, 'signature': 'xUsXj0HkgkDrfwTTv1sRU+Pxdz0=', 'displaytext':
'Fat Type Disk offering', 'response': 'json'}
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Sending GET Cmd : createDiskOffering===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.49.195
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cAname=Fat+Type+Disk+offeringcommand=createDiskOfferingdisksize=1signature=xUsXj0HkgkDrfwTTv1sRU%2BPxdz0%3Ddisplaytext=Fat+Type+Disk+offeringresponse=json
HTTP/1.1 200 291
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Response : {iscustomized : False, name : u'Fat Type Disk offering', created :
u'2014-05-11T00:03:40-0700', storagetype : u'shared', displaytext : u'Fat
Type Disk offering', disksize : 1, id :
u'eb697298-f969-41dd-a7c2-8426cdcb17be', displayoffering : True}
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Created Disk offering with ID: eb697298-f969-41dd-a7c2-8426cdcb17be
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Payload: {'apiKey':
u'leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA',
'id': u'eb697298-f969-41dd-a7c2-8426cdcb17be', 'command':
'listDiskOfferings', 'signature': '6YyaurkycNHqoKtas5aoAY7J3k0=', 'response':
'json'}
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Sending GET Cmd : listDiskOfferings===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.49.195
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cAid=eb697298-f969-41dd-a7c2-8426cdcb17becommand=listDiskOfferingssignature=6YyaurkycNHqoKtas5aoAY7J3k0%3Dresponse=json
HTTP/1.1 200 304
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Response : [{iscustomized : False, name : u'Fat Type Disk offering', created
: u'2014-05-11T00:03:40-0700', storagetype : u'shared', displaytext : u'Fat
Type Disk offering', disksize : 1, id :
u'eb697298-f969-41dd-a7c2-8426cdcb17be', displayoffering : True}]
test_04_create_fat_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): CRITICAL:
FAILED: test_04_create_fat_type_disk_offering: ['Traceback (most recent call
last):\n', ' File /usr/local/lib/python2.7/unittest/case.py, line 318, in
run\ntestMethod()\n', ' File
/Repo_30X/ipcl/cloudstack/test/integration/smoke/test_disk_offerings.py,
line 169, in test_04_create_fat_type_disk_offering\nCheck provisionig
type in createServiceOffering\n', ' File
