[jira] [Created] (CLOUDSTACK-8593) [Marvin] set __testName if it is not assigned a proper name in the test flow
Srikanteswararao Talluri created CLOUDSTACK-8593: Summary: [Marvin] set __testName if it is not assigned a proper name in the test flow Key: CLOUDSTACK-8593 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8593 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.6.0 2015-06-26 11:36:54,094 - CRITICAL - EXCEPTION: Failure:: ['Traceback (most recent call last):\n', ' File /usr/lib/python2.7/site-packages/nose/case.py, line 132, in run\n self.beforeTest(result)\n', ' File /usr/lib/python2.7/site-packages/nose/case.py, line 74, in beforeTest\nbeforeTest(self.test)\n', ' File /usr/lib/python2.7/site-packages/nose/proxy.py, line 117, in beforeTest\nself.plugins.beforeTest(self.test)\n', ' File /usr/lib/python2.7/site-packages/nose/plugins/manager.py, line 99, in __call__\nreturn self.call(*arg, **kw)\n', ' File /usr/lib/python2.7/site-packages/nose/plugins/manager.py, line 167, in simple\nresult = meth(*arg, **kw)\n', ' File /usr/lib/python2.7/site-packages/Marvin-4.6.0_SNAPSHOT-py2.7.egg/marvin/marvinPlugin.py, line 172, in beforeTest\njoin([self.__identifier, self.__testName])\n', 'TypeError: sequence item 0: expected string, NoneType found\n'] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8378) add test setup health check script to the smoke test
Srikanteswararao Talluri created CLOUDSTACK-8378: Summary: add test setup health check script to the smoke test Key: CLOUDSTACK-8378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8378 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri add test setup health check script to the smoke test - which checks for the state of system VMs - which checks for the state of default builtin template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8378) add test setup health check script to the smoke test
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-8378. Resolution: Fixed closing this bug as the script is already available under tools/marvin/marvin add test setup health check script to the smoke test Key: CLOUDSTACK-8378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8378 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri add test setup health check script to the smoke test - which checks for the state of system VMs - which checks for the state of default builtin template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8379) add support to marvin to enable deployed zone based on the value provided in config file
Srikanteswararao Talluri created CLOUDSTACK-8379:
Summary: add support to marvin to enable deployed zone based on
the value provided in config file
Key: CLOUDSTACK-8379
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8379
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: marvin
Affects Versions: 4.6.0
Reporter: Srikanteswararao Talluri
Assignee: Srikanteswararao Talluri
Fix For: 4.6.0
add support to marvin to enable deployed zone based on the value provided in
config file
if under zone section, if the 'enabled' element is not mentioned, then zone
will be enabled otherwise zone will be enabled/disabled based on value provided
('false' or 'true') for 'enabled'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8352) [marvin] Integrate vcenter communication through marvin
Srikanteswararao Talluri created CLOUDSTACK-8352: Summary: [marvin] Integrate vcenter communication through marvin Key: CLOUDSTACK-8352 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8352 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.6.0 Marvin should be able to get details of host, vm, dvswitch etc., from vcenter. This is going to be implemented using vmware sdk for python pyvmomi. Usage: vc_object = Vcenter(x.x.x.x, username, password) print '###get one dc' print(vc_object.get_datacenters(name='testDC')) print '###get multiple dcs' for i in vc_object.get_datacenters(): print print '###get one dv' print vc_object.get_dvswitches(name='dvSwitch') print '###get multiple dvs' for i in vc_object.get_dvswitches(): print print '###get one dvportgroup' print(vc_object.get_dvportgroups(name='cloud.guest.207.200.1-dvSwitch')) print ###get one dvportgroup and the vms associated with it for vm in vc_object.get_dvportgroups(name='cloud.guest.207.200.1-dvSwitch')[0]['dvportgroup']['vmlist']: print(vm.name) print(vm.network) print '###get multiple dvportgroups' for i in vc_object.get_dvportgroups(): print print vc_object.get_vms(name='VM1') -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8161) [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14324170#comment-14324170 ] Srikanteswararao Talluri edited comment on CLOUDSTACK-8161 at 2/17/15 1:35 PM: --- Yes [~bhaisaab], I can bring these changes into 4.5, before doing that I want to get some other changes too. was (Author: talluri): Yes https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bhaisaab, I can bring these changes into 4.5, before doing that I want to get some other changes too. [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available Key: CLOUDSTACK-8161 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8161 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: LXC Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 mark the data volume related operations as skipped if RBD storage pool is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8161) [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14324170#comment-14324170 ] Srikanteswararao Talluri edited comment on CLOUDSTACK-8161 at 2/17/15 1:34 PM: --- Yes https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bhaisaab, I can bring these changes into 4.5, before doing that I want to get some other changes too. was (Author: talluri): Yes ~bhaisaab, I can bring these changes into 4.5, before doing that I want to get some other changes too. [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available Key: CLOUDSTACK-8161 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8161 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: LXC Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 mark the data volume related operations as skipped if RBD storage pool is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8161) [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14324170#comment-14324170 ] Srikanteswararao Talluri edited comment on CLOUDSTACK-8161 at 2/17/15 1:33 PM: --- Yes ~rohityadav, I can bring these changes into 4.5, before doing that I want to get some other changes too. was (Author: talluri): Yes, I can bring these changes into 4.5, before doing that I want to get some other changes too. [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available Key: CLOUDSTACK-8161 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8161 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: LXC Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 mark the data volume related operations as skipped if RBD storage pool is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8161) [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14324170#comment-14324170 ] Srikanteswararao Talluri edited comment on CLOUDSTACK-8161 at 2/17/15 1:34 PM: --- Yes ~bhaisaab, I can bring these changes into 4.5, before doing that I want to get some other changes too. was (Author: talluri): Yes ~rohityadav, I can bring these changes into 4.5, before doing that I want to get some other changes too. [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available Key: CLOUDSTACK-8161 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8161 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: LXC Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 mark the data volume related operations as skipped if RBD storage pool is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8161) [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14324170#comment-14324170 ] Srikanteswararao Talluri commented on CLOUDSTACK-8161: -- Yes, I can bring these changes into 4.5, before doing that I want to get some other changes too. [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available Key: CLOUDSTACK-8161 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8161 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: LXC Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 mark the data volume related operations as skipped if RBD storage pool is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8229) [marvin] add zone wide primary storage support to deployDataCenter
Srikanteswararao Talluri created CLOUDSTACK-8229: Summary: [marvin] add zone wide primary storage support to deployDataCenter Key: CLOUDSTACK-8229 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8229 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.6.0 marvin deployDataCenter should be able to handle 'scope' attribute p rovided in configuration file and deploy zone using zone wide primary storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8229) [marvin] add zone wide primary storage support to deployDataCenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-8229. [marvin] add zone wide primary storage support to deployDataCenter -- Key: CLOUDSTACK-8229 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8229 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.6.0 marvin deployDataCenter should be able to handle 'scope' attribute p rovided in configuration file and deploy zone using zone wide primary storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8229) [marvin] add zone wide primary storage support to deployDataCenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-8229. -- Resolution: Fixed [marvin] add zone wide primary storage support to deployDataCenter -- Key: CLOUDSTACK-8229 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8229 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.6.0 marvin deployDataCenter should be able to handle 'scope' attribute p rovided in configuration file and deploy zone using zone wide primary storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8161) [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available
Srikanteswararao Talluri created CLOUDSTACK-8161: Summary: [Automation]: mark the data volume related operations on LXC as skipped if RBD storage pool is not available Key: CLOUDSTACK-8161 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8161 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: LXC Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 mark the data volume related operations as skipped if RBD storage pool is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-4587) VM is failing to deploy on a Legacy zone after adding zone wide primary storage and moving cluster wide primary storage to maintenance mode
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-4587. After moving the cluster scoped primary storages into maintenance mode, SystemVMs came up on zone wide primary storage. Hence, closing the bug. VM is failing to deploy on a Legacy zone after adding zone wide primary storage and moving cluster wide primary storage to maintenance mode Key: CLOUDSTACK-4587 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4587 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.1 Reporter: Sailaja Mada Assignee: Likitha Shetty Fix For: 4.5.0 Attachments: failureloigs.rar, logs.rar, vmdeploylogs.rar Steps: 1. Upgraded from 307 to 4.2 using VMWARE Cluster with Cluster level primary storage 2. Add Zone wide primary storage after upgrade 3. Move the cluster level scope storage to Maintenance mode 4. Try to deploy new VM. Observation: VM is failing to deploy on a Legacy zone after adding zone wide primary storage and moving cluster wide primary storage to maintenance mode 2013-09-01 14:21:10,323 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Network id=207 is already implemented 2013-09-01 14:21:10,354 DEBUG [network.guru.PodBasedNetworkGuru] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Allocated a nic NicProfile[119-35-4a8f547b-7bff-4b3f-ba10-b0146af4d1bb-10.102.195.111-null for VM[DomainRouter|r-35-VM] 2013-09-01 14:21:10,390 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Checking if we need to prepare 1 volumes for VM[DomainRouter|r-35-VM] 2013-09-01 14:21:10,400 DEBUG [storage.image.TemplateDataFactoryImpl] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) template 203 is already in store:2, type:Image 2013-09-01 14:21:10,409 DEBUG [storage.image.TemplateDataFactoryImpl] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) template 203 is already in store:203, type:Primary 2013-09-01 14:21:10,410 DEBUG [storage.volume.VolumeServiceImpl] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Found template 203-2-3cfe22ca-3a33-39a0-bf5e-0dab154869fd in storage pool 203 with VMTemplateStoragePool id: 11 2013-09-01 14:21:10,421 DEBUG [storage.volume.VolumeServiceImpl] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Acquire lock on VMTemplateStoragePool 11 with timeout 3600 seconds 2013-09-01 14:21:10,423 INFO [storage.volume.VolumeServiceImpl] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) lock is acquired for VMTemplateStoragePool 11 2013-09-01 14:21:10,431 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) copyAsync inspecting src type TEMPLATE copyAsync inspecting dest type TEMPLATE 2013-09-01 14:21:10,519 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) copy object failed: java.lang.NullPointerException at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyObject(AncientDataMotionStrategy.java:210) at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:411) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:55) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:440) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:569) at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2536) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2592) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2740) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1872) at
[jira] [Closed] (CLOUDSTACK-6853) Fail to remove the network when VM that used to run on this network (but not anymore) still exist
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-6853. Verified. Closing the bug Fail to remove the network when VM that used to run on this network (but not anymore) still exist - Key: CLOUDSTACK-6853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Priority: Critical Fix For: 4.4.0 Steps to reproduce: 1) Create 2 networks 2) Deploy vm in network1. 3) Add vm to network2 using addNic api. 4) Remove vm from network2 using removeNic api. Try to remove the network2. The removal should be successful as there are no vms belong to it anymore. Bug: the network fails to remove, and the error message says that there is a vm (created on step2) still belonging to the network. Its a bug in the DB search method where we look for the VM in a particular network. In this case we do joins between table1=user_vm and table2=nics based on instance_id. As long as the result in table1 (vm) is not removed, its being returned to the user when the matching record is found in table2, no matter if the record in table2 is removed or not. It just has to exist there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6426) Event Bus no longer receives events for AsyncJobs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri closed CLOUDSTACK-6426.
Assignee: Srikanteswararao Talluri (was: Murali Reddy)
nothing to verify, as this issue can not be reproduced.
Event Bus no longer receives events for AsyncJobs
-
Key: CLOUDSTACK-6426
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6426
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.3.0, 4.4.0
Reporter: David Grizzanti
Assignee: Srikanteswararao Talluri
It appears that as of 4.3, the async job manager no longer publishes messages
to the event bus for async jobs. Prior to 4.3, messages for
starting/completing AsyncJob were published to the Event Bus.
Example:
Event {:source=management-server, :type=AsyncJobEvent,
:action=submit, :resource_type=None, :resource_id=*}
{instanceType=None, jobId=e52fe236-9109-49f2-96e9-02cc1bebf3f8,
processStatus=0, commandEventType=NIC.CREATE, resultCode=0,
command=org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd,
account=b32dc958-b904-11e3-b3f0-080027079e3d,
user=b32e02b0-b904-11e3-b3f0-080027079e3d}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7865) [Automation] Fix the script /maint/test_bugs.py - Missing attributes used in class
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri resolved CLOUDSTACK-7865.
--
Resolution: Fixed
[Automation] Fix the script /maint/test_bugs.py - Missing attributes used
in class
Key: CLOUDSTACK-7865
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7865
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
I see the following errors in execution of two test cases in test_bugs.py:
*First Error*:
{noformat}
Stacktrace
File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
File /root/cloudstack/test/integration/component/maint/test_bugs.py, line
396, in test_CLOUDSTACK_6181_stoppedvm_root_resize
virtualmachineid=self.virtual_machine.id,
'\'Test42xBugsMgmtSvr\' object has no attribute \'virtual_machine\'\n
{noformat}
*Second Error*
{noformat}
Stacktrace
File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
File /root/cloudstack/test/integration/component/maint/test_bugs.py, line
464, in test_CLOUDSTACK_6181_vm_root_resize
virtualmachineid=self.virtual_machine.id,
'\'Test42xBugsMgmtSvr\' object has no attribute \'virtual_machine\'\n
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7865) [Automation] Fix the script /maint/test_bugs.py - Missing attributes used in class
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri closed CLOUDSTACK-7865.
[Automation] Fix the script /maint/test_bugs.py - Missing attributes used
in class
Key: CLOUDSTACK-7865
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7865
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
I see the following errors in execution of two test cases in test_bugs.py:
*First Error*:
{noformat}
Stacktrace
File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
File /root/cloudstack/test/integration/component/maint/test_bugs.py, line
396, in test_CLOUDSTACK_6181_stoppedvm_root_resize
virtualmachineid=self.virtual_machine.id,
'\'Test42xBugsMgmtSvr\' object has no attribute \'virtual_machine\'\n
{noformat}
*Second Error*
{noformat}
Stacktrace
File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
File /root/cloudstack/test/integration/component/maint/test_bugs.py, line
464, in test_CLOUDSTACK_6181_vm_root_resize
virtualmachineid=self.virtual_machine.id,
'\'Test42xBugsMgmtSvr\' object has no attribute \'virtual_machine\'\n
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7899) [NetAppVSC]Unable to resize a volume
Srikanteswararao Talluri created CLOUDSTACK-7899: Summary: [NetAppVSC]Unable to resize a volume Key: CLOUDSTACK-7899 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7899 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Unable to resize a volume residing on storage provisioned by netapp VSC. Resize is going on forever. This is completed quickly when I tried to resize a volume on a non-netapp provisioned volume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7900) [NetAppVSC]Unable to download a volume
Srikanteswararao Talluri created CLOUDSTACK-7900:
Summary: [NetAppVSC]Unable to download a volume
Key: CLOUDSTACK-7900
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7900
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: 4.4.0
Reporter: Srikanteswararao Talluri
Unable to download a volume residing on storage provisioned by netapp VSC.
2014-05-13 23:05:17,275 DEBUG [c.c.a.t.Request] (API-Job-Executor-29:job-278
ctx-6acf5903) Seq 6-722141364: Received: { Ans: , MgmtId: 6777458393139, via:
6, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2014-05-13 23:05:17,322 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-29:job-278) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
com.cloud.exception.UnsupportedServiceException: Extract entity url is not yet
supported for this image store provider.
at
com.netapp.kanto.storagesubsystem.NetAppDataStoreDriver.createEntityExtractUrl(NetAppDataStoreDriver.java:329)
at
org.apache.cloudstack.storage.image.store.ImageStoreImpl.createEntityExtractUrl(ImageStoreImpl.java:204)
at
com.cloud.storage.VolumeApiServiceImpl.extractVolume(VolumeApiServiceImpl.java:1936)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy213.extractVolume(Unknown Source)
at
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:131)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:97)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:495)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:50)
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:47)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:452)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-05-13 23:05:17,325 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-29:job-278) Complete async job-278, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Extract
entity url is not yet supported for this image store provider.}
2014-05-13 23:05:17,344 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-29:job-278) Done executing
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd for job-278
2014-05-13 23:05:17,356 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-29:job-278) Remove job-278 from job m
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7901) [NetAppVSC]Unable to create deployment on NetApp VSC provisioned primary storage
Srikanteswararao Talluri created CLOUDSTACK-7901: Summary: [NetAppVSC]Unable to create deployment on NetApp VSC provisioned primary storage Key: CLOUDSTACK-7901 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7901 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Unable to create VM on storage provisioned by netapp VSC. VM deployment was succesful on a non netapp vsc provisioned storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-5352) CPU cap calculated incorrectly for VMs on XenServer hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-5352. CPU cap calculated incorrectly for VMs on XenServer hosts - Key: CLOUDSTACK-5352 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5352 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.3.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.3.0 The CPU cap assigned to VMs on XenServer hosts (via VCPUs-params parameter) is not calculated correctly. The assigned values are too low and can result in performance problems. This seems related to CPU overprovisioning. The assigned CPU cap is approximately the expected cap / CPU overprovisioning value. The customer is using CloudStack 4.2.0 with XenServer 6.1. On the customer environment they have several VMs that were created before upgrading to 4.2.0 from 3.0.6 and never rebooted, and those VMs appear to have the expected CPU cap. I see similar results on a CS 4.2.1 setup with a XS 6.2 host with 1x E31220L CPU – 2x physical cores / 4x logical cores (with hyperthreading) at 2.20GHz – 8800 MHz total (confirmed in op_host_capacity), a Compute Offering with 2200 MHz and 4 cores gives a VM with: [root@csdemo-xen2 ~]# xe vm-list params=name-label,uuid,VCPUs-params name-label=i-2-87-VM uuid ( RO) : 7cd5893e-728a-a0f3-c2cf-f3464cb8b9cb name-label ( RW): i-2-87-VM VCPUs-params (MRW): weight: 84; cap: 131 And with a Compute Offering with 2200 MHz and 1 core gives a VM with: [root@csdemo-xen2 ~]# xe vm-list params=name-label,uuid,VCPUs-params name-label=i-2-87-VM uuid ( RO) : c17cd63a-f6d5-8f76-d7f1-eb34d574e0dd name-label ( RW): i-2-87-VM VCPUs-params (MRW): weight: 84; cap: 32 The configured cap does not make sense in either example. In this environment, cpu.overprovisioning.factor is 3 for the cluster and 1 in Global Settings. In example 1 the cap should be: 2200 * 0.99 * 4 / 2200 * 100 = 396 But it is: 2200 * 0.99 * 4 / (3*2200) * 100 = 132 For example 2 it should be: 2200 * 0.99 * 1 / 2200 * 100 = 99 But it is: 2200 * 0.99 * 1 / (3*2200) * 100 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5352) CPU cap calculated incorrectly for VMs on XenServer hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206381#comment-14206381 ] Srikanteswararao Talluri commented on CLOUDSTACK-5352: -- Verified on 4.5 1. compute offering:500MHZ CPU,1 core,CPU cap-enabled. Host speed:4 core with 2.3 GHZ. cpu cap= [(speed*vcpu*0.99)/hostspeed ]*100 cpu cap=500MHz*1*0.99/2300MHZ *100=21.5 [root@Rack1Pod1Host29 ~]# xe vm-list params=name-label,uuid,VCPUs-params name-label=i-2-19-VM uuid ( RO) : b2246b3b-8eb9-f835-10a9-53d535873b6c name-label ( RW): i-2-19-VM VCPUs-params (MRW): weight: 17; cap: 20 2. compute offering:500MHZ CPU,3 core,CPU cap-enabled. Host speed:4 core with 2.3 GHZ cpu cap=500MHz*3*0.99/2300MHZ *100=64.5 [root@Rack1Pod1Host29 ~]# xe vm-list params=name-label,uuid,VCPUs-params name-label=i-2-20-VM uuid ( RO) : ebc11adb-25fa-1b97-b449-f2ca8b0e6e99 name-label ( RW): i-2-20-VM VCPUs-params (MRW): weight: 17; cap: 62 CPU cap calculated incorrectly for VMs on XenServer hosts - Key: CLOUDSTACK-5352 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5352 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.3.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.3.0 The CPU cap assigned to VMs on XenServer hosts (via VCPUs-params parameter) is not calculated correctly. The assigned values are too low and can result in performance problems. This seems related to CPU overprovisioning. The assigned CPU cap is approximately the expected cap / CPU overprovisioning value. The customer is using CloudStack 4.2.0 with XenServer 6.1. On the customer environment they have several VMs that were created before upgrading to 4.2.0 from 3.0.6 and never rebooted, and those VMs appear to have the expected CPU cap. I see similar results on a CS 4.2.1 setup with a XS 6.2 host with 1x E31220L CPU – 2x physical cores / 4x logical cores (with hyperthreading) at 2.20GHz – 8800 MHz total (confirmed in op_host_capacity), a Compute Offering with 2200 MHz and 4 cores gives a VM with: [root@csdemo-xen2 ~]# xe vm-list params=name-label,uuid,VCPUs-params name-label=i-2-87-VM uuid ( RO) : 7cd5893e-728a-a0f3-c2cf-f3464cb8b9cb name-label ( RW): i-2-87-VM VCPUs-params (MRW): weight: 84; cap: 131 And with a Compute Offering with 2200 MHz and 1 core gives a VM with: [root@csdemo-xen2 ~]# xe vm-list params=name-label,uuid,VCPUs-params name-label=i-2-87-VM uuid ( RO) : c17cd63a-f6d5-8f76-d7f1-eb34d574e0dd name-label ( RW): i-2-87-VM VCPUs-params (MRW): weight: 84; cap: 32 The configured cap does not make sense in either example. In this environment, cpu.overprovisioning.factor is 3 for the cluster and 1 in Global Settings. In example 1 the cap should be: 2200 * 0.99 * 4 / 2200 * 100 = 396 But it is: 2200 * 0.99 * 4 / (3*2200) * 100 = 132 For example 2 it should be: 2200 * 0.99 * 1 / 2200 * 100 = 99 But it is: 2200 * 0.99 * 1 / (3*2200) * 100 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7824) systemvm generation failures
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7824. -- Resolution: Fixed systemvm generation failures Key: CLOUDSTACK-7824 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7824 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.5.0 There was an issue related to openswan installation on debian 7.6.0 and uuencode missing on the vm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7824) systemvm generation failures
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-7824. systemvm generation failures Key: CLOUDSTACK-7824 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7824 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.5.0 There was an issue related to openswan installation on debian 7.6.0 and uuencode missing on the vm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7824) systemvm generation failures
Srikanteswararao Talluri created CLOUDSTACK-7824: Summary: systemvm generation failures Key: CLOUDSTACK-7824 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7824 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.5.0 There was an issue related to openswan installation on debian 7.6.0 and uuencode missing on the vm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7817) use debian 7.7.0 in the creation of system vm template
Srikanteswararao Talluri created CLOUDSTACK-7817: Summary: use debian 7.7.0 in the creation of system vm template Key: CLOUDSTACK-7817 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7817 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.1 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.2.1 Update the URL to point to debian7.7.0 in the definition.rb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7817) use debian 7.7.0 in the creation of system vm template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7817. -- Resolution: Fixed use debian 7.7.0 in the creation of system vm template -- Key: CLOUDSTACK-7817 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7817 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.1 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.2.1 Update the URL to point to debian7.7.0 in the definition.rb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7817) use debian 7.7.0 in the creation of system vm template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-7817. use debian 7.7.0 in the creation of system vm template -- Key: CLOUDSTACK-7817 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7817 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.1 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.2.1 Update the URL to point to debian7.7.0 in the definition.rb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7053) [Automation] Tasks for writing automated test cases for few product bugs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-7053. [Automation] Tasks for writing automated test cases for few product bugs Key: CLOUDSTACK-7053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7053 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7053) [Automation] Tasks for writing automated test cases for few product bugs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7053. -- Resolution: Fixed [Automation] Tasks for writing automated test cases for few product bugs Key: CLOUDSTACK-7053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7053 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7390) [Automation] Fix the script test_bugs.py - Invalid Parameters
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri reassigned CLOUDSTACK-7390:
Assignee: Srikanteswararao Talluri (was: Gaurav Aradhye)
[Automation] Fix the script test_bugs.py - Invalid Parameters
---
Key: CLOUDSTACK-7390
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7390
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
Script is at: component/maint/.
{code}
@attr(tags=[advanced, basic])
@attr(required_hardware=false)
@attr(configuration='apply.allocation.algorithm.to.pods')
def test_es_47_list_os_types_win_2012(self):
@Desc: Test VM creation while apply.allocation.algorithm.to.pods is
set to true
@Reference: https://issues.apache.org/jira/browse/CLOUDSTACK-4947
@Steps:
Step1: register windows 2012 VM template as windows 8 template
Step2: deploy a VM with windows2012 template and Verify that VM
creation is successful
# register windows 2012 VM template as windows 8 template
self.win2012_template = Template.register(
self.apiClient,
self.services[win2012template],
zoneid=self.zone.id,
account=self.account.name,
domainid=self.domain.id,
hypervisor=self.hypervisor
)
# Wait for template to download
self.win2012_template.download(self.apiClient)
self.cleanup.append(self.win2012_template)
# Wait for template status to be changed across
time.sleep(60)
# Deploy
self.debug(Deploying win 2012 VM in account: %s % self.account.name)
self.services[virtual_machine][displayname] = win2012
self.services[virtual_machine][zoneid] = self.zone.id
self.services[virtual_machine][template] =
self.win2012_template.id
vm1 = VirtualMachine.create(
self.apiClient,
self.services[virtual_machine2],
accountid=self.account.name,
domainid=self.account.domainid,
serviceofferingid=self.service_offering.id,
)
self.cleanup.append(vm1)
# Verify VM state
self.assertEqual(
vm1.state,
'Running',
Check VM state is Running or not
)
return
{code}
Client Error Information:
test_es_47_list_os_types_win_2012
(integration.component.maint.test_bugs.Test42xBugsMgmtSvr): DEBUG:
Sending GET Cmd : listTemplates===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.135.39
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?templatefilter=selfapiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwzoneid=f2acfe0c-c8c8-4353-8f97-a3e0f14d6357command=listTemplatessignature=LjryRXT0OpAYRm%2BuM5slT8BkAh4%3Did=1ee5bf28-5cbe-41e4-ba11-0418ecda39c4response=json
HTTP/1.1 200 847
test_es_47_list_os_types_win_2012
(integration.component.maint.test_bugs.Test42xBugsMgmtSvr): DEBUG: Response :
[{domain : u'ROOT', domainid : u'9d7d4d5c-281e-11e4-b06a-d2bc9de3652e',
ostypename : u'Windows 8 (64-bit)', zoneid :
u'f2acfe0c-c8c8-4353-8f97-a3e0f14d6357', displaytext : u'win2012', ostypeid :
u'9d9979e6-281e-11e4-b06a-d2bc9de3652e', passwordenabled : False, id :
u'1ee5bf28-5cbe-41e4-ba11-0418ecda39c4', size : 34359738368, isready : True,
format : u'OVA', templatetype : u'USER', details : {hypervisortoolsversion :
u'xenserver61'}, zonename : u'XenRT-Zone-0', status : u'Download Complete',
isdynamicallyscalable : False, tags : [], isfeatured : False, sshkeyenabled :
False, isextractable : False, crossZones : False, account :
u'test-a-Test42xBugsMgmtSvr-BJ4H02', name : u'win2012-S1SJ8X', created :
u'2014-08-20T13:24:49+', hypervisor : u'XenServer', ispublic : False,
checksum : u'b31fec1e736b8bc27db9d0f6740c6622'}]
test_es_47_list_os_types_win_2012
(integration.component.maint.test_bugs.Test42xBugsMgmtSvr): DEBUG: Deploying
[jira] [Assigned] (CLOUDSTACK-7389) [Automation] Fix the script test_bugs.py - Unable to find Ostype is required for registering template
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri reassigned CLOUDSTACK-7389:
Assignee: Srikanteswararao Talluri (was: Gaurav Aradhye)
[Automation] Fix the script test_bugs.py - Unable to find Ostype is
required for registering template
---
Key: CLOUDSTACK-7389
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7389
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
Script is at: component/maint/.
{code}
@attr(required_hardware=false)
@attr(storage=s3)
def test_es_1863_register_template_s3_domain_admin_user(self):
@Desc: Test whether cloudstack allows Domain admin or user to
register a template using
S3/Swift object store.
@Steps:
Step1: create a Domain and users in it.
Step2: Register a template as Domain admin.
Step3: Register a template as Domain user.
Step4: Template should be registered successfully.
# Step1: create a Domain and users in it.
self.newdomain = Domain.create(self.apiClient,
self.services[domain])
#create account in the domain
self.account_domain = Account.create(
self.apiClient,
self.services[account],
domainid=self.newdomain.id
)
self.cleanup.append(self.account_domain)
self.cleanup.append(self.newdomain)
# Getting authentication for user in newly created Account in domain
self.domain_user = self.account_domain.user[0]
self.domain_userapiclient =
self.testClient.getUserApiClient(self.domain_user.username,
self.newdomain.name)
# Step2: Register a template as Domain admin.
self.domain_template = Template.register(
self.apiClient,
self.services[templateregister],
zoneid=self.zone.id,
account=self.account_domain.name,
domainid=self.newdomain.id,
hypervisor=self.hypervisor
)
# Wait for template to download
self.domain_template.download(self.api_client)
# Wait for template status to be changed across
time.sleep(60)
# Step3: Register a template as Domain user.
self.domain_user_template = Template.register(
self.domain_userapiclient,
self.services[templateregister],
zoneid=self.zone.id,
account=self.account_domain.name,
domainid=self.newdomain.id,
hypervisor=self.hypervisor
)
{code}
*Error Message*
Unable to find Ostype is required for registering template
begin captured stdout -
=== TestName: test_es_1863_register_template_s3_domain_admin_user | Status :
EXCEPTION ===
- end captured stdout --
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7389) [Automation] Fix the script test_bugs.py - Unable to find Ostype is required for registering template
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri resolved CLOUDSTACK-7389.
--
Resolution: Fixed
[Automation] Fix the script test_bugs.py - Unable to find Ostype is
required for registering template
---
Key: CLOUDSTACK-7389
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7389
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
Script is at: component/maint/.
{code}
@attr(required_hardware=false)
@attr(storage=s3)
def test_es_1863_register_template_s3_domain_admin_user(self):
@Desc: Test whether cloudstack allows Domain admin or user to
register a template using
S3/Swift object store.
@Steps:
Step1: create a Domain and users in it.
Step2: Register a template as Domain admin.
Step3: Register a template as Domain user.
Step4: Template should be registered successfully.
# Step1: create a Domain and users in it.
self.newdomain = Domain.create(self.apiClient,
self.services[domain])
#create account in the domain
self.account_domain = Account.create(
self.apiClient,
self.services[account],
domainid=self.newdomain.id
)
self.cleanup.append(self.account_domain)
self.cleanup.append(self.newdomain)
# Getting authentication for user in newly created Account in domain
self.domain_user = self.account_domain.user[0]
self.domain_userapiclient =
self.testClient.getUserApiClient(self.domain_user.username,
self.newdomain.name)
# Step2: Register a template as Domain admin.
self.domain_template = Template.register(
self.apiClient,
self.services[templateregister],
zoneid=self.zone.id,
account=self.account_domain.name,
domainid=self.newdomain.id,
hypervisor=self.hypervisor
)
# Wait for template to download
self.domain_template.download(self.api_client)
# Wait for template status to be changed across
time.sleep(60)
# Step3: Register a template as Domain user.
self.domain_user_template = Template.register(
self.domain_userapiclient,
self.services[templateregister],
zoneid=self.zone.id,
account=self.account_domain.name,
domainid=self.newdomain.id,
hypervisor=self.hypervisor
)
{code}
*Error Message*
Unable to find Ostype is required for registering template
begin captured stdout -
=== TestName: test_es_1863_register_template_s3_domain_admin_user | Status :
EXCEPTION ===
- end captured stdout --
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7390) [Automation] Fix the script test_bugs.py - Invalid Parameters
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri resolved CLOUDSTACK-7390.
--
Resolution: Fixed
[Automation] Fix the script test_bugs.py - Invalid Parameters
---
Key: CLOUDSTACK-7390
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7390
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
Script is at: component/maint/.
{code}
@attr(tags=[advanced, basic])
@attr(required_hardware=false)
@attr(configuration='apply.allocation.algorithm.to.pods')
def test_es_47_list_os_types_win_2012(self):
@Desc: Test VM creation while apply.allocation.algorithm.to.pods is
set to true
@Reference: https://issues.apache.org/jira/browse/CLOUDSTACK-4947
@Steps:
Step1: register windows 2012 VM template as windows 8 template
Step2: deploy a VM with windows2012 template and Verify that VM
creation is successful
# register windows 2012 VM template as windows 8 template
self.win2012_template = Template.register(
self.apiClient,
self.services[win2012template],
zoneid=self.zone.id,
account=self.account.name,
domainid=self.domain.id,
hypervisor=self.hypervisor
)
# Wait for template to download
self.win2012_template.download(self.apiClient)
self.cleanup.append(self.win2012_template)
# Wait for template status to be changed across
time.sleep(60)
# Deploy
self.debug(Deploying win 2012 VM in account: %s % self.account.name)
self.services[virtual_machine][displayname] = win2012
self.services[virtual_machine][zoneid] = self.zone.id
self.services[virtual_machine][template] =
self.win2012_template.id
vm1 = VirtualMachine.create(
self.apiClient,
self.services[virtual_machine2],
accountid=self.account.name,
domainid=self.account.domainid,
serviceofferingid=self.service_offering.id,
)
self.cleanup.append(vm1)
# Verify VM state
self.assertEqual(
vm1.state,
'Running',
Check VM state is Running or not
)
return
{code}
Client Error Information:
test_es_47_list_os_types_win_2012
(integration.component.maint.test_bugs.Test42xBugsMgmtSvr): DEBUG:
Sending GET Cmd : listTemplates===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.135.39
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?templatefilter=selfapiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwzoneid=f2acfe0c-c8c8-4353-8f97-a3e0f14d6357command=listTemplatessignature=LjryRXT0OpAYRm%2BuM5slT8BkAh4%3Did=1ee5bf28-5cbe-41e4-ba11-0418ecda39c4response=json
HTTP/1.1 200 847
test_es_47_list_os_types_win_2012
(integration.component.maint.test_bugs.Test42xBugsMgmtSvr): DEBUG: Response :
[{domain : u'ROOT', domainid : u'9d7d4d5c-281e-11e4-b06a-d2bc9de3652e',
ostypename : u'Windows 8 (64-bit)', zoneid :
u'f2acfe0c-c8c8-4353-8f97-a3e0f14d6357', displaytext : u'win2012', ostypeid :
u'9d9979e6-281e-11e4-b06a-d2bc9de3652e', passwordenabled : False, id :
u'1ee5bf28-5cbe-41e4-ba11-0418ecda39c4', size : 34359738368, isready : True,
format : u'OVA', templatetype : u'USER', details : {hypervisortoolsversion :
u'xenserver61'}, zonename : u'XenRT-Zone-0', status : u'Download Complete',
isdynamicallyscalable : False, tags : [], isfeatured : False, sshkeyenabled :
False, isextractable : False, crossZones : False, account :
u'test-a-Test42xBugsMgmtSvr-BJ4H02', name : u'win2012-S1SJ8X', created :
u'2014-08-20T13:24:49+', hypervisor : u'XenServer', ispublic : False,
checksum : u'b31fec1e736b8bc27db9d0f6740c6622'}]
test_es_47_list_os_types_win_2012
(integration.component.maint.test_bugs.Test42xBugsMgmtSvr): DEBUG: Deploying
win 2012 VM in account:
[jira] [Assigned] (CLOUDSTACK-7388) [Automation] Fix the script test_redundant_router.py - Script is hardcoded to use password as Host's password
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri reassigned CLOUDSTACK-7388:
Assignee: Srikanteswararao Talluri (was: Gaurav Aradhye)
[Automation] Fix the script test_redundant_router.py - Script is hardcoded
to use password as Host's password
-
Key: CLOUDSTACK-7388
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7388
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
Script is at: component/maint/.
Observe the below code in test_redundant_router.py script:
{code}
...
.
.
},
host: {
username: root,
password: password,
publicport: 22,
},
network: {
.
.
.
.
@attr(tags=[advanced, advancedns, ssh])
def test_redundantVR_internals(self):
Test redundant router internals
.
.
.
else:
result = get_process_status(
backup_host.ipaddress,
self.services['host'][publicport],
self.services['host'][username],
self.services['host'][password],
backup_router.linklocalip,
'ip addr show eth2',
)
res = str(result)
.
.
.
{code}
The above code should be changed to use the host information from
configuration file outside this script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7388) [Automation] Fix the script test_redundant_router.py - Script is hardcoded to use password as Host's password
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri resolved CLOUDSTACK-7388.
--
Resolution: Fixed
[Automation] Fix the script test_redundant_router.py - Script is hardcoded
to use password as Host's password
-
Key: CLOUDSTACK-7388
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7388
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.5.0
Script is at: component/maint/.
Observe the below code in test_redundant_router.py script:
{code}
...
.
.
},
host: {
username: root,
password: password,
publicport: 22,
},
network: {
.
.
.
.
@attr(tags=[advanced, advancedns, ssh])
def test_redundantVR_internals(self):
Test redundant router internals
.
.
.
else:
result = get_process_status(
backup_host.ipaddress,
self.services['host'][publicport],
self.services['host'][username],
self.services['host'][password],
backup_router.linklocalip,
'ip addr show eth2',
)
res = str(result)
.
.
.
{code}
The above code should be changed to use the host information from
configuration file outside this script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7431) [Automation] Fix the script test_ldap.py - Move the Ldap configuration information to test_data.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri reassigned CLOUDSTACK-7431: Assignee: Srikanteswararao Talluri [Automation] Fix the script test_ldap.py - Move the Ldap configuration information to test_data.py Key: CLOUDSTACK-7431 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7431 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 Currently because the ldap configuration is hard coded in the script it is failing to work on other setups with different ldap configuration. Please move that information to test_data.py *Error Message* addLdapConfiguration failed Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=ldap Stacktrace File /usr/lib/python2.7/unittest/case.py, line 332, in run testMethod() File /root/cloudstack/test/integration/component/test_ldap.py, line 154, in test_01_addLdapConfiguration self.assertEquals(self.ldapconfRes,1,addLdapConfiguration failed) File /usr/lib/python2.7/unittest/case.py, line 516, in assertEqual assertion_func(first, second, msg=msg) File /usr/lib/python2.7/unittest/case.py, line 509, in _baseAssertEqual raise self.failureException(msg) 'addLdapConfiguration failed\n Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7431) [Automation] Fix the script test_ldap.py - Move the Ldap configuration information to test_data.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7431. -- Resolution: Fixed [Automation] Fix the script test_ldap.py - Move the Ldap configuration information to test_data.py Key: CLOUDSTACK-7431 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7431 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 Currently because the ldap configuration is hard coded in the script it is failing to work on other setups with different ldap configuration. Please move that information to test_data.py *Error Message* addLdapConfiguration failed Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=ldap Stacktrace File /usr/lib/python2.7/unittest/case.py, line 332, in run testMethod() File /root/cloudstack/test/integration/component/test_ldap.py, line 154, in test_01_addLdapConfiguration self.assertEquals(self.ldapconfRes,1,addLdapConfiguration failed) File /usr/lib/python2.7/unittest/case.py, line 516, in assertEqual assertion_func(first, second, msg=msg) File /usr/lib/python2.7/unittest/case.py, line 509, in _baseAssertEqual raise self.failureException(msg) 'addLdapConfiguration failed\n Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7433) [Automation] Fix the script test_deploy_vm_userdata_reg.py - Host credentials are hardcoded in the script
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri reassigned CLOUDSTACK-7433: Assignee: Srikanteswararao Talluri [Automation] Fix the script test_deploy_vm_userdata_reg.py - Host credentials are hardcoded in the script --- Key: CLOUDSTACK-7433 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7433 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 The host credentials are hardcoded in the script. Please take the host specific information from test_data.py which is configurable. *Error Message* SSH Connection Failed Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=deploy_vm_userdata Stacktrace File /usr/lib/python2.7/unittest/case.py, line 332, in run testMethod() File /root/cloudstack/test/integration/component/test_deploy_vm_userdata_reg.py, line 209, in test_deployvm_userdata_post cmd File /usr/local/lib/python2.7/dist-packages/marvin/lib/utils.py, line 198, in get_process_status ssh = SshClient(hostip, port, username, password) File /usr/local/lib/python2.7/dist-packages/marvin/sshClient.py, line 81, in __init__ raise internalError(SSH Connection Failed) 'SSH Connection Failed\n Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=deploy_vm_userdata -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7228) [Automation] Unable to shrink data disk attached to a VM on XenServer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri resolved CLOUDSTACK-7228.
--
Resolution: Fixed
This should get fixed with John's patch. Marking it fixed. Please reopen if
this reappears.
[Automation] Unable to shrink data disk attached to a VM on XenServer
-
Key: CLOUDSTACK-7228
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7228
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test, Volumes
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Chandan Purushothama
Priority: Critical
Fix For: 4.5.0
Attachments: management-server.zip
==
Automation Code:
==
def test_08_resize_volume(self):
Test resize a volume
#Verify the size is the new size is what we wanted it to be.
self.debug(
Attaching volume (ID: %s) to VM (ID: %s) % (
self.volume.id,
self.virtual_machine.id
))
self.virtual_machine.attach_volume(self.apiClient, self.volume)
self.attached = True
hosts = Host.list(self.apiClient, id=self.virtual_machine.hostid)
self.assertTrue(isinstance(hosts, list))
self.assertTrue(len(hosts) 0)
self.debug(Found %s host % hosts[0].hypervisor)
if hosts[0].hypervisor == XenServer:
self.virtual_machine.stop(self.apiClient)
elif hosts[0].hypervisor.lower() == vmware:
self.skipTest(Resize Volume is unsupported on VmWare)
#resize the data disk
self.debug(Resize Volume ID: %s % self.volume.id)
self.services[disk_offering][disksize] = 20
disk_offering_20_GB = DiskOffering.create(
self.apiclient,
self.services[disk_offering]
)
self.cleanup.append(disk_offering_20_GB)
cmd= resizeVolume.resizeVolumeCmd()
cmd.id = self.volume.id
cmd.diskofferingid = disk_offering_20_GB.id
self.apiClient.resizeVolume(cmd)
===
Error Thrown in Automation Logs:
===
=
ERROR: Test resize a volume
Traceback (most recent call last):
File /home/chandan/test_volumes.py, line 693, in test_08_resize_volume
self.apiClient.resizeVolume(cmd)
File
/usr/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
line 1672, in resizeVolume
response = self.connection.marvinRequest(command, response_type=response,
method=method)
File /usr/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 379, in marvinRequest
raise e
Exception: Job failed: {jobprocstatus : 0, created :
u'2014-08-07T16:45:25-0700', cmd :
u'org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin',
userid : u'89a9018a-12a8-11e4-b75e-06098c000757', jobstatus : 2, jobid :
u'7d5c9749-67d6-4fab-a0bf-f5bc8722b276', jobresultcode : 530, jobresulttype :
u'object', jobresult : {errorcode : 530, errortext : u'Job failed due to
exception failed to resize volume:SR_BACKEND_FAILURE_79VDI Invalid size
[opterr=shrinking not allowed]'}, accountid :
u'89a8f4e2-12a8-11e4-b75e-06098c000757'}
begin captured stdout -
=== TestName: test_08_resize_volume | Status : EXCEPTION ===
==
Error in Management Server Log:
==
2014-08-07 14:15:39,459 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-23:ctx-62ca6450 job-1314/job-1315 ctx-0761b68e) Execute VM
work job:
com.cloud.storage.VmWorkResizeVolume{volumeId:172,currentSize:21474836480,newSize:10737418240,newServiceOfferingId:43,shrinkOk:true,userId:2,accountId:2,vmId:162,handlerName:VolumeApiServiceImpl}
2014-08-07 14:15:39,487 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-23:ctx-62ca6450 job-1314/job-1315 ctx-0761b68e) Seq
1-1425952232016183856: Sending { Cmd , MgmtId: 6638073284439, via:
1(Rack3Host6.lab.vmops.com), Ver: v1, Flags: 100011,
[jira] [Resolved] (CLOUDSTACK-7442) [Automation] Fix the script test_project_resources.py - No permissions updated, please verify the account names
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7442. -- Resolution: Fixed [Automation] Fix the script test_project_resources.py - No permissions updated, please verify the account names - Key: CLOUDSTACK-7442 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7442 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Gaurav Aradhye Priority: Critical Fix For: 4.5.0 The following script failed during regression run: integration.component.test_project_resources.TestTemplates.test_05_use_private_template_in_project *Error Message* Exception occured: Execute cmd: updatetemplatepermissions failed, due to: errorCode: 431, errorText:Unable to grant a launch permission to account PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75, account not found. No permissions updated, please verify the account names and retry. Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=project_resources Stacktrace File /usr/lib/python2.7/unittest/case.py, line 332, in run testMethod() File /root/cloudstack/test/integration/component/test_project_resources.py, line 768, in test_05_use_private_template_in_project self.fail(Exception occured: %s % e) File /usr/lib/python2.7/unittest/case.py, line 413, in fail raise self.failureException(msg) 'Exception occured: Execute cmd: updatetemplatepermissions failed, due to: errorCode: 431, errorText:Unable to grant a launch permission to account PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75, account not found. No permissions updated, please verify the account names and retry.\n Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=project_resources -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7426) [Automation] Failed to update template permissions in test_05_use_private_template_in_project
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7426. -- Resolution: Fixed [Automation] Failed to update template permissions in test_05_use_private_template_in_project - Key: CLOUDSTACK-7426 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7426 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Gaurav Aradhye Priority: Critical Fix For: 4.5.0 Error while executing the following test *integration.component.test_project_resources.TestTemplates.test_05_use_private_template_in_project (from nosetests)* *Error Message* Exception occured: Execute cmd: updatetemplatepermissions failed, due to: errorCode: 431, errorText:Unable to grant a launch permission to account PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75, account not found. No permissions updated, please verify the account names and retry. Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=project_resources Stacktrace File /usr/lib/python2.7/unittest/case.py, line 332, in run testMethod() File /root/cloudstack/test/integration/component/test_project_resources.py, line 768, in test_05_use_private_template_in_project self.fail(Exception occured: %s % e) File /usr/lib/python2.7/unittest/case.py, line 413, in fail raise self.failureException(msg) 'Exception occured: Execute cmd: updatetemplatepermissions failed, due to: errorCode: 431, errorText:Unable to grant a launch permission to account PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75, account not found. No permissions updated, please verify the account names and retry.\n Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=project_resources -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7053) [Automation] Tasks for writing automated test cases for few product bugs
Srikanteswararao Talluri created CLOUDSTACK-7053: Summary: [Automation] Tasks for writing automated test cases for few product bugs Key: CLOUDSTACK-7053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7053 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7009) [Automation]serviceofferingdetails needs to be handled properly in base.py
Srikanteswararao Talluri created CLOUDSTACK-7009: Summary: [Automation]serviceofferingdetails needs to be handled properly in base.py Key: CLOUDSTACK-7009 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7009 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 enhance base.py to handle the serviceofferingdetails we should be able to format the API request in the form of serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7009) [Automation]serviceofferingdetails needs to be handled properly in base.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7009. -- Resolution: Fixed [Automation]serviceofferingdetails needs to be handled properly in base.py -- Key: CLOUDSTACK-7009 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7009 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 enhance base.py to handle the serviceofferingdetails we should be able to format the API request in the form of serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6995) Stress Test to test multiple Remote Access VPN Connections to VPC
Srikanteswararao Talluri created CLOUDSTACK-6995: Summary: Stress Test to test multiple Remote Access VPN Connections to VPC Key: CLOUDSTACK-6995 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6995 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: Srikanteswararao Talluri Assignee: Chandan Purushothama Fix For: 4.4.0 Stress Test to test multiple Remote Access VPN Connections to VPC -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6963) [Automation] test_deploy_vm failing with error global name 'configureSimulator' is not defined
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6963. -- Resolution: Not a Problem Assignee: Srikanteswararao Talluri use correct attributes. [Automation] test_deploy_vm failing with error global name 'configureSimulator' is not defined Key: CLOUDSTACK-6963 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6963 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 Test case from below suite failing integration.smoke.test_deploy_vm /usr/local/lib/python2.7/unittest/case.py, line 311, in run\n self.setUp()\n', ' File /data/Repo2/qa/cloudstack/test/integration/smoke/test_deploy_vm.py, line 312, in setUp\ncount=6)\n', ' File /usr/local/lib/python2.7/site-packages/marvin/lib/base.py, line 4657, in create\ncmd = configureSimulator.configureSimulatorCmd()\n', NameError: global name 'configureSimulator' is not defined\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/unittest/case.py, line 311, in run self.setUp() File /data/Repo2/qa/cloudstack/test/integration/smoke/test_deploy_vm.py, line 312, in setUp count=6) File /usr/local/lib/python2.7/site-packages/marvin/lib/base.py, line 4657, in create cmd = configureSimulator.configureSimulatorCmd() 'global name \'configureSimulator\' is not defined\n begin captured stdout -\n=== TestName: test_deploy_vm_start_failure | Status : EXCEPTION ===\n\n\n- end captured stdout --\n begin captured logging \ntest_deploy_vm_start_failure (integration.smoke.test_deploy_vm.TestDeployVMStartFailure): DEBUG: STARTED : TC: test_deploy_vm_start_failure :::\ntest_deploy_vm_start_failure -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6904) [Automation] marvin signature generation is going wrong as 'typeInfo' is part of payload
Srikanteswararao Talluri created CLOUDSTACK-6904: Summary: [Automation] marvin signature generation is going wrong as 'typeInfo' is part of payload Key: CLOUDSTACK-6904 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6904 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Signature generation for the API call is going wrong because newly added 'typeInfo' is going as part of payload. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6492) [Automation] strftime is not imported explicitly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-6492. [Automation] strftime is not imported explicitly Key: CLOUDSTACK-6492 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6492 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Deploy DC is failing with latest marvin changes Branch acs-infra-fmt set up to track remote branch acs-infra-fmt from origin. === Marvin Parse Config Successful === === Marvin Setting TestData Successful=== Log Folder Path: /tmp//MarvinLogs//Apr_23_2014_23_23_03_DTNRUA. All logs will be available here === Marvin Init Logging Successful=== Deploy DC Started Exception Occurred while persisting DC Settings: ['Traceback (most recent call last):\n', ' File /var/lib/jenkins/workspace/test-setup-advancedzone-master/187/lib/python2.7/site-packages/marvin/deployDataCenter.py, line 70, in __persistDcConfig\nts = time.strftime(%b_%d_%Y_%H_%M_%S,\n', AttributeError: 'builtin_function_or_method' object has no attribute 'strftime'\n] Deploy DC Successful= -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6492) [Automation] strftime is not imported explicitly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6492. -- Resolution: Fixed [Automation] strftime is not imported explicitly Key: CLOUDSTACK-6492 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6492 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Deploy DC is failing with latest marvin changes Branch acs-infra-fmt set up to track remote branch acs-infra-fmt from origin. === Marvin Parse Config Successful === === Marvin Setting TestData Successful=== Log Folder Path: /tmp//MarvinLogs//Apr_23_2014_23_23_03_DTNRUA. All logs will be available here === Marvin Init Logging Successful=== Deploy DC Started Exception Occurred while persisting DC Settings: ['Traceback (most recent call last):\n', ' File /var/lib/jenkins/workspace/test-setup-advancedzone-master/187/lib/python2.7/site-packages/marvin/deployDataCenter.py, line 70, in __persistDcConfig\nts = time.strftime(%b_%d_%Y_%H_%M_%S,\n', AttributeError: 'builtin_function_or_method' object has no attribute 'strftime'\n] Deploy DC Successful= -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6904) [Automation] marvin signature generation is going wrong as 'typeInfo' is part of payload
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-6904. [Automation] marvin signature generation is going wrong as 'typeInfo' is part of payload Key: CLOUDSTACK-6904 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6904 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Signature generation for the API call is going wrong because newly added 'typeInfo' is going as part of payload. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-4906) add netaddr to marvin dependency list
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-4906: - Component/s: (was: Test Tools) marvin add netaddr to marvin dependency list - Key: CLOUDSTACK-4906 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4906 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.2.1 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Add 'netaddr' package to the marvin installation dependency list. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-4906) add netaddr to marvin dependency list
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-4906. add netaddr to marvin dependency list - Key: CLOUDSTACK-4906 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4906 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.2.1 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Add 'netaddr' package to the marvin installation dependency list. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6904) [Automation] marvin signature generation is going wrong as 'typeInfo' is part of payload
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6904. -- Resolution: Fixed [Automation] marvin signature generation is going wrong as 'typeInfo' is part of payload Key: CLOUDSTACK-6904 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6904 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Signature generation for the API call is going wrong because newly added 'typeInfo' is going as part of payload. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-4906) add netaddr to marvin dependency list
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-4906: - Issue Type: Test (was: Bug) add netaddr to marvin dependency list - Key: CLOUDSTACK-4906 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4906 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.2.1 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Add 'netaddr' package to the marvin installation dependency list. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-4906) add netaddr to marvin dependency list
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-4906. -- Resolution: Fixed add netaddr to marvin dependency list - Key: CLOUDSTACK-4906 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4906 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.2.1 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Add 'netaddr' package to the marvin installation dependency list. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6760) [Automation] integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm is failing for KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri reassigned CLOUDSTACK-6760: Assignee: Srikanteswararao Talluri [Automation] integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm is failing for KVM Key: CLOUDSTACK-6760 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6760 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Koushik Das Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Scale VM is only supported for XS and Vmware. So test integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm always fails on KVM. The test should be fixed to handle this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6738) [Automation] Expunge VM and guestVLAN range tests are failing consistently
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006939#comment-14006939 ] Srikanteswararao Talluri commented on CLOUDSTACK-6738: -- We were not sure these are test issues/product issues at the time of bug creation. Now, I see that these two tests are passing when run standalone. Hence, there could be a problem with cleanup in earlier tests. [Automation] Expunge VM and guestVLAN range tests are failing consistently -- Key: CLOUDSTACK-6738 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6738 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.4.0 test_dedicateGuestVlanRange and test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6738) [Automation] Expunge VM and guestVLAN range tests are failing consistently
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6738. -- Resolution: Fixed I am marking this as resolved since both the test cases are passing. Please re-open this bug with more details if it is observed in latest runs. [Automation] Expunge VM and guestVLAN range tests are failing consistently -- Key: CLOUDSTACK-6738 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6738 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.4.0 test_dedicateGuestVlanRange and test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6738) [Automation] Expunge VM and guestVLAN range tests are failing consistently
Srikanteswararao Talluri created CLOUDSTACK-6738: Summary: [Automation] Expunge VM and guestVLAN range tests are failing consistently Key: CLOUDSTACK-6738 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6738 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.4.0 test_dedicateGuestVlanRange and test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (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 updated CLOUDSTACK-6629:
-
Assignee: (was: 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
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
[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
[jira] [Updated] (CLOUDSTACK-6498) [Automation] unable to start management server after restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-6498: - Attachment: cloud.sql cloud database dump [Automation] unable to start management server after restart Key: CLOUDSTACK-6498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6498 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: advanced zone xenserer 6.2 Reporter: Srikanteswararao Talluri Assignee: Harikrishna Patnala Priority: Blocker Fix For: 4.5.0 Attachments: cloud.sql, log.tar.gz on the daily automation environment, After the zone is deployed , system VMs came up fine. After setting few global settings, I tried to restart management server, it never came up again. I could see some db exceptions related to duplicate keys. I will attach management server logs to this bug for your reference. Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) 14761,2-9 96% -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6498) [Automation] unable to start management server after restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980820#comment-13980820 ] Srikanteswararao Talluri commented on CLOUDSTACK-6498: -- Management server was rebooted using service cloudstack-management stop;service cloudstack-management start [Automation] unable to start management server after restart Key: CLOUDSTACK-6498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6498 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: advanced zone xenserer 6.2 Reporter: Srikanteswararao Talluri Assignee: Harikrishna Patnala Priority: Blocker Fix For: 4.5.0 Attachments: cloud.sql, log.tar.gz on the daily automation environment, After the zone is deployed , system VMs came up fine. After setting few global settings, I tried to restart management server, it never came up again. I could see some db exceptions related to duplicate keys. I will attach management server logs to this bug for your reference. Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) 14761,2-9 96% -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6511) [Automation] Fixes for failures in BVT and component runs
Srikanteswararao Talluri created CLOUDSTACK-6511: Summary: [Automation] Fixes for failures in BVT and component runs Key: CLOUDSTACK-6511 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6511 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Fixes for failures in BVT and component runs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6511) [Automation] Fixes for failures in BVT and component runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-6511. [Automation] Fixes for failures in BVT and component runs - Key: CLOUDSTACK-6511 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6511 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Fixes for failures in BVT and component runs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6511) [Automation] Fixes for failures in BVT and component runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6511. -- Resolution: Fixed [Automation] Fixes for failures in BVT and component runs - Key: CLOUDSTACK-6511 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6511 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Fixes for failures in BVT and component runs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6492) [Automation] strftime is not imported explicitly
Srikanteswararao Talluri created CLOUDSTACK-6492: Summary: [Automation] strftime is not imported explicitly Key: CLOUDSTACK-6492 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6492 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Deploy DC is failing with latest marvin changes Branch acs-infra-fmt set up to track remote branch acs-infra-fmt from origin. === Marvin Parse Config Successful === === Marvin Setting TestData Successful=== Log Folder Path: /tmp//MarvinLogs//Apr_23_2014_23_23_03_DTNRUA. All logs will be available here === Marvin Init Logging Successful=== Deploy DC Started Exception Occurred while persisting DC Settings: ['Traceback (most recent call last):\n', ' File /var/lib/jenkins/workspace/test-setup-advancedzone-master/187/lib/python2.7/site-packages/marvin/deployDataCenter.py, line 70, in __persistDcConfig\nts = time.strftime(%b_%d_%Y_%H_%M_%S,\n', AttributeError: 'builtin_function_or_method' object has no attribute 'strftime'\n] Deploy DC Successful= -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6498) [Automation] unable to start management server after restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-6498: - Attachment: log.tar.gz management server logs [Automation] unable to start management server after restart Key: CLOUDSTACK-6498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6498 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: advanced zone xenserer 6.2 Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 Attachments: log.tar.gz on the daily automation environment, After the zone is deployed , system VMs came up fine. After setting few global settings, I tried to restart management server, it never came up again. I could see some db exceptions related to duplicate keys. I will attach management server logs to this bug for your reference. Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) 14761,2-9 96% -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6498) [Automation] unable to start management server after restart
Srikanteswararao Talluri created CLOUDSTACK-6498: Summary: [Automation] unable to start management server after restart Key: CLOUDSTACK-6498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6498 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: advanced zone xenserer 6.2 Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 on the daily automation environment, After the zone is deployed , system VMs came up fine. After setting few global settings, I tried to restart management server, it never came up again. I could see some db exceptions related to duplicate keys. I will attach management server logs to this bug for your reference. Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) 14761,2-9 96% -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6416) Missing cloud-scripts in systemvm template built from 4.2 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri reassigned CLOUDSTACK-6416: Assignee: Srikanteswararao Talluri Missing cloud-scripts in systemvm template built from 4.2 branch Key: CLOUDSTACK-6416 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6416 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.0 Environment: 4.2 systemvm template Reporter: Sateesh Chodapuneedi Assignee: Srikanteswararao Talluri Priority: Blocker cloud-scripts.tar is not built properly with scripts. It was filled up with source code of cloudstack project from ACS git repository. While building systemvm template, in postinstall.sh file, cloudstack source would be downloaded from ACS git repository and patching scripts would be bundled as cloud-scripts.tar after extracting cloudstack source tar ball. Untar operation of source tar ball failed with error no space left on device. Build script is not failing at this point but this is resulting in mal-formed cloud-scripts.tar. cloudstack-HEAD-2a02369/awsapi/src/com/amazon/ec2/DescribeConversionTasksType.java tar: /usr/share/cloud/cloud-scripts.tar: Cannot write: No space left on device tar: Error is not recoverable: exiting now ++ cd /opt ++ rm -fr /opt/cloudstack-HEAD-2a02369 /opt/cloudstack.tar.gz cloudstack.tar.gz ++ chkconfig --add cloud-early-config cloud-early-config: unknown service ++ chkconfig cloud-early-config on cloud-early-config: unknown service ++ chkconfig --add cloud-passwd-srvr cloud-passwd-srvr: unknown service ++ chkconfig cloud-passwd-srvr off cloud-passwd-srvr: unknown service ++ chkconfig --add cloud cloud: unknown service ++ chkconfig cloud off cloud: unknown service Downloaded system vm template generated by jenkins from http://jenkins.buildacloud.org/view/4.2/job/build-systemvm-4.2/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6416) Missing cloud-scripts in systemvm template built from 4.2 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969593#comment-13969593 ] Srikanteswararao Talluri commented on CLOUDSTACK-6416: -- There is a problem with tools/appliance/definitions/systemvmtemplate64/postinstall.sh which gets cloudstack.tar.gz as below snapshot_url=https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=snapshot;h=HEAD;sf=tgz which fetches latest master. However, 4.2 branch has a different directory structure than master branch. Hence, postinstall.sh script is failing to include scripts in cloud-scripts.tar This issue can be fixed by fetching appropriate branch snapshot rather than from the latest one. snapshot_url=https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=snapshot;h=4.2;sf=tgz Will push this change in a while Missing cloud-scripts in systemvm template built from 4.2 branch Key: CLOUDSTACK-6416 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6416 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.0 Environment: 4.2 systemvm template Reporter: Sateesh Chodapuneedi Assignee: Srikanteswararao Talluri Priority: Blocker cloud-scripts.tar is not built properly with scripts. It was filled up with source code of cloudstack project from ACS git repository. While building systemvm template, in postinstall.sh file, cloudstack source would be downloaded from ACS git repository and patching scripts would be bundled as cloud-scripts.tar after extracting cloudstack source tar ball. Untar operation of source tar ball failed with error no space left on device. Build script is not failing at this point but this is resulting in mal-formed cloud-scripts.tar. cloudstack-HEAD-2a02369/awsapi/src/com/amazon/ec2/DescribeConversionTasksType.java tar: /usr/share/cloud/cloud-scripts.tar: Cannot write: No space left on device tar: Error is not recoverable: exiting now ++ cd /opt ++ rm -fr /opt/cloudstack-HEAD-2a02369 /opt/cloudstack.tar.gz cloudstack.tar.gz ++ chkconfig --add cloud-early-config cloud-early-config: unknown service ++ chkconfig cloud-early-config on cloud-early-config: unknown service ++ chkconfig --add cloud-passwd-srvr cloud-passwd-srvr: unknown service ++ chkconfig cloud-passwd-srvr off cloud-passwd-srvr: unknown service ++ chkconfig --add cloud cloud: unknown service ++ chkconfig cloud off cloud: unknown service Downloaded system vm template generated by jenkins from http://jenkins.buildacloud.org/view/4.2/job/build-systemvm-4.2/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6416) Missing cloud-scripts in systemvm template built from 4.2 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969593#comment-13969593 ] Srikanteswararao Talluri edited comment on CLOUDSTACK-6416 at 4/15/14 2:58 PM: --- There is a problem with tools/appliance/definitions/systemvmtemplate64/postinstall.sh which gets cloudstack.tar.gz as below snapshot_url=https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=snapshot;h=HEAD;sf=tgz which fetches latest master. However, 4.2 branch has a different directory structure than master branch. Hence, postinstall.sh script is failing to include scripts in cloud-scripts.tar In 4.2: systemvm files are placed under patches folder cd patches/systemvm/debian/config Srikanteswararaos-MacBook-Air:config talluri$ ls etc opt rootvar In master: systemvm files are directly placed under root cd systemvm/patches/debian/config Srikanteswararaos-MacBook-Air:config talluri$ ls etc opt rootvar This issue can be fixed by fetching appropriate branch snapshot rather than from the latest one. snapshot_url=https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=snapshot;h=4.2;sf=tgz was (Author: talluri): There is a problem with tools/appliance/definitions/systemvmtemplate64/postinstall.sh which gets cloudstack.tar.gz as below snapshot_url=https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=snapshot;h=HEAD;sf=tgz which fetches latest master. However, 4.2 branch has a different directory structure than master branch. Hence, postinstall.sh script is failing to include scripts in cloud-scripts.tar This issue can be fixed by fetching appropriate branch snapshot rather than from the latest one. snapshot_url=https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=snapshot;h=4.2;sf=tgz Will push this change in a while Missing cloud-scripts in systemvm template built from 4.2 branch Key: CLOUDSTACK-6416 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6416 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.0 Environment: 4.2 systemvm template Reporter: Sateesh Chodapuneedi Assignee: Srikanteswararao Talluri Priority: Blocker cloud-scripts.tar is not built properly with scripts. It was filled up with source code of cloudstack project from ACS git repository. While building systemvm template, in postinstall.sh file, cloudstack source would be downloaded from ACS git repository and patching scripts would be bundled as cloud-scripts.tar after extracting cloudstack source tar ball. Untar operation of source tar ball failed with error no space left on device. Build script is not failing at this point but this is resulting in mal-formed cloud-scripts.tar. cloudstack-HEAD-2a02369/awsapi/src/com/amazon/ec2/DescribeConversionTasksType.java tar: /usr/share/cloud/cloud-scripts.tar: Cannot write: No space left on device tar: Error is not recoverable: exiting now ++ cd /opt ++ rm -fr /opt/cloudstack-HEAD-2a02369 /opt/cloudstack.tar.gz cloudstack.tar.gz ++ chkconfig --add cloud-early-config cloud-early-config: unknown service ++ chkconfig cloud-early-config on cloud-early-config: unknown service ++ chkconfig --add cloud-passwd-srvr cloud-passwd-srvr: unknown service ++ chkconfig cloud-passwd-srvr off cloud-passwd-srvr: unknown service ++ chkconfig --add cloud cloud: unknown service ++ chkconfig cloud off cloud: unknown service Downloaded system vm template generated by jenkins from http://jenkins.buildacloud.org/view/4.2/job/build-systemvm-4.2/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6416) Missing cloud-scripts in systemvm template built from 4.2 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6416. -- Resolution: Fixed Missing cloud-scripts in systemvm template built from 4.2 branch Key: CLOUDSTACK-6416 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6416 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.0 Environment: 4.2 systemvm template Reporter: Sateesh Chodapuneedi Assignee: Srikanteswararao Talluri Priority: Blocker cloud-scripts.tar is not built properly with scripts. It was filled up with source code of cloudstack project from ACS git repository. While building systemvm template, in postinstall.sh file, cloudstack source would be downloaded from ACS git repository and patching scripts would be bundled as cloud-scripts.tar after extracting cloudstack source tar ball. Untar operation of source tar ball failed with error no space left on device. Build script is not failing at this point but this is resulting in mal-formed cloud-scripts.tar. cloudstack-HEAD-2a02369/awsapi/src/com/amazon/ec2/DescribeConversionTasksType.java tar: /usr/share/cloud/cloud-scripts.tar: Cannot write: No space left on device tar: Error is not recoverable: exiting now ++ cd /opt ++ rm -fr /opt/cloudstack-HEAD-2a02369 /opt/cloudstack.tar.gz cloudstack.tar.gz ++ chkconfig --add cloud-early-config cloud-early-config: unknown service ++ chkconfig cloud-early-config on cloud-early-config: unknown service ++ chkconfig --add cloud-passwd-srvr cloud-passwd-srvr: unknown service ++ chkconfig cloud-passwd-srvr off cloud-passwd-srvr: unknown service ++ chkconfig --add cloud cloud: unknown service ++ chkconfig cloud off cloud: unknown service Downloaded system vm template generated by jenkins from http://jenkins.buildacloud.org/view/4.2/job/build-systemvm-4.2/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6363) [Automation] jetty server is going OOM for simulator
Srikanteswararao Talluri created CLOUDSTACK-6363: Summary: [Automation] jetty server is going OOM for simulator Key: CLOUDSTACK-6363 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6363 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Simulator Affects Versions: 4.4.0 Environment: simulator advanced zone Reporter: Srikanteswararao Talluri Assignee: Koushik Das Priority: Critical Fix For: 4.4.0 JVM is going OOM after running regression test suite. Please find the thread dump and heap dump attached to this bug -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6363) [Automation] jetty server is going OOM for simulator
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-6363: - Attachment: thread_dump_jetty [Automation] jetty server is going OOM for simulator Key: CLOUDSTACK-6363 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6363 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Simulator Affects Versions: 4.4.0 Environment: simulator advanced zone Reporter: Srikanteswararao Talluri Assignee: Koushik Das Priority: Critical Fix For: 4.4.0 Attachments: thread_dump_jetty JVM is going OOM after running regression test suite. Please find the thread dump and heap dump attached to this bug -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6125. -- Resolution: Fixed [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases - Key: CLOUDSTACK-6125 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6125 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Reporter: Santhosh Kumar Edukulla Assignee: Srikanteswararao Talluri Original Estimate: 120h Remaining Estimate: 120h This bug is logged to track the categorization of all test cases. We have to go through all of the test cases and divide them into two groups: 1. Provisioning Tests: Tests that require actual hardware. (e.g. Start/Stop VM on ESX, XS, and KVM; Create/Remove rules on VR or network equipment; Create Snapshot on storage). 2. Self-Service Tests: Tests that tests our self-service business logic. Self-Service tests are tests for CloudStack’s business logic. It’s not a test of whether actual provisioning succeeded. VM placement Snapshot policies Resource limits Usage Resource cleanups Note: I have added an initial estimate to this case. As well, we need to do incremental segregation and have them reviewed parallelly with alex\abhi. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6341) [Automation] Failed to deploy virtual machine
Srikanteswararao Talluri created CLOUDSTACK-6341: Summary: [Automation] Failed to deploy virtual machine Key: CLOUDSTACK-6341 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6341 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: advanced zone XenServer 6.2 Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.4.0 Automated test runs are blocked due to this issue. Job failed due to exception com.cloud.agent.api.Answer cannot be cast to com.cloud.agent.api.StopAnswer Link to test failure: http://jenkins.buildacloud.org/job/test-smoke-matrix-4.4/11/suite=test_deploy_vm/testReport/integration.smoke.test_deploy_vm/TestDeployVM/test_deploy_vm/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6341) [Automation] Failed to deploy virtual machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-6341: - Attachment: mslog.zip [Automation] Failed to deploy virtual machine - Key: CLOUDSTACK-6341 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6341 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: advanced zone XenServer 6.2 Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.4.0 Attachments: mslog.zip Automated test runs are blocked due to this issue. Job failed due to exception com.cloud.agent.api.Answer cannot be cast to com.cloud.agent.api.StopAnswer Link to test failure: http://jenkins.buildacloud.org/job/test-smoke-matrix-4.4/11/suite=test_deploy_vm/testReport/integration.smoke.test_deploy_vm/TestDeployVM/test_deploy_vm/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6286) [Automation] VM deployment is failing in simulator
Srikanteswararao Talluri created CLOUDSTACK-6286: Summary: [Automation] VM deployment is failing in simulator Key: CLOUDSTACK-6286 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6286 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Simulator Affects Versions: 4.5.0 Environment: simulator Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.5.0 VM deployment is failing on simulator for various reasons WARN [c.c.a.d.ParamGenericValidationWorker] (1776782853@qtp-639315233-4:ctx-eba7435f ctx-70cf4009) Received unknown parameters for command listSystemVms. Unknown parameters : listall ERROR [c.c.a.m.SimulatorManagerImpl] (DirectAgent-5:ctx-64065a9d) Simulator does not implement command of type com.cloud.agent.api.routing.AggregationControlCommand ERROR [c.c.a.m.SimulatorManagerImpl] (DirectAgent-17:ctx-f03c00cf) Simulator does not implement command of type com.cloud.agent.api.routing.AggregationControlCommand ERROR [c.c.a.m.SimulatorManagerImpl] (DirectAgent-9:ctx-5cb2aaed) Simulator does not implement command of type com.cloud.agent.api.routing.AggregationControlCommand WARN [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-2:Job-97/Job-98 ctx-b42ce022) Failed to re-program the network as a part of network Ntwk[210|Guest|8] implement due to aggregated commands execution failure! ERROR [c.c.a.m.SimulatorManagerImpl] (DirectAgent-7:ctx-b44ea1f7) Simulator does not implement command of type com.cloud.agent.api.routing.AggregationControlCommand INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-2:Job-97/Job-98 ctx-b42ce022) Unable to contact resource. com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply network rules as a part of network Ntwk[210|Guest|8] implement at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1110) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:992) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1272) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:982) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5149) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5294) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:495) 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) = -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6239) [Automation] jasypt decryption error is thrown after restarting console proxy VM
Srikanteswararao Talluri created CLOUDSTACK-6239: Summary: [Automation] jasypt decryption error is thrown after restarting console proxy VM Key: CLOUDSTACK-6239 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6239 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Fix For: 4.4.0 STEPS TO REPRODUCE: 1. create a zone and let SSVM and CPVM come up. 2. restart CPVM. i am hitting the following error while CPVM is being restarted. 2014-03-14 05:48:55,917 DEBUG [cloud.resource.ResourceState] (AgentConnectTaskPool-11423:ctx-abee3e50) Resource state update: [id = 8; name = v-6-VM; old state = Creating; event = InternalCreated; new state = Enabled] 2014-03-14 05:48:55,917 DEBUG [cloud.host.Status] (AgentConnectTaskPool-11423:ctx-abee3e50) Transition:[Resource state = Enabled, Agent event = AgentConnected, Host id = 8, name = v-6-VM] 2014-03-14 05:48:55,922 DEBUG [cloud.host.Status] (AgentConnectTaskPool-11423:ctx-abee3e50) Agent status update: [id = 8; name = v-6-VM; old status = Creating; event = AgentConnected; new status = Connecting; old update count = 0; new update count = 1] 2014-03-14 05:48:55,922 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) create ClusteredAgentAttache for 8 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: XcpServerDiscoverer 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: HypervServerDiscoverer 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: DeploymentPlanningManagerImpl 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: ClusteredVirtualMachineManagerImpl 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: NetworkOrchestrator 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: StoragePoolMonitor 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: SecurityGroupListener 2014-03-14 05:48:55,924 INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-11423:ctx-abee3e50) Received a host startup notification 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: SecondaryStorageListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: UploadListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: BehindOnPingListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: DirectNetworkStatsListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: ConsoleProxyListener 2014-03-14 05:48:55,928 DEBUG [utils.crypt.DBEncryptionUtil] (AgentConnectTaskPool-11423:ctx-abee3e50) Error while decrypting: A1i0Flrc5LPgCsx3V7cOVQ 2014-03-14 05:48:55,929 ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Monitor ConsoleProxyListener says there is an error in the connect process for 8 due to null org.jasypt.exceptions.EncryptionOperationNotPossibleException at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:981) at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725) at com.cloud.utils.crypt.DBEncryptionUtil.decrypt(DBEncryptionUtil.java:63) at org.apache.cloudstack.framework.config.impl.ConfigurationVO.getValue(ConfigurationVO.java:125) at org.apache.cloudstack.framework.config.ConfigKey.value(ConfigKey.java:136) at org.apache.cloudstack.framework.security.keys.KeysManagerImpl.getEncryptionKey(KeysManagerImpl.java:72) at com.cloud.consoleproxy.AgentHookBase.getEncryptorPassword(AgentHookBase.java:232) at com.cloud.consoleproxy.AgentHookBase.startAgentHttpHandlerInVM(AgentHookBase.java:198) at com.cloud.consoleproxy.ConsoleProxyListener.processConnect(ConsoleProxyListener.java:71) at
[jira] [Updated] (CLOUDSTACK-6239) [Automation] jasypt decryption error is thrown after restarting console proxy VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-6239: - Priority: Blocker (was: Major) [Automation] jasypt decryption error is thrown after restarting console proxy VM Key: CLOUDSTACK-6239 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6239 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.4.0 STEPS TO REPRODUCE: 1. create a zone and let SSVM and CPVM come up. 2. restart CPVM. i am hitting the following error while CPVM is being restarted. 2014-03-14 05:48:55,917 DEBUG [cloud.resource.ResourceState] (AgentConnectTaskPool-11423:ctx-abee3e50) Resource state update: [id = 8; name = v-6-VM; old state = Creating; event = InternalCreated; new state = Enabled] 2014-03-14 05:48:55,917 DEBUG [cloud.host.Status] (AgentConnectTaskPool-11423:ctx-abee3e50) Transition:[Resource state = Enabled, Agent event = AgentConnected, Host id = 8, name = v-6-VM] 2014-03-14 05:48:55,922 DEBUG [cloud.host.Status] (AgentConnectTaskPool-11423:ctx-abee3e50) Agent status update: [id = 8; name = v-6-VM; old status = Creating; event = AgentConnected; new status = Connecting; old update count = 0; new update count = 1] 2014-03-14 05:48:55,922 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) create ClusteredAgentAttache for 8 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: XcpServerDiscoverer 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: HypervServerDiscoverer 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: DeploymentPlanningManagerImpl 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: ClusteredVirtualMachineManagerImpl 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: NetworkOrchestrator 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: StoragePoolMonitor 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: SecurityGroupListener 2014-03-14 05:48:55,924 INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-11423:ctx-abee3e50) Received a host startup notification 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: SecondaryStorageListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: UploadListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: BehindOnPingListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: DirectNetworkStatsListener 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: ConsoleProxyListener 2014-03-14 05:48:55,928 DEBUG [utils.crypt.DBEncryptionUtil] (AgentConnectTaskPool-11423:ctx-abee3e50) Error while decrypting: A1i0Flrc5LPgCsx3V7cOVQ 2014-03-14 05:48:55,929 ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-11423:ctx-abee3e50) Monitor ConsoleProxyListener says there is an error in the connect process for 8 due to null org.jasypt.exceptions.EncryptionOperationNotPossibleException at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:981) at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725) at com.cloud.utils.crypt.DBEncryptionUtil.decrypt(DBEncryptionUtil.java:63) at org.apache.cloudstack.framework.config.impl.ConfigurationVO.getValue(ConfigurationVO.java:125) at org.apache.cloudstack.framework.config.ConfigKey.value(ConfigKey.java:136) at
[jira] [Created] (CLOUDSTACK-6222) [Automation] config generator script is broken
Srikanteswararao Talluri created CLOUDSTACK-6222: Summary: [Automation] config generator script is broken Key: CLOUDSTACK-6222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6222 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Config generator scripts are broken because of the changes in configGenerator.py tools/marvin/marvin/configGenerator.py tools/marvin/marvin/sandbox/advanced/advanced_env.py tools/marvin/marvin/sandbox/advancedsg/advancedsg_env.py tools/marvin/marvin/sandbox/basic/basic_env.py tools/marvin/marvin/sandbox/demo/simulator/simulator_setup.py 1. = python basic_env.py Traceback (most recent call last): File basic_env.py, line 142, in module cfg = describeResources(cfg_parser) File basic_env.py, line 55, in describeResources pn = physical_network() NameError: global name 'physical_network' is not defined == 2. Fix the logger path in the config file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6222) [Automation] config generator script is broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-6222. tested and config files are generated successfully [Automation] config generator script is broken -- Key: CLOUDSTACK-6222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Config generator scripts are broken because of the changes in configGenerator.py tools/marvin/marvin/configGenerator.py tools/marvin/marvin/sandbox/advanced/advanced_env.py tools/marvin/marvin/sandbox/advancedsg/advancedsg_env.py tools/marvin/marvin/sandbox/basic/basic_env.py tools/marvin/marvin/sandbox/demo/simulator/simulator_setup.py 1. = python basic_env.py Traceback (most recent call last): File basic_env.py, line 142, in module cfg = describeResources(cfg_parser) File basic_env.py, line 55, in describeResources pn = physical_network() NameError: global name 'physical_network' is not defined == 2. Fix the logger path in the config file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6222) [Automation] config generator script is broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-6222. -- Resolution: Fixed [Automation] config generator script is broken -- Key: CLOUDSTACK-6222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.4.0 Config generator scripts are broken because of the changes in configGenerator.py tools/marvin/marvin/configGenerator.py tools/marvin/marvin/sandbox/advanced/advanced_env.py tools/marvin/marvin/sandbox/advancedsg/advancedsg_env.py tools/marvin/marvin/sandbox/basic/basic_env.py tools/marvin/marvin/sandbox/demo/simulator/simulator_setup.py 1. = python basic_env.py Traceback (most recent call last): File basic_env.py, line 142, in module cfg = describeResources(cfg_parser) File basic_env.py, line 55, in describeResources pn = physical_network() NameError: global name 'physical_network' is not defined == 2. Fix the logger path in the config file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-6125: - Status: Reviewable (was: In Progress) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases - Key: CLOUDSTACK-6125 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6125 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Reporter: Santhosh Kumar Edukulla Assignee: Srikanteswararao Talluri Original Estimate: 120h Remaining Estimate: 120h This bug is logged to track the categorization of all test cases. We have to go through all of the test cases and divide them into two groups: 1. Provisioning Tests: Tests that require actual hardware. (e.g. Start/Stop VM on ESX, XS, and KVM; Create/Remove rules on VR or network equipment; Create Snapshot on storage). 2. Self-Service Tests: Tests that tests our self-service business logic. Self-Service tests are tests for CloudStack’s business logic. It’s not a test of whether actual provisioning succeeded. VM placement Snapshot policies Resource limits Usage Resource cleanups Note: I have added an initial estimate to this case. As well, we need to do incremental segregation and have them reviewed parallelly with alex\abhi. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923633#comment-13923633 ] Srikanteswararao Talluri commented on CLOUDSTACK-6125: -- Added a page with all my findings for Advanced and Basic zone reports on simulator https://cwiki.apache.org/confluence/display/CLOUDSTACK/Test+Automation+report+on+Simulator Please review so that i can add tags to the tests as 'self-service' or 'provisioning' in the repo if required. [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases - Key: CLOUDSTACK-6125 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6125 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Reporter: Santhosh Kumar Edukulla Assignee: Srikanteswararao Talluri Original Estimate: 120h Remaining Estimate: 120h This bug is logged to track the categorization of all test cases. We have to go through all of the test cases and divide them into two groups: 1. Provisioning Tests: Tests that require actual hardware. (e.g. Start/Stop VM on ESX, XS, and KVM; Create/Remove rules on VR or network equipment; Create Snapshot on storage). 2. Self-Service Tests: Tests that tests our self-service business logic. Self-Service tests are tests for CloudStack’s business logic. It’s not a test of whether actual provisioning succeeded. VM placement Snapshot policies Resource limits Usage Resource cleanups Note: I have added an initial estimate to this case. As well, we need to do incremental segregation and have them reviewed parallelly with alex\abhi. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6146) subsequent migration fails as cloud stack renames files after 1st migration
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-6146:
-
Fix Version/s: (was: 4.4.0)
4.3.0
subsequent migration fails as cloud stack renames files after 1st migration
---
Key: CLOUDSTACK-6146
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6146
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Environment: ESXi 5.5
Reporter: praveena palaniswamy
Assignee: Likitha Shetty
Fix For: 4.3.0
CLoudplatform/Cloudstack, renames the files after first successful migration
and therefore, subsequent migration fails. This happens with
CloudPlatform 4.3
Hypervisor: ESXi5.5
1.File name gets renamed after migration, which inturn fails subsequent
migrations (CLOUDSTACK issue)
a.Before migration of data disk the contents of VM folder can be seen
below
[root@host148 i-2-3-VM]# ls -l
total 40060
-rw---. 1 root root 3221225472 Feb 13 2014
7868703c4e8345a58d568ece092baa0e-flat.vmdk
-rw---. 1 root root518 Feb 13 06:05
7868703c4e8345a58d568ece092baa0e.vmdk
[root@host148 i-2-3-VM]#
b.After migration, cloudstack renames the file name
7868703c4e8345a58d568ece092baa0e.vmdk to i-2-3-VM_2.vmdk
[root@host148 i-2-3-VM]# ls -l
total 19072
-rw---. 1 root root 3221225472 Feb 13 2014 i-2-3-VM_2-flat.vmdk
-rw---. 1 root root519 Feb 13 2014 i-2-3-VM_2.vmdk
[root@host148 i-2-3-VM]#
c.So when we call the migration for the second time, cloudstack looks for
the file “7868703c4e8345a58d568ece092baa0e.vmdk” and it does not find it and
migration fails.
d.Be it from netapp to non-netapp, or netapp to netapp, all the
subsequent migration fails with the following message
2014-02-13 06:17:57,399 ERROR [c.c.h.v.r.VmwareResource]
(DirectAgent-415:ctx-33da787a 10.61.166.68) Catch Exception
java.lang.Exception due to java.lang.Exception: No such disk device:
7868703c4e8345a58d568ece092baa0e.vmdk
java.lang.Exception: No such disk device:
7868703c4e8345a58d568ece092baa0e.vmdk
at
com.cloud.hypervisor.vmware.resource.VmwareResource.getVirtualDiskInfo(VmwareResource.java:4420)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4397)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:454)
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$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-02-13 06:17:57,400 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-415:ctx-33da787a) Seq 1-2016020265: Response Received:
2014-02-13 06:17:57,401 DEBUG [c.c.a.t.Request]
(DirectAgent-415:ctx-33da787a) Seq 1-2016020265: Processing: { Ans: ,
MgmtId: 52230907924, via: 1, Ver: v1, Flags: 110,
[{com.cloud.agent.api.storage.MigrateVolumeAnswer:{result:false,details:Catch
Exception java.lang.Exception due to java.lang.Exception: No such disk
device: 7868703c4e8345a58d568ece092baa0e.vmdk,wait:0}}] }
2014-02-13 06:17:57,401 DEBUG [c.c.a.t.Request] (Job-Executor-7:ctx-5972265e
ctx-d2079367) Seq 1-2016020265: Received: { Ans: , MgmtId: 52230907924, via:
1, Ver: v1, Flags: 110, { MigrateVolumeAnswer } }
2014-02-13 06:17:57,401 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
[jira] [Updated] (CLOUDSTACK-6146) subsequent migration fails as cloud stack renames files after 1st migration
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-6146:
-
Priority: Critical (was: Major)
subsequent migration fails as cloud stack renames files after 1st migration
---
Key: CLOUDSTACK-6146
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6146
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Environment: ESXi 5.5
Reporter: praveena palaniswamy
Assignee: Likitha Shetty
Priority: Critical
Fix For: 4.3.0
CLoudplatform/Cloudstack, renames the files after first successful migration
and therefore, subsequent migration fails. This happens with
CloudPlatform 4.3
Hypervisor: ESXi5.5
1.File name gets renamed after migration, which inturn fails subsequent
migrations (CLOUDSTACK issue)
a.Before migration of data disk the contents of VM folder can be seen
below
[root@host148 i-2-3-VM]# ls -l
total 40060
-rw---. 1 root root 3221225472 Feb 13 2014
7868703c4e8345a58d568ece092baa0e-flat.vmdk
-rw---. 1 root root518 Feb 13 06:05
7868703c4e8345a58d568ece092baa0e.vmdk
[root@host148 i-2-3-VM]#
b.After migration, cloudstack renames the file name
7868703c4e8345a58d568ece092baa0e.vmdk to i-2-3-VM_2.vmdk
[root@host148 i-2-3-VM]# ls -l
total 19072
-rw---. 1 root root 3221225472 Feb 13 2014 i-2-3-VM_2-flat.vmdk
-rw---. 1 root root519 Feb 13 2014 i-2-3-VM_2.vmdk
[root@host148 i-2-3-VM]#
c.So when we call the migration for the second time, cloudstack looks for
the file “7868703c4e8345a58d568ece092baa0e.vmdk” and it does not find it and
migration fails.
d.Be it from netapp to non-netapp, or netapp to netapp, all the
subsequent migration fails with the following message
2014-02-13 06:17:57,399 ERROR [c.c.h.v.r.VmwareResource]
(DirectAgent-415:ctx-33da787a 10.61.166.68) Catch Exception
java.lang.Exception due to java.lang.Exception: No such disk device:
7868703c4e8345a58d568ece092baa0e.vmdk
java.lang.Exception: No such disk device:
7868703c4e8345a58d568ece092baa0e.vmdk
at
com.cloud.hypervisor.vmware.resource.VmwareResource.getVirtualDiskInfo(VmwareResource.java:4420)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4397)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:454)
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$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-02-13 06:17:57,400 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-415:ctx-33da787a) Seq 1-2016020265: Response Received:
2014-02-13 06:17:57,401 DEBUG [c.c.a.t.Request]
(DirectAgent-415:ctx-33da787a) Seq 1-2016020265: Processing: { Ans: ,
MgmtId: 52230907924, via: 1, Ver: v1, Flags: 110,
[{com.cloud.agent.api.storage.MigrateVolumeAnswer:{result:false,details:Catch
Exception java.lang.Exception due to java.lang.Exception: No such disk
device: 7868703c4e8345a58d568ece092baa0e.vmdk,wait:0}}] }
2014-02-13 06:17:57,401 DEBUG [c.c.a.t.Request] (Job-Executor-7:ctx-5972265e
ctx-d2079367) Seq 1-2016020265: Received: { Ans: , MgmtId: 52230907924, via:
1, Ver: v1, Flags: 110, { MigrateVolumeAnswer } }
2014-02-13 06:17:57,401 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
[jira] [Commented] (CLOUDSTACK-6146) subsequent migration fails as cloud stack renames files after 1st migration
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13908149#comment-13908149
]
Srikanteswararao Talluri commented on CLOUDSTACK-6146:
--
Marked fix version as 4.3 and this is a critical bug
subsequent migration fails as cloud stack renames files after 1st migration
---
Key: CLOUDSTACK-6146
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6146
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Environment: ESXi 5.5
Reporter: praveena palaniswamy
Assignee: Likitha Shetty
Priority: Critical
Fix For: 4.3.0
CLoudplatform/Cloudstack, renames the files after first successful migration
and therefore, subsequent migration fails. This happens with
CloudPlatform 4.3
Hypervisor: ESXi5.5
1.File name gets renamed after migration, which inturn fails subsequent
migrations (CLOUDSTACK issue)
a.Before migration of data disk the contents of VM folder can be seen
below
[root@host148 i-2-3-VM]# ls -l
total 40060
-rw---. 1 root root 3221225472 Feb 13 2014
7868703c4e8345a58d568ece092baa0e-flat.vmdk
-rw---. 1 root root518 Feb 13 06:05
7868703c4e8345a58d568ece092baa0e.vmdk
[root@host148 i-2-3-VM]#
b.After migration, cloudstack renames the file name
7868703c4e8345a58d568ece092baa0e.vmdk to i-2-3-VM_2.vmdk
[root@host148 i-2-3-VM]# ls -l
total 19072
-rw---. 1 root root 3221225472 Feb 13 2014 i-2-3-VM_2-flat.vmdk
-rw---. 1 root root519 Feb 13 2014 i-2-3-VM_2.vmdk
[root@host148 i-2-3-VM]#
c.So when we call the migration for the second time, cloudstack looks for
the file “7868703c4e8345a58d568ece092baa0e.vmdk” and it does not find it and
migration fails.
d.Be it from netapp to non-netapp, or netapp to netapp, all the
subsequent migration fails with the following message
2014-02-13 06:17:57,399 ERROR [c.c.h.v.r.VmwareResource]
(DirectAgent-415:ctx-33da787a 10.61.166.68) Catch Exception
java.lang.Exception due to java.lang.Exception: No such disk device:
7868703c4e8345a58d568ece092baa0e.vmdk
java.lang.Exception: No such disk device:
7868703c4e8345a58d568ece092baa0e.vmdk
at
com.cloud.hypervisor.vmware.resource.VmwareResource.getVirtualDiskInfo(VmwareResource.java:4420)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4397)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:454)
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$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-02-13 06:17:57,400 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-415:ctx-33da787a) Seq 1-2016020265: Response Received:
2014-02-13 06:17:57,401 DEBUG [c.c.a.t.Request]
(DirectAgent-415:ctx-33da787a) Seq 1-2016020265: Processing: { Ans: ,
MgmtId: 52230907924, via: 1, Ver: v1, Flags: 110,
[{com.cloud.agent.api.storage.MigrateVolumeAnswer:{result:false,details:Catch
Exception java.lang.Exception due to java.lang.Exception: No such disk
device: 7868703c4e8345a58d568ece092baa0e.vmdk,wait:0}}] }
2014-02-13 06:17:57,401 DEBUG [c.c.a.t.Request] (Job-Executor-7:ctx-5972265e
ctx-d2079367) Seq 1-2016020265: Received: { Ans: , MgmtId: 52230907924, via:
1, Ver: v1, Flags: 110, { MigrateVolumeAnswer } }
[jira] [Created] (CLOUDSTACK-6130) [Automation] listPublicAdress is failing
Srikanteswararao Talluri created CLOUDSTACK-6130: Summary: [Automation] listPublicAdress is failing Key: CLOUDSTACK-6130 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6130 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 Priority: Blocker Fix For: 4.4.0 List PublicAddress call is resulting in following error: listpublicipaddresses failed, due to: errorCode: 530, errorText:DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@4847303b: SELECT COUNT(*) FROM user_ip_address INNER JOIN account ON user_ip_address.account_id=account.id INNER JOIN vlan ON user_ip_address.vlan_db_id=vlan.id WHERE user_ip_address.account_id=5 AND user_ip_address.allocated IS NOT NULL AND (account.type != 'VirtualNetwork' ) AND (vlan.vlan_type = ** NOT SPECIFIED ** ) Link to automated test failure: http://jenkins.buildacloud.org/view/cloudstack-qa-master/job/test-smoke-matrix-master/5/suite=test_network/testReport/integration.smoke.test_network/TestReleaseIP/test_releaseIP/ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6131) [Automation] unable to dedicate a vlan range
Srikanteswararao Talluri created CLOUDSTACK-6131: Summary: [Automation] unable to dedicate a vlan range Key: CLOUDSTACK-6131 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6131 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.3.0 Steps to reproduce: === #1. List the available physical network using ListPhysicalNetwork # 2. Add a Guest Vlan range to the available physical network using UpdatePhysicalNetwork # 3. Dedicate the created guest vlan range to user account using DedicateGuestVlanRange Link to automated test failure: http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-smoke-matrix-4.3/1194/suite=test_guest_vlan_range/testReport/integration.smoke.test_guest_vlan_range/TestDedicateGuestVlanRange/test_dedicateGuestVlanRange/ Link to management server log: http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-matrix-4.3/distro=centos63,hypervisor=kvm,profile=kvm-centos63/lastSuccessfulBuild/artifact/246.tar.bz2 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-6131) [Automation] unable to dedicate a vlan range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-6131. Resolution: Not A Problem [Automation] unable to dedicate a vlan range - Key: CLOUDSTACK-6131 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6131 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.3.0 Steps to reproduce: === #1. List the available physical network using ListPhysicalNetwork # 2. Add a Guest Vlan range to the available physical network using UpdatePhysicalNetwork # 3. Dedicate the created guest vlan range to user account using DedicateGuestVlanRange Link to automated test failure: http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-smoke-matrix-4.3/1194/suite=test_guest_vlan_range/testReport/integration.smoke.test_guest_vlan_range/TestDedicateGuestVlanRange/test_dedicateGuestVlanRange/ Link to management server log: http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-matrix-4.3/distro=centos63,hypervisor=kvm,profile=kvm-centos63/lastSuccessfulBuild/artifact/246.tar.bz2 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6084) [Automation] NPE :Failed to create private gateway
Srikanteswararao Talluri created CLOUDSTACK-6084: Summary: [Automation] NPE :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 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 [agent.manager.DirectAgentAttache] (DirectAgent-310:ctx-dca6e64d) Ping from 2(apache-81-2) Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,916 DEBUG [network.vpc.VpcManagerImpl] (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Created vpc gateway entry VpcGateway[1|10.147.30.200|6] Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 10:23:49,935 DEBUG
[jira] [Updated] (CLOUDSTACK-6084) [Automation] Failed to create private gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-6084: - Summary: [Automation] Failed to create private gateway (was: [Automation] NPE :Failed to create private gateway) [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 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 [agent.manager.DirectAgentAttache] (DirectAgent-310:ctx-dca6e64d) Ping from
[jira] [Created] (CLOUDSTACK-6085) [Automation] exception while destroying CPVM/SSVM
Srikanteswararao Talluri created CLOUDSTACK-6085: Summary: [Automation] exception while destroying CPVM/SSVM Key: CLOUDSTACK-6085 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6085 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: xenserver6.2 , advanced zone Reporter: Srikanteswararao Talluri Priority: Critical Fix For: 4.4.0 Caught the following exception exception while destroying SSVM/CPVM. Service Dhcp is not supported in the network id=200 BVT failure : http://jenkins.buildacloud.org/job/test-smoke-matrix-master/2/suite=test_ssvm/testReport/integration.smoke.test_ssvm/TestSSVMs/test_09_destroy_ssvm/ Logs: http://jenkins.buildacloud.org/view/cloudstack-qa-master/job/test-matrix-master/3/distro=centos63,hypervisor=xen,profile=xen62/artifact/3.tar.bz2 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6086) [Automation] Failed to restart network
Srikanteswararao Talluri created CLOUDSTACK-6086: Summary: [Automation] Failed to restart network Key: CLOUDSTACK-6086 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6086 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 Priority: Critical Fix For: 4.4.0 Following tests failed during BVT run on latest master: http://jenkins.buildacloud.org/job/test-smoke-matrix-master/2/suite=test_routers/testReport/integration.smoke.test_routers/TestRouterServices/test_03_restart_network_cleanup/ http://jenkins.buildacloud.org/job/test-smoke-matrix-master/2/suite=test_routers/testReport/integration.smoke.test_routers/TestRouterServices/test_04_restart_network_wo_cleanup/ Logs: http://jenkins.buildacloud.org/view/cloudstack-qa-master/job/test-matrix-master/3/distro=centos63,hypervisor=xen,profile=xen62/artifact/3.tar.bz2 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6037) NPE: createZone is failing
Srikanteswararao Talluri created CLOUDSTACK-6037: Summary: NPE: createZone is failing Key: CLOUDSTACK-6037 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6037 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: simulator Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.4.0 createzone is leading to null pointer exception ===START=== 0:0:0:0:0:0:0:1 -- GET apiKey=KFzBif3dP05fiswvBQinoXhTuCIJ1486joeuFF00K4t4NRfASfuO3NAu91V0_RaCDa-2-iRO-1RS1yTQY7-OVAname=Sandbox-simulatorguestcidraddress=10.1.1.0%2F24dns1=10.147.28.6response=jsoncommand=createZonesignature=r1GVuOmky%2Fe%2BD2PrYuU2DGtmgtI%3Dnetworktype=Advancedinternaldns1=10.147.28.6 2014-02-06 01:26:24,561 WARN [c.c.a.d.ParamGenericValidationWorker] (1098327041@qtp-873745902-11:ctx-e309a5b3 ctx-288e38c3 ctx-8e4c188b) Received unkown parameters for command createzoneresponse. Unknown parameters : signature apikey 2014-02-06 01:26:24,595 DEBUG [o.a.c.e.o.NetworkOrchestrator] (1098327041@qtp-873745902-11:ctx-e309a5b3 ctx-288e38c3 ctx-8e4c188b) Releasing lock for Acct[25788f1c-8e9d-11e3-8e98-062a0033-system] 2014-02-06 01:26:24,624 DEBUG [c.c.u.d.T.Transaction] (1098327041@qtp-873745902-11:ctx-e309a5b3 ctx-288e38c3 ctx-8e4c188b) Rolling back the transaction: Time = 50 Name = 1098327041@qtp-873745902-11; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-Transaction.execute:46-ConfigurationManagerImpl.createZone:1782-ConfigurationManagerImpl.createZone:1922-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:601-AopUtils.invokeJoinpointUsingReflection:317 2014-02-06 01:26:24,643 ERROR [c.c.a.ApiServer] (1098327041@qtp-873745902-11:ctx-e309a5b3 ctx-288e38c3 ctx-8e4c188b) unhandled exception executing api command: createZone java.lang.NullPointerException at org.apache.cloudstack.network.contrail.management.ContrailGuru.canHandle(ContrailGuru.java:99) at org.apache.cloudstack.network.contrail.management.ContrailGuru.design(ContrailGuru.java:119) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:636) at com.cloud.configuration.ConfigurationManagerImpl.createDefaultSystemNetworks(ConfigurationManagerImpl.java:1865) at com.cloud.configuration.ConfigurationManagerImpl$6.doInTransaction(ConfigurationManagerImpl.java:1795) at com.cloud.configuration.ConfigurationManagerImpl$6.doInTransaction(ConfigurationManagerImpl.java:1782) at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.utils.db.Transaction.execute(Transaction.java:46) at com.cloud.configuration.ConfigurationManagerImpl.createZone(ConfigurationManagerImpl.java:1782) at com.cloud.configuration.ConfigurationManagerImpl.createZone(ConfigurationManagerImpl.java:1922) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.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 $Proxy112.createZone(Unknown Source) at org.apache.cloudstack.api.command.admin.zone.CreateZoneCmd.execute(CreateZoneCmd.java:170) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:109) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:329) at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) at
