[jira] [Commented] (CLOUDSTACK-7509) test_ss_limits.TestSecondaryStorageLimits.test_04_copy_template_1_root_domain_admin failed due to missing bound method

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126671#comment-14126671
 ] 

ASF subversion and git services commented on CLOUDSTACK-7509:
-

Commit bbb3ea5983928df66704ab78cef0a1c3e292cbe9 in cloudstack's branch 
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bbb3ea5 ]

CLOUDSTACK-7509: Added missing bound method in base library for copyTemplate 
operation

Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org


 test_ss_limits.TestSecondaryStorageLimits.test_04_copy_template_1_root_domain_admin
  failed due to missing bound method
 --

 Key: CLOUDSTACK-7509
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7509
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Bound method for copyTemplate is missing in library, hence test cases failed 
 during copy operation.
 test_04_copy_template_1_root_domain_admin 
 (integration.component.test_ss_limits.TestSecondaryStorageLimits): CRITICAL: 
 EXCEPTION: test_04_copy_template_1_root_domain_admin: ['Traceback (most 
 recent call last):\n', '  File /usr/local/lib/python2.7/unittest/case.py, 
 line 318, in run\ntestMethod()\n', '  File 
 /usr/local/lib/python2.7/site-packages/ddt.py, line 114, in wrapper\n
 return func(self, *args, **kwargs)\n', '  File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_ss_limits.py, 
 line 369, in test_04_copy_template\nsourcezoneid = template.zoneid)\n', 
 'TypeError: copy() takes exactly 5 arguments (4 given)\n']
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
 testMethod()
   File /usr/local/lib/python2.7/site-packages/ddt.py, line 114, in wrapper
 return func(self, *args, **kwargs)
   File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_ss_limits.py, 
 line 369, in test_04_copy_template
 sourcezoneid = template.zoneid)
 'copy() takes exactly 5 arguments (4 given)\n  begin 
 captured stdout  -\n=== TestName: 
 test_04_copy_template_1_root_domain_admin | Status : EXCEPTION 
 ===\n\n\n-  end captured stdout  
 --\n  begin captured logging  
 \ntest_04_copy_template_1_root_domain_admin 
 (integration.component.test_ss_limits.TestSecondaryStorageLimits): DEBUG: 
 STARTED : TC: test_04_copy_template_1_root_domain_admin 
 :::\ntest_04_copy_template_1_root_domain_admin 
 (integration.component.test_ss_limits.TestSecondaryStorageLimits): DEBUG: 
 Payload: {\'apiKey\': 
 u\'OK1UH4l8UUYHDWdnVSWETzepdzs07VAwZBCYZwS4W2zHupX3PAISs1Ug7oMKUBO17rHHkOr3ZAKFVf2fsKYIvQ\',
  \'command\': \'listZones\', \'signature\': \'H8DhzBD18g1bf1QQ1r7w5RU+eRU=\', 
 \'response\': \'json\'}\ntest_04_copy_template_1_root_domain_admin 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7515) [LXC] user VM is getting different mac than the one with router for the same VM in case of shared network

2014-09-09 Thread shweta agarwal (JIRA)
shweta agarwal created CLOUDSTACK-7515:
--

 Summary: [LXC] user VM is getting different mac than the one with 
router  for the same VM in case of shared network
 Key: CLOUDSTACK-7515
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7515
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: KVM, Network Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.5.0


Repro steps:

1. Create a advanced zone with LXC hosts having 2 clusters .one cluster having 
one host and other having two host .all host are LXC
2. Create a shared Network
3. Create a VM  using only shared network as default network

Bug:
Notice mac address that VM has is different than the one Router has for the 
same vm 

router VM shows

cat /etc/dhcphosts.txt
06:2e:70:00:00:1d,set:10_147_31_148,10.147.31.148,VM-bb8425ca-d97a-48dc-a69d-7ceb3ba454e2,infinite
06:b7:8a:00:00:18,set:10_147_31_143,10.147.31.143,VM-afcdd0b3-59e0-4104-8fe8-f12b344c6336,infinite
06:45:08:00:00:19,set:10_147_31_144,10.147.31.144,VM-ef2bbfd7-59d1-4e43-97fb-1a1ac233be9b,infinite
06:e2:c6:00:00:1b,set:10_147_31_146,10.147.31.146,VM-f0e8245a-b382-45d7-a01d-e63c111fbef5,infinite

For USER VM with  IP 10.147.31.144
router has mac06:45:08:00:00:19 but VM  has mac  06:4d:15:46:f3:c6 

Ifconfig on VM  shows
 ifconfig
eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
inet6 fe80::44d:15ff:fe46:f3c6  prefixlen 64  scopeid 0x20link
ether 06:4d:15:46:f3:c6  txqueuelen 1000  (Ethernet)
RX packets 1938  bytes 414054 (404.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 14  bytes 2700 (2.6 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73UP,LOOPBACK,RUNNING  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10host
loop  txqueuelen 0  (Local Loopback)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Notice even IP is not set for such VMs

Attaching Ms and agent logs









--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7516) test_snapshots.py - VM Deploy failed because the account was using template belonging to different account to deploy the instance

2014-09-09 Thread Gaurav Aradhye (JIRA)
Gaurav Aradhye created CLOUDSTACK-7516:
--

 Summary: test_snapshots.py - VM Deploy failed because the account 
was using template belonging to different account to deploy the instance
 Key: CLOUDSTACK-7516
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7516
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
 Fix For: 4.5.0


Following test case failed:

integration.component.test_snapshots.TestCreateVMSnapshotTemplate.test_01_createVM_snapshotTemplate

Reason:
Execute cmd: deployvirtualmachine failed, due to: errorCode: 531, 
errorText:Acct[51d00171-895e-4893-90c8-6630b98f852a-test-TestCreateVMSnapshotTemplate-BJ9XFN]
 does not have permission to operate with resource 
Acct[e7b7973c-3512-11e4-9ac6-1a6f7bb0d0a8-admin]

Solution:
Create the template with the api client of the account itself, and not the api 
client of root domain account. So that account will have permission to use the 
resources (template)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7506) Secondary Storage LImits test cases are failing while registering template with error Invalid Parameters - Hypervisor is required

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126693#comment-14126693
 ] 

ASF subversion and git services commented on CLOUDSTACK-7506:
-

Commit d08d71427bba562aa8b46a54143a783051297494 in cloudstack's branch 
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d08d714 ]

CLOUDSTACK-7506: Fix base library to read hypevisor value from dictionary as 
opposed to only from function parameter

Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org


 Secondary Storage LImits test cases are failing while registering template 
 with error Invalid Parameters - Hypervisor is required
 ---

 Key: CLOUDSTACK-7506
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7506
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Base library function is reading hypervisor value only from function 
 parameter and not from services dictionary. But the test cases are passing 
 hypervisor value from dictionary.
 Solution:
 Read the hypervisor value from the services dict if it's not passed through 
 the function parameter.
 Details:
 test_01_deploy_vm_domain_limit_reached 
 (integration.component.test_ss_max_limits.TestMaxSecondaryStorageLimits): 
 DEBUG: CmdName: registerTemplate Parameter : hypervisor is Required
 test_01_deploy_vm_domain_limit_reached 
 (integration.component.test_ss_max_limits.TestMaxSecondaryStorageLimits): 
 ERROR: marvinRequest : CmdName: 
 marvin.cloudstackAPI.registerTemplate.registerTemplateCmd object at 
 0x2855a10 Exception: ['Traceback (most recent call last):\n', '  File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 353, in marvinRequest\nraise self.__lastError\n', 
 'InvalidParameterException: Invalid Parameters\n']
 Traceback (most recent call last):
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 353, in marvinRequest
 raise self.__lastError
 InvalidParameterException: Invalid Parameters
 test_01_deploy_vm_domain_limit_reached 
 (integration.component.test_ss_max_limits.TestMaxSecondaryStorageLimits): 
 CRITICAL: FAILED: test_01_deploy_vm_domain_limit_reached: ['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/component/test_ss_max_limits.py, 
 line 183, in test_01_deploy_vm_domain_limit_reached\n
 self.assertEqual(response[0], PASS, response[1])\n', '  File 
 /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual\n
 assertion_func(first, second, msg=msg)\n', '  File 
 /usr/local/lib/python2.7/unittest/case.py, line 487, in _baseAssertEqual\n  
   raise self.failureException(msg)\n', 'AssertionError: Invalid Parameters\n']
 -  end captured logging  -



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7497) [UI] deploy VM failing as hypervisor type passed is KVM instead of LXC

2014-09-09 Thread Abhinandan Prateek (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-7497:
---
Assignee: Stephen Turner

 [UI] deploy VM  failing as hypervisor type passed is KVM instead of LXC
 ---

 Key: CLOUDSTACK-7497
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7497
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Stephen Turner
Priority: Blocker
 Fix For: 4.5.0


 Repro steps:
 Create a LXC zone with 2 cluster one LXc and one KVM
 Create  VM  with LXC template
 Bug:
 Deploy vm fails as hypervisor type is passed as KVM
 014-09-05 14:06:09,520 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24) ===START===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:09,581 INFO  [c.c.a.ApiServer] (catalina-exec-8:ctx-7b5dcb24 
 ctx-2a5b99cd) Hypervisor passed to the deployVm call, is different from the 
 hypervisor type of the template
 2014-09-05 14:06:09,582 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24 ctx-2a5b99cd) ===END===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:12,573 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
 (secstorage-1:ctx-6de2885c) Zone 2 is ready to launch secondary storage VM
 2014-09-05 14:06:12,689 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
 (consoleproxy-1:ctx-a134b2b7) Zone 2 is ready to launch console proxy



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7497) [UI] deploy VM failing as hypervisor type passed is KVM instead of LXC

2014-09-09 Thread Abhinandan Prateek (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126694#comment-14126694
 ] 

Abhinandan Prateek commented on CLOUDSTACK-7497:


Stephen,
  Can you have someone look into it ?

 [UI] deploy VM  failing as hypervisor type passed is KVM instead of LXC
 ---

 Key: CLOUDSTACK-7497
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7497
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Stephen Turner
Priority: Blocker
 Fix For: 4.5.0


 Repro steps:
 Create a LXC zone with 2 cluster one LXc and one KVM
 Create  VM  with LXC template
 Bug:
 Deploy vm fails as hypervisor type is passed as KVM
 014-09-05 14:06:09,520 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24) ===START===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:09,581 INFO  [c.c.a.ApiServer] (catalina-exec-8:ctx-7b5dcb24 
 ctx-2a5b99cd) Hypervisor passed to the deployVm call, is different from the 
 hypervisor type of the template
 2014-09-05 14:06:09,582 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24 ctx-2a5b99cd) ===END===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:12,573 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
 (secstorage-1:ctx-6de2885c) Zone 2 is ready to launch secondary storage VM
 2014-09-05 14:06:12,689 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
 (consoleproxy-1:ctx-a134b2b7) Zone 2 is ready to launch console proxy



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7515) [LXC] user VM is getting different mac than the one with router for the same VM in case of shared network

2014-09-09 Thread shweta agarwal (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal updated CLOUDSTACK-7515:
---
Attachment: agent-router.tar.gz
management-server.log.2014-09-08.gz
agen-user-vm.tar.gz

 [LXC] user VM is getting different mac than the one with router  for the same 
 VM in case of shared network
 --

 Key: CLOUDSTACK-7515
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7515
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Network Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.5.0

 Attachments: agen-user-vm.tar.gz, agent-router.tar.gz, 
 management-server.log.2014-09-08.gz


 Repro steps:
 1. Create a advanced zone with LXC hosts having 2 clusters .one cluster 
 having one host and other having two host .all host are LXC
 2. Create a shared Network
 3. Create a VM  using only shared network as default network
 Bug:
 Notice mac address that VM has is different than the one Router has for the 
 same vm 
 router VM shows
 cat /etc/dhcphosts.txt
 06:2e:70:00:00:1d,set:10_147_31_148,10.147.31.148,VM-bb8425ca-d97a-48dc-a69d-7ceb3ba454e2,infinite
 06:b7:8a:00:00:18,set:10_147_31_143,10.147.31.143,VM-afcdd0b3-59e0-4104-8fe8-f12b344c6336,infinite
 06:45:08:00:00:19,set:10_147_31_144,10.147.31.144,VM-ef2bbfd7-59d1-4e43-97fb-1a1ac233be9b,infinite
 06:e2:c6:00:00:1b,set:10_147_31_146,10.147.31.146,VM-f0e8245a-b382-45d7-a01d-e63c111fbef5,infinite
 For USER VM with  IP 10.147.31.144
 router has mac06:45:08:00:00:19 but VM  has mac  06:4d:15:46:f3:c6 
 Ifconfig on VM  shows
  ifconfig
 eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
 inet6 fe80::44d:15ff:fe46:f3c6  prefixlen 64  scopeid 0x20link
 ether 06:4d:15:46:f3:c6  txqueuelen 1000  (Ethernet)
 RX packets 1938  bytes 414054 (404.3 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 14  bytes 2700 (2.6 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 lo: flags=73UP,LOOPBACK,RUNNING  mtu 65536
 inet 127.0.0.1  netmask 255.0.0.0
 inet6 ::1  prefixlen 128  scopeid 0x10host
 loop  txqueuelen 0  (Local Loopback)
 RX packets 0  bytes 0 (0.0 B)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 0  bytes 0 (0.0 B)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 Notice even IP is not set for such VMs
 Attaching Ms and agent logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7515) [LXC] user VM is getting different mac than the one with router for the same VM in case of shared network

2014-09-09 Thread shweta agarwal (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal updated CLOUDSTACK-7515:
---
Description: 
Repro steps:

1. Create a advanced zone with LXC hosts having 2 clusters .one cluster having 
one host and other having two host .all host are LXC
2. Create a shared Network
3. Create a VM  using only shared network as default network

Bug:
Notice mac address that VM has is different than the one Router has for the 
same vm 

router VM shows

cat /etc/dhcphosts.txt
06:2e:70:00:00:1d,set:10_147_31_148,10.147.31.148,VM-bb8425ca-d97a-48dc-a69d-7ceb3ba454e2,infinite
06:b7:8a:00:00:18,set:10_147_31_143,10.147.31.143,VM-afcdd0b3-59e0-4104-8fe8-f12b344c6336,infinite
06:45:08:00:00:19,set:10_147_31_144,10.147.31.144,VM-ef2bbfd7-59d1-4e43-97fb-1a1ac233be9b,infinite
06:e2:c6:00:00:1b,set:10_147_31_146,10.147.31.146,VM-f0e8245a-b382-45d7-a01d-e63c111fbef5,infinite

For USER VM with  IP 10.147.31.144
router has mac06:45:08:00:00:19 but VM  has mac  06:4d:15:46:f3:c6 

Ifconfig on VM  shows
 ifconfig
eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
inet6 fe80::44d:15ff:fe46:f3c6  prefixlen 64  scopeid 0x20link
ether 06:4d:15:46:f3:c6  txqueuelen 1000  (Ethernet)
RX packets 1938  bytes 414054 (404.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 14  bytes 2700 (2.6 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73UP,LOOPBACK,RUNNING  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10host
loop  txqueuelen 0  (Local Loopback)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Additional information : 
dumpxml of LXC vm shows same mac which is available with router



Notice even IP is not set for such VMs

Attaching Ms and agent logs







  was:
Repro steps:

1. Create a advanced zone with LXC hosts having 2 clusters .one cluster having 
one host and other having two host .all host are LXC
2. Create a shared Network
3. Create a VM  using only shared network as default network

Bug:
Notice mac address that VM has is different than the one Router has for the 
same vm 

router VM shows

cat /etc/dhcphosts.txt
06:2e:70:00:00:1d,set:10_147_31_148,10.147.31.148,VM-bb8425ca-d97a-48dc-a69d-7ceb3ba454e2,infinite
06:b7:8a:00:00:18,set:10_147_31_143,10.147.31.143,VM-afcdd0b3-59e0-4104-8fe8-f12b344c6336,infinite
06:45:08:00:00:19,set:10_147_31_144,10.147.31.144,VM-ef2bbfd7-59d1-4e43-97fb-1a1ac233be9b,infinite
06:e2:c6:00:00:1b,set:10_147_31_146,10.147.31.146,VM-f0e8245a-b382-45d7-a01d-e63c111fbef5,infinite

For USER VM with  IP 10.147.31.144
router has mac06:45:08:00:00:19 but VM  has mac  06:4d:15:46:f3:c6 

Ifconfig on VM  shows
 ifconfig
eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
inet6 fe80::44d:15ff:fe46:f3c6  prefixlen 64  scopeid 0x20link
ether 06:4d:15:46:f3:c6  txqueuelen 1000  (Ethernet)
RX packets 1938  bytes 414054 (404.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 14  bytes 2700 (2.6 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73UP,LOOPBACK,RUNNING  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10host
loop  txqueuelen 0  (Local Loopback)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Notice even IP is not set for such VMs

Attaching Ms and agent logs








 [LXC] user VM is getting different mac than the one with router  for the same 
 VM in case of shared network
 --

 Key: CLOUDSTACK-7515
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7515
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Network Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.5.0

 Attachments: agen-user-vm.tar.gz, agent-router.tar.gz, 
 management-server.log.2014-09-08.gz


 Repro steps:
 1. Create a advanced zone with LXC hosts having 2 clusters .one cluster 
 having one host and other having two host .all host are LXC
 2. Create a shared Network
 3. Create a VM  using only shared network as default network
 Bug:
 Notice mac address that VM has is different than the one Router has for the 
 same vm 
 router VM shows
 cat 

[jira] [Commented] (CLOUDSTACK-7393) [Automation] Fix the script test_vpc_vm_life_cycle.py - Code is hardcoded to use certain host tags

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126715#comment-14126715
 ] 

ASF subversion and git services commented on CLOUDSTACK-7393:
-

Commit bd8eaf86fe07c8c90f71da8ca430cfb489159655 in cloudstack's branch 
refs/heads/4.4 from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bd8eaf8 ]

CLOUDSTACK-7393: Expunging VM immediately and removing unncessary wait in 
test_vpc_vm_life_cycle.py

Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org
(cherry picked from commit 402fc914cf4047b7faf1b1410972bb5a4ae5b29d)

Conflicts:
test/integration/component/test_vpc_vm_life_cycle.py


 [Automation] Fix the script test_vpc_vm_life_cycle.py - Code is hardcoded 
 to use certain host tags
 

 Key: CLOUDSTACK-7393
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7393
 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


 *Script is present at:*
 component/test_vpc_vm_life_cycle.py
 Currently script assumes that the deployment has hosts with host_tags host1 
 and host2 and uses two service offerings with these host_tags. The script 
 is hardcoded with the above information. The proper design and correction 
 should be as follows.
 Find the cluster with two hosts
 If no two host cluster is found error out with proper message
 Edit the host tags on the two hosts to two different unique names
 Create corresponding service offerings with the two different unique names
 Conduct the tests
 In teardown script section of the script, edit the host tags on the hosts 
 to empty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7509) test_ss_limits.TestSecondaryStorageLimits.test_04_copy_template_1_root_domain_admin failed due to missing bound method

2014-09-09 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye resolved CLOUDSTACK-7509.

Resolution: Fixed

 test_ss_limits.TestSecondaryStorageLimits.test_04_copy_template_1_root_domain_admin
  failed due to missing bound method
 --

 Key: CLOUDSTACK-7509
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7509
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Bound method for copyTemplate is missing in library, hence test cases failed 
 during copy operation.
 test_04_copy_template_1_root_domain_admin 
 (integration.component.test_ss_limits.TestSecondaryStorageLimits): CRITICAL: 
 EXCEPTION: test_04_copy_template_1_root_domain_admin: ['Traceback (most 
 recent call last):\n', '  File /usr/local/lib/python2.7/unittest/case.py, 
 line 318, in run\ntestMethod()\n', '  File 
 /usr/local/lib/python2.7/site-packages/ddt.py, line 114, in wrapper\n
 return func(self, *args, **kwargs)\n', '  File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_ss_limits.py, 
 line 369, in test_04_copy_template\nsourcezoneid = template.zoneid)\n', 
 'TypeError: copy() takes exactly 5 arguments (4 given)\n']
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
 testMethod()
   File /usr/local/lib/python2.7/site-packages/ddt.py, line 114, in wrapper
 return func(self, *args, **kwargs)
   File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_ss_limits.py, 
 line 369, in test_04_copy_template
 sourcezoneid = template.zoneid)
 'copy() takes exactly 5 arguments (4 given)\n  begin 
 captured stdout  -\n=== TestName: 
 test_04_copy_template_1_root_domain_admin | Status : EXCEPTION 
 ===\n\n\n-  end captured stdout  
 --\n  begin captured logging  
 \ntest_04_copy_template_1_root_domain_admin 
 (integration.component.test_ss_limits.TestSecondaryStorageLimits): DEBUG: 
 STARTED : TC: test_04_copy_template_1_root_domain_admin 
 :::\ntest_04_copy_template_1_root_domain_admin 
 (integration.component.test_ss_limits.TestSecondaryStorageLimits): DEBUG: 
 Payload: {\'apiKey\': 
 u\'OK1UH4l8UUYHDWdnVSWETzepdzs07VAwZBCYZwS4W2zHupX3PAISs1Ug7oMKUBO17rHHkOr3ZAKFVf2fsKYIvQ\',
  \'command\': \'listZones\', \'signature\': \'H8DhzBD18g1bf1QQ1r7w5RU+eRU=\', 
 \'response\': \'json\'}\ntest_04_copy_template_1_root_domain_admin 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7506) Secondary Storage LImits test cases are failing while registering template with error Invalid Parameters - Hypervisor is required

2014-09-09 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye resolved CLOUDSTACK-7506.

Resolution: Fixed

 Secondary Storage LImits test cases are failing while registering template 
 with error Invalid Parameters - Hypervisor is required
 ---

 Key: CLOUDSTACK-7506
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7506
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Base library function is reading hypervisor value only from function 
 parameter and not from services dictionary. But the test cases are passing 
 hypervisor value from dictionary.
 Solution:
 Read the hypervisor value from the services dict if it's not passed through 
 the function parameter.
 Details:
 test_01_deploy_vm_domain_limit_reached 
 (integration.component.test_ss_max_limits.TestMaxSecondaryStorageLimits): 
 DEBUG: CmdName: registerTemplate Parameter : hypervisor is Required
 test_01_deploy_vm_domain_limit_reached 
 (integration.component.test_ss_max_limits.TestMaxSecondaryStorageLimits): 
 ERROR: marvinRequest : CmdName: 
 marvin.cloudstackAPI.registerTemplate.registerTemplateCmd object at 
 0x2855a10 Exception: ['Traceback (most recent call last):\n', '  File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 353, in marvinRequest\nraise self.__lastError\n', 
 'InvalidParameterException: Invalid Parameters\n']
 Traceback (most recent call last):
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 353, in marvinRequest
 raise self.__lastError
 InvalidParameterException: Invalid Parameters
 test_01_deploy_vm_domain_limit_reached 
 (integration.component.test_ss_max_limits.TestMaxSecondaryStorageLimits): 
 CRITICAL: FAILED: test_01_deploy_vm_domain_limit_reached: ['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/component/test_ss_max_limits.py, 
 line 183, in test_01_deploy_vm_domain_limit_reached\n
 self.assertEqual(response[0], PASS, response[1])\n', '  File 
 /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual\n
 assertion_func(first, second, msg=msg)\n', '  File 
 /usr/local/lib/python2.7/unittest/case.py, line 487, in _baseAssertEqual\n  
   raise self.failureException(msg)\n', 'AssertionError: Invalid Parameters\n']
 -  end captured logging  -



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7515) [LXC] user VM is getting different mac than the one with router for the same VM in case of shared network

2014-09-09 Thread shweta agarwal (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal updated CLOUDSTACK-7515:
---
Priority: Blocker  (was: Critical)

 [LXC] user VM is getting different mac than the one with router  for the same 
 VM in case of shared network
 --

 Key: CLOUDSTACK-7515
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7515
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Network Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agen-user-vm.tar.gz, agent-router.tar.gz, 
 management-server.log.2014-09-08.gz


 Repro steps:
 1. Create a advanced zone with LXC hosts having 2 clusters .one cluster 
 having one host and other having two host .all host are LXC
 2. Create a shared Network
 3. Create a VM  using only shared network as default network
 Bug:
 Notice mac address that VM has is different than the one Router has for the 
 same vm 
 router VM shows
 cat /etc/dhcphosts.txt
 06:2e:70:00:00:1d,set:10_147_31_148,10.147.31.148,VM-bb8425ca-d97a-48dc-a69d-7ceb3ba454e2,infinite
 06:b7:8a:00:00:18,set:10_147_31_143,10.147.31.143,VM-afcdd0b3-59e0-4104-8fe8-f12b344c6336,infinite
 06:45:08:00:00:19,set:10_147_31_144,10.147.31.144,VM-ef2bbfd7-59d1-4e43-97fb-1a1ac233be9b,infinite
 06:e2:c6:00:00:1b,set:10_147_31_146,10.147.31.146,VM-f0e8245a-b382-45d7-a01d-e63c111fbef5,infinite
 For USER VM with  IP 10.147.31.144
 router has mac06:45:08:00:00:19 but VM  has mac  06:4d:15:46:f3:c6 
 Ifconfig on VM  shows
  ifconfig
 eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
 inet6 fe80::44d:15ff:fe46:f3c6  prefixlen 64  scopeid 0x20link
 ether 06:4d:15:46:f3:c6  txqueuelen 1000  (Ethernet)
 RX packets 1938  bytes 414054 (404.3 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 14  bytes 2700 (2.6 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 lo: flags=73UP,LOOPBACK,RUNNING  mtu 65536
 inet 127.0.0.1  netmask 255.0.0.0
 inet6 ::1  prefixlen 128  scopeid 0x10host
 loop  txqueuelen 0  (Local Loopback)
 RX packets 0  bytes 0 (0.0 B)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 0  bytes 0 (0.0 B)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 Additional information : 
 dumpxml of LXC vm shows same mac which is available with router
 Notice even IP is not set for such VMs
 Attaching Ms and agent logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7515) [LXC] user VM is getting different mac than the one with router for the same VM in case of shared network

2014-09-09 Thread shweta agarwal (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126749#comment-14126749
 ] 

shweta agarwal commented on CLOUDSTACK-7515:


making it blocker as its stopping my all testing related to shared networks

 [LXC] user VM is getting different mac than the one with router  for the same 
 VM in case of shared network
 --

 Key: CLOUDSTACK-7515
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7515
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Network Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agen-user-vm.tar.gz, agent-router.tar.gz, 
 management-server.log.2014-09-08.gz


 Repro steps:
 1. Create a advanced zone with LXC hosts having 2 clusters .one cluster 
 having one host and other having two host .all host are LXC
 2. Create a shared Network
 3. Create a VM  using only shared network as default network
 Bug:
 Notice mac address that VM has is different than the one Router has for the 
 same vm 
 router VM shows
 cat /etc/dhcphosts.txt
 06:2e:70:00:00:1d,set:10_147_31_148,10.147.31.148,VM-bb8425ca-d97a-48dc-a69d-7ceb3ba454e2,infinite
 06:b7:8a:00:00:18,set:10_147_31_143,10.147.31.143,VM-afcdd0b3-59e0-4104-8fe8-f12b344c6336,infinite
 06:45:08:00:00:19,set:10_147_31_144,10.147.31.144,VM-ef2bbfd7-59d1-4e43-97fb-1a1ac233be9b,infinite
 06:e2:c6:00:00:1b,set:10_147_31_146,10.147.31.146,VM-f0e8245a-b382-45d7-a01d-e63c111fbef5,infinite
 For USER VM with  IP 10.147.31.144
 router has mac06:45:08:00:00:19 but VM  has mac  06:4d:15:46:f3:c6 
 Ifconfig on VM  shows
  ifconfig
 eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
 inet6 fe80::44d:15ff:fe46:f3c6  prefixlen 64  scopeid 0x20link
 ether 06:4d:15:46:f3:c6  txqueuelen 1000  (Ethernet)
 RX packets 1938  bytes 414054 (404.3 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 14  bytes 2700 (2.6 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 lo: flags=73UP,LOOPBACK,RUNNING  mtu 65536
 inet 127.0.0.1  netmask 255.0.0.0
 inet6 ::1  prefixlen 128  scopeid 0x10host
 loop  txqueuelen 0  (Local Loopback)
 RX packets 0  bytes 0 (0.0 B)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 0  bytes 0 (0.0 B)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 Additional information : 
 dumpxml of LXC vm shows same mac which is available with router
 Notice even IP is not set for such VMs
 Attaching Ms and agent logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instanc

2014-09-09 Thread Sailaja Mada (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126763#comment-14126763
 ] 

Sailaja Mada commented on CLOUDSTACK-7505:
--

1.  Register  ISO and Installed Windows 8/2012 operating System 
2.  Attach PV tools and installed on to the Guest OS 

xe vm-param-list for this vm

uuid ( RO)  : f5b3e0b2-d61a-d0cc-2638-616feb9fc0d0
name-label ( RW): i-2-7-VM
  name-description ( RW): Clones of this template will 
automatically provision their storage when first booted and then reconfigure 
themselves with the optimal settings for Windows 8 (64-bit).
  user-version ( RW): 1
 is-a-template ( RW): false
 is-a-snapshot ( RO): false
   snapshot-of ( RO): not in database
 snapshots ( RO):
 snapshot-time ( RO): 19700101T00:00:00Z
 snapshot-info ( RO):
parent ( RO): not in database
  children ( RO):
 is-control-domain ( RO): false
   power-state ( RO): running
 memory-actual ( RO): 2147487744
 memory-target ( RO): unknown
   memory-overhead ( RO): 20971520
 memory-static-max ( RW): 2147483648
memory-dynamic-max ( RW): 2147483648
memory-dynamic-min ( RW): 2147483648
 memory-static-min ( RW): 2147483648
  suspend-VDI-uuid ( RW): not in database
   suspend-SR-uuid ( RW): not in database
  VCPUs-params (MRW): weight: 33; cap: 0
 VCPUs-max ( RW): 2
  VCPUs-at-startup ( RW): 2
actions-after-shutdown ( RW): Destroy
  actions-after-reboot ( RW): Restart
   actions-after-crash ( RW): Destroy
 console-uuids (SRO): b59bf3aa-cd56-cd96-0b3b-439d8a2860f2
  platform (MRW): timeoffset: 0; viridian: true; acpi: 1; 
apic: true; pae: true; videoram: 8; nx: true; vga: std
allowed-operations (SRO): changing_dynamic_range; migrate_send; 
pool_migrate; changing_VCPUs_live; suspend; hard_reboot; hard_shutdown; 
clean_reboot; clean_shutdown; pause; checkpoint; snapshot
current-operations (SRO):
blocked-operations (MRW):
   allowed-VBD-devices (SRO): 1; 2; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 
14; 15
   allowed-VIF-devices (SRO): 1; 2; 3; 4; 5; 6
possible-hosts ( RO): d079d968-6311-4bb2-87b7-0dc017971fa1
   HVM-boot-policy ( RW): BIOS order
   HVM-boot-params (MRW): order: dc
 HVM-shadow-multiplier ( RW): 1.000
 PV-kernel ( RW):
PV-ramdisk ( RW):
   PV-args ( RW):
PV-legacy-args ( RW):
 PV-bootloader ( RW):
PV-bootloader-args ( RW):
   last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: 
17bee3ff-bfebfbff-0001-2c100800
  last-boot-record ( RO): '('struct' ('uuid' 
'f5b3e0b2-d61a-d0cc-2638-616feb9fc0d0') ('allowed_operations' ('array')) 
('current_operations' ('struct' 
('OpaqueRef:a2590e3b-e04f-ea4a-66f1-4a90bcf5729a' 'start_on'))) ('power_state' 
'Halted') ('name_label' 'i-2-7-VM') ('name_description' 'Clones of this 
template will automatically provision their storage when first booted and then 
reconfigure themselves with the optimal settings for Windows 8 (64-bit).') 
('user_version' '1') ('is_a_template' ('boolean' '0')) ('suspend_VDI' 
'OpaqueRef:NULL') ('resident_on' 'OpaqueRef:NULL') ('affinity' 
'OpaqueRef:01ec70b4-aadf-5a08-7649-2e81495f3ff1') ('memory_overhead' 
'20971520') ('memory_target' '4294967296') ('memory_static_max' '2147483648') 
('memory_dynamic_max' '2147483648') ('memory_dynamic_min' '2147483648') 
('memory_static_min' '2147483648') ('VCPUs_params' ('struct' ('weight' '33') 
('cap' '0'))) ('VCPUs_max' '2') ('VCPUs_at_startup' '2') 
('actions_after_shutdown' 'destroy') ('actions_after_reboot' 'restart') 
('actions_after_crash' 'destroy') ('consoles' ('array')) ('VIFs' ('array' 
'OpaqueRef:c71b8934-60d5-c8c9-88fe-44b3357fb73b')) ('VBDs' ('array' 
'OpaqueRef:dda2c6d4-eed0-2888-d56f-604e90a4560c' 
'OpaqueRef:5eb90a80-63c8-0d2e-e1ce-0da8ab42d8f0')) ('crash_dumps' ('array')) 
('VTPMs' ('array')) ('PV_bootloader' '') ('PV_kernel' '') ('PV_ramdisk' '') 
('PV_args' '') ('PV_bootloader_args' '') ('PV_legacy_args' '') 
('HVM_boot_policy' 'BIOS order') ('HVM_boot_params' ('struct' ('order' 'dc'))) 
('HVM_shadow_multiplier' ('double' '1')) ('platform' ('struct' ('viridian' 
'true') ('acpi' '1') ('apic' 'true') ('pae' 'true') ('videoram' '8') ('nx' 
'true') ('vga' 'std'))) ('PCI_bus' '') ('other_config' ('struct' ('mac_seed' 
'5232f4ca-45f7-5e01-65bb-9fc14eab8ff1') ('install-methods' 'cdrom') ('vm_uuid' 

[jira] [Updated] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances

2014-09-09 Thread Sailaja Mada (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sailaja Mada updated CLOUDSTACK-7505:
-
Attachment: i-2-10-VM-from-tools-template
i-2-7-vm-params-after-registeriso-PVtoolsinstallation

 Windows 2012 and Windows 8 instances created with 6.5 PV tools installed 
 template are getting into repair state, Later XenServer 6.5 Is shutting down 
 these instances automatically 
 

 Key: CLOUDSTACK-7505
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.5.0
Reporter: Sailaja Mada
Priority: Blocker
 Attachments: i-2-10-VM-from-tools-template, 
 i-2-7-vm-params-after-registeriso-PVtoolsinstallation


 Steps:
 1. Configure Adv Zone using XenServer 6.5 
 2.  Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools 
 installed.I have enabled option Original XS Version is 6.1+: Yes
 3. Deployed VM using this template 
 4. VM got started and moved to running state. But  got  into repair state, 
 Later XenServer 6.5 Is shutting down these instances automatically.
 VM Parameters are : 
   platform (MRW): timeoffset: 0; viridian: true; acpi: 1; 
 ap
 ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std
 allowed-operations (SRO): changing_dynamic_range; hard_reboot; 
 hard_
 shutdown; pause; snapshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7421) [Automation] Exceptions in orchestrate* methods from virtualMachineManagerImpl are shown in log

2014-09-09 Thread Jayapal Reddy (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayapal Reddy updated CLOUDSTACK-7421:
--
Summary: [Automation] Exceptions in orchestrate* methods from 
virtualMachineManagerImpl are shown in log  (was: [Automation] Remove nic from 
default report CloudRuntimeException in log)

 [Automation] Exceptions in orchestrate* methods from 
 virtualMachineManagerImpl are shown in log
 ---

 Key: CLOUDSTACK-7421
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7421
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Rayees Namathponnan
Assignee: Jayapal Reddy
 Fix For: 4.5.0


 Steps to reproduce 
 1 ) Deploy VM 
 2) Add one more nic
 3) remove default nic the VM 
 Result 
 Below exception thrown in log, it should be handled with proper messgae 
 cloud.vm.VmWorkRemoveNicFromVm for VM 30, job origin: 248
 2014-08-23 09:50:33,665 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-61:ctx-5c747fe0 job-248/job-249) Unable to complete 
 AsyncJobVO {id:249, userId: 2, accountId: 2, instanceType: null, instanceId: 
 null, cmd: com.cloud.vm.VmWorkRemoveNicFromVm, cmdInfo: 
 rO0ABXNyACJjb20uY2xvdWQudm0uVm1Xb3JrUmVtb3ZlTmljRnJvbVZtxM1Xh9nBu10CAAFMAAVuaWNJZHQAEExqYXZhL2xhbmcvTG9uZzt4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAB50ABlWaXJ0dWFsTWFjaGluZU1hbmFnZXJJbXBsc3IADmphdmEubGFuZy5Mb25nO4vkkMyPI98CAAFKAAV2YWx1ZXhyABBqYXZhLmxhbmcuTnVtYmVyhqyVHQuU4IsCAAB4cABI,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 90928106758026, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Sat Aug 23 09:50:32 PDT 2014}, job origin:248
 com.cloud.utils.exception.CloudRuntimeException: Failed to remove nic from 
 VM[User|i-18-30-TestVM] in Ntwk[222|Guest|17], nic is default.
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:2963)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:4690)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4738)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7421) [Automation] Exceptions in orchestrate* methods from virtualMachineManagerImpl are shown in log

2014-09-09 Thread Jayapal Reddy (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126779#comment-14126779
 ] 

Jayapal Reddy commented on CLOUDSTACK-7421:
---

I tried to fix the issue mentioned in the description (remove nic from vm), 
observed that there are other method which are start with orchestrate* are 
throwing exceptions which are not catched. These exceptions are showed in the 
logs.

In virtualMachineMangerImpl.java method orchestrate* 
(orchestrateRemoveNicFromVm, orchestrateAddVmToNetwork, 
orchestrateRemoveVmFromNetwork etc) thrown exceptions are not catcher by the 
async job implementation.

The fix needs to be done generically in vmwork async job implementaiton.

 

 [Automation] Exceptions in orchestrate* methods from 
 virtualMachineManagerImpl are shown in log
 ---

 Key: CLOUDSTACK-7421
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7421
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Rayees Namathponnan
Assignee: Jayapal Reddy
 Fix For: 4.5.0


 Steps to reproduce 
 1 ) Deploy VM 
 2) Add one more nic
 3) remove default nic the VM 
 Result 
 Below exception thrown in log, it should be handled with proper messgae 
 cloud.vm.VmWorkRemoveNicFromVm for VM 30, job origin: 248
 2014-08-23 09:50:33,665 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-61:ctx-5c747fe0 job-248/job-249) Unable to complete 
 AsyncJobVO {id:249, userId: 2, accountId: 2, instanceType: null, instanceId: 
 null, cmd: com.cloud.vm.VmWorkRemoveNicFromVm, cmdInfo: 
 rO0ABXNyACJjb20uY2xvdWQudm0uVm1Xb3JrUmVtb3ZlTmljRnJvbVZtxM1Xh9nBu10CAAFMAAVuaWNJZHQAEExqYXZhL2xhbmcvTG9uZzt4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAB50ABlWaXJ0dWFsTWFjaGluZU1hbmFnZXJJbXBsc3IADmphdmEubGFuZy5Mb25nO4vkkMyPI98CAAFKAAV2YWx1ZXhyABBqYXZhLmxhbmcuTnVtYmVyhqyVHQuU4IsCAAB4cABI,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 90928106758026, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Sat Aug 23 09:50:32 PDT 2014}, job origin:248
 com.cloud.utils.exception.CloudRuntimeException: Failed to remove nic from 
 VM[User|i-18-30-TestVM] in Ntwk[222|Guest|17], nic is default.
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:2963)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:4690)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4738)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7421) [Automation] Exceptions in orchestrate* methods from virtualMachineManagerImpl are shown in log

2014-09-09 Thread Jayapal Reddy (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayapal Reddy updated CLOUDSTACK-7421:
--
Assignee: (was: Jayapal Reddy)

 [Automation] Exceptions in orchestrate* methods from 
 virtualMachineManagerImpl are shown in log
 ---

 Key: CLOUDSTACK-7421
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7421
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Rayees Namathponnan
 Fix For: 4.5.0


 Steps to reproduce 
 1 ) Deploy VM 
 2) Add one more nic
 3) remove default nic the VM 
 Result 
 Below exception thrown in log, it should be handled with proper messgae 
 cloud.vm.VmWorkRemoveNicFromVm for VM 30, job origin: 248
 2014-08-23 09:50:33,665 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-61:ctx-5c747fe0 job-248/job-249) Unable to complete 
 AsyncJobVO {id:249, userId: 2, accountId: 2, instanceType: null, instanceId: 
 null, cmd: com.cloud.vm.VmWorkRemoveNicFromVm, cmdInfo: 
 rO0ABXNyACJjb20uY2xvdWQudm0uVm1Xb3JrUmVtb3ZlTmljRnJvbVZtxM1Xh9nBu10CAAFMAAVuaWNJZHQAEExqYXZhL2xhbmcvTG9uZzt4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAB50ABlWaXJ0dWFsTWFjaGluZU1hbmFnZXJJbXBsc3IADmphdmEubGFuZy5Mb25nO4vkkMyPI98CAAFKAAV2YWx1ZXhyABBqYXZhLmxhbmcuTnVtYmVyhqyVHQuU4IsCAAB4cABI,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 90928106758026, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Sat Aug 23 09:50:32 PDT 2014}, job origin:248
 com.cloud.utils.exception.CloudRuntimeException: Failed to remove nic from 
 VM[User|i-18-30-TestVM] in Ntwk[222|Guest|17], nic is default.
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:2963)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:4690)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4738)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Issue Comment Deleted] (CLOUDSTACK-7184) HA should wait for at least 'xen.heartbeat.interval' sec before starting HA on vm's when host is marked down

2014-09-09 Thread Daan Hoogland (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daan Hoogland updated CLOUDSTACK-7184:
--
Comment: was deleted

(was: Hi, I am currently out of office and will be back Tuesday the 23rd of 
September. During this time I will have limited access to e-mail and might not 
be able to take your call. For urgent matter regarding ASR please contact 
int-...@schubergphilis.com instead. For Cloud IaaS matters please contact 
int-cl...@schubergphilis.com.

Kind regards,
Joris van Lieshout


Schuberg Philis
schubergphilis.com

+31207506672
+31651428188
)

 HA should wait for at least 'xen.heartbeat.interval' sec before starting HA 
 on vm's when host is marked down
 

 Key: CLOUDSTACK-7184
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7184
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server, XenServer
Affects Versions: 4.3.0, 4.4.0, 4.5.0
 Environment: CloudStack 4.3 with XenServer 6.2 hypervisors
Reporter: Remi Bergsma
Priority: Blocker

 Hypervisor got isolated for 30 seconds due to a network issue. CloudStack did 
 discover this and marked the host as down, and immediately started HA. Just 
 18 seconds later the hypervisor returned and we ended up with 5 vm's that 
 were running on two hypervisors at the same time. 
 This, of course, resulted in file system corruption and the loss of the vm's. 
 One side of the story is why XenServer allowed this to happen (will not 
 bother you with this one). The CloudStack side of the story: HA should only 
 start after at least xen.heartbeat.interval seconds. If the host is down long 
 enough, the Xen heartbeat script will fence the hypervisor and prevent 
 corruption. If it is not down long enough, nothing should happen.
 Logs (short):
 2014-07-25 05:03:28,596 WARN  [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-122:ctx-690badc5) Unable to get current status on 505(mccpvmXX)
 .
 2014-07-25 05:03:31,920 ERROR [c.c.a.m.AgentManagerImpl] 
 (AgentTaskPool-10:ctx-11b9af3e) Host is down: 505-mccpvmXX.  Starting HA on 
 the VMs
 .
 2014-07-25 05:03:49,655 DEBUG [c.c.h.Status] (ClusteredAgentManager 
 Timer:ctx-0e00979c) Transition:[Resource state = Enabled, Agent event = 
 AgentDisconnected, Host id = 505, name = mccpvmXX]
 cs marks host down: 2014-07-25  05:03:31,920
 cs marks host up: 2014-07-25  05:03:49,655



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (CLOUDSTACK-7184) HA should wait for at least 'xen.heartbeat.interval' sec before starting HA on vm's when host is marked down

2014-09-09 Thread Daan Hoogland (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daan Hoogland reassigned CLOUDSTACK-7184:
-

Assignee: Daan Hoogland

 HA should wait for at least 'xen.heartbeat.interval' sec before starting HA 
 on vm's when host is marked down
 

 Key: CLOUDSTACK-7184
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7184
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server, XenServer
Affects Versions: 4.3.0, 4.4.0, 4.5.0
 Environment: CloudStack 4.3 with XenServer 6.2 hypervisors
Reporter: Remi Bergsma
Assignee: Daan Hoogland
Priority: Blocker

 Hypervisor got isolated for 30 seconds due to a network issue. CloudStack did 
 discover this and marked the host as down, and immediately started HA. Just 
 18 seconds later the hypervisor returned and we ended up with 5 vm's that 
 were running on two hypervisors at the same time. 
 This, of course, resulted in file system corruption and the loss of the vm's. 
 One side of the story is why XenServer allowed this to happen (will not 
 bother you with this one). The CloudStack side of the story: HA should only 
 start after at least xen.heartbeat.interval seconds. If the host is down long 
 enough, the Xen heartbeat script will fence the hypervisor and prevent 
 corruption. If it is not down long enough, nothing should happen.
 Logs (short):
 2014-07-25 05:03:28,596 WARN  [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-122:ctx-690badc5) Unable to get current status on 505(mccpvmXX)
 .
 2014-07-25 05:03:31,920 ERROR [c.c.a.m.AgentManagerImpl] 
 (AgentTaskPool-10:ctx-11b9af3e) Host is down: 505-mccpvmXX.  Starting HA on 
 the VMs
 .
 2014-07-25 05:03:49,655 DEBUG [c.c.h.Status] (ClusteredAgentManager 
 Timer:ctx-0e00979c) Transition:[Resource state = Enabled, Agent event = 
 AgentDisconnected, Host id = 505, name = mccpvmXX]
 cs marks host down: 2014-07-25  05:03:31,920
 cs marks host up: 2014-07-25  05:03:49,655



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7518) SSVM stop/start is not initiating the download for Partially downloaded ISO's

2014-09-09 Thread Sailaja Mada (JIRA)
Sailaja Mada created CLOUDSTACK-7518:


 Summary: SSVM stop/start is not initiating the download for 
Partially downloaded ISO's 
 Key: CLOUDSTACK-7518
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7518
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Template, XenServer
Affects Versions: 4.5.0
Reporter: Sailaja Mada
Priority: Critical
 Attachments: isologs.zip

Setup:

1. Configure Adv Zone with XS 6.5 
2.  Register Windows 2012 ISO , Waited for it to download 20% 
3. Stop SSVM 
4. ISO details gets the status as SSVM Agent  disconnected
5. Start SSVM 

Observation: 

SSVM stop/start is not initiating the download for Partially downloaded 
templates/ISO's 






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7518) SSVM stop/start is not initiating the download for Partially downloaded ISO's

2014-09-09 Thread Sailaja Mada (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sailaja Mada updated CLOUDSTACK-7518:
-
Attachment: isologs.zip

 SSVM stop/start is not initiating the download for Partially downloaded ISO's 
 --

 Key: CLOUDSTACK-7518
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7518
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template, XenServer
Affects Versions: 4.5.0
Reporter: Sailaja Mada
Priority: Critical
 Fix For: 4.5.0

 Attachments: isologs.zip


 Setup:
 1. Configure Adv Zone with XS 6.5 
 2.  Register Windows 2012 ISO , Waited for it to download 20% 
 3. Stop SSVM 
 4. ISO details gets the status as SSVM Agent  disconnected
 5. Start SSVM 
 Observation: 
 SSVM stop/start is not initiating the download for Partially downloaded 
 templates/ISO's 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7518) SSVM stop/start is not initiating the download for Partially downloaded ISO's

2014-09-09 Thread Sailaja Mada (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sailaja Mada updated CLOUDSTACK-7518:
-
Fix Version/s: 4.5.0

 SSVM stop/start is not initiating the download for Partially downloaded ISO's 
 --

 Key: CLOUDSTACK-7518
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7518
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template, XenServer
Affects Versions: 4.5.0
Reporter: Sailaja Mada
Priority: Critical
 Fix For: 4.5.0

 Attachments: isologs.zip


 Setup:
 1. Configure Adv Zone with XS 6.5 
 2.  Register Windows 2012 ISO , Waited for it to download 20% 
 3. Stop SSVM 
 4. ISO details gets the status as SSVM Agent  disconnected
 5. Start SSVM 
 Observation: 
 SSVM stop/start is not initiating the download for Partially downloaded 
 templates/ISO's 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7419) Document How to configure SAML SSO/SLO with CloudStack

2014-09-09 Thread Rohit Yadav (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav closed CLOUDSTACK-7419.
---

 Document How to configure SAML SSO/SLO with CloudStack
 --

 Key: CLOUDSTACK-7419
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7419
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Rohit Yadav
Assignee: Rohit Yadav
Priority: Minor
 Fix For: 4.5.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7419) Document How to configure SAML SSO/SLO with CloudStack

2014-09-09 Thread Rohit Yadav (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav resolved CLOUDSTACK-7419.
-
Resolution: Fixed

Merged pr on master

 Document How to configure SAML SSO/SLO with CloudStack
 --

 Key: CLOUDSTACK-7419
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7419
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Rohit Yadav
Assignee: Rohit Yadav
Priority: Minor
 Fix For: 4.5.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-6682) SSL Offload setup fail ( Unable to decode certificate chain using cloud monkey )

2014-09-09 Thread Rohit Yadav (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav closed CLOUDSTACK-6682.
---
Resolution: Invalid

CloudMonkey is simply printing the issue raised by Management server, the issue 
is with uploadSslCert command. If you get this issue again please re-file with 
steps to reproduce. This api works for me and this issue is not caused by 
cloudmonkey.

 SSL Offload setup fail ( Unable to decode certificate chain using cloud 
 monkey )
 

 Key: CLOUDSTACK-6682
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6682
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Cloudmonkey
Affects Versions: 4.3.0
 Environment: XenServer 6.2, Cloudmonkey 5.1
Reporter: young joon jeong
Assignee: Rohit Yadav

 i tried ssl offload using cloudMonkey CLI. but failed to execute due to an 
 follow error message.
 2014-05-15 17:12:49,112 INFO  [cloud.api.ApiServer] 
 (catalina-exec-11:ctx-1bd06c6a) (userId=2 accountId=2 
 sessionId=08E9A6FF3418155D010DE1044F72546B) 121.160.134.63 -- POST 
 command=login domain=/
 2014-05-15 17:12:49,137 INFO  [cloud.api.ApiServer] 
 (catalina-exec-5:ctx-629547b3 ctx-12bf11a8) (userId=2 accountId=2 
 sessionId=08E9A6FF3418155D010DE1044F72546B) 121.160.134.63 -- GET 
 signatureversion=3certificate=sktelecom.com.crtexpires=2014-05-15T08%3A22%3A44%2Bprivatekey=sktelecom.com.keysessionkey=TjQ2CU2p1IegLsbjp2%2BJvjKv%2Fj4%3Dcommand=uploadSslCertcertchain=chainca.crtresponse=json
  530 Unable to decode certificate chain



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7519) [Task] Use bound/unbound menthods instead of calling API directly from test case

2014-09-09 Thread Gaurav Aradhye (JIRA)
Gaurav Aradhye created CLOUDSTACK-7519:
--

 Summary: [Task] Use bound/unbound menthods instead of calling API 
directly from test case
 Key: CLOUDSTACK-7519
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7519
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
 Fix For: 4.5.0


test_templates.py file has many instances where direct APIs are called from the 
test case. Instead we have the methods in base library that can be used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7519) [Task] Use bound/unbound menthods instead of calling API directly from test case

2014-09-09 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye updated CLOUDSTACK-7519:
---
Status: Reviewable  (was: In Progress)

 [Task] Use bound/unbound menthods instead of calling API directly from test 
 case
 

 Key: CLOUDSTACK-7519
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7519
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 test_templates.py file has many instances where direct APIs are called from 
 the test case. Instead we have the methods in base library that can be used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7456) Command-line flag to control display type of cloudmonkey

2014-09-09 Thread Rohit Yadav (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav closed CLOUDSTACK-7456.
---
Resolution: Fixed

Fixed on master, this will come in next version. -d on command line to specific 
json, default or table output. But, this will override only if cloudmonkey is 
ran from command line, in interpreter mode a command like set display/profile 
will change the output format passed on cmd line.

https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=commit;h=f1f27e3

 Command-line flag to control display type of cloudmonkey
 

 Key: CLOUDSTACK-7456
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7456
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Cloudmonkey
 Environment: Cloudmonkey 5.2
Reporter: Shalom Bhooshi
Assignee: Rohit Yadav
Priority: Minor

 It would be useful to have cloudmonkey take command-line flags (-j, -t, -d) 
 that control the display type (json, tabular, default, etc) in addition to 
 the default set in ~/.cloudmonkey/config.
 This would allow for scripts requiring json to control the output without 
 affecting the user's preferences (usually default or tabular).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7459) CloudMonkey does not honour quoted/escaped (keyword) arguments containing whitespace

2014-09-09 Thread Rohit Yadav (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav closed CLOUDSTACK-7459.
---
Resolution: Fixed

Fixed on master;

Refs: master, origin/HEAD, origin/master, 5.2.0-13-g1980b6c
Author: Rohit Yadav rohit.ya...@shapeblue.com
AuthorDate: Tue Sep 9 14:45:25 2014 +0200
Commit: Rohit Yadav rohit.ya...@shapeblue.com
CommitDate: Tue Sep 9 14:47:03 2014 +0200

CLOUDSTACK-7459: Honour quoted/escaped arguments from command line


 CloudMonkey does not honour quoted/escaped (keyword) arguments containing 
 whitespace
 

 Key: CLOUDSTACK-7459
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7459
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Cloudmonkey
 Environment: cloudmonkey 5.2.0
Reporter: Shalom Bhooshi
Assignee: Rohit Yadav

 {code}
 # cloudmonkey --version
 cloudmonkey 5.2.0
 {code}
 {code}
 # bash --version
 GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
 {code}
 This is expected to work.
 {code}
 # cloudmonkey list ostypes keyword='Windows Server 2012'
 Error:Unauthorized None
 {code}
 As is this.
 {code}
 # cloudmonkey list ostypes keyword=Windows\ Server\ 2012
 Error:Unauthorized None
 {code}
 One needs to escape the whitespace further in the quoted string. This is not 
 expected.
 {code}
 # cloudmonkey list ostypes keyword='Windows\ Server\ 2012'
 {
   count: 1,
   ostype: [
 {
   description: Windows Server 2012 (64-bit),
   id: 7d6609ea-49ef-11e3-9349-001d096561b2,
   oscategoryid: 762042ae-49ef-11e3-9349-001d096561b2
 }
   ]
 }
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7520) UI: keep advanced search parameters visible after search has been run

2014-09-09 Thread Mihaela Stoica (JIRA)
Mihaela Stoica created CLOUDSTACK-7520:
--

 Summary: UI: keep advanced search parameters visible after search 
has been run
 Key: CLOUDSTACK-7520
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7520
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.5.0
Reporter: Mihaela Stoica
 Fix For: 4.5.0


After user runs an advanced search, the parameters they have entered into the 
search box disappear.
- This causes confusion, because users often can't remember what they have 
searched for to get their current search results.
- Parameters entered into the advance search box should remain visible after 
user runs the
 search, to mitigate confusion and enable way-finding.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (CLOUDSTACK-7520) UI: keep advanced search parameters visible after search has been run

2014-09-09 Thread Mihaela Stoica (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mihaela Stoica reassigned CLOUDSTACK-7520:
--

Assignee: Mihaela Stoica

 UI: keep advanced search parameters visible after search has been run
 -

 Key: CLOUDSTACK-7520
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7520
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: Mihaela Stoica
Assignee: Mihaela Stoica
 Fix For: 4.5.0


 After user runs an advanced search, the parameters they have entered into the 
 search box disappear.
 - This causes confusion, because users often can't remember what they have 
 searched for to get their current search results.
 - Parameters entered into the advance search box should remain visible after 
 user runs the
  search, to mitigate confusion and enable way-finding.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7520) [UI] keep advanced search parameters visible after search has been run

2014-09-09 Thread Mihaela Stoica (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mihaela Stoica updated CLOUDSTACK-7520:
---
Summary: [UI] keep advanced search parameters visible after search has been 
run  (was: UI: keep advanced search parameters visible after search has been 
run)

 [UI] keep advanced search parameters visible after search has been run
 --

 Key: CLOUDSTACK-7520
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7520
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: Mihaela Stoica
Assignee: Mihaela Stoica
 Fix For: 4.5.0


 After user runs an advanced search, the parameters they have entered into the 
 search box disappear.
 - This causes confusion, because users often can't remember what they have 
 searched for to get their current search results.
 - Parameters entered into the advance search box should remain visible after 
 user runs the
  search, to mitigate confusion and enable way-finding.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7502) [UI] Host detail page - Display KVM agent version and Qemu version

2014-09-09 Thread Mihaela Stoica (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mihaela Stoica updated CLOUDSTACK-7502:
---
Summary: [UI] Host detail page - Display KVM agent version and Qemu version 
 (was: UI - Host detail page - Display KVM agent version and Qemu version)

 [UI] Host detail page - Display KVM agent version and Qemu version
 --

 Key: CLOUDSTACK-7502
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7502
 Project: CloudStack
  Issue Type: Task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: Mihaela Stoica
Assignee: Mihaela Stoica
 Fix For: 4.5.0


 UI - Host detail page - Display KVM agent version and Qemu version.
 For KVM hosts, Host detail page should include KVM agent version and Qemu 
 version.
 The information can be obtained via listHosts API command, details field: 
 CCP.Qemu.Img.Version is the version of qemu image, and CCP.KVM.Agent.Version 
 is the version of kvm agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7520) [UI] keep advanced search parameters visible after search has been run

2014-09-09 Thread Mihaela Stoica (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126992#comment-14126992
 ] 

Mihaela Stoica commented on CLOUDSTACK-7520:


Review request: https://reviews.apache.org/r/25476/

 [UI] keep advanced search parameters visible after search has been run
 --

 Key: CLOUDSTACK-7520
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7520
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: Mihaela Stoica
Assignee: Mihaela Stoica
 Fix For: 4.5.0


 After user runs an advanced search, the parameters they have entered into the 
 search box disappear.
 - This causes confusion, because users often can't remember what they have 
 searched for to get their current search results.
 - Parameters entered into the advance search box should remain visible after 
 user runs the
  search, to mitigate confusion and enable way-finding.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7159) Add state parameter to the listPublicIpAddresses API call

2014-09-09 Thread Ilia Shakitko (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilia Shakitko closed CLOUDSTACK-7159.
-

 Add state parameter to the listPublicIpAddresses API call
 -

 Key: CLOUDSTACK-7159
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7159
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Reporter: Ilia Shakitko
Priority: Minor
 Fix For: Future, 4.5.0


 Few times we've faced an impedemence of having a list of Free 
 publicIpAddresses. You have to go thru all the IPs with (allocatedonly = 
 false) and filter out the Free once. It's not a big deal, but it's an extra 
 time and traffic between CloudStack and an API consumer.
 It would be useful to have state parameter. In this case you can query API 
 like this:
 {code}
 list publicipaddresses forvirtualnetwork=false state=free
 {code}
 and have a list of Free publicIpAddresses.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7159) Add state parameter to the listPublicIpAddresses API call

2014-09-09 Thread Ilia Shakitko (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilia Shakitko resolved CLOUDSTACK-7159.
---
Resolution: Implemented

 Add state parameter to the listPublicIpAddresses API call
 -

 Key: CLOUDSTACK-7159
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7159
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Reporter: Ilia Shakitko
Priority: Minor
 Fix For: Future, 4.5.0


 Few times we've faced an impedemence of having a list of Free 
 publicIpAddresses. You have to go thru all the IPs with (allocatedonly = 
 false) and filter out the Free once. It's not a big deal, but it's an extra 
 time and traffic between CloudStack and an API consumer.
 It would be useful to have state parameter. In this case you can query API 
 like this:
 {code}
 list publicipaddresses forvirtualnetwork=false state=free
 {code}
 and have a list of Free publicIpAddresses.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7520) [UI] keep advanced search parameters visible after search has been run

2014-09-09 Thread Mihaela Stoica (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mihaela Stoica updated CLOUDSTACK-7520:
---
Status: Reviewable  (was: In Progress)

 [UI] keep advanced search parameters visible after search has been run
 --

 Key: CLOUDSTACK-7520
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7520
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: Mihaela Stoica
Assignee: Mihaela Stoica
 Fix For: 4.5.0


 After user runs an advanced search, the parameters they have entered into the 
 search box disappear.
 - This causes confusion, because users often can't remember what they have 
 searched for to get their current search results.
 - Parameters entered into the advance search box should remain visible after 
 user runs the
  search, to mitigate confusion and enable way-finding.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Siavash Safi (JIRA)
Siavash Safi created CLOUDSTACK-7521:


 Summary: DB migration from 4.2.1 to 4.4.0 fails
 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker


I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
fails to start.
After checking syslog I noticed an exception related to DB migration.
Here is the mysql error output when trying to run migration schema manually:
{noformat}
root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
/usr/share/cloudstack-management/setup/db/schema-421to430.sql
Enter password:
ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that column/key 
exists
ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
column/key exists
ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
column/key exists
ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
column/key exists
ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
ERROR 1060 (42S21) at line 40: Duplicate column name 'power_state_update_count'
ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
(errno: 121)
ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
'network_details'
ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
ERROR 1054 (42S22) at line 597: Unknown column 'display_detail' in 
'volume_details'
ERROR 1054 (42S22) at line 598: Unknown column 'display_detail' in 'nic_details'
ERROR 1054 (42S22) at line 599: Unknown column 'display_detail' in 
'user_vm_details'
ERROR 1060 (42S21) at line 600: Duplicate column name 'display'
ERROR 1060 (42S21) at line 601: Duplicate column name 'display'
ERROR 1064 (42000) at line 634: You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near '--insert into cloud.monitoring_services(id, uuid, service, 
process_name, service' at line 1
ERROR 1064 (42000) at line 635: You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near '--insert into cloud.monitoring_services(id, uuid, service, 
process_name, service' at line 1
ERROR 1064 (42000) at line 636: You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near '--insert into cloud.monitoring_services(id, uuid, service, 
process_name, service' at line 1
ERROR 1064 (42000) at line 637: You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near '--insert into cloud.monitoring_services(id, uuid, service, 
process_name,  servic' at line 1
ERROR 1064 (42000) at line 787: You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near '--ALTER TABLE `cloud_usage`.`usage_vm_instance` ADD COLUMN 
`cpu_speed` INT(10) U' at line 1
ERROR 1060 (42S21) at line 833: Duplicate column name 'name'
ERROR 1060 (42S21) at line 838: Duplicate column name 
'is_exclusive_gslb_provider'
ERROR 1091 (42000) at line 897: Can't DROP 'cpu'; 

[jira] [Commented] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Rohit Yadav (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127017#comment-14127017
 ] 

Rohit Yadav commented on CLOUDSTACK-7521:
-

When you upgraded CloudStack to 4.4.0, it must have failed at some other point. 
By running 421-to-430 sql the issue of failing due to duplicate column is 
expected. Can you share logs from the management server which started and 
failed, the real issue would be in that log.

4.2.1 users have been able to upgrade to 4.3.0 in past so probably it's not the 
4.2.1 to 4.3.0 upgrade path causing the error for you. Can you also share what 
ACS 4.2.1 build you're using noredist (nonoss) or oss?

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker

 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
 ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that 
 column/key exists
 ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
 column/key exists
 ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
 column/key exists
 ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
 column/key exists
 ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
 ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
 ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
 ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
 ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
 ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
 ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
 ERROR 1060 (42S21) at line 40: Duplicate column name 
 'power_state_update_count'
 ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
 ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
 (errno: 121)
 ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
 ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
 ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
 ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
 ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
 ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
 ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
 ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
 ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
 ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
 ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
 'network_details'
 ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 597: Unknown column 'display_detail' in 
 'volume_details'
 ERROR 1054 (42S22) at line 598: Unknown column 'display_detail' in 
 'nic_details'
 ERROR 1054 (42S22) at line 599: Unknown column 'display_detail' in 
 'user_vm_details'
 ERROR 1060 (42S21) at line 600: Duplicate column name 'display'
 ERROR 1060 (42S21) at line 601: Duplicate column name 'display'
 ERROR 1064 (42000) at line 634: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 635: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 636: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, 

[jira] [Closed] (CLOUDSTACK-7398) Security Group Rule tags are not being deleted on rule deletion

2014-09-09 Thread Ilia Shakitko (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilia Shakitko closed CLOUDSTACK-7398.
-

Committed to master.

 Security Group Rule tags are not being deleted on rule deletion
 ---

 Key: CLOUDSTACK-7398
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7398
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Affects Versions: 4.5.0
Reporter: Ilia Shakitko
Priority: Minor
 Fix For: 4.5.0


 If you add a tag to a SecurityGroup rule and then delete that rule itself, 
 existing tags for that rule won't be deleted (like it's done in Firewall case)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7398) Security Group Rule tags are not being deleted on rule deletion

2014-09-09 Thread Ilia Shakitko (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilia Shakitko resolved CLOUDSTACK-7398.
---
Resolution: Fixed

 Security Group Rule tags are not being deleted on rule deletion
 ---

 Key: CLOUDSTACK-7398
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7398
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Affects Versions: 4.5.0
Reporter: Ilia Shakitko
Priority: Minor
 Fix For: 4.5.0


 If you add a tag to a SecurityGroup rule and then delete that rule itself, 
 existing tags for that rule won't be deleted (like it's done in Firewall case)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Siavash Safi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siavash Safi updated CLOUDSTACK-7521:
-
Attachment: management-server.log

Server Management log file.

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker
 Attachments: management-server.log


 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
 ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that 
 column/key exists
 ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
 column/key exists
 ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
 column/key exists
 ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
 column/key exists
 ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
 ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
 ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
 ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
 ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
 ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
 ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
 ERROR 1060 (42S21) at line 40: Duplicate column name 
 'power_state_update_count'
 ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
 ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
 (errno: 121)
 ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
 ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
 ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
 ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
 ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
 ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
 ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
 ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
 ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
 ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
 ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
 'network_details'
 ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 597: Unknown column 'display_detail' in 
 'volume_details'
 ERROR 1054 (42S22) at line 598: Unknown column 'display_detail' in 
 'nic_details'
 ERROR 1054 (42S22) at line 599: Unknown column 'display_detail' in 
 'user_vm_details'
 ERROR 1060 (42S21) at line 600: Duplicate column name 'display'
 ERROR 1060 (42S21) at line 601: Duplicate column name 'display'
 ERROR 1064 (42000) at line 634: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 635: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 636: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 637: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name,  servic' at line 1
 ERROR 1064 (42000) at line 787: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL 

[jira] [Comment Edited] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Siavash Safi (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127145#comment-14127145
 ] 

Siavash Safi edited comment on CLOUDSTACK-7521 at 9/9/14 4:06 PM:
--

I'm using the packages from this repository: http://cloudstack.apt-get.eu/ubuntu


was (Author: siavashs):
Server Management log file.

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker
 Attachments: management-server.log


 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
 ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that 
 column/key exists
 ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
 column/key exists
 ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
 column/key exists
 ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
 column/key exists
 ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
 ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
 ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
 ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
 ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
 ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
 ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
 ERROR 1060 (42S21) at line 40: Duplicate column name 
 'power_state_update_count'
 ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
 ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
 (errno: 121)
 ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
 ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
 ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
 ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
 ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
 ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
 ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
 ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
 ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
 ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
 ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
 'network_details'
 ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 597: Unknown column 'display_detail' in 
 'volume_details'
 ERROR 1054 (42S22) at line 598: Unknown column 'display_detail' in 
 'nic_details'
 ERROR 1054 (42S22) at line 599: Unknown column 'display_detail' in 
 'user_vm_details'
 ERROR 1060 (42S21) at line 600: Duplicate column name 'display'
 ERROR 1060 (42S21) at line 601: Duplicate column name 'display'
 ERROR 1064 (42000) at line 634: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 635: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 636: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 637: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, 

[jira] [Commented] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Rohit Yadav (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127155#comment-14127155
 ] 

Rohit Yadav commented on CLOUDSTACK-7521:
-

Are you by any chance using a patched version of 4.2.1? I checked 4.4 and 4.3 
branches, 4.2.1 never had the vm_work_job table. A workaround is that you back 
up your database, drop this table and try again.

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker
 Attachments: management-server.log


 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
 ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that 
 column/key exists
 ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
 column/key exists
 ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
 column/key exists
 ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
 column/key exists
 ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
 ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
 ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
 ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
 ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
 ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
 ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
 ERROR 1060 (42S21) at line 40: Duplicate column name 
 'power_state_update_count'
 ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
 ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
 (errno: 121)
 ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
 ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
 ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
 ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
 ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
 ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
 ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
 ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
 ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
 ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
 ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
 'network_details'
 ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 597: Unknown column 'display_detail' in 
 'volume_details'
 ERROR 1054 (42S22) at line 598: Unknown column 'display_detail' in 
 'nic_details'
 ERROR 1054 (42S22) at line 599: Unknown column 'display_detail' in 
 'user_vm_details'
 ERROR 1060 (42S21) at line 600: Duplicate column name 'display'
 ERROR 1060 (42S21) at line 601: Duplicate column name 'display'
 ERROR 1064 (42000) at line 634: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 635: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 636: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 637: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into 

[jira] [Assigned] (CLOUDSTACK-7497) [UI] deploy VM failing as hypervisor type passed is KVM instead of LXC

2014-09-09 Thread Stephen Turner (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Turner reassigned CLOUDSTACK-7497:
--

Assignee: Jessica Wang  (was: Stephen Turner)

Jessica, have you encountered this before? Could you have a look at it, please?

 [UI] deploy VM  failing as hypervisor type passed is KVM instead of LXC
 ---

 Key: CLOUDSTACK-7497
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7497
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Jessica Wang
Priority: Blocker
 Fix For: 4.5.0


 Repro steps:
 Create a LXC zone with 2 cluster one LXc and one KVM
 Create  VM  with LXC template
 Bug:
 Deploy vm fails as hypervisor type is passed as KVM
 014-09-05 14:06:09,520 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24) ===START===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:09,581 INFO  [c.c.a.ApiServer] (catalina-exec-8:ctx-7b5dcb24 
 ctx-2a5b99cd) Hypervisor passed to the deployVm call, is different from the 
 hypervisor type of the template
 2014-09-05 14:06:09,582 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24 ctx-2a5b99cd) ===END===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:12,573 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
 (secstorage-1:ctx-6de2885c) Zone 2 is ready to launch secondary storage VM
 2014-09-05 14:06:12,689 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
 (consoleproxy-1:ctx-a134b2b7) Zone 2 is ready to launch console proxy



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Rohit Yadav (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127159#comment-14127159
 ] 

Rohit Yadav commented on CLOUDSTACK-7521:
-

Siavash, I cannot find 4.2 release on this repo: 
http://cloudstack.apt-get.eu/ubuntu
perhaps you mean to say the rhel one? I'm using the packages from this 
repository: http://cloudstack.apt-get.eu/rhel/4.2?

In any case, this repo is not officially maintained by Apache CloudStack 
project so I cannot share if this one adds any patches or modifications on 
4.2.1 release. In such a case, this issue is invalid for us, there is nothing 
much we can do for you. You may though try workarounds and hacking the db.

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker
 Attachments: management-server.log


 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
 ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that 
 column/key exists
 ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
 column/key exists
 ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
 column/key exists
 ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
 column/key exists
 ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
 ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
 ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
 ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
 ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
 ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
 ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
 ERROR 1060 (42S21) at line 40: Duplicate column name 
 'power_state_update_count'
 ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
 ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
 (errno: 121)
 ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
 ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
 ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
 ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
 ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
 ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
 ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
 ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
 ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
 ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
 ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
 'network_details'
 ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 597: Unknown column 'display_detail' in 
 'volume_details'
 ERROR 1054 (42S22) at line 598: Unknown column 'display_detail' in 
 'nic_details'
 ERROR 1054 (42S22) at line 599: Unknown column 'display_detail' in 
 'user_vm_details'
 ERROR 1060 (42S21) at line 600: Duplicate column name 'display'
 ERROR 1060 (42S21) at line 601: Duplicate column name 'display'
 ERROR 1064 (42000) at line 634: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 635: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right syntax 
 to use near '--insert into cloud.monitoring_services(id, uuid, service, 
 process_name, service' at line 1
 ERROR 1064 (42000) at line 636: You have an error in your SQL syntax; check 
 the manual that corresponds to your MySQL server version for the right 

[jira] [Commented] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Siavash Safi (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127165#comment-14127165
 ] 

Siavash Safi commented on CLOUDSTACK-7521:
--

I'm using the 4.2.1 package from the same repository:
{noformat}
~# apt-cache show cloudstack-management
Package: cloudstack-management
Priority: extra
Section: libs
Installed-Size: 148538
Maintainer: Wido den Hollander w...@widodh.nl
Architecture: all
Source: cloudstack
Version: 4.2.1
Depends: cloudstack-common (= 4.2.1), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
Conflicts: cloud-client, cloud-client-ui, cloud-server
Filename: dists/precise/4.2/pool/cloudstack-management_4.2.1_all.deb
Size: 138050662
MD5sum: 86a004b47c04553746d7c17c1fdf4001
SHA1: ea05a1420e2fa116cfbfac955ca7649933508274
SHA256: 62052bb12bfa1dc9eea9b06ff58eff6061bfbb4f6863b4be5c040600a1532286
SHA512: 
b651ed6147760db1ae1dad8a29586bb28d37b6190ef593536806e3782e429f9e65285e4ab23d26d609a7d9eee591da27810c0b9a3d06c8fdb61640e241c9a442
Description: CloudStack server library
 The CloudStack management server
Homepage: http://www.cloudstack.org/
{noformat}

I tried dropping that table but then it complained about another table.
Note: I pasted a wrong output when I logged the issue. It's updated now.

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker
 Attachments: management-server.log


 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
 ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that 
 column/key exists
 ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
 column/key exists
 ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
 column/key exists
 ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
 column/key exists
 ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
 ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
 ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
 ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
 ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
 ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
 ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
 ERROR 1060 (42S21) at line 40: Duplicate column name 
 'power_state_update_count'
 ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
 ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
 (errno: 121)
 ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
 ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
 ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
 ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
 ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
 ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
 ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
 ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
 ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
 ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
 ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
 ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
 'network_details'
 ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
 ERROR 1054 (42S22) at line 597: Unknown column 'display_detail' in 
 'volume_details'
 ERROR 1054 (42S22) at line 598: Unknown column 'display_detail' in 
 'nic_details'
 ERROR 1054 (42S22) at line 599: Unknown column 'display_detail' in 
 'user_vm_details'
 ERROR 1060 (42S21) at line 600: Duplicate column name 'display'
 ERROR 1060 (42S21) at line 601: Duplicate column name 'display'
 ERROR 1064 (42000) at line 634: You have an error in your SQL syntax; check 
 the 

[jira] [Updated] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Siavash Safi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siavash Safi updated CLOUDSTACK-7521:
-
Description: 
I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
fails to start.
After checking syslog I noticed an exception related to DB migration.
Here is the mysql error output when trying to run migration schema manually:
{noformat}
root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
/usr/share/cloudstack-management/setup/db/schema-421to430.sql
Enter password:
ERROR 1050 (42S01) at line 64: Table 'vm_work_job' already exists
ERROR 1050 (42S01) at line 75: Table 'async_job_journal' already exists
ERROR 1050 (42S01) at line 86: Table 'async_job_join_map' already exists
ERROR 1046 (3D000) at line 483: No database selected
ERROR 1046 (3D000) at line 498: No database selected
ERROR 1050 (42S01) at line 583: Table 'firewall_rule_details' already exists
ERROR 1050 (42S01) at line 615: Table 'ldap_configuration' already exists
ERROR 1050 (42S01) at line 624: Table 'monitoring_services' already exists
ERROR 1062 (23000) at line 634: Duplicate entry '1' for key 'PRIMARY'
ERROR 1062 (23000) at line 635: Duplicate entry '2' for key 'PRIMARY'
ERROR 1062 (23000) at line 636: Duplicate entry '3' for key 'PRIMARY'
ERROR 1062 (23000) at line 637: Duplicate entry '4' for key 'PRIMARY'
ERROR 1050 (42S01) at line 641: Table 'usage_event_details' already exists
ERROR 1050 (42S01) at line 650: Table 'usage_event_details' already exists
ERROR 1050 (42S01) at line 659: Table 'user_ip_address_details' already exists
ERROR 1050 (42S01) at line 669: Table 'remote_access_vpn_details' already exists
ERROR 1060 (42S21) at line 787: Duplicate column name 'cpu_speed'
ERROR 1050 (42S01) at line 791: Table 'vpc_details' already exists
ERROR 1050 (42S01) at line 802: Table 'vpc_gateway_details' already exists
ERROR 1050 (42S01) at line 812: Table 'network_acl_details' already exists
ERROR 1050 (42S01) at line 822: Table 'network_acl_item_details' already exists
ERROR 1050 (42S01) at line 847: Table 's2s_vpn_gateway_details' already exists
ERROR 1050 (42S01) at line 876: Table 's2s_customer_gateway_details' already 
exists
ERROR 1050 (42S01) at line 887: Table 's2s_vpn_connection_details' already 
exists{noformat}

  was:
I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
fails to start.
After checking syslog I noticed an exception related to DB migration.
Here is the mysql error output when trying to run migration schema manually:
{noformat}
root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
/usr/share/cloudstack-management/setup/db/schema-421to430.sql
Enter password:
ERROR 1060 (42S21) at line 25: Duplicate column name 'related'
ERROR 1091 (42000) at line 26: Can't DROP 'session_key'; check that column/key 
exists
ERROR 1091 (42000) at line 27: Can't DROP 'job_cmd_originator'; check that 
column/key exists
ERROR 1091 (42000) at line 28: Can't DROP 'callback_type'; check that 
column/key exists
ERROR 1091 (42000) at line 29: Can't DROP 'callback_address'; check that 
column/key exists
ERROR 1060 (42S21) at line 31: Duplicate column name 'job_type'
ERROR 1060 (42S21) at line 32: Duplicate column name 'job_dispatcher'
ERROR 1060 (42S21) at line 33: Duplicate column name 'job_executing_msid'
ERROR 1060 (42S21) at line 34: Duplicate column name 'job_pending_signals'
ERROR 1060 (42S21) at line 36: Duplicate column name 'keep_alive_enabled'
ERROR 1060 (42S21) at line 38: Duplicate column name 'power_state'
ERROR 1060 (42S21) at line 39: Duplicate column name 'power_state_update_time'
ERROR 1060 (42S21) at line 40: Duplicate column name 'power_state_update_count'
ERROR 1060 (42S21) at line 41: Duplicate column name 'power_host'
ERROR 1005 (HY000) at line 42: Can't create table 'cloud.#sql-12ce_27f86f3' 
(errno: 121)
ERROR 1060 (42S21) at line 44: Duplicate column name 'lb_protocol'
ERROR 1060 (42S21) at line 117: Duplicate column name 'default_value'
ERROR 1060 (42S21) at line 118: Duplicate column name 'updated'
ERROR 1060 (42S21) at line 119: Duplicate column name 'scope'
ERROR 1060 (42S21) at line 120: Duplicate column name 'is_dynamic'
ERROR 1060 (42S21) at line 125: Duplicate column name 'state'
ERROR 1060 (42S21) at line 126: Duplicate column name 'hv_ss_reserve'
ERROR 1060 (42S21) at line 128: Duplicate column name 'hv_ss_reserve'
ERROR 1060 (42S21) at line 139: Duplicate column name 'vpc_id'
ERROR 1060 (42S21) at line 141: Duplicate column name 'passive'
ERROR 1060 (42S21) at line 508: Duplicate column name 'cpu_sockets'
ERROR 1060 (42S21) at line 509: Duplicate column name 'hyperv_network_label'
ERROR 1060 (42S21) at line 594: Duplicate column name 'display'
ERROR 1054 (42S22) at line 595: Unknown column 'display_detail' in 
'network_details'
ERROR 1060 (42S21) at line 596: Duplicate column name 'display'
ERROR 1054 (42S22) at line 

[jira] [Commented] (CLOUDSTACK-490) Multiple disks on templates

2014-09-09 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127179#comment-14127179
 ] 

Clément Mutz commented on CLOUDSTACK-490:
-

What's new of this issue ?

Thanks,


 Multiple disks on templates
 ---

 Key: CLOUDSTACK-490
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-490
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template
Reporter: Clayton Weise
Priority: Minor

 After some discussion in IRC today the thought came up that it would be nice 
 for the ability to create a template that has not only a root drive but 
 multiple data drives attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Siavash Safi (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127165#comment-14127165
 ] 

Siavash Safi edited comment on CLOUDSTACK-7521 at 9/9/14 4:19 PM:
--

I'm using the 4.2.1 package from the same repository:
{noformat}
~# apt-cache show cloudstack-management
Package: cloudstack-management
Priority: extra
Section: libs
Installed-Size: 148538
Maintainer: Wido den Hollander w...@widodh.nl
Architecture: all
Source: cloudstack
Version: 4.2.1
Depends: cloudstack-common (= 4.2.1), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
Conflicts: cloud-client, cloud-client-ui, cloud-server
Filename: dists/precise/4.2/pool/cloudstack-management_4.2.1_all.deb
Size: 138050662
MD5sum: 86a004b47c04553746d7c17c1fdf4001
SHA1: ea05a1420e2fa116cfbfac955ca7649933508274
SHA256: 62052bb12bfa1dc9eea9b06ff58eff6061bfbb4f6863b4be5c040600a1532286
SHA512: 
b651ed6147760db1ae1dad8a29586bb28d37b6190ef593536806e3782e429f9e65285e4ab23d26d609a7d9eee591da27810c0b9a3d06c8fdb61640e241c9a442
Description: CloudStack server library
 The CloudStack management server
Homepage: http://www.cloudstack.org/
{noformat}

Direct link to the package: 
http://cloudstack.apt-get.eu/ubuntu/pool/cloudstack-management_4.2.1_all.deb
I tried dropping that table but then it complained about another table.
Note: I pasted a wrong output when I logged the issue. It's updated now.


was (Author: siavashs):
I'm using the 4.2.1 package from the same repository:
{noformat}
~# apt-cache show cloudstack-management
Package: cloudstack-management
Priority: extra
Section: libs
Installed-Size: 148538
Maintainer: Wido den Hollander w...@widodh.nl
Architecture: all
Source: cloudstack
Version: 4.2.1
Depends: cloudstack-common (= 4.2.1), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
Conflicts: cloud-client, cloud-client-ui, cloud-server
Filename: dists/precise/4.2/pool/cloudstack-management_4.2.1_all.deb
Size: 138050662
MD5sum: 86a004b47c04553746d7c17c1fdf4001
SHA1: ea05a1420e2fa116cfbfac955ca7649933508274
SHA256: 62052bb12bfa1dc9eea9b06ff58eff6061bfbb4f6863b4be5c040600a1532286
SHA512: 
b651ed6147760db1ae1dad8a29586bb28d37b6190ef593536806e3782e429f9e65285e4ab23d26d609a7d9eee591da27810c0b9a3d06c8fdb61640e241c9a442
Description: CloudStack server library
 The CloudStack management server
Homepage: http://www.cloudstack.org/
{noformat}

I tried dropping that table but then it complained about another table.
Note: I pasted a wrong output when I logged the issue. It's updated now.

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker
 Attachments: management-server.log


 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1050 (42S01) at line 64: Table 'vm_work_job' already exists
 ERROR 1050 (42S01) at line 75: Table 'async_job_journal' already exists
 ERROR 1050 (42S01) at line 86: Table 'async_job_join_map' already exists
 ERROR 1046 (3D000) at line 483: No database selected
 ERROR 1046 (3D000) at line 498: No database selected
 ERROR 1050 (42S01) at line 583: Table 'firewall_rule_details' already exists
 ERROR 1050 (42S01) at line 615: Table 'ldap_configuration' already exists
 ERROR 1050 (42S01) at line 624: Table 'monitoring_services' already exists
 ERROR 1062 (23000) at line 634: Duplicate entry '1' for key 'PRIMARY'
 ERROR 1062 (23000) at line 635: Duplicate entry '2' for key 'PRIMARY'
 ERROR 1062 (23000) at line 636: Duplicate entry '3' for key 'PRIMARY'
 ERROR 1062 (23000) at line 637: Duplicate entry '4' for key 'PRIMARY'
 ERROR 1050 (42S01) at line 641: Table 'usage_event_details' already exists
 ERROR 1050 (42S01) at line 650: Table 'usage_event_details' already exists
 ERROR 1050 (42S01) at line 659: Table 'user_ip_address_details' already exists
 ERROR 1050 (42S01) at line 669: Table 'remote_access_vpn_details' already 
 exists
 ERROR 1060 (42S21) at line 787: Duplicate column name 'cpu_speed'
 ERROR 1050 (42S01) at line 791: Table 'vpc_details' already exists
 ERROR 1050 (42S01) at line 802: Table 'vpc_gateway_details' already exists
 ERROR 1050 (42S01) at line 812: 

[jira] [Commented] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0 fails

2014-09-09 Thread Rohit Yadav (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127216#comment-14127216
 ] 

Rohit Yadav commented on CLOUDSTACK-7521:
-

Siavash, just remove the sql statements from 
/usr/share/cloudstack-management/setup/db/schema-421to430.sql etc which is 
failing you.

I'll check this deb file and if it's not ACS issue, we'll close this issue.

 DB migration from 4.2.1 to 4.4.0 fails
 --

 Key: CLOUDSTACK-7521
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
 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: Siavash Safi
Priority: Blocker
 Attachments: management-server.log


 I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it 
 fails to start.
 After checking syslog I noticed an exception related to DB migration.
 Here is the mysql error output when trying to run migration schema manually:
 {noformat}
 root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud  
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Enter password:
 ERROR 1050 (42S01) at line 64: Table 'vm_work_job' already exists
 ERROR 1050 (42S01) at line 75: Table 'async_job_journal' already exists
 ERROR 1050 (42S01) at line 86: Table 'async_job_join_map' already exists
 ERROR 1046 (3D000) at line 483: No database selected
 ERROR 1046 (3D000) at line 498: No database selected
 ERROR 1050 (42S01) at line 583: Table 'firewall_rule_details' already exists
 ERROR 1050 (42S01) at line 615: Table 'ldap_configuration' already exists
 ERROR 1050 (42S01) at line 624: Table 'monitoring_services' already exists
 ERROR 1062 (23000) at line 634: Duplicate entry '1' for key 'PRIMARY'
 ERROR 1062 (23000) at line 635: Duplicate entry '2' for key 'PRIMARY'
 ERROR 1062 (23000) at line 636: Duplicate entry '3' for key 'PRIMARY'
 ERROR 1062 (23000) at line 637: Duplicate entry '4' for key 'PRIMARY'
 ERROR 1050 (42S01) at line 641: Table 'usage_event_details' already exists
 ERROR 1050 (42S01) at line 650: Table 'usage_event_details' already exists
 ERROR 1050 (42S01) at line 659: Table 'user_ip_address_details' already exists
 ERROR 1050 (42S01) at line 669: Table 'remote_access_vpn_details' already 
 exists
 ERROR 1060 (42S21) at line 787: Duplicate column name 'cpu_speed'
 ERROR 1050 (42S01) at line 791: Table 'vpc_details' already exists
 ERROR 1050 (42S01) at line 802: Table 'vpc_gateway_details' already exists
 ERROR 1050 (42S01) at line 812: Table 'network_acl_details' already exists
 ERROR 1050 (42S01) at line 822: Table 'network_acl_item_details' already 
 exists
 ERROR 1050 (42S01) at line 847: Table 's2s_vpn_gateway_details' already exists
 ERROR 1050 (42S01) at line 876: Table 's2s_customer_gateway_details' already 
 exists
 ERROR 1050 (42S01) at line 887: Table 's2s_vpn_connection_details' already 
 exists{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Reopened] (CLOUDSTACK-7495) [Automation][HyperV] Stack trace along with error message - CloudStack currently only supports volumes marked as the KVM, VMware, or XenServer hypervisor type for r

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama reopened CLOUDSTACK-7495:
--

The bug has been filed primarily to address the stack trace issue. I apologize 
for not being clear in my bug report. We should not display stack trace along 
with an error message. Please suppress the stack trace,

Thank you,
Chandan.

 [Automation][HyperV] Stack trace along with error message - CloudStack 
 currently only supports volumes marked as the KVM, VMware, or XenServer 
 hypervisor type for resize.
 --

 Key: CLOUDSTACK-7495
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7495
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
 Fix For: 4.5.0


 {code}
 2014-09-03 17:55:32,084 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-11:ctx-5e814549 ctx-6724d865 ctx-56a27ef7) ===END===  
 10.220.135.217 -- GET  
 jobid=3f397629-d004-4020-a97d-8aa277ea2c61apiKey=hCPmYiAF1lm_sBLrhXIEWXCJt0vYbxzkeFfv7E1ZhyPPL_TF6BvI8cVOm2AqLlzWwa2w9dO0eFQu6SafM_st3gcommand=queryAsyncJobResultresponse=jsonsignature=6X9pGZqTxQTAxWy4N73kVno%2B62s%3D
 2014-09-03 17:55:32,091 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-123:ctx-0a86f6fa job-255) Unexpected exception while 
 executing 
 org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin
 com.cloud.exception.InvalidParameterValueException: CloudStack currently only 
 supports volumes marked as the KVM, VMware, or XenServer hypervisor type for 
 resize.
   at 
 com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:725)
   at 
 com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:150)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:601)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at $Proxy184.resizeVolume(Unknown Source)
   at 
 org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin.execute(ResizeVolumeCmdByAdmin.java:37)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
   at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
   at 

[jira] [Closed] (CLOUDSTACK-7444) [Automation] Fix the script test_snapshots_improvement.py - Templates are registered as admin's

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7444.


Closing the bug as the it is no longer seen in the automation run

 [Automation] Fix the script test_snapshots_improvement.py - Templates are 
 registered as admin's
 -

 Key: CLOUDSTACK-7444
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7444
 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


 Template got registered as admin's . Please correct the template registration 
 part of the code.
 client log info:
 {code}
 test_03_concurrent_snapshots_create_template 
 (integration.component.test_snapshots_improvement.TestCreateSnapshot): DEBUG: 
 Response : {jobprocstatus : 0, created : u'2014-08-24T14:39:48+', 
 jobresult : {template : {domain : u'ROOT', domainid : 
 u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', ostypename : u'CentOS 5.3 (64-bit)', 
 zoneid : u'eb811e7d-59d4-4c72-a965-80d9e30572d1', displaytext : u'Public 
 Template', ostypeid : u'56b1e2f2-2b4d-11e4-89bd-1e5d0e053e75', 
 passwordenabled : False, id : u'84226c9b-7bdb-4273-92f4-de4232018779', size : 
 21474836480, isready : True, format : u'VHD', templatetype : u'USER', details 
 : {platform : u'viridian:true;acpi:1;apic:true;pae:true;nx:true', 
 hypervisortoolsversion : u'xenserver56'}, zonename : u'XenRT-Zone-0', status 
 : u'Download Complete', isdynamicallyscalable : False, tags : [], isfeatured 
 : False, sshkeyenabled : False, account : u'admin', isextractable : True, 
 crossZones : False, sourcetemplateid : 
 u'56af8f20-2b4d-11e4-89bd-1e5d0e053e75', name : u'Public template-F700B7', 
 created : u'2014-08-24T14:39:48+', hypervisor : u'XenServer', ispublic : 
 False}}, cmd : 
 u'org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin', 
 userid : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
 u'dd5857f2-f08f-4121-aa31-b83dfdb1bb3c', jobresultcode : 0, jobinstanceid : 
 u'84226c9b-7bdb-4273-92f4-de4232018779', jobresulttype : u'object', 
 jobinstancetype : u'Template', accountid : 
 u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
 test_03_concurrent_snapshots_create_template 
 (integration.component.test_snapshots_improvement.TestCreateSnapshot): DEBUG: 
 ===Jobid:dd5857f2-f08f-4121-aa31-b83dfdb1bb3c ; StartTime:Sun Aug 24 14:39:48 
 2014 ; EndTime:Sun Aug 24 14:42:39 2014 ; TotalTime:-170===
 test_03_concurrent_snapshots_create_template 
 (integration.component.test_snapshots_improvement.TestCreateSnapshot): DEBUG: 
 Response : {jobprocstatus : 0, created : u'2014-08-24T14:39:48+', 
 jobresult : {template : {domain : u'ROOT', domainid : 
 u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', ostypename : u'CentOS 5.3 (64-bit)', 
 zoneid : u'eb811e7d-59d4-4c72-a965-80d9e30572d1', displaytext : u'Public 
 Template', ostypeid : u'56b1e2f2-2b4d-11e4-89bd-1e5d0e053e75', 
 passwordenabled : False, id : u'84226c9b-7bdb-4273-92f4-de4232018779', size : 
 21474836480, isready : True, format : u'VHD', templatetype : u'USER', details 
 : {platform : u'viridian:true;acpi:1;apic:true;pae:true;nx:true', 
 hypervisortoolsversion : u'xenserver56'}, zonename : u'XenRT-Zone-0', status 
 : u'Download Complete', isdynamicallyscalable : False, tags : [], isfeatured 
 : False, sshkeyenabled : False, account : u'admin', isextractable : True, 
 crossZones : False, sourcetemplateid : 
 u'56af8f20-2b4d-11e4-89bd-1e5d0e053e75', name : u'Public template-F700B7', 
 created : u'2014-08-24T14:39:48+', hypervisor : u'XenServer', ispublic : 
 False}}, cmd : 
 u'org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin', 
 userid : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
 u'dd5857f2-f08f-4121-aa31-b83dfdb1bb3c', jobresultcode : 0, jobinstanceid : 
 u'84226c9b-7bdb-4273-92f4-de4232018779', jobresulttype : u'object', 
 jobinstancetype : u'Template', accountid : 
 u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
 test_03_concurrent_snapshots_create_template 
 (integration.component.test_snapshots_improvement.TestCreateSnapshot): DEBUG: 
 Verifying if templates are created properly or not?
 test_03_concurrent_snapshots_create_template 
 (integration.component.test_snapshots_improvement.TestCreateSnapshot): DEBUG: 
 Payload: {'account': 
 u'test-TestSnapshotOnRootVolume-test_03_concurrent_snapshots_create_template-W9TVVS',
  'domainid': u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', 'templatefilter': 
 'self', 'apiKey': 
 

[jira] [Closed] (CLOUDSTACK-7442) [Automation] Fix the script test_project_resources.py - No permissions updated, please verify the account names

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7442.


Closing the bug as it is no longer seen in the automation runs

 [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] [Reopened] (CLOUDSTACK-7441) [Automation] Fix the script test_resource_limits.py - Templates are registered as admin's

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama reopened CLOUDSTACK-7441:
--

The commit fixes only test_05_templates_per_account.  It doesn't fix the bug at 
test_05_templates_per_domain. Reopening the bug to fix it.

 [Automation] Fix the script test_resource_limits.py - Templates are 
 registered as admin's
 ---

 Key: CLOUDSTACK-7441
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7441
 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


 Two test cases are failing in the test suite: *test_05_templates_per_account* 
  *test_05_templates_per_domain*
 *Error Message*
 Exception not raised   Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File /root/cloudstack/test/integration/component/test_resource_limits.py, 
 line 844, in test_05_templates_per_account
 domainid=self.account_1.domainid,
   File /usr/lib/python2.7/unittest/case.py, line 116, in __exit__
 {0} not raised.format(exc_name))
 'Exception not raised\n
 Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits

 *Error Message*
 Exception not raised   Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File /root/cloudstack/test/integration/component/test_resource_limits.py, 
 line 1355, in test_05_templates_per_domain
 domainid=self.account.domainid,
   File /usr/lib/python2.7/unittest/case.py, line 116, in __exit__
 {0} not raised.format(exc_name))
 'Exception not raised\n
 Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits

 *Bug Information in the Client result logs:*
 {code}
 ==
 FAIL: Test Templates limit per account
 --
 Traceback (most recent call last):
   File /root/cloudstack/test/integration/component/test_resource_limits.py, 
 line 844, in test_05_templates_per_account
 domainid=self.account_1.domainid,
 AssertionError: Exception not raised
   begin captured stdout  -
 === TestName: test_05_templates_per_account | Status : FAILED ===
 .
 .
 .
 .
 test_05_templates_per_account 
 (integration.component.test_resource_limits.TestResourceLimitsAccount): 
 DEBUG: Response : {jobprocstatus : 0, created : u'2014-08-24T14:19:11+', 
 jobresult : {domain : u'ROOT', domainid : 
 u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', ostypename : u'CentOS 5.3 (64-bit)', 
 zoneid : u'eb811e7d-59d4-4c72-a965-80d9e30572d1', displaytext : u'Cent OS 
 Template', ostypeid : u'56b1e2f2-2b4d-11e4-89bd-1e5d0e053e75', 
 passwordenabled : False, id : u'c406715b-aa97-4361-a212-32cdfba76b00', size : 
 21474836480, isready : True, format : u'VHD', templatetype : u'USER', details 
 : {platform : u'viridian:true;acpi:1;apic:true;pae:true;nx:true', 
 Message.ReservedCapacityFreed.Flag : u'false'}, zonename : u'XenRT-Zone-0', 
 status : u'Download Complete', isdynamicallyscalable : False, tags : [], 
 isfeatured : False, sshkeyenabled : False, account : u'admin', isextractable 
 : True, crossZones : False, sourcetemplateid : 
 u'56af8f20-2b4d-11e4-89bd-1e5d0e053e75', name : u'Cent OS Template-LS47A4', 
 created : u'2014-08-24T14:19:11+', hypervisor : u'XenServer', ispublic : 
 False}, cmd : 
 u'org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin', 
 userid : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
 u'e9295a94-4dfd-4c27-a405-fab4975f0eee', jobresultcode : 0, jobinstanceid : 
 u'c406715b-aa97-4361-a212-32cdfba76b00', jobresulttype : u'object', 
 jobinstancetype : u'Template', accountid : 
 u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
 test_05_templates_per_account 
 (integration.component.test_resource_limits.TestResourceLimitsAccount): 
 DEBUG: ===Jobid:e9295a94-4dfd-4c27-a405-fab4975f0eee ; StartTime:Sun Aug 24 
 14:19:12 2014 ; EndTime:Sun Aug 24 14:20:52 2014 ; TotalTime:-100===
 test_05_templates_per_account 
 

[jira] [Closed] (CLOUDSTACK-7439) [Automation] Fix the script test_tags.py - Unable to find resource by uuid since it is already destroyed

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7439.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Fix the script test_tags.py - Unable to find resource by uuid 
 since it is already destroyed 
 ---

 Key: CLOUDSTACK-7439
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7439
 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


 I am not sure whether we allow creation of tags on destroyed VMs. Currently 
 that Use case fails.
 *Error Message*
 Job failed: {jobprocstatus : 0, created : u'2014-08-24T15:44:22+', cmd : 
 u'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd', userid : 
 u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 2, jobid : 
 u'37f08e53-2f4a-40d5-a241-687948b2afb8', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : u'Unable to find 
 resource by uuid 9ea1264a-3914-41b4-9807-28e442ce752d and type UserVm'}, 
 accountid : u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}   Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=tags
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File /root/cloudstack/test/integration/component/test_tags.py, line 2249, 
 in test_22_create_tag_destroyed_vm
 tags={'region': 'India'}
   File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line 
 3783, in create
 return Tag(apiclient.createTags(cmd).__dict__)
   File 
 /usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 2294, in createTags
 response = self.connection.marvinRequest(command, response_type=response, 
 method=method)
   File 
 /usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, line 
 379, in marvinRequest
 raise e
 'Job failed: {jobprocstatus : 0, created : u\'2014-08-24T15:44:22+\', cmd 
 : u\'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd\', userid : 
 u\'77df13d2-2b4d-11e4-89bd-1e5d0e053e75\', jobstatus : 2, jobid : 
 u\'37f08e53-2f4a-40d5-a241-687948b2afb8\', jobresultcode : 530, jobresulttype 
 : u\'object\', jobresult : {errorcode : 530, errortext : u\'Unable to find 
 resource by uuid 9ea1264a-3914-41b4-9807-28e442ce752d and type UserVm\'}, 
 accountid : u\'77df055e-2b4d-11e4-89bd-1e5d0e053e75\'}\n
 Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=tags
   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7437) [Automation] Fix the script test_escalations_snapshots.py - unable to find a snapshot with id

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7437.


Closing the bug as it is no longer seen in automation run.

 [Automation] Fix the script test_escalations_snapshots.py - unable to find 
 a snapshot with id
 ---

 Key: CLOUDSTACK-7437
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7437
 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
 Fix For: 4.5.0


 Do not add the created snapshot to the cleanup resources since it has been 
 consciously deleted during the test case (test_01). Since the snapshot is no 
 longer there the cleanup_resources method results in an error.
 integration.component.test_escalations_snapshots.TestSnapshots.test_01_list_volume_snapshots_pagination
  (from nosetests)
 *Error Message*
 Job failed: {jobprocstatus : 0, created : u'2014-08-24T19:01:28+', 
 jobresult : {errorcode : 530, errortext : u'unable to find a snapshot with id 
 43'}, cmd : 
 u'org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd', userid 
 : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 2, jobid : 
 u'0fb9d284-9908-4e37-b176-b83eb2792399', jobresultcode : 530, jobinstanceid : 
 u'2b4a7334-c477-4dbb-a870-3a6c1ed5fcfb', jobresulttype : u'object', 
 jobinstancetype : u'Snapshot', accountid : 
 u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}   Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=escalations_snapsh
 *Stacktrace*
   File /usr/lib/python2.7/unittest/case.py, line 361, in run
 self.tearDown()
   File 
 /root/cloudstack/test/integration/component/test_escalations_snapshots.py, 
 line 106, in tearDown
 cleanup_resources(self.apiClient, self.cleanup)
   File /usr/local/lib/python2.7/dist-packages/marvin/lib/utils.py, line 
 121, in cleanup_resources
 obj.delete(api_client)
   File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line 986, 
 in delete
 apiclient.deleteSnapshot(cmd)
   File 
 /usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 784, in deleteSnapshot
 response = self.connection.marvinRequest(command, response_type=response, 
 method=method)
   File 
 /usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, line 
 379, in marvinRequest
 raise e
 'Job failed: {jobprocstatus : 0, created : u\'2014-08-24T19:01:28+\', 
 jobresult : {errorcode : 530, errortext : u\'unable to find a snapshot with 
 id 43\'}, cmd : 
 u\'org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd\', 
 userid : u\'77df13d2-2b4d-11e4-89bd-1e5d0e053e75\', jobstatus : 2, jobid : 
 u\'0fb9d284-9908-4e37-b176-b83eb2792399\', jobresultcode : 530, jobinstanceid 
 : u\'2b4a7334-c477-4dbb-a870-3a6c1ed5fcfb\', jobresulttype : u\'object\', 
 jobinstancetype : u\'Snapshot\', accountid : 
 u\'77df055e-2b4d-11e4-89bd-1e5d0e053e75\'}\n
 Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=escalations_snapsh
 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7426) [Automation] Failed to update template permissions in test_05_use_private_template_in_project

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7426.


Closing the bug as it is no longer seen in automation run.

 [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] [Closed] (CLOUDSTACK-7425) [Automation] Failed to create network offering due to Invalid Service - Lb

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7425.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Failed to create network offering due to Invalid Service - Lb
 --

 Key: CLOUDSTACK-7425
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7425
 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


 On Executing *test_persistent_networks.py* script, following error was seen 
 during creation of network offering.
 *nose.suite.ContextSuite context=TestRestartPersistentNetwork:setup* 
 *Error*
 Execute cmd: createnetworkoffering failed, due to: errorCode: 431, 
 errorText:Invalid service  Lb   Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=persistent_network
 *Stacktrace*
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in 
 run
 self.setUp()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in 
 setUp
 self.setupContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in 
 setupContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /root/cloudstack/test/integration/component/test_persistent_networks.py, 
 line 1352, in setUpClass
 conservemode=False)
   File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line 
 2039, in create
 return NetworkOffering(apiclient.createNetworkOffering(cmd).__dict__)
   File 
 /usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 1864, in createNetworkOffering
 response = self.connection.marvinRequest(command, response_type=response, 
 method=method)
   File 
 /usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, line 
 379, in marvinRequest
 raise e
 'Execute cmd: createnetworkoffering failed, due to: errorCode: 431, 
 errorText:Invalid service  Lb\n
 Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=persistent_network
 
 ===
 Logs on Management Server:
 ===
 {code}
 2014-08-24 07:29:03,321 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-11:ctx-9045f4ed) ===START===  10.220.135.73 -- GET  
 apiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgserviceproviderlist%5B2%5D.provider=VirtualRouterdisplaytext=Test+Nw+off+isolated+persistent-J1SARJserviceproviderlist%5B0%5D.service=Dhcpserviceproviderlist%5B4%5D.provider=VirtualRouterserviceproviderlist%5B1%5D.provider=VirtualRouteravailability=Optionalconservemode=Falseserviceproviderlist%5B3%5D.service=Dnsserviceproviderlist%5B0%5D.provider=VirtualRouterserviceproviderlist%5B1%5D.service=Lbserviceproviderlist%5B4%5D.service=PortForwardingsupportedservices=Dhcp%2CDns%2CSourceNat%2CPortForwarding%2C+Lbtraffictype=GUESTresponse=jsonname=Test+Nw+off+isolated+persistent-7NEHE0ispersistent=Trueserviceproviderlist%5B3%5D.provider=VirtualRouterguestiptype=Isolatedserviceproviderlist%5B2%5D.service=SourceNatcommand=createNetworkOfferingsignature=CSPMyaOuzQIuJ7pds6h0z1Zrz6Y%3D
 2014-08-24 07:29:03,324 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-25:ctx-4341a2a9 ctx-fe97e223 ctx-49ec168d) ===END===  
 10.220.135.73 -- GET  
 username=User-JEOYWOaccount=test-TestUserLogin-test_01_non_root_admin_Privileges-CCFZPYdomainid=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75firstname=Userlastname=Useremail=user%40test.comapiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgcommand=createUsersignature=ibJAEjnOZiNMtVgyWqHd1HW4W3w%3Dresponse=json
 2014-08-24 07:29:03,332 INFO  [c.c.a.ApiServer] 
 (catalina-exec-11:ctx-9045f4ed ctx-fab16efe ctx-a9b84bb9) Invalid service  Lb
 2014-08-24 07:29:03,332 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-11:ctx-9045f4ed ctx-fab16efe ctx-a9b84bb9) ===END===  
 10.220.135.73 -- GET  
 

[jira] [Closed] (CLOUDSTACK-7407) [Automation] Fix the script test_vpc_distributed_routing_offering.py - Skip the tests if the Physical Network doesnt have Ovs provider supported

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7407.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Fix the script test_vpc_distributed_routing_offering.py - Skip 
 the tests if the Physical Network doesnt have Ovs provider supported
 --

 Key: CLOUDSTACK-7407
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7407
 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


 Test cases in this test suite are failing with the following error:
 *Error Message*
 Execute cmd: createvpc failed, due to: errorCode: 431, errorText:Provider Ovs 
 should be enabled in at least one physical network of the zone specified.
 Please add code to the test script to skip the test suite execution if 
 Physical Network of the Zone doesn't support Ovs Provider



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7423) [Automation] Unable to start Virtual Machine due to - Unable to apply dhcp entry on router

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7423.


Closing the bug based on Murali's comment

 [Automation] Unable to start Virtual Machine due to - Unable to apply dhcp 
 entry on router
 --

 Key: CLOUDSTACK-7423
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7423
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.5.0


 Unable to start after stopping a User VM as part of 
 *integration.component.test_cpu_project_limits.TestProjectsCPULimits.test_01_project_counts_start_stop_instance*
 
 *Error Message*
 
 Failed to start instance: Job failed: {jobprocstatus : 0, created : 
 u'2014-08-24T09:23:02+', jobresult : {errorcode : 530, errortext : u'Job 
 failed due to exception Unable to create a deployment for 
 VM[User|i-218-404-VM]'}, cmd : 
 u'org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin', userid : 
 u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 2, jobid : 
 u'76b12bb1-52fc-45f4-933f-31399cefd624', jobresultcode : 530, jobinstanceid : 
 u'f565ab82-6d89-416e-9d93-9b04cf2667d0', jobresulttype : u'object', 
 jobinstancetype : u'VirtualMachine', accountid : 
 u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}   Logs available at 
 http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=cpu_project_limits
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File 
 /root/cloudstack/test/integration/component/test_cpu_project_limits.py, 
 line 263, in test_01_project_counts_start_stop_instance
 self.fail(Failed to start instance: %s % e)
   File /usr/lib/python2.7/unittest/case.py, line 413, in fail
 raise self.failureException(msg)
 'Failed to start instance: Job failed: {jobprocstatus : 0, created : 
 u\'2014-08-24T09:23:02+\', jobresult : {errorcode : 530, errortext : 
 u\'Job failed due to exception Unable to create a deployment for 
 VM[User|i-218-404-VM]\'}, cmd : 
 u\'org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin\', userid : 
 u\'77df13d2-2b4d-11e4-89bd-1e5d0e053e75\', jobstatus : 2, jobid : 
 u\'76b12bb1-52fc-45f4-933f-31399cefd624\', jobresultcode : 530, jobinstanceid 
 : u\'f565ab82-6d89-416e-9d93-9b04cf2667d0\', jobresulttype : u\'object\', 
 jobinstancetype : u\'VirtualMachine\', accountid : 
 u\'77df055e-2b4d-11e4-89bd-1e5d0e053e75\'}\n
 ===
 Error of Management Server Log:
 ===
 {code}
 2014-08-24 09:23:03,513 INFO  [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-21:ctx-e6e44390 job-2922/job-2923 ctx-2994f1d0) Unable to 
 contact resource.
 com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is 
 unreachable: Unable to apply dhcp entry on router 
   at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:4031)
   at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:3150)
   at sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:601)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at $Proxy190.applyDhcpEntry(Unknown Source)
   at 
 com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:924)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElement(NetworkOrchestrator.java:1251)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1373)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1309)

[jira] [Closed] (CLOUDSTACK-7393) [Automation] Fix the script test_vpc_vm_life_cycle.py - Code is hardcoded to use certain host tags

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7393.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Fix the script test_vpc_vm_life_cycle.py - Code is hardcoded 
 to use certain host tags
 

 Key: CLOUDSTACK-7393
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7393
 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


 *Script is present at:*
 component/test_vpc_vm_life_cycle.py
 Currently script assumes that the deployment has hosts with host_tags host1 
 and host2 and uses two service offerings with these host_tags. The script 
 is hardcoded with the above information. The proper design and correction 
 should be as follows.
 Find the cluster with two hosts
 If no two host cluster is found error out with proper message
 Edit the host tags on the two hosts to two different unique names
 Create corresponding service offerings with the two different unique names
 Conduct the tests
 In teardown script section of the script, edit the host tags on the hosts 
 to empty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7390) [Automation] Fix the script test_bugs.py - Invalid Parameters

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7390.


Closing the bug as it is no longer seen in the automation run.

 [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 

[jira] [Closed] (CLOUDSTACK-7389) [Automation] Fix the script test_bugs.py - Unable to find Ostype is required for registering template

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7389.


Closing the bug as it is no longer seen in the automation run.

 [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] [Closed] (CLOUDSTACK-7380) [Automation] Fix the script test_egress_fw_rules.py - 18 Test Cases are failing due to hard code guest network cidr

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7380.


Closing the bug as it is no longer seen in the automation run

 [Automation] Fix the script test_egress_fw_rules.py - 18 Test Cases are 
 failing due to hard code guest network cidr
 -

 Key: CLOUDSTACK-7380
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7380
 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: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


 18 Test cases in the test_egress_fw_rules.py script fails if the guest 
 network is any network other than 10.1.1.0/24 network. The script assumes the 
 guest network to be 10.1.1.0/24 network. Added code to the test suite so that 
 the test cases will work for isolated guest network with any network cidr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-6440) [Automation] test_02_sys_template_ready test case on test_secondary_storage.py failed - listTemplates response is empty

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-6440.


Closing the bug as it is no longer seen in the automation run.

 [Automation] test_02_sys_template_ready test case on 
 test_secondary_storage.py failed - listTemplates response is empty
 -

 Key: CLOUDSTACK-6440
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6440
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, IAM
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.4.0


 System VM Template ID seems to have been made a required parameter while 
 querying for the System VM Templates inorder to list the Template.
 
 listTemplatesResponse:
 
 'NoneType' object is not iterable
   begin captured logging  
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 STARTED : TC: test_02_sys_template_ready :::
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 sending GET request: listZones {'name': u'test0'}
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Computed Signature by Marvin: t23Z4s6lQrS2hRbKTWxJfI+9a5k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=test0command=listZonessignature=t23Z4s6lQrS2hRbKTWxJfI%2B9a5k%3Dresponse=json
  HTTP/1.1 200 394
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=test0command=listZonessignature=t23Z4s6lQrS2hRbKTWxJfI%2B9a5k%3Dresponse=json
  Response: { listzonesresponse : { count:1 ,zone : [  
 {id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
  ] } }
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 sending GET request: listPods {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  HTTP/1.1 200 314
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  Response: { listpodsresponse : { count:1 ,pod : [  
 {id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
  ] } }
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 sending GET request: listZones {'name': u'test1'}
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Computed Signature by Marvin: Tt/qzyUZeeDi5QbtHNV6Ve7DHao=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=test1command=listZonessignature=Tt%2FqzyUZeeDi5QbtHNV6Ve7DHao%3Dresponse=json
  HTTP/1.1 200 394
 test_02_sys_template_ready 
 

[jira] [Closed] (CLOUDSTACK-6443) [Automation] Two Test Cases failed on test_volumes.py - AttributeError: VirtualMachine instance has no attribute 'hostid'

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-6443.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Two Test Cases failed on test_volumes.py - AttributeError: 
 VirtualMachine instance has no attribute 'hostid'
 ---

 Key: CLOUDSTACK-6443
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6443
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, IAM
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.4.0


 Two Test Cases Failed:
 test_07_resize_fail
 test_08_resize_volume
 *Error Message1*:
 VirtualMachine instance has no attribute 'hostid'
   begin captured logging  
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 STARTED : TC: test_07_resize_fail :::
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: Fail 
 Resize Volume ID: b5521198-97f1-4f2c-afea-fcadf70d4249
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 sending GET request: resizeVolume {'diskofferingid': 
 u'9015ab2c-1d88-4e39-bcd8-d7fa22a1b2ca', 'id': 'invalid id'}
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Computed Signature by Marvin: bCeC5im5Fgxi23vWk4lBzKbQm7A=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=bCeC5im5Fgxi23vWk4lBzKbQm7A%3Ddiskofferingid=9015ab2c-1d88-4e39-bcd8-d7fa22a1b2caid=invalid+id
  HTTP/1.1 431 330
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=bCeC5im5Fgxi23vWk4lBzKbQm7A%3Ddiskofferingid=9015ab2c-1d88-4e39-bcd8-d7fa22a1b2caid=invalid+id
  Response: { resizevolumeresponse : 
 {uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to 
 execute API command resizevolume due to invalid value. Invalid parameter id 
 value=invalid id due to incorrect long value format, or entity does not exist 
 or due to incorrect parameter annotation for the field in api cmd class.} }
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 sending GET request: resizeVolume {'diskofferingid': 'invalid id', 'id': 
 u'b5521198-97f1-4f2c-afea-fcadf70d4249'}
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Computed Signature by Marvin: DbNaHKDzesuJcTU1thWGQg88UPk=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=DbNaHKDzesuJcTU1thWGQg88UPk%3Ddiskofferingid=invalid+idid=b5521198-97f1-4f2c-afea-fcadf70d4249
  HTTP/1.1 431 342
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=DbNaHKDzesuJcTU1thWGQg88UPk%3Ddiskofferingid=invalid+idid=b5521198-97f1-4f2c-afea-fcadf70d4249
  Response: { resizevolumeresponse : 
 {uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to 
 execute API command resizevolume due to invalid value. Invalid parameter 
 diskofferingid value=invalid id due to incorrect long value format, or entity 
 does not exist or due to incorrect parameter annotation for the field in api 
 cmd class.} }
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 sending GET request: listVolumes {'virtualmachineid': 
 u'bca5f583-139f-46e4-87d5-09fb5adac313', 'type': 'ROOT', 'listall': True}
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Computed Signature by Marvin: f1JO1y9Ye2m1qw3+QCZu9+B8zRo=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 

[jira] [Closed] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-6444.


Closing the bug as it is no longer seen in automation run


 [Automation] test_01_primary_storage_iscsi  failed on 
 test_primary_storage.py - Wrong iscsi path format - it should be 
 /targetIQN/LUN 
 

 Key: CLOUDSTACK-6444
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Error Message:
 Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
   begin captured logging  
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 STARTED : TC: test_01_primary_storage_iscsi :::
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listZones {}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  HTTP/1.1 200 735
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  Response: { listzonesresponse : { count:2 ,zone : [  
 {id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
  
 {id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listPods {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  HTTP/1.1 200 314
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  Response: { listpodsresponse : { count:1 ,pod : [  
 {id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listClusters {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 

[jira] [Commented] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN

2014-09-09 Thread Sudha Ponnaganti (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127418#comment-14127418
 ] 

Sudha Ponnaganti commented on CLOUDSTACK-6444:
--

I am working out of cambridge office from 9/8 - 9/12. Will respond during UK 
working hours


 [Automation] test_01_primary_storage_iscsi  failed on 
 test_primary_storage.py - Wrong iscsi path format - it should be 
 /targetIQN/LUN 
 

 Key: CLOUDSTACK-6444
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Error Message:
 Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
   begin captured logging  
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 STARTED : TC: test_01_primary_storage_iscsi :::
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listZones {}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  HTTP/1.1 200 735
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  Response: { listzonesresponse : { count:2 ,zone : [  
 {id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
  
 {id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listPods {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  HTTP/1.1 200 314
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  Response: { listpodsresponse : { count:1 ,pod : [  
 {id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listClusters {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
 requests.packages.urllib3.connectionpool: 

[jira] [Closed] (CLOUDSTACK-7013) [Automation] AttributeError: type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7013.


Closing the bug as it is no longer seen in the automation run.

 [Automation] AttributeError: type object 
 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'
 -

 Key: CLOUDSTACK-7013
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7013
 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: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ==
 Bug in test script:
 ==
 cls.account = 
 Account.create(cls.api_client,cls.services[account],domainid = 
 cls.domain.id)
 cls.append(cls.account)  BUG: should be cls.__cleanup.append
 cls.service_offering = 
 ServiceOffering.create(cls.api_client,cls.services[service_offering])
 cls._cleanup.append(cls.service_offering)
 
 Test Script Failure:
 
 test_26_add_nic_insufficient_permission 
 (integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
  CRITICAL: EXCEPTION: test_26_add_nic_insufficient_permission: ['Traceback 
 (most recent call last):\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run\n
 self.setUp()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n  
   self.setupContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in 
 setupContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
  line 1392, in setUpClass\ncls.append(cls.account)\n', AttributeError: 
 type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 
 'append'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in 
 run
 self.setUp()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in 
 setUp
 self.setupContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in 
 setupContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
  line 1392, in setUpClass
 cls.append(cls.account)
 'type object \'TestFailureScenariosRemoveNicFromVM\' has no attribute 
 \'append\'\n  begin captured logging  
 \ntest_26_add_nic_insufficient_permission 
 (integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
  DEBUG: Payload: {\'apiKey\': 
 u\'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q\',
  \'id\': u\'853b13be-4f75-4ca9-9f7c-3cf303d3cc2d\', \'state\': \'Disabled\', 
 \'command\': \'updateNetworkOffering\', \'signature\': 
 \'pP6GEHIbIDVHMxeYxAyQahpCxbI=\', \'response\': 
 \'json\'}\ntest_26_add_nic_insufficient_permission 
 (integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
  DEBUG: Sending GET Cmd : 
 updateNetworkOffering===\nrequests.packages.urllib3.connectionpool: INFO: 
 Starting new HTTP connection (1): 
 10.220.153.217\nrequests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qid=853b13be-4f75-4ca9-9f7c-3cf303d3cc2dstate=Disabledcommand=updateNetworkOfferingsignature=pP6GEHIbIDVHMxeYxAyQahpCxbI%3Dresponse=json
  HTTP/1.1 200 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7014) [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7014.


Closing the bug as it is no longer seen in the automation run.

 [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute 
 '_TestAffinityGroupsAdminUser__cleanup 
 ---

 Key: CLOUDSTACK-7014
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7014
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ==
 Bug in test script:
 ==
 @classmethod
 def tearDownClass(cls):
 try:
 cls.api_client = super(TestAffinityGroupsAdminUser, 
 cls).getClsTestClient().getApiClient()
 #Clean up, terminate the created templates
 cleanup_resources(cls.api_client, cls.__cleanup)  BUG: It 
 should be cls._cleanup
 except Exception as e:
 raise Exception(Warning: Exception during cleanup : %s % e)
 
 Test Script Failure:
 
 Warning: Exception during cleanup : type object 'TestAffinityGroupsAdminUser' 
 has no attribute '_TestAffinityGroupsAdminUser__cleanup'
   begin captured logging  
 test_07_delete_aff_grp_of_other_user 
 (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): 
 CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: ['Traceback (most 
 recent call last):\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n
 self.tearDown()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\nself.teardownContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 1501, in tearDownClass\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type 
 object 'TestAffinityGroupsAdminUser' has no attribute 
 '_TestAffinityGroupsAdminUser__cleanup'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in 
 run
 self.tearDown()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown
 self.teardownContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 1501, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 'Warning: Exception during cleanup : type object 
 \'TestAffinityGroupsAdminUser\' has no attribute 
 \'_TestAffinityGroupsAdminUser__cleanup\'\n  begin 
 captured logging  
 \ntest_07_delete_aff_grp_of_other_user 
 (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): 
 CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: [\'Traceback (most 
 recent call last):\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n   
  self.tearDown()\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\\nself.teardownContext(ancestor)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\\ntry_run(context, names)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run\\nreturn func()\\n\', \'  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 1501, in tearDownClass\\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type 
 object \'TestAffinityGroupsAdminUser\' has no attribute 
 \'_TestAffinityGroupsAdminUser__cleanup\'\\n]\n-  end 
 captured logging  -'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7016) [Automation] type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7016.


Closing the bug as it is no longer seen in automation run.

 [Automation] type object 'TestDeployVMAffinityGroups' has no attribute 
 '_TestDeployVMAffinityGroups__cleanup
 

 Key: CLOUDSTACK-7016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7016
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ==
 Bug in test script:
 ==
 @classmethod
 def tearDownClass(cls):
 try:
 cls.api_client = super(TestDeployVMAffinityGroups, 
 cls).getClsTestClient().getApiClient()
 #Clean up, terminate the created templates
 cleanup_resources(cls.api_client, cls.__cleanup)  BUG: It 
 should be cls._cleanup
 except Exception as e:
 raise Exception(Warning: Exception during cleanup : %s % e)
 =
 Error Message:
 =
 Warning: Exception during cleanup : type object 'TestDeployVMAffinityGroups' 
 has no attribute '_TestDeployVMAffinityGroups__cleanup'
   begin captured logging  
 test_10_deploy_vm_by_aff_grp_name_and_id 
 (integration.component.test_affinity_groups.TestDeployVMAffinityGroups): 
 CRITICAL: EXCEPTION: test_10_deploy_vm_by_aff_grp_name_and_id: ['Traceback 
 (most recent call last):\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n
 self.tearDown()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\nself.teardownContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 1154, in tearDownClass\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type 
 object 'TestDeployVMAffinityGroups' has no attribute 
 '_TestDeployVMAffinityGroups__cleanup'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in 
 run
 self.tearDown()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown
 self.teardownContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 1154, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 'Warning: Exception during cleanup : type object 
 \'TestDeployVMAffinityGroups\' has no attribute 
 \'_TestDeployVMAffinityGroups__cleanup\'\n  begin 
 captured logging  
 \ntest_10_deploy_vm_by_aff_grp_name_and_id 
 (integration.component.test_affinity_groups.TestDeployVMAffinityGroups): 
 CRITICAL: EXCEPTION: test_10_deploy_vm_by_aff_grp_name_and_id: [\'Traceback 
 (most recent call last):\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n   
  self.tearDown()\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\\nself.teardownContext(ancestor)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\\ntry_run(context, names)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run\\nreturn func()\\n\', \'  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 1154, in tearDownClass\\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type 
 object \'TestDeployVMAffinityGroups\' has no attribute 
 \'_TestDeployVMAffinityGroups__cleanup\'\\n]\n-  end 
 captured logging  -'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7015) [Automation] type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup'

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7015.


Closing the bug as it is no longer seen in automation run.

 [Automation] type object 'TestDeleteAffinityGroups' has no attribute 
 '_TestDeleteAffinityGroups__cleanup'
 -

 Key: CLOUDSTACK-7015
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7015
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ==
 Bug in test script:
 ==
 @classmethod
 def tearDownClass(cls):
 try:
 cls.api_client = super(TestDeleteAffinityGroups, 
 cls).getClsTestClient().getApiClient()
 #Clean up, terminate the created templates
 cleanup_resources(cls.api_client, cls.__cleanup)  BUG: It 
 should be cls._cleanup
 except Exception as e:
 raise Exception(Warning: Exception during cleanup : %s % e)
 
 Error Message
 
 Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' 
 has no attribute '_TestDeleteAffinityGroups__cleanup'
   begin captured logging  
 test_09_delete_aff_grp_root_admin 
 (integration.component.test_affinity_groups.TestDeleteAffinityGroups): 
 CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: ['Traceback (most 
 recent call last):\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n
 self.tearDown()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\nself.teardownContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 599, in tearDownClass\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type 
 object 'TestDeleteAffinityGroups' has no attribute 
 '_TestDeleteAffinityGroups__cleanup'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in 
 run
 self.tearDown()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown
 self.teardownContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 599, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 'Warning: Exception during cleanup : type object \'TestDeleteAffinityGroups\' 
 has no attribute \'_TestDeleteAffinityGroups__cleanup\'\n 
  begin captured logging  
 \ntest_09_delete_aff_grp_root_admin 
 (integration.component.test_affinity_groups.TestDeleteAffinityGroups): 
 CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: [\'Traceback (most 
 recent call last):\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n   
  self.tearDown()\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\\nself.teardownContext(ancestor)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\\ntry_run(context, names)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run\\nreturn func()\\n\', \'  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 599, in tearDownClass\\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type 
 object \'TestDeleteAffinityGroups\' has no attribute 
 \'_TestDeleteAffinityGroups__cleanup\'\\n]\n-  end 
 captured logging  -'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7019) [Automation] type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7019.


Closing the bug as it is no longer seen in automation run.

 [Automation] type object 'TestListAffinityGroups' has no attribute 
 '_TestListAffinityGroups__cleanup
 

 Key: CLOUDSTACK-7019
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7019
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ==
 Bug in test script:
 ==
 @classmethod
 def tearDownClass(cls):
 try:
 cls.api_client = super(TestListAffinityGroups, 
 cls).getClsTestClient().getApiClient()
 #Clean up, terminate the created templates
 cleanup_resources(cls.api_client, cls.__cleanup)   BUG: It 
 should be cls._cleanup
 except Exception as e:
 raise Exception(Warning: Exception during cleanup : %s % e)
 
 Error Message
 
 Warning: Exception during cleanup : type object 'TestListAffinityGroups' has 
 no attribute '_TestListAffinityGroups__cleanup'
   begin captured logging  
 test_07_list_all_vms_in_aff_grp 
 (integration.component.test_affinity_groups.TestListAffinityGroups): 
 CRITICAL: EXCEPTION: test_07_list_all_vms_in_aff_grp: ['Traceback (most 
 recent call last):\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n
 self.tearDown()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\nself.teardownContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 351, in tearDownClass\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type 
 object 'TestListAffinityGroups' has no attribute 
 '_TestListAffinityGroups__cleanup'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in 
 run
 self.tearDown()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown
 self.teardownContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 351, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 'Warning: Exception during cleanup : type object \'TestListAffinityGroups\' 
 has no attribute \'_TestListAffinityGroups__cleanup\'\n 
  begin captured logging  
 \ntest_07_list_all_vms_in_aff_grp 
 (integration.component.test_affinity_groups.TestListAffinityGroups): 
 CRITICAL: EXCEPTION: test_07_list_all_vms_in_aff_grp: [\'Traceback (most 
 recent call last):\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n   
  self.tearDown()\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\\nself.teardownContext(ancestor)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\\ntry_run(context, names)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run\\nreturn func()\\n\', \'  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 351, in tearDownClass\\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type 
 object \'TestListAffinityGroups\' has no attribute 
 \'_TestListAffinityGroups__cleanup\'\\n]\n-  end 
 captured logging  -'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7125) [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be backedup before creating a Template from it

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7125.


Closing the bug as it is no longer seen in automation run.

 [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be 
 backedup before creating a Template from it
 

 Key: CLOUDSTACK-7125
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7125
 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


 Failed to create Template as Snapshot is not BackedUp yet
 =
 Error:
 =
 CloudstackAPIException: Execute cmd: createtemplate failed, due to: 
 errorCode: 431, errorText:Snapshot id=3 is not in BackedUp state yet and 
 can't be used for template creation
 test_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): CRITICAL: EXCEPTION: 
 test_02_check_size_snapshotTemplate: ['Traceback (most recent call last):\n', 
 '  File /usr/lib/python2.7/unittest/case.py, line 332, in run\n
 testMethod()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate\n
 self.services[template]\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot\nreturn 
 Template(apiclient.createTemplate(cmd).__dict__)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate\nresponse = 
 self.connection.marvinRequest(command, response_type=response, 
 method=method)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest\nraise e\n', CloudstackAPIException: Execute 
 cmd: createtemplate failed, due to: errorCode: 431, errorText:Snapshot id=3 
 is not in BackedUp state yet and can't be used for template creation\n]
 -  end captured logging  -
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate
 self.services[template]
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot
 return Template(apiclient.createTemplate(cmd).__dict__)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate
 response = self.connection.marvinRequest(command, response_type=response, 
 method=method)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest
 raise e
 'Execute cmd: createtemplate failed, due to: errorCode: 431, 
 errorText:Snapshot id=3 is not in BackedUp state yet and can\'t be used for 
 template creation\n  begin captured stdout  
 -\n=== TestName: test_02_check_size_snapshotTemplate | 
 Status : EXCEPTION ===\n\n\n-  end captured stdout  
 --\n  begin captured logging  
 \ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: 
 STARTED : TC: test_02_check_size_snapshotTemplate 
 :::\ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: Payload: 
 {\'account\': u\'test-TestTemplates-test_01_create_template-PV1LCJ\', 
 \'domainid\': u\'7ccbf6bc-08ed-11e4-887d-928d578f5db8\', \'volumeid\': 
 u\'7aa4cc3c-5c23-4b30-a30d-b48bd735ebcc\', \'apiKey\': 
 u\'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA\',
  \'command\': \'createSnapshot\', \'signature\': 
 \'xX9H+dRDsmZwsicoTcSlP+yZo7g=\', \'response\': 
 \'json\'}\ntest_02_check_size_snapshotTemplate 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7025) [Automation] Failed to deply virtual machine: 'TestAddNetworkToVirtualMachine' object has no attribute 'defaultNetworkId'

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7025.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Failed to deply virtual machine: 
 'TestAddNetworkToVirtualMachine' object has no attribute 'defaultNetworkId'
 -

 Key: CLOUDSTACK-7025
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7025
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ===
 Bug in Script:
 ===
 try:
 virtual_machine = VirtualMachine.create(
 self.api_client, self.services[virtual_machine],
 accountid=self.account.name, domainid=self.account.domainid,
 serviceofferingid=self.service_offering.id,
 mode=self.zone.networktype,
 networkids=[self.defaultNetworkId]) -- BUG: There is no 
 reference to defaultNetworkId specified anywhere before this code in the 
 TestAddNetworkToVirtualMachine class
 self.cleanup.append(virtual_machine)
 except Exception as e:
 self.fail(Failed to deply virtual machine: %s % e)
 
 Error Message:
 
 Failed to deply virtual machine: 'TestAddNetworkToVirtualMachine' object has 
 no attribute 'defaultNetworkId'
   begin captured stdout  -
 === TestName: test_03_add_nw_multiple_times_1_isolated | Status : FAILED ===
 -  end captured stdout  --
   begin captured logging  
 test_03_add_nw_multiple_times_1_isolated 
 (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine):
  DEBUG: STARTED : TC: test_03_add_nw_multiple_times_1_isolated 
 :::
 test_03_add_nw_multiple_times_1_isolated 
 (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine):
  CRITICAL: FAILED: test_03_add_nw_multiple_times_1_isolated: ['Traceback 
 (most recent call last):\n', '  File /usr/lib/python2.7/unittest/case.py, 
 line 332, in run\ntestMethod()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/ddt.py, line 114, in wrapper\n
 return func(self, *args, **kwargs)\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
  line 408, in test_03_add_nw_multiple_times\nself.fail(Failed to deply 
 virtual machine: %s % e)\n', '  File /usr/lib/python2.7/unittest/case.py, 
 line 413, in fail\nraise self.failureException(msg)\n', AssertionError: 
 Failed to deply virtual machine: 'TestAddNetworkToVirtualMachine' object has 
 no attribute 'defaultNetworkId'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File /usr/local/lib/python2.7/dist-packages/ddt.py, line 114, in wrapper
 return func(self, *args, **kwargs)
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
  line 408, in test_03_add_nw_multiple_times
 self.fail(Failed to deply virtual machine: %s % e)
   File /usr/lib/python2.7/unittest/case.py, line 413, in fail
 raise self.failureException(msg)
 'Failed to deply virtual machine: \'TestAddNetworkToVirtualMachine\' object 
 has no attribute \'defaultNetworkId\'\n  begin captured 
 stdout  -\n=== TestName: 
 test_03_add_nw_multiple_times_1_isolated | Status : FAILED 
 ===\n\n\n-  end captured stdout  
 --\n  begin captured logging  
 \ntest_03_add_nw_multiple_times_1_isolated 
 (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine):
  DEBUG: STARTED : TC: test_03_add_nw_multiple_times_1_isolated 
 :::\ntest_03_add_nw_multiple_times_1_isolated 
 (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine):
  CRITICAL: FAILED: test_03_add_nw_multiple_times_1_isolated: [\'Traceback 
 (most recent call last):\\n\', \'  File 
 /usr/lib/python2.7/unittest/case.py, line 332, in run\\n
 testMethod()\\n\', \'  File /usr/local/lib/python2.7/dist-packages/ddt.py, 
 line 114, in wrapper\\nreturn func(self, *args, **kwargs)\\n\', \'  File 
 

[jira] [Closed] (CLOUDSTACK-7024) [Automation] Deletion of Account that manages a project failed during cleanup of TestTemplateUsage Tests

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7024.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Deletion of Account that manages a project failed during cleanup 
 of TestTemplateUsage Tests
 

 Key: CLOUDSTACK-7024
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7024
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 =
 Error Message:
 =
 Warning: Exception during cleanup : Job failed: {jobprocstatus : 0, created : 
 u'2014-06-26T05:54:00+', cmd : 
 u'org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd', userid : 
 u'57dd7fb6-fc58-11e3-919f-4eba41a459a4', jobstatus : 2, jobid : 
 u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : uThe account id=313 
 manages project(s) with ids 40, and can't be removed}, accountid : 
 u'57dd7098-fc58-11e3-919f-4eba41a459a4'}
   begin captured logging  
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: Payload: 
 {'signature': 'umKBWTVC8csMC7iBWcrmlZP7Bns=', 'apiKey': 
 u'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q',
  'command': 'deleteAccount', 'id': u'6096abdb-9fe1-45ef-af30-6ecca7210515', 
 'response': 'json'}
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: 
 Sending GET Cmd : deleteAccount===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.153.217
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?signature=umKBWTVC8csMC7iBWcrmlZP7Bns%3DapiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qcommand=deleteAccountid=6096abdb-9fe1-45ef-af30-6ecca7210515response=json
  HTTP/1.1 200 78
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: === 
 Jobid: 0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d Started ===
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: Payload: 
 {'signature': '6MrHAB+DBVozv8OPtH8iU4S5bOc=', 'apiKey': 
 u'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q',
  'command': 'queryAsyncJobResult', 'response': 'json', 'jobid': 
 u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d'}
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: 
 Sending GET Cmd : queryAsyncJobResult===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.153.217
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?signature=6MrHAB%2BDBVozv8OPtH8iU4S5bOc%3DapiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qcommand=queryAsyncJobResultresponse=jsonjobid=0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d
  HTTP/1.1 200 343
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: Response 
 : {jobprocstatus : 0, created : u'2014-06-26T05:54:00+', cmd : 
 u'org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd', userid : 
 u'57dd7fb6-fc58-11e3-919f-4eba41a459a4', jobstatus : 0, jobid : 
 u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d', jobresultcode : 0, accountid : 
 u'57dd7098-fc58-11e3-919f-4eba41a459a4'}
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: === 
 JobId:0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d is Still Processing, Will TimeOut 
 in:3595 
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: Payload: 
 {'signature': '6MrHAB+DBVozv8OPtH8iU4S5bOc=', 'apiKey': 
 u'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q',
  'command': 'queryAsyncJobResult', 'response': 'json', 'jobid': 
 u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d'}
 test_01_template_usage 
 (integration.component.test_project_usage.TestTemplateUsage): DEBUG: 
 Sending GET Cmd : queryAsyncJobResult===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.153.217
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 

[jira] [Closed] (CLOUDSTACK-7021) [Automation] type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7021.


Closing the bug as it is no longer seen in the automation run.

 [Automation] type object 'TestUpdateVMAffinityGroups' has no attribute 
 '_TestUpdateVMAffinityGroups__cleanup
 

 Key: CLOUDSTACK-7021
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7021
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ===
 Bug in Script:
 ===
 @classmethod
 def tearDownClass(cls):
 try:
 cls.api_client = super(TestUpdateVMAffinityGroups, 
 cls).getClsTestClient().getApiClient()
 #Clean up, terminate the created templates
 cleanup_resources(cls.api_client, cls.__cleanup) --- BUG: It 
 should be cls._cleanup
 except Exception as e:
 raise Exception(Warning: Exception during cleanup : %s % e)
 =
 Error Message:
 =
 Warning: Exception during cleanup : type object 'TestUpdateVMAffinityGroups' 
 has no attribute '_TestUpdateVMAffinityGroups__cleanup'
   begin captured logging  
 test_05_update_aff_grp_on_running_vm 
 (integration.component.test_affinity_groups.TestUpdateVMAffinityGroups): 
 CRITICAL: EXCEPTION: test_05_update_aff_grp_on_running_vm: ['Traceback (most 
 recent call last):\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n
 self.tearDown()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\nself.teardownContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 870, in tearDownClass\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type 
 object 'TestUpdateVMAffinityGroups' has no attribute 
 '_TestUpdateVMAffinityGroups__cleanup'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in 
 run
 self.tearDown()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown
 self.teardownContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 870, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 'Warning: Exception during cleanup : type object 
 \'TestUpdateVMAffinityGroups\' has no attribute 
 \'_TestUpdateVMAffinityGroups__cleanup\'\n  begin 
 captured logging  
 \ntest_05_update_aff_grp_on_running_vm 
 (integration.component.test_affinity_groups.TestUpdateVMAffinityGroups): 
 CRITICAL: EXCEPTION: test_05_update_aff_grp_on_running_vm: [\'Traceback (most 
 recent call last):\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n   
  self.tearDown()\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in 
 tearDown\\nself.teardownContext(ancestor)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in 
 teardownContext\\ntry_run(context, names)\\n\', \'  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run\\nreturn func()\\n\', \'  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py,
  line 870, in tearDownClass\\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type 
 object \'TestUpdateVMAffinityGroups\' has no attribute 
 \'_TestUpdateVMAffinityGroups__cleanup\'\\n]\n-  end 
 captured logging  -'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7022) [Automation] AttributeError: type object 'TestVpnUsage' has no attribute 'sevice_offering'

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7022.


Closing the bug as it is no longer seen in automation run.

 [Automation] AttributeError: type object 'TestVpnUsage' has no attribute 
 'sevice_offering'
 --

 Key: CLOUDSTACK-7022
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7022
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ===
 Bug in Script:
 ===
 cls.service_offering = ServiceOffering.create(
 cls.api_client,
 cls.services[service_offering]
 )
 cls._cleanup.append(cls.sevice_offering) --- BUG: Typo in the 
 service_offering variable name
 cls.virtual_machine = VirtualMachine.create(
 cls.api_client,
 cls.services[server],
 templateid=template.id,
 accountid=cls.account.name,
 domainid=cls.account.domainid,
 serviceofferingid=cls.service_offering.id
 )
 cls.public_ip = PublicIPAddress.create(
cls.api_client,

 accountid=cls.virtual_machine.account,
zoneid=cls.virtual_machine.zoneid,

 domainid=cls.virtual_machine.domainid,
services=cls.services[server]
)
 return
 =
 Exception:
 =
 test_01_volume_usage (integration.component.test_usage.TestVolumeUsage): 
 CRITICAL: EXCEPTION: test_01_volume_usage: ['Traceback (most recent call 
 last):\n', '  File /usr/local/lib/python2.7/dist-packages/nose/suite.py, 
 line 208, in run\nself.setUp()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n  
   self.setupContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in 
 setupContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
  line 1482, in setUpClass\ncls._cleanup.append(cls.sevice_offering)\n', 
 AttributeError: type object 'TestVpnUsage' has no attribute 
 'sevice_offering'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in 
 run
 self.setUp()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in 
 setUp
 self.setupContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in 
 setupContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
  line 1482, in setUpClass
 cls._cleanup.append(cls.sevice_offering)
 'type object \'TestVpnUsage\' has no attribute 
 \'sevice_offering\'\n  begin captured logging  
 \ntest_01_volume_usage 
 (integration.component.test_usage.TestVolumeUsage): DEBUG: Payload: 
 {\'signature\': \'aZ6mt3aURCG51ejqTw7v2/RuQFQ=\', \'apiKey\': 
 u\'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q\',
  \'command\': \'deleteServiceOffering\', \'id\': 
 u\'3a72e88f-7886-42d3-be1a-99fd15908112\', \'response\': 
 \'json\'}\ntest_01_volume_usage 
 (integration.component.test_usage.TestVolumeUsage): DEBUG: Sending 
 GET Cmd : 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7367) [Automation] Fix the script test_add_remove_network.py - Listing VM after VM's deletion doesnt show VM in the list

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7367.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Fix the script test_add_remove_network.py - Listing VM after 
 VM's deletion doesnt show VM in the list
 

 Key: CLOUDSTACK-7367
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7367
 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
 Fix For: 4.5.0


 *Test Client Error Stack Trace:*
 {code}
 ---
 FAIL: update default nic of vm when vm is state is not Running or Stopped
 ---
 Traceback (most recent call last):
   File /home/chandan/test_add_remove_network.py, line 1777, in 
 test_23_update_nic_incorrect_vm_state
 vm_list_validation_result[2])
 AssertionError: vm list validation failed due to INVALID INPUT
   begin captured stdout  -
 === TestName: test_23_update_nic_incorrect_vm_state | Status : FAILED ===
 {code}
 *Root Cause Analysis:*
 *From the results log of Marvin Run, Observe Response : None for ListVMs 
 after VM's deletion:*
 {code}
 test_23_update_nic_incorrect_vm_state 
 (test_add_remove_network.TestFailureScenariosUpdateVirtualMachineNIC): DEBUG: 
 Sending GET Cmd : queryAsyncJobResult===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.130.79
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?jobid=2dabf6ab-e871-48ea-a6c8-ef1862dc4f5dapiKey=ZI83p8k86jxdFO75d5mjeU5qvLiMvSK2tUnhcSfQc2TDbIJWI4MuvF1w0SkSZ3RB-pykb4VhQaLUVhq6apOqogcommand=queryAsyncJobResultresponse=jsonsignature=FK3sso3aJJvft%2BLJUoqXGRwohAk%3D
  HTTP/1.1 200 536
 test_23_update_nic_incorrect_vm_state 
 (test_add_remove_network.TestFailureScenariosUpdateVirtualMachineNIC): DEBUG: 
 Response : {jobprocstatus : 0, created : u'2014-08-12T19:01:14-0700', 
 jobresult : {affinitygroup : [], nic : [], securitygroup : [], tags : []}, 
 cmd : u'org.apache.cloudstack.api.command.admin.vm.DestroyVMCmdByAdmin', 
 userid : u'89a9018a-12a8-11e4-b75e-06098c000757', jobstatus : 1, jobid : 
 u'2dabf6ab-e871-48ea-a6c8-ef1862dc4f5d', jobresultcode : 0, jobinstanceid : 
 u'e6953bc0-14b0-4b01-8e10-9174964f4892', jobresulttype : u'object', 
 jobinstancetype : u'VirtualMachine', accountid : 
 u'89a8f4e2-12a8-11e4-b75e-06098c000757'}
 test_23_update_nic_incorrect_vm_state 
 (test_add_remove_network.TestFailureScenariosUpdateVirtualMachineNIC): DEBUG: 
 ===Jobid:2dabf6ab-e871-48ea-a6c8-ef1862dc4f5d ; StartTime:Tue Aug 12 18:40:12 
 2014 ; EndTime:Tue Aug 12 18:41:08 2014 ; TotalTime:-55===
 test_23_update_nic_incorrect_vm_state 
 (test_add_remove_network.TestFailureScenariosUpdateVirtualMachineNIC): DEBUG: 
 Response : {jobprocstatus : 0, created : u'2014-08-12T19:01:14-0700', 
 jobresult : {affinitygroup : [], nic : [], securitygroup : [], tags : []}, 
 cmd : u'org.apache.cloudstack.api.command.admin.vm.DestroyVMCmdByAdmin', 
 userid : u'89a9018a-12a8-11e4-b75e-06098c000757', jobstatus : 1, jobid : 
 u'2dabf6ab-e871-48ea-a6c8-ef1862dc4f5d', jobresultcode : 0, jobinstanceid : 
 u'e6953bc0-14b0-4b01-8e10-9174964f4892', jobresulttype : u'object', 
 jobinstancetype : u'VirtualMachine', accountid : 
 u'89a8f4e2-12a8-11e4-b75e-06098c000757'}
 test_23_update_nic_incorrect_vm_state 
 (test_add_remove_network.TestFailureScenariosUpdateVirtualMachineNIC): DEBUG: 
 Payload: {'apiKey': 
 u'ZI83p8k86jxdFO75d5mjeU5qvLiMvSK2tUnhcSfQc2TDbIJWI4MuvF1w0SkSZ3RB-pykb4VhQaLUVhq6apOqog',
  'id': u'e6953bc0-14b0-4b01-8e10-9174964f4892', 'response': 'json', 
 'command': 'listVirtualMachines', 'signature': 'hBKJs25V40Y/ocF51bJ4MvRvEik='}
 test_23_update_nic_incorrect_vm_state 
 (test_add_remove_network.TestFailureScenariosUpdateVirtualMachineNIC): DEBUG: 
 Sending GET Cmd : listVirtualMachines===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.130.79
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?signature=hBKJs25V40Y%2FocF51bJ4MvRvEik%3DapiKey=ZI83p8k86jxdFO75d5mjeU5qvLiMvSK2tUnhcSfQc2TDbIJWI4MuvF1w0SkSZ3RB-pykb4VhQaLUVhq6apOqogcommand=listVirtualMachinesid=e6953bc0-14b0-4b01-8e10-9174964f4892response=json
  HTTP/1.1 200 39
 test_23_update_nic_incorrect_vm_state 
 

[jira] [Closed] (CLOUDSTACK-7228) [Automation] Unable to shrink data disk attached to a VM on XenServer

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7228.


Closing the bug as it is no longer seen in automation run.

 [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, 
 [{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:32f13207-5e56-4ed7-847a-4f1db3dea1e0,pool:{id:1,uuid:afb9d57d-6258-3eaa-bf14-803cdba34506,host:10.223.110.232,path:/export/home/chandan/44-130-79-z2/primary,port:2049,type:NetworkFilesystem},vmInstance:i-71-162-MyTestVM,newSize:10737418240,currentSize:21474836480,shrinkOk:true,wait:0}}]
  }
 2014-08-07 14:15:39,487 

[jira] [Reopened] (CLOUDSTACK-7310) [Automation] XenServer does not support shrink data disk. CloudStack should prevent such an operation on XenServer

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama reopened CLOUDSTACK-7310:
--

Alex, 

Bug https://issues.apache.org/jira/browse/CLOUDSTACK-7228 has been filed to fix 
the test script. Bug https://issues.apache.org/jira/browse/CLOUDSTACK-7310 has 
been filed to fix the CCP API Code to not allow any Users do such an operation. 
Though the two bugs are related to the same component, they are not duplicates 
as they are addressing two separate issues. Reopening this bug to address CCP 
API Code,

Thank you,
Chandan.

 [Automation] XenServer does not support shrink data disk. CloudStack should 
 prevent such an operation on XenServer
 --

 Key: CLOUDSTACK-7310
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7310
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Volumes, XenServer
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: John Dilley
Priority: Critical
 Fix For: 4.5.0


 XenServer does not allowing shrinking of disks currently. Please add code on 
 Cloudstack to prevent such an operation (similar to VMWare case). Failing to 
 prevent such an operation on XenServer leads to 
 https://issues.apache.org/jira/browse/CLOUDSTACK-7228 . 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (CLOUDSTACK-7497) [UI] deploy VM failing as hypervisor type passed is KVM instead of LXC

2014-09-09 Thread Jessica Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang reassigned CLOUDSTACK-7497:


Assignee: shweta agarwal  (was: Jessica Wang)

Shweta,

(1) Please provide:
(i) database dump
or
(ii) your web site and username/password

(2) When you tried to deploy VM, did you choose template or ISO?

Jessica

 [UI] deploy VM  failing as hypervisor type passed is KVM instead of LXC
 ---

 Key: CLOUDSTACK-7497
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7497
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: shweta agarwal
Priority: Blocker
 Fix For: 4.5.0


 Repro steps:
 Create a LXC zone with 2 cluster one LXc and one KVM
 Create  VM  with LXC template
 Bug:
 Deploy vm fails as hypervisor type is passed as KVM
 014-09-05 14:06:09,520 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24) ===START===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:09,581 INFO  [c.c.a.ApiServer] (catalina-exec-8:ctx-7b5dcb24 
 ctx-2a5b99cd) Hypervisor passed to the deployVm call, is different from the 
 hypervisor type of the template
 2014-09-05 14:06:09,582 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-8:ctx-7b5dcb24 ctx-2a5b99cd) ===END===  10.146.0.131 -- GET  
 command=deployVirtualMachineresponse=jsonsessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3Dzoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82atemplateid=2175190d-212a-4078-aedb-d25e4ddcdeb3hypervisor=KVMserviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810baffinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48_=1409906169711
 2014-09-05 14:06:12,573 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
 (secstorage-1:ctx-6de2885c) Zone 2 is ready to launch secondary storage VM
 2014-09-05 14:06:12,689 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
 (consoleproxy-1:ctx-a134b2b7) Zone 2 is ready to launch console proxy



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7184) HA should wait for at least 'xen.heartbeat.interval' sec before starting HA on vm's when host is marked down

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127488#comment-14127488
 ] 

ASF subversion and git services commented on CLOUDSTACK-7184:
-

Commit 7f97bf7c58a348e684f7138c93c287a3c86ca55b in cloudstack's branch 
refs/heads/hotfix/4.4/CLOUDSTACK-7184 from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7f97bf7 ]

CLOUDSTACK-7184: xenheartbeat gets passed timeout and interval

 HA should wait for at least 'xen.heartbeat.interval' sec before starting HA 
 on vm's when host is marked down
 

 Key: CLOUDSTACK-7184
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7184
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server, XenServer
Affects Versions: 4.3.0, 4.4.0, 4.5.0
 Environment: CloudStack 4.3 with XenServer 6.2 hypervisors
Reporter: Remi Bergsma
Assignee: Daan Hoogland
Priority: Blocker

 Hypervisor got isolated for 30 seconds due to a network issue. CloudStack did 
 discover this and marked the host as down, and immediately started HA. Just 
 18 seconds later the hypervisor returned and we ended up with 5 vm's that 
 were running on two hypervisors at the same time. 
 This, of course, resulted in file system corruption and the loss of the vm's. 
 One side of the story is why XenServer allowed this to happen (will not 
 bother you with this one). The CloudStack side of the story: HA should only 
 start after at least xen.heartbeat.interval seconds. If the host is down long 
 enough, the Xen heartbeat script will fence the hypervisor and prevent 
 corruption. If it is not down long enough, nothing should happen.
 Logs (short):
 2014-07-25 05:03:28,596 WARN  [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-122:ctx-690badc5) Unable to get current status on 505(mccpvmXX)
 .
 2014-07-25 05:03:31,920 ERROR [c.c.a.m.AgentManagerImpl] 
 (AgentTaskPool-10:ctx-11b9af3e) Host is down: 505-mccpvmXX.  Starting HA on 
 the VMs
 .
 2014-07-25 05:03:49,655 DEBUG [c.c.h.Status] (ClusteredAgentManager 
 Timer:ctx-0e00979c) Transition:[Resource state = Enabled, Agent event = 
 AgentDisconnected, Host id = 505, name = mccpvmXX]
 cs marks host down: 2014-07-25  05:03:31,920
 cs marks host up: 2014-07-25  05:03:49,655



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-6438) [Automation] Creation of Template from Volume failed due to the requested plugin could not be found.

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-6438.


Closing the bug as it is no longer seen in automation runs.

 [Automation] Creation of Template from Volume failed due to the requested 
 plugin could not be found.
 

 Key: CLOUDSTACK-6438
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6438
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 
 The requested plugin could not be found.
 
 2014-04-16 15:55:43,850 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-41:job-97) Executing AsyncJobVO {id:97, userId: 2, 
 accountId: 2, instanceType: Template, instanceId: 205, cmd: 
 org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin, 
 cmdInfo: 
 {cmdEventType:TEMPLATE.CREATE,ctxUserId:2,ispublic:False,isextractable:False,httpmethod:GET,volumeid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,domainid:fe2a30b2-c5a8-11e3-8f55-66bc12ed7ec3,isfeatured:False,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,ostypeid:feba4b70-c5a8-11e3-8f55-66bc12ed7ec3,id:205,response:json,name:Cent
  OS Template-7WLKMH,passwordenabled:False,displaytext:Cent OS 
 Template,account:test-TestCreateTemplate-SCKX71,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,ctxAccountId:2,ctxStartEventId:291,signature:8ILr8Hdfhc35eHAm1D0L7lkgRw4\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:55:43,853 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b) ===START===  10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,877 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-41:job-97 ctx-554395e3) Received unknown parameters for 
 command createTemplate. Unknown parameters : isextractable account
 2014-04-16 15:55:43,921 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b ctx-62916341 ctx-11cd890f) ===END===  
 10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,947 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] 
 (API-Job-Executor-41:job-97 ctx-554395e3) template 205 is already in store:1, 
 type:Image
 2014-04-16 15:55:43,972 DEBUG [o.a.c.s.m.AncientDataMotionStrategy] 
 (API-Job-Executor-41:job-97 ctx-554395e3) copyAsync inspecting src type 
 VOLUME copyAsync inspecting dest type TEMPLATE
 2014-04-16 15:55:44,005 DEBUG [c.c.a.t.Request] (API-Job-Executor-41:job-97 
 ctx-554395e3) Seq 2-7234469851417280562: Sending  { Cmd , MgmtId: 
 112957957439171, via: 2(marron.lab.vmops.com), Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ac0c4b04-6b72-38b1-a72f-c7fe7163d17a,id:1,poolType:NetworkFilesystem,host:nfs1-ccp.citrix.com,path:/home/common/automation/SC_QA_AUTO7/primary4,port:2049,url:NetworkFilesystem://nfs1-ccp.citrix.com/home/common/automation/SC_QA_AUTO7/primary4/?ROLE=PrimarySTOREUUID=ac0c4b04-6b72-38b1-a72f-c7fe7163d17a}},name:ROOT-17,size:21474836480,path:01269023-5389-407f-8dfc-a3ab22074207,volumeId:19,vmName:i-12-17-QA,accountId:12,format:VHD,id:19,deviceId:0,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/12/205,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,id:205,format:RAW,accountId:12,hvm:true,displayText:Cent
  OS 
 Template,imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://nfs1-ccp.citrix.com:/home/common/automation/SC_QA_AUTO7/secondary4,_role:Image}},name:27b30290f-74f3-391d-ac26-5a9a8ba769f6,hypervisorType:XenServer}},executeInSequence:false,options:{},wait:10800}}]
  }
 2014-04-16 15:55:44,006 DEBUG [c.c.a.t.Request] 

[jira] [Closed] (CLOUDSTACK-6442) [Automation] Extraction of Volume failed due to the requested plugin could not be found.

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-6442.


Closing the bug as it is no longer seen in automation run

 [Automation] Extraction of Volume failed due to the requested plugin could 
 not be found.
 

 Key: CLOUDSTACK-6442
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6442
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Use Case:
 Extract Volume from the Setup
 
 The requested plugin could not be found.
 
 2014-04-16 15:59:56,332 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669) ===START===  10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,335 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Processing Seq 4-314:  { Cmd , 
 MgmtId: -1, via: 4, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:1,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2014-04-16 15:59:56,343 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Sending Seq 4-314:  { Ans: , 
 MgmtId: 112957957439171, via: 4, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2014-04-16 15:59:56,369 DEBUG [c.c.u.AccountManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) Access to 
 {Vol[31|vm=null|DATADISK]} granted to 
 Acct[ed7cd506-e810-496f-94ee-3e422b3a6449-test-TestVolumes-test_01_create_volume-7K52C0]
  by RoleBasedEntityAccessChecker
 2014-04-16 15:59:56,388 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) submit async 
 job-169, details: AsyncJobVO {id:169, userId: 2, accountId: 2, instanceType: 
 Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:59:56,389 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) ===END===  
 10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,394 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-76:job-169) Add job-169 into job monitoring
 2014-04-16 15:59:56,394 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-76:job-169) Executing AsyncJobVO {id:169, userId: 2, 
 accountId: 2, instanceType: Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:59:56,395 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-20:ctx-fecf5e4b) ===START===  10.223.240.161 -- GET  
 

[jira] [Commented] (CLOUDSTACK-7184) HA should wait for at least 'xen.heartbeat.interval' sec before starting HA on vm's when host is marked down

2014-09-09 Thread Daan Hoogland (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127523#comment-14127523
 ] 

Daan Hoogland commented on CLOUDSTACK-7184:
---

Could some of you please review hotfix/4.4/CLOUDSTACK-7184

I could do with some advice on how to thoroughly test this functionality as
well.

thanks,
Daan


On Tue, Sep 9, 2014 at 10:22 PM, ASF subversion and git services (JIRA) 




-- 
Daan


 HA should wait for at least 'xen.heartbeat.interval' sec before starting HA 
 on vm's when host is marked down
 

 Key: CLOUDSTACK-7184
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7184
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server, XenServer
Affects Versions: 4.3.0, 4.4.0, 4.5.0
 Environment: CloudStack 4.3 with XenServer 6.2 hypervisors
Reporter: Remi Bergsma
Assignee: Daan Hoogland
Priority: Blocker

 Hypervisor got isolated for 30 seconds due to a network issue. CloudStack did 
 discover this and marked the host as down, and immediately started HA. Just 
 18 seconds later the hypervisor returned and we ended up with 5 vm's that 
 were running on two hypervisors at the same time. 
 This, of course, resulted in file system corruption and the loss of the vm's. 
 One side of the story is why XenServer allowed this to happen (will not 
 bother you with this one). The CloudStack side of the story: HA should only 
 start after at least xen.heartbeat.interval seconds. If the host is down long 
 enough, the Xen heartbeat script will fence the hypervisor and prevent 
 corruption. If it is not down long enough, nothing should happen.
 Logs (short):
 2014-07-25 05:03:28,596 WARN  [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-122:ctx-690badc5) Unable to get current status on 505(mccpvmXX)
 .
 2014-07-25 05:03:31,920 ERROR [c.c.a.m.AgentManagerImpl] 
 (AgentTaskPool-10:ctx-11b9af3e) Host is down: 505-mccpvmXX.  Starting HA on 
 the VMs
 .
 2014-07-25 05:03:49,655 DEBUG [c.c.h.Status] (ClusteredAgentManager 
 Timer:ctx-0e00979c) Transition:[Resource state = Enabled, Agent event = 
 AgentDisconnected, Host id = 505, name = mccpvmXX]
 cs marks host down: 2014-07-25  05:03:31,920
 cs marks host up: 2014-07-25  05:03:49,655



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7184) HA should wait for at least 'xen.heartbeat.interval' sec before starting HA on vm's when host is marked down

2014-09-09 Thread John Kinsella (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127569#comment-14127569
 ] 

John Kinsella commented on CLOUDSTACK-7184:
---

No, KVM uses kvmheartbeat.sh, which unfortunately looks a lot different than 
xenheartbeat.sh.

Looks like the issue I've seen is different, will try to track it 
down/replicate and file a separate bug.

Patch looks clean, but I'm not in position to test it at the moment.


 HA should wait for at least 'xen.heartbeat.interval' sec before starting HA 
 on vm's when host is marked down
 

 Key: CLOUDSTACK-7184
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7184
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Management Server, XenServer
Affects Versions: 4.3.0, 4.4.0, 4.5.0
 Environment: CloudStack 4.3 with XenServer 6.2 hypervisors
Reporter: Remi Bergsma
Assignee: Daan Hoogland
Priority: Blocker

 Hypervisor got isolated for 30 seconds due to a network issue. CloudStack did 
 discover this and marked the host as down, and immediately started HA. Just 
 18 seconds later the hypervisor returned and we ended up with 5 vm's that 
 were running on two hypervisors at the same time. 
 This, of course, resulted in file system corruption and the loss of the vm's. 
 One side of the story is why XenServer allowed this to happen (will not 
 bother you with this one). The CloudStack side of the story: HA should only 
 start after at least xen.heartbeat.interval seconds. If the host is down long 
 enough, the Xen heartbeat script will fence the hypervisor and prevent 
 corruption. If it is not down long enough, nothing should happen.
 Logs (short):
 2014-07-25 05:03:28,596 WARN  [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-122:ctx-690badc5) Unable to get current status on 505(mccpvmXX)
 .
 2014-07-25 05:03:31,920 ERROR [c.c.a.m.AgentManagerImpl] 
 (AgentTaskPool-10:ctx-11b9af3e) Host is down: 505-mccpvmXX.  Starting HA on 
 the VMs
 .
 2014-07-25 05:03:49,655 DEBUG [c.c.h.Status] (ClusteredAgentManager 
 Timer:ctx-0e00979c) Transition:[Resource state = Enabled, Agent event = 
 AgentDisconnected, Host id = 505, name = mccpvmXX]
 cs marks host down: 2014-07-25  05:03:31,920
 cs marks host up: 2014-07-25  05:03:49,655



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7020) [Automation] Exception: Warning: Exception during cleanup : type object 'TestTemplateUsage' has no attribute '_cleanup'

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7020.


Closing the bug as it is no longer seen in automation run.

 [Automation] Exception: Warning: Exception during cleanup : type object 
 'TestTemplateUsage' has no attribute '_cleanup'
 ---

 Key: CLOUDSTACK-7020
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7020
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.4.0


 ===
 Bug in Script:
 ===
 class TestTemplateUsage(cloudstackTestCase):
 @classmethod
 def setUpClass(cls):
 cls.testClient = super(TestTemplateUsage, cls).getClsTestClient()
 cls.api_client = cls.testClient.getApiClient()
 cls.services = Services().services
 # Get Zone, Domain and templates
 cls.domain = get_domain(cls.api_client)
 cls.zone = get_zone(cls.api_client, cls.testClient.getZoneForTests())
 cls.services['mode'] = cls.zone.networktype
 cls.services[server][zoneid] = cls.zone.id
 template = get_template(
 cls.api_client,
 cls.zone.id,
 cls.services[ostype]
 )
 cls.services[server][zoneid] = cls.zone.id
 try:
 cls.account = Account.create(
 cls.api_client,
 cls.services[account],
 domainid=cls.domain.id
 )
 cls._cleanup.append(cls.account)   --- BUG: _cleanup 
 variable should be initialized to empty list.
 cls.services[account] = cls.account.name
 cls.service_offering = ServiceOffering.create(
 cls.api_client,
 cls.services[service_offering]
 )
 cls._cleanup.append(cls.service_offering)
 #create virtual machine
 ==
 Error Information:
 ==
 test_01_snapshot_usage (integration.component.test_usage.TestSnapshotUsage): 
 CRITICAL: EXCEPTION: test_01_snapshot_usage: ['Traceback (most recent call 
 last):\n', '  File /usr/local/lib/python2.7/dist-packages/nose/suite.py, 
 line 208, in run\nself.setUp()\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n  
   self.setupContext(ancestor)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in 
 setupContext\ntry_run(context, names)\n', '  File 
 /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n 
return func()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
  line 702, in setUpClass\ncls.tearDownClass()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
  line 712, in tearDownClass\nraise Exception(Warning: Exception during 
 cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type 
 object 'TestTemplateUsage' has no attribute '_cleanup'\n]
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in 
 run
 self.setUp()
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in 
 setUp
 self.setupContext(ancestor)
   File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in 
 setupContext
 try_run(context, names)
   File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in 
 try_run
 return func()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
  line 702, in setUpClass
 cls.tearDownClass()
   File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
  line 712, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 'Warning: Exception during cleanup : type object \'TestTemplateUsage\' has no 
 attribute \'_cleanup\'\n 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instanc

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127602#comment-14127602
 ] 

ASF subversion and git services commented on CLOUDSTACK-7505:
-

Commit fcf2c1b6bc08037cca9952d5c97490c74e29876b in cloudstack's branch 
refs/heads/master from [~anthonyxu]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fcf2c1b ]

CLOUDSTACK-7505:

  if VM is created from ISO, don't change platform metadat for VM on XS


 Windows 2012 and Windows 8 instances created with 6.5 PV tools installed 
 template are getting into repair state, Later XenServer 6.5 Is shutting down 
 these instances automatically 
 

 Key: CLOUDSTACK-7505
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.5.0
Reporter: Sailaja Mada
Priority: Blocker
 Attachments: i-2-10-VM-from-tools-template, 
 i-2-7-vm-params-after-registeriso-PVtoolsinstallation


 Steps:
 1. Configure Adv Zone using XenServer 6.5 
 2.  Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools 
 installed.I have enabled option Original XS Version is 6.1+: Yes
 3. Deployed VM using this template 
 4. VM got started and moved to running state. But  got  into repair state, 
 Later XenServer 6.5 Is shutting down these instances automatically.
 VM Parameters are : 
   platform (MRW): timeoffset: 0; viridian: true; acpi: 1; 
 ap
 ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std
 allowed-operations (SRO): changing_dynamic_range; hard_reboot; 
 hard_
 shutdown; pause; snapshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instance

2014-09-09 Thread Anthony Xu (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Xu resolved CLOUDSTACK-7505.

Resolution: Fixed
  Assignee: Anthony Xu

commit fcf2c1b6bc08037cca9952d5c97490c74e29876b
Author: Anthony Xu anthony...@citrix.com
Date:   Tue Sep 9 14:01:23 2014 -0700

CLOUDSTACK-7505:

  if VM is created from ISO, don't change platform metadat for VM on XS

 Windows 2012 and Windows 8 instances created with 6.5 PV tools installed 
 template are getting into repair state, Later XenServer 6.5 Is shutting down 
 these instances automatically 
 

 Key: CLOUDSTACK-7505
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.5.0
Reporter: Sailaja Mada
Assignee: Anthony Xu
Priority: Blocker
 Attachments: i-2-10-VM-from-tools-template, 
 i-2-7-vm-params-after-registeriso-PVtoolsinstallation


 Steps:
 1. Configure Adv Zone using XenServer 6.5 
 2.  Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools 
 installed.I have enabled option Original XS Version is 6.1+: Yes
 3. Deployed VM using this template 
 4. VM got started and moved to running state. But  got  into repair state, 
 Later XenServer 6.5 Is shutting down these instances automatically.
 VM Parameters are : 
   platform (MRW): timeoffset: 0; viridian: true; acpi: 1; 
 ap
 ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std
 allowed-operations (SRO): changing_dynamic_range; hard_reboot; 
 hard_
 shutdown; pause; snapshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CLOUDSTACK-7148) [Automation] Fix the script test_redundant_router_cleanups.py - TypeError: this constructor takes no arguments

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7148.


Closing the bug as it is no longer seen in the automation run.

 [Automation] Fix the script test_redundant_router_cleanups.py - TypeError: 
 this constructor takes no arguments
 

 Key: CLOUDSTACK-7148
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7148
 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: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.5.0


 self.assertEqual(
 len(routers),
 2,
 Length of the list router should be 2 (Backup  master)
 )
 self.debug(Stopping the user VM: %s % virtual_machine.name)
 try:
 virtual_machine.stop(self.apiclient)
 except Exception as e:
 self.fail(Failed to stop guest Vm: %s - %s %
 (virtual_machine.name, e))
 interval = Configurations( -- BUG: Missing list method
 self.apiclient,
 name='network.gc.interval'
 )
 delay = int(interval[0].value)
 interval = Configurations.list(
 self.apiclient,
 name='network.gc.wait'
 )
 exp = int(interval[0].value)
 self.debug(Sleeping for network gc wait + interval time)
 # Sleep to ensure that all resources are deleted
 time.sleep((delay + exp) * 2)
 
 Error Message:
 
 est_network_gc 
 (integration.component.test_redundant_router_cleanups.TestRedundantRouterNetworkCleanups):
  DEBUG: Sending GET Cmd : listVirtualMachines===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.41
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=K1eKecmH_8ipIelDho9Wm-HZm0WhiIw-2cGFZveZJdKOwB_Cchln9O4QBNxkyy8U8UHCRt_leTpa-yvEb04EOAid=ecabe928-5dd9-4f53-a5b1-c758e664ac28response=jsoncommand=listVirtualMachinessignature=%2Fu2ByYo%2F3d%2BN3YRaFn00CddqfgA%3DlistAll=True
  HTTP/1.1 200 1374
 test_network_gc 
 (integration.component.test_redundant_router_cleanups.TestRedundantRouterNetworkCleanups):
  DEBUG: Response : [{domain : u'ROOT', domainid : 
 u'ae89b9d2-0901-11e4-a9bc-5a9383355ca2', haenable : False, templatename : 
 u'CentOS 5.6(64-bit) no GUI (XenServer)', securitygroup : [], zoneid : 
 u'9f076f9c-266e-4d26-b6b5-05e197181167', cpunumber : 1, ostypeid : 142, 
 passwordenabled : False, instancename : u'i-376-589-VM', id : 
 u'ecabe928-5dd9-4f53-a5b1-c758e664ac28', displayvm : True, state : 
 u'Stopped', guestosid : u'aea0f246-0901-11e4-a9bc-5a9383355ca2', cpuspeed : 
 100, serviceofferingid : u'956b0c1a-94a2-42e8-97a4-ed5cc4ff8afd', zonename : 
 u'XenRT-Zone-0', isdynamicallyscalable : True, displayname : u'Test VM', tags 
 : [], nic : [{networkid : u'4e47e163-7ee2-4bd2-807d-d53867768688', macaddress 
 : u'02:00:0b:4c:00:01', type : u'Isolated', id : 
 u'd0ac745f-c73f-43d6-847c-665067c70bb3', traffictype : u'Guest', netmask : 
 u'255.255.255.0', ipaddress : u'192.168.200.253', networkname : u'Test 
 Network', gateway : u'192.168.200.1', isdefault : True}], memory : 128, 
 templateid : u'ae8e25a8-0901-11e4-a9bc-5a9383355ca2', affinitygroup : [], 
 account : u'test-TestRedundantRouterNetworkCleanups-test_network_gc-YG37AT', 
 name : u'VM-ecabe928-5dd9-4f53-a5b1-c758e664ac28', created : 
 u'2014-07-12T12:49:11+', hypervisor : u'XenServer', rootdevicetype : 
 u'ROOT', rootdeviceid : 0, serviceofferingname : u'Tiny Instance', 
 templatedisplaytext : u'CentOS 5.6(64-bit) no GUI (XenServer)'}]
 test_network_gc 
 (integration.component.test_redundant_router_cleanups.TestRedundantRouterNetworkCleanups):
  CRITICAL: EXCEPTION: test_network_gc: ['Traceback (most recent call 
 last):\n', '  File /usr/lib/python2.7/unittest/case.py, line 332, in run\n  
   testMethod()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_redundant_router_cleanups.py,
  line 597, in test_network_gc\nname=\'network.gc.interval\'\n', 
 'TypeError: this constructor takes no arguments\n']
 -  end captured logging  -
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File 
 

[jira] [Closed] (CLOUDSTACK-7137) [Automation] Fix the script test_escalations_securitygroups.py - Unable to execute API command deletesecuritygroup due to invalid value.

2014-09-09 Thread Chandan Purushothama (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-7137.


Closing the bug as it is no longer seen in automation runs.

 [Automation] Fix the script test_escalations_securitygroups.py - Unable to 
 execute API command deletesecuritygroup due to invalid value.
 --

 Key: CLOUDSTACK-7137
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7137
 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: Ashutosk Kelkar
Priority: Critical
 Fix For: 4.5.0


 
 Error Message:
 
 test_01_list_securitygroups_pagination 
 (integration.component.test_escalations_securitygroups.TestSecurityGroups): 
 DEBUG: Sending GET Cmd : deleteSecurityGroup===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAresponse=jsoncommand=deleteSecurityGroupsignature=JB2or4xVThMUY0Pob4shmnqTe5s%3Did=66eeb3b4-3b3d-4037-8483-7ed1a1485893
  HTTP/1.1 431 370
 test_01_list_securitygroups_pagination 
 (integration.component.test_escalations_securitygroups.TestSecurityGroups): 
 ERROR: Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj\nraise 
 cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
 'CloudstackAPIException: Execute cmd: deletesecuritygroup failed, due to: 
 errorCode: 431, errorText:Unable to execute API command deletesecuritygroup 
 due to invalid value. Invalid parameter id 
 value=66eeb3b4-3b3d-4037-8483-7ed1a1485893 due to incorrect long value 
 format, or entity does not exist or due to incorrect parameter annotation for 
 the field in api cmd class.\n']
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse
 response_cls)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj
 raise cloudstackException.CloudstackAPIException(respname, errMsg)
 CloudstackAPIException: Execute cmd: deletesecuritygroup failed, due to: 
 errorCode: 431, errorText:Unable to execute API command deletesecuritygroup 
 due to invalid value. Invalid parameter id 
 value=66eeb3b4-3b3d-4037-8483-7ed1a1485893 due to incorrect long value 
 format, or entity does not exist or due to incorrect parameter annotation for 
 the field in api cmd class.
 test_01_list_securitygroups_pagination 
 (integration.component.test_escalations_securitygroups.TestSecurityGroups): 
 ERROR: marvinRequest : CmdName: 
 marvin.cloudstackAPI.deleteSecurityGroup.deleteSecurityGroupCmd object at 
 0x276fa90 Exception: ['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest\nraise self.__lastError\n', 
 'CloudstackAPIException: Execute cmd: deletesecuritygroup failed, due to: 
 errorCode: 431, errorText:Unable to execute API command deletesecuritygroup 
 due to invalid value. Invalid parameter id 
 value=66eeb3b4-3b3d-4037-8483-7ed1a1485893 due to incorrect long value 
 format, or entity does not exist or due to incorrect parameter annotation for 
 the field in api cmd class.\n']
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest
 raise self.__lastError
 CloudstackAPIException: Execute cmd: deletesecuritygroup failed, due to: 
 errorCode: 431, errorText:Unable to execute API command deletesecuritygroup 
 due to invalid value. Invalid parameter id 
 value=66eeb3b4-3b3d-4037-8483-7ed1a1485893 due to incorrect long value 
 format, or entity does not exist or due to incorrect parameter annotation for 
 the field in api cmd class.
 test_01_list_securitygroups_pagination 
 

[jira] [Commented] (CLOUDSTACK-7514) Automation] - Automate ACL test cases relating to listSnapshots()

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127629#comment-14127629
 ] 

ASF subversion and git services commented on CLOUDSTACK-7514:
-

Commit 7a79fd1c5ee4ca93e8e133f3dcda21de565a4888 in cloudstack's branch 
refs/heads/master from [~sangeethah]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7a79fd1 ]

CLOUDSTACK-7514-[Automation] - Automate ACL test cases relating to 
listSnapshots()


 Automation] - Automate ACL test cases relating to listSnapshots()
 -

 Key: CLOUDSTACK-7514
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7514
 Project: CloudStack
  Issue Type: Task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: marvin
Affects Versions: 4.4.0
Reporter: Sangeetha Hariharan

 [Automation] - Automate ACL test cases relating to listSnapshots()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7033) [Automation] - Automate ACL test cases relating to isolate Network for deleteNetwork() api..

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127632#comment-14127632
 ] 

ASF subversion and git services commented on CLOUDSTACK-7033:
-

Commit 9b65759f36ed5894cf0e193508930a5f62b9165a in cloudstack's branch 
refs/heads/master from [~sangeethah]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9b65759 ]

CLOUDSTACK-7033-[Automation] - Automate ACL test cases relating to isolate 
Network for deleteNetwork() api


 [Automation] - Automate ACL test cases relating to isolate Network for 
 deleteNetwork() api..
 

 Key: CLOUDSTACK-7033
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7033
 Project: CloudStack
  Issue Type: Task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: marvin
Affects Versions: 4.4.0
Reporter: Sangeetha Hariharan
Assignee: Sangeetha Hariharan

 [Automation] - Automate ACL test cases relating to isolate Network for 
 deleteNetwork() api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7310) XenServer does not support shrink data disk. CloudStack should prevent such an operation on XenServer

2014-09-09 Thread Alex Brett (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Brett updated CLOUDSTACK-7310:
---
Component/s: (was: Automation)
   Assignee: (was: John Dilley)
Summary: XenServer does not support shrink data disk. CloudStack should 
prevent such an operation on XenServer  (was: [Automation] XenServer does not 
support shrink data disk. CloudStack should prevent such an operation on 
XenServer)

Fair enough - in that case removing the automation tag/component and 
unassigning from John Dilley, as I know he will not be fixing the API code...

 XenServer does not support shrink data disk. CloudStack should prevent such 
 an operation on XenServer
 -

 Key: CLOUDSTACK-7310
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7310
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes, XenServer
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


 XenServer does not allowing shrinking of disks currently. Please add code on 
 Cloudstack to prevent such an operation (similar to VMWare case). Failing to 
 prevent such an operation on XenServer leads to 
 https://issues.apache.org/jira/browse/CLOUDSTACK-7228 . 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7311) XenServer does not support shrink data disk. FS on cwiki needs to be corrected

2014-09-09 Thread Anthony Xu (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Xu resolved CLOUDSTACK-7311.

Resolution: Fixed

FS is updated

 XenServer does not support shrink data disk. FS on cwiki needs to be corrected
 --

 Key: CLOUDSTACK-7311
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7311
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Critical
 Fix For: 4.5.0


 Hello Marcus,
 Based on https://issues.apache.org/jira/browse/CLOUDSTACK-7310, Please make 
 the corresponding changes to Feature FS at 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Resize+Data+Volumes,
 Thank you,
 Chandan.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7261) CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property

2014-09-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127665#comment-14127665
 ] 

ASF subversion and git services commented on CLOUDSTACK-7261:
-

Commit 07c9c02789ac1aeb79b7ca79140e3fff1e0bc956 in cloudstack's branch 
refs/heads/master from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=07c9c02 ]

CLOUDSTACK-7261: related UI change after lsitSystemVMs/listRouters API were 
fixed to return hypervisor property while state is running.


 CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor 
 property 
 

 Key: CLOUDSTACK-7261
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7261
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0


 listSystemVMs API and listRouters API doesn't return hypervisor property and 
 this is important for scalevm operation, since its not implemented for all 
 the hypervisors



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7261) CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property

2014-09-09 Thread Jessica Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-7261.
--
Resolution: Fixed

 CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor 
 property 
 

 Key: CLOUDSTACK-7261
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7261
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0


 listSystemVMs API and listRouters API doesn't return hypervisor property and 
 this is important for scalevm operation, since its not implemented for all 
 the hypervisors



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


  1   2   >