[jira] [Resolved] (CLOUDSTACK-5463) Hyper-V does not report stopped VMs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5463.
---
Resolution: Fixed
It was fixed in commit d45ee3ef21fd55c8a1cf1373225cab81389ad8c7 and
3ec7497e1ebcaa65a8cbd24c27326356355ac8cc; as part of vmsync changes. When a vm
is stopped outside cloudstack; say by Hyper-V manager; the state of the vm is
updated to stopped in cloudstack db too.
Hyper-V does not report stopped VMs
---
Key: CLOUDSTACK-5463
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5463
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Donal Lafferty
Assignee: Devdeep Singh
Labels: Hyper-V
Fix For: 4.4.0
The Hyper-V agent is never asked whether a VM is running. E.g. it is only
asked the VmStats:
2013-12-11 06:28:08,544 [32] INFO HypervResource.HypervResourceController
[7bbebc6a-400a-4d9f-832a-06924b823ba4] -
com.cloud.agent.api.GetVmStatsCommand{
vmNames: [
i-2-3-VM
],
hostGuid: 700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource,
hostName: 10.70.176.29,
contextMap: {},
wait: 0
}
2013-12-11 06:28:08,716 [32] DEBUG HypervResource.WmiCallsV2
[7bbebc6a-400a-4d9f-832a-06924b823ba4] - VM
20E0665F-4EE0-42A5-AC94-03DC9D3B5E8C(elementName i-2-3-VM) has 1 CPUs, and
load of 0
2013-12-11 06:28:08,717 [32] INFO HypervResource.HypervResourceController
[7bbebc6a-400a-4d9f-832a-06924b823ba4] - {
com.cloud.agent.api.GetVmStatsAnswer: {
vmStatsMap: {
i-2-3-VM: {
cpuUtilization: 0.0,
networkReadKBs: 1.0,
networkWriteKBs: 1.0,
numCPUs: 1,
entityType: vm
}
},
result: true,
contextMap: {}
}
}
Therefore, if the VM shut itself down, the management server thinks it is
still running.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6257) Private template creation issue - Check if VM is in stopped state before creating template from its volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye closed CLOUDSTACK-6257. -- Resolution: Fixed Private template creation issue - Check if VM is in stopped state before creating template from its volume -- Key: CLOUDSTACK-6257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6257 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: Ashutosk Kelkar Assignee: Ashutosk Kelkar Labels: automation Fix For: 4.4.0 Following test cases are failing in case VM does not go into stopped state before creating template from its volume. test_01_template_usage test_05_templates_per_account test_05_templates_per_domain test_06_template_tag test_03_delete_template test_01_template_usage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6536) Code Cleanup: Remove wait and check stopped state code after VM stop operation from all test cases
Gaurav Aradhye created CLOUDSTACK-6536: -- Summary: Code Cleanup: Remove wait and check stopped state code after VM stop operation from all test cases Key: CLOUDSTACK-6536 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6536 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: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.4.0 In many test cases, code snippet that waits for certain time interval and verifies that the VM is in stopped state exists after VM stop operation. This code snippet is no longer necessary as the VM state is verified after stop operation in the marvin library itself. So it is better to remove this, and add try catch block around VM stop command so that the exception raised from the library is caught properly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-6257) Private template creation issue - Check if VM is in stopped state before creating template from its volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye reopened CLOUDSTACK-6257: Private template creation issue - Check if VM is in stopped state before creating template from its volume -- Key: CLOUDSTACK-6257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6257 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: Ashutosk Kelkar Assignee: Ashutosk Kelkar Labels: automation Fix For: 4.4.0 Following test cases are failing in case VM does not go into stopped state before creating template from its volume. test_01_template_usage test_05_templates_per_account test_05_templates_per_domain test_06_template_tag test_03_delete_template test_01_template_usage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6537) Test Case Changes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Girish Shilamkar reassigned CLOUDSTACK-6537: Assignee: Girish Shilamkar (was: Gaurav Aradhye) Test Case Changes - Key: CLOUDSTACK-6537 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6537 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Gaurav Aradhye Assignee: Girish Shilamkar Fix For: 4.4.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6536) Code Cleanup: Remove wait and check stopped state code after VM stop operation from all test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Girish Shilamkar reassigned CLOUDSTACK-6536: Assignee: Girish Shilamkar (was: Gaurav Aradhye) Code Cleanup: Remove wait and check stopped state code after VM stop operation from all test cases Key: CLOUDSTACK-6536 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6536 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: Gaurav Aradhye Assignee: Girish Shilamkar Labels: automation Fix For: 4.4.0 In many test cases, code snippet that waits for certain time interval and verifies that the VM is in stopped state exists after VM stop operation. This code snippet is no longer necessary as the VM state is verified after stop operation in the marvin library itself. So it is better to remove this, and add try catch block around VM stop command so that the exception raised from the library is caught properly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-6257) Private template creation issue - Check if VM is in stopped state before creating template from its volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Girish Shilamkar reopened CLOUDSTACK-6257: -- Private template creation issue - Check if VM is in stopped state before creating template from its volume -- Key: CLOUDSTACK-6257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6257 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: Ashutosk Kelkar Assignee: Girish Shilamkar Labels: automation Fix For: 4.4.0 Following test cases are failing in case VM does not go into stopped state before creating template from its volume. test_01_template_usage test_05_templates_per_account test_05_templates_per_domain test_06_template_tag test_03_delete_template test_01_template_usage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6257) Private template creation issue - Check if VM is in stopped state before creating template from its volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Girish Shilamkar reassigned CLOUDSTACK-6257: Assignee: Girish Shilamkar (was: Ashutosk Kelkar) Private template creation issue - Check if VM is in stopped state before creating template from its volume -- Key: CLOUDSTACK-6257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6257 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: Ashutosk Kelkar Assignee: Girish Shilamkar Labels: automation Fix For: 4.4.0 Following test cases are failing in case VM does not go into stopped state before creating template from its volume. test_01_template_usage test_05_templates_per_account test_05_templates_per_domain test_06_template_tag test_03_delete_template test_01_template_usage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6536) Code Cleanup: Remove wait and check stopped state code after VM stop operation from all test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye reassigned CLOUDSTACK-6536: -- Assignee: Gaurav Aradhye (was: Girish Shilamkar) Code Cleanup: Remove wait and check stopped state code after VM stop operation from all test cases Key: CLOUDSTACK-6536 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6536 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: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.4.0 In many test cases, code snippet that waits for certain time interval and verifies that the VM is in stopped state exists after VM stop operation. This code snippet is no longer necessary as the VM state is verified after stop operation in the marvin library itself. So it is better to remove this, and add try catch block around VM stop command so that the exception raised from the library is caught properly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6537) Test Case Changes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye reassigned CLOUDSTACK-6537: -- Assignee: Gaurav Aradhye (was: Girish Shilamkar) Test Case Changes - Key: CLOUDSTACK-6537 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6537 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.4.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6389) test__01_nic requires advanced zone but it tagged as basic test case
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985270#comment-13985270 ] ASF subversion and git services commented on CLOUDSTACK-6389: - Commit cfa783fef27f64ebdd42f66c59445cb37c9a9764 in cloudstack's branch refs/heads/4.4-automation from [~santhoshe] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cfa783f ] Added fix for CLOUDSTACK-6389 Added changes for CLOUDSTACK-6389. More details in the bug. Signed-off-by: Santhosh Edukulla santhosh.eduku...@citrix.com Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test__01_nic requires advanced zone but it tagged as basic test case Key: CLOUDSTACK-6389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6389 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Reporter: Chethan Krishnappa Assignee: Santhosh Kumar Edukulla test_nic.py which is under smoke tests is tagged as basic mode test but test runs only if the zone is advanced. if zone.networktype != 'Advanced': self.skipTest(Cannot run this test with a basic zone, please use advanced!) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6389) test__01_nic requires advanced zone but it tagged as basic test case
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985269#comment-13985269 ] ASF subversion and git services commented on CLOUDSTACK-6389: - Commit cfa783fef27f64ebdd42f66c59445cb37c9a9764 in cloudstack's branch refs/heads/4.4-automation from [~santhoshe] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cfa783f ] Added fix for CLOUDSTACK-6389 Added changes for CLOUDSTACK-6389. More details in the bug. Signed-off-by: Santhosh Edukulla santhosh.eduku...@citrix.com Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test__01_nic requires advanced zone but it tagged as basic test case Key: CLOUDSTACK-6389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6389 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Reporter: Chethan Krishnappa Assignee: Santhosh Kumar Edukulla test_nic.py which is under smoke tests is tagged as basic mode test but test runs only if the zone is advanced. if zone.networktype != 'Advanced': self.skipTest(Cannot run this test with a basic zone, please use advanced!) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6389) test__01_nic requires advanced zone but it tagged as basic test case
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985273#comment-13985273 ] ASF subversion and git services commented on CLOUDSTACK-6389: - Commit 6c9b21907c2600f320d2afc2fb7273fae73b7ba1 in cloudstack's branch refs/heads/master from [~santhoshe] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6c9b219 ] Added fix for CLOUDSTACK-6389 Added changes for CLOUDSTACK-6389. More details in the bug. Signed-off-by: Santhosh Edukulla santhosh.eduku...@citrix.com Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test__01_nic requires advanced zone but it tagged as basic test case Key: CLOUDSTACK-6389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6389 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Reporter: Chethan Krishnappa Assignee: Santhosh Kumar Edukulla test_nic.py which is under smoke tests is tagged as basic mode test but test runs only if the zone is advanced. if zone.networktype != 'Advanced': self.skipTest(Cannot run this test with a basic zone, please use advanced!) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6389) test__01_nic requires advanced zone but it tagged as basic test case
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985272#comment-13985272 ] ASF subversion and git services commented on CLOUDSTACK-6389: - Commit 6c9b21907c2600f320d2afc2fb7273fae73b7ba1 in cloudstack's branch refs/heads/master from [~santhoshe] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6c9b219 ] Added fix for CLOUDSTACK-6389 Added changes for CLOUDSTACK-6389. More details in the bug. Signed-off-by: Santhosh Edukulla santhosh.eduku...@citrix.com Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test__01_nic requires advanced zone but it tagged as basic test case Key: CLOUDSTACK-6389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6389 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Reporter: Chethan Krishnappa Assignee: Santhosh Kumar Edukulla test_nic.py which is under smoke tests is tagged as basic mode test but test runs only if the zone is advanced. if zone.networktype != 'Advanced': self.skipTest(Cannot run this test with a basic zone, please use advanced!) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6512) IAM - Not able to list shared networks in the Vm deployment flow.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985281#comment-13985281 ] ASF subversion and git services commented on CLOUDSTACK-6512: - Commit 2f35ef2f9ba5504d6bf0ee0c4e328f2f3c85b7fd in cloudstack's branch refs/heads/4.4 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2f35ef2 ] CLOUDSTACK-6512:IAM - Not able to list shared networks in the Vm deployment flow. This commit is to revert ec5ee761d98c67c7da2ea70b623d4a9f3da966b5 to still use old logic for listNetworks to keep old behavior instead of new IAM model. IAM - Not able to list shared networks in the Vm deployment flow. - Key: CLOUDSTACK-6512 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6512 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Environment: Build from 4.4. Reporter: Sangeetha Hariharan Assignee: Min Chen Priority: Critical Fix For: 4.4.0 IAM - Not able to list shared networks in the Vm deployment flow. Steps to reproduce the problem: Create a shared network that is domain specific / account specific. Log in as the account which should have access to this shared network. Using UI , try to deploy a VM using this shared network. shared network is not displayed in the list of networks. This is the call made by UI: http://10.223.49.6:8080/client/api?command=listNetworksresponse=jsonsessionkey=Enn1TgriYaANFQ%2BDKJR7T2Jc9l0%3DzoneId=fdd0ce43-41b8-49ef-9e59-70ead27bda4ccanusefordeploy=truedomainid=a59a0ce2-b5aa-4460-ade8-91d26e048bc4account=testD1_=1398446574911 When Networks are listed using the network tab , then we see the shared network being listed. Following API call without the domainid and account paramater is able to return the shared network. http://10.223.49.6:8080/client/api?command=listNetworksresponse=jsonsessionkey=Enn1TgriYaANFQ%2BDKJR7T2Jc9l0%3DlistAll=truepage=1pagesize=20_=1398446422647 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6533) IAM - Templates - Public templates do not have permissions to be used by ROOT group.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985283#comment-13985283 ] ASF subversion and git services commented on CLOUDSTACK-6533: - Commit 504bd0377d8053a911f9823e06ce288af057446b in cloudstack's branch refs/heads/4.4 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=504bd03 ] CLOUDSTACK-6533: IAM - Templates - Public templates do not have permissions to be used by ROOT group. IAM - Templates - Public templates do not have permissions to be used by ROOT group. Key: CLOUDSTACK-6533 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6533 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Environment: Build from 4.4 Reporter: Sangeetha Hariharan Assignee: Min Chen Priority: Critical Fix For: 4.4.0 IAM - Templates - Public templates do not have permissions to be used by ROOT group. As regular user create a public template. In iam_policy_permission policy we do not have permission for Admin group. mysql select * from iam_policy_permission where scope_id = 206; +--+---+---++--+--+-++---+-+-+ | id | policy_id | action| resource_type | scope_id | scope| access_type | permission | recursive | removed | created | +--+---+---++--+--+-++---+-+-+ | 4949 | 3 | listTemplates | VirtualMachineTemplate | 206 | RESOURCE | UseEntry| Allow | 0 | NULL| 2014-04-29 11:03:52 | | 4950 | 1 | listTemplates | VirtualMachineTemplate | 206 | RESOURCE | UseEntry| Allow | 0 | NULL| 2014-04-29 11:03:52 | mysql select * from vm_template where id=206; +-+--++--++--+--+-+--+-++-+-++--+-+-+---+-+--+-+-+-+-++--+--+-++--+-+--+ | id | unique_name | name | uuid | public | featured | type | hvm | bits | url | format | created | removed | account_id | checksum | display_text| enable_password | enable_sshkey | guest_os_id | bootable | prepopulate | cross_zones | extractable | hypervisor_type | source_template_id | template_tag | sort_key | size| state | update_count | updated | dynamically_scalable | +-+--++--++--+--+-+--+-++-+-++--+-+-+---+-+--+-+-+-+-++--+--+-++--+-+--+ | 206 | 206-318-179129bc-531f-31fe-a21d-23a8aa7b666f | Public_featured_d2a-G3GJQW | 265192c9-88d3-41d4-b435-6d3c3e5d256a | 1 | 1 | USER | 1 | 64 | http://10.223.110.232:/test.vhd | VHD| 2014-04-29 11:03:52 | NULL|318 | NULL | public and feature Template | 0 | 0 | 12 |1 | 0 | 0 | 1 | Simulator | NULL | NULL |0 | 5242880 | Active |0 | NULL| 0 |
[jira] [Commented] (CLOUDSTACK-6513) IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985282#comment-13985282 ] ASF subversion and git services commented on CLOUDSTACK-6513: - Commit 4ca65496c2605eb2264d0acc7a43c2c539a3d9b0 in cloudstack's branch refs/heads/4.4 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4ca6549 ] CLOUDSTACK-6513: IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list. This commit reverts listTemplates behavior to 4.3 old logic without using consistent interpretation of list parameters adopted in new IAM model. IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list. --- Key: CLOUDSTACK-6513 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6513 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Environment: Build from 4.4 Reporter: Sangeetha Hariharan Assignee: Min Chen Priority: Critical Fix For: 4.4.0 IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list. Steps to reproduce the problem: As user1 , Create a private template and a public template. Grant access to the private template for user2 using updateTemplatePermissions. As user2 , list templates with templatefilter=shared. This returns both public and the the shared template. GET http://10.223.49.6/client/api?command=listTemplatespagesize=100page=1listAll=truetemplatefilter=sharedapiKey=SrgUY-U-nUl4qsOyn409kCjA2jC7dR5ReIV9SjdnmzLOn3c0Fm-vZbDSpkldUjuqLAXt5ShodtXYOgRB5NCnJQsignature=WBO8ll9nyjiB29aVq%2FpUsEQrthM%3D \n\n ?xml version=1.0 encoding=UTF-8?listtemplatesresponse cloud-stack-version=4.4.0-SNAPSHOTcount6/counttemplateida2065bcc-7139-46b0-ac15-db7d3ff7dd75/idnamePublic_featured_d1a-TP7TPK/namedisplaytextpublic and feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:35-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD1A/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD1/domaindomainid691ab662-6793-42a0-96e6-3b31a2c4e52d/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateidce1635dc-1fcb-4f60-8d2f-d1129a3771ce/idnamePublic_not_featured_d2a-NPYFSN/namedisplaytextpublic and not feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:36-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedfalse/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD2/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD2/domaindomainid18222e53-7221-4d6f-9a76-8f59869f24b2/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateid223e0c09-e18e-4188-9d8e-7ff2e2305547/idnamePrivate_featured_d1-E9PQHO/namedisplaytextprivate and featured Template/displaytextispublicfalse/ispubliccreated2014-04-21T13:50:36-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD1A/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD1/domaindomainid691ab662-6793-42a0-96e6-3b31a2c4e52d/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateida7b69a5e-4cb3-45fa-b3e7-dab3a6b73e45/idnamePublic_not_featured_d1a-XOCR05/namedisplaytextpublic and not feature
[jira] [Commented] (CLOUDSTACK-6513) IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985285#comment-13985285 ] ASF subversion and git services commented on CLOUDSTACK-6513: - Commit 683c242ed343c56483768849c97b0398e407605a in cloudstack's branch refs/heads/4.4 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=683c242 ] CLOUDSTACK-6513: Optimize code by removing deprecated utility to QueryManagerImpl as private method just used for listTemplates and listAffinityGroups to avoid misuse by new list APIs. IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list. --- Key: CLOUDSTACK-6513 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6513 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Environment: Build from 4.4 Reporter: Sangeetha Hariharan Assignee: Min Chen Priority: Critical Fix For: 4.4.0 IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list. Steps to reproduce the problem: As user1 , Create a private template and a public template. Grant access to the private template for user2 using updateTemplatePermissions. As user2 , list templates with templatefilter=shared. This returns both public and the the shared template. GET http://10.223.49.6/client/api?command=listTemplatespagesize=100page=1listAll=truetemplatefilter=sharedapiKey=SrgUY-U-nUl4qsOyn409kCjA2jC7dR5ReIV9SjdnmzLOn3c0Fm-vZbDSpkldUjuqLAXt5ShodtXYOgRB5NCnJQsignature=WBO8ll9nyjiB29aVq%2FpUsEQrthM%3D \n\n ?xml version=1.0 encoding=UTF-8?listtemplatesresponse cloud-stack-version=4.4.0-SNAPSHOTcount6/counttemplateida2065bcc-7139-46b0-ac15-db7d3ff7dd75/idnamePublic_featured_d1a-TP7TPK/namedisplaytextpublic and feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:35-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD1A/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD1/domaindomainid691ab662-6793-42a0-96e6-3b31a2c4e52d/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateidce1635dc-1fcb-4f60-8d2f-d1129a3771ce/idnamePublic_not_featured_d2a-NPYFSN/namedisplaytextpublic and not feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:36-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedfalse/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD2/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD2/domaindomainid18222e53-7221-4d6f-9a76-8f59869f24b2/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateid223e0c09-e18e-4188-9d8e-7ff2e2305547/idnamePrivate_featured_d1-E9PQHO/namedisplaytextprivate and featured Template/displaytextispublicfalse/ispubliccreated2014-04-21T13:50:36-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD1A/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD1/domaindomainid691ab662-6793-42a0-96e6-3b31a2c4e52d/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateida7b69a5e-4cb3-45fa-b3e7-dab3a6b73e45/idnamePublic_not_featured_d1a-XOCR05/namedisplaytextpublic and not feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:35-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedfalse/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3
[jira] [Commented] (CLOUDSTACK-6532) Affinity Groups - As admin user, not able to list all affinity groups available for regular users by passing account and domainId paramater.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985284#comment-13985284
]
ASF subversion and git services commented on CLOUDSTACK-6532:
-
Commit 4f9b298817386d9eff8677e3c168f1dfdc7f6aeb in cloudstack's branch
refs/heads/4.4 from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4f9b298 ]
CLOUDSTACK-6532:Affinity Groups - As admin user, not able to list all
affinity groups available for regular users by passing account and
domainId paramater. This is to revert IAM way of implementing
listAffinityGroupsCmd, will bring it back when we have implemented real
impersonation.
Affinity Groups - As admin user, not able to list all affinity groups
available for regular users by passing account and domainId paramater.
Key: CLOUDSTACK-6532
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6532
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: IAM
Affects Versions: 4.4.0
Environment: Build from 4.4
Reporter: Sangeetha Hariharan
Assignee: Min Chen
Priority: Critical
Fix For: 4.4.0
Create an anti-affinity group as regular user.
As admin user, try to list all affinity groups available for regular users by
passing account and domainId parameter.
http://10.223.49.6:8080/client/api?command=listAffinityGroupsresponse=jsonsessionkey=okCw58hoD%2BrUSZ9NO5LKHz6ie9U%3D_=1398792364257account=testD1A-TestVMList-U27DEVdomainId=71dcc0ac-c230-4e96-97ad-6e4f3ddc53cf
No affinity group is listed.
As regular user:
{ listaffinitygroupsresponse : { count:1 ,affinitygroup : [
{id:bee9a7c5-3124-46b6-b258-893c8c9cc244,name:test-123,description:test-123,account:testD1A-TestVMList-U27DEV,domainid:71dcc0ac-c230-4e96-97ad-6e4f3ddc53cf,domain:D1-19BDAN,type:host
anti-affinity} ] } }
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6255) UI for supporting region level VPC, distributed routing enabled VPC and stretched L2 neworks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-6255. -- Resolution: Fixed UI for supporting region level VPC, distributed routing enabled VPC and stretched L2 neworks Key: CLOUDSTACK-6255 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6255 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.0 Reporter: Murali Reddy Assignee: Gabor Apati-Nagy Fix For: 4.4.0 UI for supporting region level VPC, distributed routing enabled VPC and stretched L2 neworks -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6510) java.lang.IllegalStateException: circular reference error during live migration of VM.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-6510:
-
Assignee: Devdeep Singh
java.lang.IllegalStateException: circular reference error during live
migration of VM.
--
Key: CLOUDSTACK-6510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.4.0
Environment: MS 4.4
XS 6.2.0
Reporter: Sanjay Tripathi
Assignee: Devdeep Singh
Fix For: 4.4.0
Getting the following exception during live migration of VM, though this is
not affecting live migration functionality:
2014-04-25 13:59:27,699 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-2:job-71/job-72 ctx-1920db32) Seq 4-3947968023343661101:
Executing: { Cmd , MgmtId: 116698015432997, via: 4(xen20.cloud.com), Ver:
v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-2-9-VM,wait:20}}]
}
2014-04-25 13:59:27,700 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-36:ctx-a412b1b1) Seq 4-3947968023343661101: Executing request
2014-04-25 13:59:27,718 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-36:ctx-a412b1b1) 3. The VM i-2-9-VM is in Running state
2014-04-25 13:59:27,719 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-36:ctx-a412b1b1) Seq 4-3947968023343661101: Response Received:
2014-04-25 13:59:27,719 DEBUG [c.c.a.t.Request] (DirectAgent-36:ctx-a412b1b1)
Seq 4-3947968023343661101: Processing: { Ans: , MgmtId: 116698015432997,
via: 4, Ver: v1, Flags: 10,
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{state:Running,result:true,wait:0}}]
}
2014-04-25 13:59:27,721 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-2:job-71/job-72 ctx-1920db32) Seq 4-3947968023343661101:
Received: { Ans: , MgmtId: 116698015432997, via: 4, Ver: v1, Flags: 10, {
CheckVirtualMachineAnswer } }
2014-04-25 13:59:27,735 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-59:ctx-3603e975) Seq 1-2562829662950522954: Response Received:
2014-04-25 13:59:27,736 DEBUG [c.c.a.t.Request]
(StatsCollector-1:ctx-8f878bfd) Seq 1-2562829662950522954: Received: { Ans:
, MgmtId: 116698015432997, via: 1, Ver: v1, Flags: 10, { GetGPUStatsAnswer } }
2014-04-25 13:59:27,807 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-2:job-71/job-72) Done with run of VM work job:
com.cloud.vm.VmWorkMigrate for VM 9, job origin: 71
2014-04-25 13:59:27,807 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-2:job-71/job-72) Unable to complete AsyncJobVO {id:72,
userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyACVjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZVdpdGhTdG9yYWdlsew9z6UxtXMCAANKAApkZXN0SG9zdElkSgAJc3JjSG9zdElkTAAMdm9sdW1lVG9Qb29sdAAPTGphdmEvdXRpbC9NYXA7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAJdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbAAEAAVzcgARamF2YS51dGlsLkhhc2hNYXAFB9rBwxZg0QMAAkYACmxvYWRGYWN0b3JJAAl0aHJlc2hvbGR4cD9MdwgQAHg,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 116698015432997, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Fri Apr 25 13:55:58 IST 2014}, job origin:71
java.lang.IllegalStateException: circular reference error
Offending field: field
Offending object: preserveType: false, type: class java.lang.reflect.Field,
obj: private long org.apache.cloudstack.storage.datastore.db.StoragePoolVO.id
at
com.google.gson.CircularReferenceException.createDetailedException(CircularReferenceException.java:43)
at
com.google.gson.JsonSerializationVisitor.visitObjectField(JsonSerializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:69)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonSerializationVisitor.getJsonElementForChild(JsonSerializationVisitor.java:147)
at
com.google.gson.JsonSerializationVisitor.addAsChildOfObject(JsonSerializationVisitor.java:127)
at
com.google.gson.JsonSerializationVisitor.visitObjectField(JsonSerializationVisitor.java:114)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:69)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonSerializationVisitor.getJsonElementForChild(JsonSerializationVisitor.java:147)
at
[jira] [Created] (CLOUDSTACK-6538) Migrating a volume causes snapshot schedule to disappear
Remi Bergsma created CLOUDSTACK-6538: Summary: Migrating a volume causes snapshot schedule to disappear Key: CLOUDSTACK-6538 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6538 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Remi Bergsma When a volume is migrated to another primary storage, the snapshot schedule that exists before migration, is no longer active after migration. Steps to reproduce: - create a volume - create a snapshot policy - note it creates an entry in cloud.snapshot_policy table - migrate volume to another primary storage - note the entry in cloud.snapshot_policy has been deleted Cause: Migrating a volume leads to a volume with a new id and uuid. Since the snapshot schedule is linked to a volume based on id, this is lost after migration. Please: - do not delete entries in cloud.snapshot_policy but mark as ‘deleted’ instead (like done on other tables) - recreate the snapshot schedule for a volume that was migrated, using its new id. Or update the table with the new id. This is a serious bug, because the user does not expect the snapshot schedule to disappear. Hence, when a snapshot is needed after migration you have a problem that cannot be fixed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6540) API: add listOrphanedSnapshots() call
Remi Bergsma created CLOUDSTACK-6540: Summary: API: add listOrphanedSnapshots() call Key: CLOUDSTACK-6540 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6540 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Remi Bergsma When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there. A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active. When I know the name of the volume, I can use a keyword search like this: list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202 count = 3 snapshot: ++--+--+ |name| created | volumeid | ++--+--+ | centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | | centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 | | centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 | ++--+--+ But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6541) The UI allows snapshot schedules that the API does not accept
Remi Bergsma created CLOUDSTACK-6541: Summary: The UI allows snapshot schedules that the API does not accept Key: CLOUDSTACK-6541 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6541 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Remi Bergsma Priority: Minor Monthly snapshot schedules for volumes can only be done on day 1-28 of month. The UI allows to select 29,30,31 and when you save it, the following error is displayed: Invalid schedule: 00:1:31 for interval type: monthly Please remove days 29,30,31 from select box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6539) When migrating a volume, warn that snapshots will be lost
Remi Bergsma created CLOUDSTACK-6539: Summary: When migrating a volume, warn that snapshots will be lost Key: CLOUDSTACK-6539 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6539 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Remi Bergsma Snapshots that are created on a volume, are not available anymore after the volume is migrated to another primary storage. This is something the user does not expect, so let’s warn for it in the UI. Alert: Migrating this volume will delete its snapshots. Sure? If NO, do nothing. If YES, proceed like we do now. Cause: Snapshots are linked to a volume id, which changes after migration. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6543) Advanced search on instances has domain list unsorted
Remi Bergsma created CLOUDSTACK-6543: Summary: Advanced search on instances has domain list unsorted Key: CLOUDSTACK-6543 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6543 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Remi Bergsma Priority: Minor UI: go to instances select little arrow to enter advanced search the domains in this list are unsorted (listed in the order they were added). Especially when there are a large number of them, this way of working takes a lot of time to select the right one. Please sort this list. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6542) Interval type not consistent in create/list snapshot schedules
Remi Bergsma created CLOUDSTACK-6542: Summary: Interval type not consistent in create/list snapshot schedules Key: CLOUDSTACK-6542 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6542 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Remi Bergsma Priority: Minor When you create a snapshot schedule, the ‘intervaltype’ has to be entered like ‘DAILY, HOURLY’ etc. create snapshotpolicy volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 schedule=23:1 intervaltype=DAILY timezone=Europe/Amsterdam maxsnaps=1 When you list the snapshot schedule, the ‘intervaltype’ is an integer, 0=HOURLY, 1=DAILY etc. list snapshotpolicies volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 count = 1 snapshotpolicy: +--+--+--+--+--+--+ | maxsnaps | intervaltype | schedule | volumeid | timezone | id | +--+--+--+--+--+--+ |1 | 1 | 23:1 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | Europe/Amsterdam | 9b736a09-4549-4638-a88d-f8ae9cc87c51 | +--+--+--+--+--+--+ Could this be made more consistent, maybe allow both formats in both calls? When you want to list a schedule, and use this data to create a new one this ‘translating’ is a bit weird. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6541) The UI allows snapshot schedules that the API does not accept
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma updated CLOUDSTACK-6541: - Component/s: UI The UI allows snapshot schedules that the API does not accept - Key: CLOUDSTACK-6541 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6541 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Remi Bergsma Priority: Minor Monthly snapshot schedules for volumes can only be done on day 1-28 of month. The UI allows to select 29,30,31 and when you save it, the following error is displayed: Invalid schedule: 00:1:31 for interval type: monthly Please remove days 29,30,31 from select box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6542) Interval type not consistent in create/list snapshot schedules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma updated CLOUDSTACK-6542: - Description: When you create a snapshot schedule, the ‘intervaltype’ has to be entered like ‘DAILY, HOURLY’ etc. create snapshotpolicy volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 schedule=23:1 intervaltype=DAILY timezone=Europe/Amsterdam maxsnaps=1 When you list the snapshot schedule, the ‘intervaltype’ is an integer, 0=HOURLY, 1=DAILY etc. list snapshotpolicies volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 count = 1 snapshotpolicy: | maxsnaps | intervaltype | schedule | volumeid | timezone | id | |1 | 1 | 23:1 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | Europe/Amsterdam | 9b736a09-4549-4638-a88d-f8ae9cc87c51 | Could this be made more consistent, maybe allow both formats in both calls? When you want to list a schedule, and use this data to create a new one this ‘translating’ is a bit weird. was: When you create a snapshot schedule, the ‘intervaltype’ has to be entered like ‘DAILY, HOURLY’ etc. create snapshotpolicy volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 schedule=23:1 intervaltype=DAILY timezone=Europe/Amsterdam maxsnaps=1 When you list the snapshot schedule, the ‘intervaltype’ is an integer, 0=HOURLY, 1=DAILY etc. list snapshotpolicies volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 count = 1 snapshotpolicy: +--+--+--+--+--+--+ | maxsnaps | intervaltype | schedule | volumeid | timezone | id | +--+--+--+--+--+--+ |1 | 1 | 23:1 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | Europe/Amsterdam | 9b736a09-4549-4638-a88d-f8ae9cc87c51 | +--+--+--+--+--+--+ Could this be made more consistent, maybe allow both formats in both calls? When you want to list a schedule, and use this data to create a new one this ‘translating’ is a bit weird. Interval type not consistent in create/list snapshot schedules -- Key: CLOUDSTACK-6542 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6542 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Remi Bergsma Priority: Minor When you create a snapshot schedule, the ‘intervaltype’ has to be entered like ‘DAILY, HOURLY’ etc. create snapshotpolicy volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 schedule=23:1 intervaltype=DAILY timezone=Europe/Amsterdam maxsnaps=1 When you list the snapshot schedule, the ‘intervaltype’ is an integer, 0=HOURLY, 1=DAILY etc. list snapshotpolicies volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23 count = 1 snapshotpolicy: | maxsnaps | intervaltype | schedule | volumeid | timezone | id | |1 | 1 | 23:1 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | Europe/Amsterdam | 9b736a09-4549-4638-a88d-f8ae9cc87c51 | Could this be made more consistent, maybe allow both formats in both calls? When you want to list a schedule, and use this data to create a new one this ‘translating’ is a bit weird. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6540) API: add listOrphanedSnapshots() call
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma updated CLOUDSTACK-6540: - Description: When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there. A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active. When I know the name of the volume, I can use a keyword search like this: list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202 count = 3 snapshot: |name| created | volumeid | | centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | | centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 | | centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 | But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots. was: When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there. A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active. When I know the name of the volume, I can use a keyword search like this: list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202 count = 3 snapshot: |name| created | volumeid | | centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | | centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 | | centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 | But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots. API: add listOrphanedSnapshots() call - Key: CLOUDSTACK-6540 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6540 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Remi Bergsma When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there. A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active. When I know the name of the volume, I can use a keyword search like this: list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202 count = 3 snapshot: |name| created | volumeid | | centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | | centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 | | centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 | But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6540) API: add listOrphanedSnapshots() call
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma updated CLOUDSTACK-6540: - Description: When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there. A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active. When I know the name of the volume, I can use a keyword search like this: list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202 count = 3 snapshot: |name| created | volumeid | | centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | | centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 | | centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 | But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots. was: When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there. A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active. When I know the name of the volume, I can use a keyword search like this: list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202 count = 3 snapshot: ++--+--+ |name| created | volumeid | ++--+--+ | centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | | centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 | | centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 | ++--+--+ But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots. API: add listOrphanedSnapshots() call - Key: CLOUDSTACK-6540 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6540 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Remi Bergsma When a volume is migrated to another primary storage, its snapshots disappear from the UI as they are linked to the now expunged volume. The snapshot itself is not marked as deleted in the database, so it stays there. A listall=true displays them all, but there is no way to tell if the snapshot is still linked to a volume that is still active. When I know the name of the volume, I can use a keyword search like this: list snapshots listall=true filter=name,created,volumeid keyword=ROOT-18202 count = 3 snapshot: |name| created | volumeid | | centos01_ROOT-18202_20140430110253 | 2014-04-30T13:02:53+0200 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 | | centos01_ROOT-18202_20140429101022 | 2014-04-29T12:10:22+0200 | 3788e908-eb75-4063-8116-ec9812d3fb95 | | centos01_ROOT-18202_20140429095746 | 2014-04-29T11:57:46+0200 | 166f7545-33e2-423a-b900-3f3cea64a868 | But there is no way to list all the orphaned ones. To garden those, please add an api call that lists all snapshots that are linked to expunged volumes. One can use its output to delete the snapshots. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6231) Cloudstack createNetworkACL cuts cidrlist at 256 characters
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985437#comment-13985437
]
ASF subversion and git services commented on CLOUDSTACK-6231:
-
Commit 2239eb4b173d1870af83174e646355be0e737c5c in cloudstack's branch
refs/heads/4.4 from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2239eb4 ]
CLOUDSTACK-6231: network acl item cidrs loaded from a seperate table
Cloudstack createNetworkACL cuts cidrlist at 256 characters
---
Key: CLOUDSTACK-6231
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6231
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.2.0, 4.3.0, 4.4.0
Reporter: Daan Hoogland
Assignee: Daan Hoogland
Fix For: 4.4.0
[2014-03-11T11:18:54+01:00] INFO: Creating acl on network SBP_VPC_MGT1_APP1:
10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.10/32,10.75.14.214/32,10.75.15.86/32,10.75.16.101/32,10.75.16.105/32,10.75.16.114/32,10.75.16.124/32,10.75.16.67/32,10.75.16.80/32,10.75.16.88/32,10.75.16.93/32,10.75.16.97/32,10.75.17.113/32,10.75.17.124/32,10.75.17.73/32,10.75.17.84/32,10.75.17.87/32,10.75.17.92/32,10.75.18.168/32,10.75.18.20/32,10.75.2.11/32,10.75.2.112/32,10.75.2.114/32,10.75.2.116/32,10.75.2.123/32,10.75.2.14/32,10.75.2.35/32,10.75.2.61/32,10.75.2.79/32,10.75.2.83/32,10.75.21.12/32,10.75.22.187/32,10.75.23.4/32,10.75.24.29/32,10.75.25.114/32,10.75.25.9/32,10.75.26.20/32,10.75.26.27/32,10.75.26.28/32,10.75.27.11/32,10.75.27.17/32,10.75.27.23/32,10.75.28.159/32,10.75.29.109/32,10.75.3.32/32,10.75.30.71/32,10.75.31.3/32,10.75.32.57/32,10.75.33.15/32,10.75.34.46/32,10.75.35.113/32,10.75.35.33/32,10.75.35.80/32,10.75.36.70/32,10.75.38.4/32,10.75.39.6/32,10.75.4.118/32,10.75.4.23/32,10.75.40.49/32,10.75.40.72/32,10.75.41.57/32,10.75.41.75/32,10.75.42.102/32,10.75.42.2/32,10.75.43.126/32,10.75.43.28/32,10.75.44.2/32,10.75.45.9/32,10.75.47.111/32,10.75.47.29/32,10.75.47.35/32,10.75.6.6/32,192.168.0.208/32,192.168.0.30/32
tcp 514/514 Ingress [2014-03-11T11:18:54+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:55+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:56+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:57+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:58+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:59+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:19:00+01:00] INFO: Job e71b6c83-a482-4765-9024-2ee9d146baa1
done, result: {networkacl={id=5f226473-8798-4336-a68d-b38a3f7a41a0,
protocol=tcp, startport=514, endport=514,
traffictype=Ingress, state=Active,
cidrlist=10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.1,
tags=[], aclid=482f3740-7eda-11e3-aa74-005056b95463, number=93,
action=Allow}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6231) Cloudstack createNetworkACL cuts cidrlist at 256 characters
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985438#comment-13985438
]
ASF subversion and git services commented on CLOUDSTACK-6231:
-
Commit 3852afa717dc147ef9dc19d7b3801c341f321e77 in cloudstack's branch
refs/heads/4.4-forward from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3852afa ]
CLOUDSTACK-6231: network acl item cidrs loaded from a seperate table
Cloudstack createNetworkACL cuts cidrlist at 256 characters
---
Key: CLOUDSTACK-6231
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6231
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.2.0, 4.3.0, 4.4.0
Reporter: Daan Hoogland
Assignee: Daan Hoogland
Fix For: 4.4.0
[2014-03-11T11:18:54+01:00] INFO: Creating acl on network SBP_VPC_MGT1_APP1:
10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.10/32,10.75.14.214/32,10.75.15.86/32,10.75.16.101/32,10.75.16.105/32,10.75.16.114/32,10.75.16.124/32,10.75.16.67/32,10.75.16.80/32,10.75.16.88/32,10.75.16.93/32,10.75.16.97/32,10.75.17.113/32,10.75.17.124/32,10.75.17.73/32,10.75.17.84/32,10.75.17.87/32,10.75.17.92/32,10.75.18.168/32,10.75.18.20/32,10.75.2.11/32,10.75.2.112/32,10.75.2.114/32,10.75.2.116/32,10.75.2.123/32,10.75.2.14/32,10.75.2.35/32,10.75.2.61/32,10.75.2.79/32,10.75.2.83/32,10.75.21.12/32,10.75.22.187/32,10.75.23.4/32,10.75.24.29/32,10.75.25.114/32,10.75.25.9/32,10.75.26.20/32,10.75.26.27/32,10.75.26.28/32,10.75.27.11/32,10.75.27.17/32,10.75.27.23/32,10.75.28.159/32,10.75.29.109/32,10.75.3.32/32,10.75.30.71/32,10.75.31.3/32,10.75.32.57/32,10.75.33.15/32,10.75.34.46/32,10.75.35.113/32,10.75.35.33/32,10.75.35.80/32,10.75.36.70/32,10.75.38.4/32,10.75.39.6/32,10.75.4.118/32,10.75.4.23/32,10.75.40.49/32,10.75.40.72/32,10.75.41.57/32,10.75.41.75/32,10.75.42.102/32,10.75.42.2/32,10.75.43.126/32,10.75.43.28/32,10.75.44.2/32,10.75.45.9/32,10.75.47.111/32,10.75.47.29/32,10.75.47.35/32,10.75.6.6/32,192.168.0.208/32,192.168.0.30/32
tcp 514/514 Ingress [2014-03-11T11:18:54+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:55+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:56+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:57+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:58+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:59+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:19:00+01:00] INFO: Job e71b6c83-a482-4765-9024-2ee9d146baa1
done, result: {networkacl={id=5f226473-8798-4336-a68d-b38a3f7a41a0,
protocol=tcp, startport=514, endport=514,
traffictype=Ingress, state=Active,
cidrlist=10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.1,
tags=[], aclid=482f3740-7eda-11e3-aa74-005056b95463, number=93,
action=Allow}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6231) Cloudstack createNetworkACL cuts cidrlist at 256 characters
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland closed CLOUDSTACK-6231.
-
Resolution: Fixed
Cloudstack createNetworkACL cuts cidrlist at 256 characters
---
Key: CLOUDSTACK-6231
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6231
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.2.0, 4.3.0, 4.4.0
Reporter: Daan Hoogland
Assignee: Daan Hoogland
Fix For: 4.4.0
[2014-03-11T11:18:54+01:00] INFO: Creating acl on network SBP_VPC_MGT1_APP1:
10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.10/32,10.75.14.214/32,10.75.15.86/32,10.75.16.101/32,10.75.16.105/32,10.75.16.114/32,10.75.16.124/32,10.75.16.67/32,10.75.16.80/32,10.75.16.88/32,10.75.16.93/32,10.75.16.97/32,10.75.17.113/32,10.75.17.124/32,10.75.17.73/32,10.75.17.84/32,10.75.17.87/32,10.75.17.92/32,10.75.18.168/32,10.75.18.20/32,10.75.2.11/32,10.75.2.112/32,10.75.2.114/32,10.75.2.116/32,10.75.2.123/32,10.75.2.14/32,10.75.2.35/32,10.75.2.61/32,10.75.2.79/32,10.75.2.83/32,10.75.21.12/32,10.75.22.187/32,10.75.23.4/32,10.75.24.29/32,10.75.25.114/32,10.75.25.9/32,10.75.26.20/32,10.75.26.27/32,10.75.26.28/32,10.75.27.11/32,10.75.27.17/32,10.75.27.23/32,10.75.28.159/32,10.75.29.109/32,10.75.3.32/32,10.75.30.71/32,10.75.31.3/32,10.75.32.57/32,10.75.33.15/32,10.75.34.46/32,10.75.35.113/32,10.75.35.33/32,10.75.35.80/32,10.75.36.70/32,10.75.38.4/32,10.75.39.6/32,10.75.4.118/32,10.75.4.23/32,10.75.40.49/32,10.75.40.72/32,10.75.41.57/32,10.75.41.75/32,10.75.42.102/32,10.75.42.2/32,10.75.43.126/32,10.75.43.28/32,10.75.44.2/32,10.75.45.9/32,10.75.47.111/32,10.75.47.29/32,10.75.47.35/32,10.75.6.6/32,192.168.0.208/32,192.168.0.30/32
tcp 514/514 Ingress [2014-03-11T11:18:54+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:55+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:56+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:57+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:58+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:59+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:19:00+01:00] INFO: Job e71b6c83-a482-4765-9024-2ee9d146baa1
done, result: {networkacl={id=5f226473-8798-4336-a68d-b38a3f7a41a0,
protocol=tcp, startport=514, endport=514,
traffictype=Ingress, state=Active,
cidrlist=10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.1,
tags=[], aclid=482f3740-7eda-11e3-aa74-005056b95463, number=93,
action=Allow}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6231) Cloudstack createNetworkACL cuts cidrlist at 256 characters
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985511#comment-13985511
]
ASF subversion and git services commented on CLOUDSTACK-6231:
-
Commit 6b0c34faeecad0e1c19181835130e7b91d2783ee in cloudstack's branch
refs/heads/master from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6b0c34f ]
CLOUDSTACK-6231: network acl item cidrs loaded from a seperate table
Conflicts:
setup/db/db/schema-430to440.sql
Cloudstack createNetworkACL cuts cidrlist at 256 characters
---
Key: CLOUDSTACK-6231
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6231
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.2.0, 4.3.0, 4.4.0
Reporter: Daan Hoogland
Assignee: Daan Hoogland
Fix For: 4.4.0
[2014-03-11T11:18:54+01:00] INFO: Creating acl on network SBP_VPC_MGT1_APP1:
10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.10/32,10.75.14.214/32,10.75.15.86/32,10.75.16.101/32,10.75.16.105/32,10.75.16.114/32,10.75.16.124/32,10.75.16.67/32,10.75.16.80/32,10.75.16.88/32,10.75.16.93/32,10.75.16.97/32,10.75.17.113/32,10.75.17.124/32,10.75.17.73/32,10.75.17.84/32,10.75.17.87/32,10.75.17.92/32,10.75.18.168/32,10.75.18.20/32,10.75.2.11/32,10.75.2.112/32,10.75.2.114/32,10.75.2.116/32,10.75.2.123/32,10.75.2.14/32,10.75.2.35/32,10.75.2.61/32,10.75.2.79/32,10.75.2.83/32,10.75.21.12/32,10.75.22.187/32,10.75.23.4/32,10.75.24.29/32,10.75.25.114/32,10.75.25.9/32,10.75.26.20/32,10.75.26.27/32,10.75.26.28/32,10.75.27.11/32,10.75.27.17/32,10.75.27.23/32,10.75.28.159/32,10.75.29.109/32,10.75.3.32/32,10.75.30.71/32,10.75.31.3/32,10.75.32.57/32,10.75.33.15/32,10.75.34.46/32,10.75.35.113/32,10.75.35.33/32,10.75.35.80/32,10.75.36.70/32,10.75.38.4/32,10.75.39.6/32,10.75.4.118/32,10.75.4.23/32,10.75.40.49/32,10.75.40.72/32,10.75.41.57/32,10.75.41.75/32,10.75.42.102/32,10.75.42.2/32,10.75.43.126/32,10.75.43.28/32,10.75.44.2/32,10.75.45.9/32,10.75.47.111/32,10.75.47.29/32,10.75.47.35/32,10.75.6.6/32,192.168.0.208/32,192.168.0.30/32
tcp 514/514 Ingress [2014-03-11T11:18:54+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:55+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:56+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:57+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:18:58+01:00] INFO: Status of job
e71b6c83-a482-4765-9024-2ee9d146baa1 is 0 [2014-03-11T11:18:59+01:00] INFO:
Status of job e71b6c83-a482-4765-9024-2ee9d146baa1 is 0
[2014-03-11T11:19:00+01:00] INFO: Job e71b6c83-a482-4765-9024-2ee9d146baa1
done, result: {networkacl={id=5f226473-8798-4336-a68d-b38a3f7a41a0,
protocol=tcp, startport=514, endport=514,
traffictype=Ingress, state=Active,
cidrlist=10.168.1.198/32,10.168.1.251/32,10.168.2.178/32,10.168.2.245/32,10.168.4.27/32,10.168.4.44/32,10.71.76.27/32,10.71.76.28/32,10.75.12.108/32,10.75.12.11/32,10.75.12.35/32,10.75.12.75/32,10.75.12.98/32,10.75.13.30/32,10.75.13.71/32,10.75.13.94/32,10.75.14.1,
tags=[], aclid=482f3740-7eda-11e3-aa74-005056b95463, number=93,
action=Allow}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5806) Storage types other than NFS/VMFS can't overprovision
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985596#comment-13985596
]
Saksham Srivastava commented on CLOUDSTACK-5806:
Marcus, Just a quick reminder in case you lost track of this.
Was looking at your snippet and wondering why do we need a comparator after all.
We only need boolean method that returns if we support over-provisioning or not.
May be something that I am missing here.
Storage types other than NFS/VMFS can't overprovision
-
Key: CLOUDSTACK-5806
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5806
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0, Future, 4.3.0
Reporter: Marcus Sorensen
Priority: Critical
Fix For: 4.4.0
Edison, Mike, or myself can probably fix this. Mgmt server hardcodes storage
types that can overprovision. Need to fix this.
Edison suggests:
We can move it to storage driver's capabilities method.
Each storage driver can report its capabilities in DataStoreDriver-
getCapabilities(), which returns a map[String, String], we can change the
signature to map[String, Object]
In CloudStackPrimaryDataStoreDriverImpl(the default storage driver)-
getCapabilities, which can return something like:
Var comparator = new storageOverProvision() {
Public Boolean isOverProvisionSupported(DataStore store) {
Var storagepool = (PrimaryDataStoreInfo)store;
If (store.getPoolType() == NFS or VMFS) {
Return true;
}
};
};
Var caps = new HashMap[String, Object]();
Caps.put(storageOverProvision, comparator);
Return caps;
}
Whenever, other places in mgt server want to check the capabilities of
overprovision, we can do the following:
Var primaryStore = DataStoreManager. getPrimaryDataStore(primaryStoreId);
var caps = primaryStore. getDriver().getCapabilities();
var overprovision = caps.get(storageOverProvision);
var result = overprovision. isOverProvisionSupported(primaryStore);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Ganesh updated CLOUDSTACK-6444:
---
Assignee: Anthony Xu
[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: Anthony Xu
Priority: Blocker
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
requests.packages.urllib3.connectionpool: DEBUG: GET
[jira] [Updated] (CLOUDSTACK-5342) [Automation] Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Ganesh updated CLOUDSTACK-5342:
---
Assignee: Saksham Srivastava
[Automation] Add NIC to virtual machine fails in KVM
Key: CLOUDSTACK-5342
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.3.0
Environment: KVM advanced
Reporter: Gaurav Aradhye
Assignee: Saksham Srivastava
Fix For: 4.4.0
Add network to VM test cases fail in KVM with following error.
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
The same test cases execute successfully on XenServer. As per the feature
specification (see
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
Add network to VM feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5806) Storage types other than NFS/VMFS can't overprovision
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985706#comment-13985706
]
Marcus Sorensen commented on CLOUDSTACK-5806:
-
No idea. Edison sent that out and I pasted it into jira to save it.
Storage types other than NFS/VMFS can't overprovision
-
Key: CLOUDSTACK-5806
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5806
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0, Future, 4.3.0
Reporter: Marcus Sorensen
Priority: Critical
Fix For: 4.4.0
Edison, Mike, or myself can probably fix this. Mgmt server hardcodes storage
types that can overprovision. Need to fix this.
Edison suggests:
We can move it to storage driver's capabilities method.
Each storage driver can report its capabilities in DataStoreDriver-
getCapabilities(), which returns a map[String, String], we can change the
signature to map[String, Object]
In CloudStackPrimaryDataStoreDriverImpl(the default storage driver)-
getCapabilities, which can return something like:
Var comparator = new storageOverProvision() {
Public Boolean isOverProvisionSupported(DataStore store) {
Var storagepool = (PrimaryDataStoreInfo)store;
If (store.getPoolType() == NFS or VMFS) {
Return true;
}
};
};
Var caps = new HashMap[String, Object]();
Caps.put(storageOverProvision, comparator);
Return caps;
}
Whenever, other places in mgt server want to check the capabilities of
overprovision, we can do the following:
Var primaryStore = DataStoreManager. getPrimaryDataStore(primaryStoreId);
var caps = primaryStore. getDriver().getCapabilities();
var overprovision = caps.get(storageOverProvision);
var result = overprovision. isOverProvisionSupported(primaryStore);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6513) IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985749#comment-13985749 ] ASF subversion and git services commented on CLOUDSTACK-6513: - Commit 412793f9b41bb03eda2b8474f9f22a12b5097327 in cloudstack's branch refs/heads/4.4-forward from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=412793f ] CLOUDSTACK-6513: remove commented code. IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list. --- Key: CLOUDSTACK-6513 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6513 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Environment: Build from 4.4 Reporter: Sangeetha Hariharan Assignee: Min Chen Priority: Critical Fix For: 4.4.0 IAM - Templates - When templates are listed with templatefilter=shared is used , we see public templates also being included in the list. Steps to reproduce the problem: As user1 , Create a private template and a public template. Grant access to the private template for user2 using updateTemplatePermissions. As user2 , list templates with templatefilter=shared. This returns both public and the the shared template. GET http://10.223.49.6/client/api?command=listTemplatespagesize=100page=1listAll=truetemplatefilter=sharedapiKey=SrgUY-U-nUl4qsOyn409kCjA2jC7dR5ReIV9SjdnmzLOn3c0Fm-vZbDSpkldUjuqLAXt5ShodtXYOgRB5NCnJQsignature=WBO8ll9nyjiB29aVq%2FpUsEQrthM%3D \n\n ?xml version=1.0 encoding=UTF-8?listtemplatesresponse cloud-stack-version=4.4.0-SNAPSHOTcount6/counttemplateida2065bcc-7139-46b0-ac15-db7d3ff7dd75/idnamePublic_featured_d1a-TP7TPK/namedisplaytextpublic and feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:35-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD1A/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD1/domaindomainid691ab662-6793-42a0-96e6-3b31a2c4e52d/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateidce1635dc-1fcb-4f60-8d2f-d1129a3771ce/idnamePublic_not_featured_d2a-NPYFSN/namedisplaytextpublic and not feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:36-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedfalse/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD2/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD2/domaindomainid18222e53-7221-4d6f-9a76-8f59869f24b2/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateid223e0c09-e18e-4188-9d8e-7ff2e2305547/idnamePrivate_featured_d1-E9PQHO/namedisplaytextprivate and featured Template/displaytextispublicfalse/ispubliccreated2014-04-21T13:50:36-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3 (64-bit)/ostypenameaccounttesttemplateD1A/accountzoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenamesize5242880/sizetemplatetypeUSER/templatetypehypervisorSimulator/hypervisordomainD1/domaindomainid691ab662-6793-42a0-96e6-3b31a2c4e52d/domainidisextractabletrue/isextractablesshkeyenabledfalse/sshkeyenabledisdynamicallyscalablefalse/isdynamicallyscalable/templatetemplateida7b69a5e-4cb3-45fa-b3e7-dab3a6b73e45/idnamePublic_not_featured_d1a-XOCR05/namedisplaytextpublic and not feature Template/displaytextispublictrue/ispubliccreated2014-04-21T13:50:35-0400/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedfalse/isfeaturedcrossZonesfalse/crossZonesostypeide5ebce64-c019-11e3-907f-4adf980f9414/ostypeidostypenameCentOS 5.3
[jira] [Created] (CLOUDSTACK-6544) [Automation] Failed to create template for ROOT volume in Xen, with Exception: callHostPlugin failed
Rayees Namathponnan created CLOUDSTACK-6544:
---
Summary: [Automation] Failed to create template for ROOT volume in
Xen, with Exception: callHostPlugin failed
Key: CLOUDSTACK-6544
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6544
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Template, XenServer
Affects Versions: 4.4.0
Environment: Build : 4.4-forward
env xen 6.2
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Steps to reproduce
Step 1 : Create advance zone in Xen
Step 2 : Deploy a VM
Step 3 : stop the vm and create template for ROOT volume
Result
Failed to create template for root volume, its failed with below error
2014-05-01 03:52:32,706 DEBUG [c.c.a.ApiServlet] (catalina-exec-10:ctx-23ef4b60
ctx-89d28d07) ===END=== 10.214.5.49 -- GET command
=queryAsyncJobResultjobId=e846719b-4902-46eb-b1ea-78c2c25d7c28response=jsonsessionkey=TZlQVYacZ8o7NBLks3fWljCNZLY%3D_=1398877226
273
2014-05-01 03:52:32,764 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-40:ctx-18182a40) callHostPlugin failed for cmd: create_sec
ondary_storage_folder with args remoteMountPath:
10.147.28.8:/vol/dgVol/automation/adv/secondary, newFolder:
template/tmpl/26/208, due to The requested plugin could not be found.
2014-05-01 03:52:32,776 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-40:ctx-18182a40) callHostPlugin failed for cmd: delete_sec
ondary_storage_folder with args folder: template/tmpl/26/208, remoteMountPath:
10.147.28.8:/vol/dgVol/automation/adv/secondary, due to The requested
plugin could not be found.
2014-05-01 03:52:32,776 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-40:ctx-18182a40) Seq 2-5867345889533626157: Exception Caught
while executing command
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd:
delete_secondary_storage_folder with args folder: te
mplate/tmpl/26/208, remoteMountPath:
10.147.28.8:/vol/dgVol/automation/adv/secondary, due to The requested plugin
could not be foun d.
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3835)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.deleteSecondaryStorageFolder(CitrixResourceBase.java:6949)
at
com.cloud.hypervisor.xen.resource.Xenserver625StorageProcessor.createTemplateFromVolume(Xenserver625StorageProcessor.java
:591)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:90)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.ja
va:52)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93)
at
com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:64)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2014-05-01 03:52:32,779 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-260:ctx-fa38312f) Seq 1-9035628227388770115: Response Receiv
ed:
2014-05-01 03:52:32,780 DEBUG [c.c.a.t.Request] (StatsCollector-1:ctx-6ae84e34)
Seq 1-9035628227388770115: Received: { Ans: , MgmtI d: 6631563722783,
via: 1, Ver:
[jira] [Updated] (CLOUDSTACK-6544) [Automation] Failed to create template for ROOT volume in Xen, with Exception: callHostPlugin failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6544: Attachment: management-server.rar [Automation] Failed to create template for ROOT volume in Xen, with Exception: callHostPlugin failed Key: CLOUDSTACK-6544 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6544 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, XenServer Affects Versions: 4.4.0 Environment: Build : 4.4-forward env xen 6.2 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Attachments: management-server.rar Steps to reproduce Step 1 : Create advance zone in Xen Step 2 : Deploy a VM Step 3 : stop the vm and create template for ROOT volume Result Failed to create template for root volume, its failed with below error 2014-05-01 03:52:32,706 DEBUG [c.c.a.ApiServlet] (catalina-exec-10:ctx-23ef4b60 ctx-89d28d07) ===END=== 10.214.5.49 -- GET command =queryAsyncJobResultjobId=e846719b-4902-46eb-b1ea-78c2c25d7c28response=jsonsessionkey=TZlQVYacZ8o7NBLks3fWljCNZLY%3D_=1398877226 273 2014-05-01 03:52:32,764 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-40:ctx-18182a40) callHostPlugin failed for cmd: create_sec ondary_storage_folder with args remoteMountPath: 10.147.28.8:/vol/dgVol/automation/adv/secondary, newFolder: template/tmpl/26/208, due to The requested plugin could not be found. 2014-05-01 03:52:32,776 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-40:ctx-18182a40) callHostPlugin failed for cmd: delete_sec ondary_storage_folder with args folder: template/tmpl/26/208, remoteMountPath: 10.147.28.8:/vol/dgVol/automation/adv/secondary, due to The requested plugin could not be found. 2014-05-01 03:52:32,776 WARN [c.c.a.m.DirectAgentAttache] (DirectAgent-40:ctx-18182a40) Seq 2-5867345889533626157: Exception Caught while executing command com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd: delete_secondary_storage_folder with args folder: te mplate/tmpl/26/208, remoteMountPath: 10.147.28.8:/vol/dgVol/automation/adv/secondary, due to The requested plugin could not be foun d. at com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3835) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.deleteSecondaryStorageFolder(CitrixResourceBase.java:6949) at com.cloud.hypervisor.xen.resource.Xenserver625StorageProcessor.createTemplateFromVolume(Xenserver625StorageProcessor.java :591) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:90) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.ja va:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93) at com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:64) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[jira] [Commented] (CLOUDSTACK-6443) [Automation] Two Test Cases failed on test_volumes.py - AttributeError: VirtualMachine instance has no attribute 'hostid'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985758#comment-13985758
]
Prachi Damle commented on CLOUDSTACK-6443:
--
Part of the error seems due to 'hostId' not set in response.
However following error is not related to IAM:
errortext:Can only resize Data volumes via new disk offering
[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: Prachi Damle
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
[jira] [Commented] (CLOUDSTACK-6295) Management server cannot start because Java 7 missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985761#comment-13985761 ] Paul Angus commented on CLOUDSTACK-6295: Yes it is the same issue as reported in CLOUDSTACK-6351. Management server cannot start because Java 7 missing - Key: CLOUDSTACK-6295 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6295 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.4.0 Environment: centos 6.5 Reporter: Paul Angus Priority: Blocker Management server cannot start because java 7 is not installed. Java 7 package dependency needs to be added into installation. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6333) [Automation] NPE observed while deleting account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985762#comment-13985762 ] Prachi Damle commented on CLOUDSTACK-6333: -- This does not look related to IAM feature. Unassigning myself from it. [Automation] NPE observed while deleting account Key: CLOUDSTACK-6333 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6333 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: KVM Reporter: Rayees Namathponnan Assignee: Prachi Damle Priority: Critical Fix For: 4.4.0 Attachments: management-server.rar This issue observed in automation run, there are many account clean up failures with NPE Also In Log observed VM state transitted from :Expunging to Expunging, why we are changing state Expunging to Expunging 2014-04-02 17:19:45,664 DEBUG [c.c.v.VirtualMachineManagerImpl] (AccountChecker-1:ctx-633521d3) Cleaning up NICS 2014-04-02 17:19:45,664 DEBUG [o.a.c.e.o.NetworkOrchestrator] (AccountChecker-1:ctx-633521d3) Cleaning network for vm: 455 2014-04-02 17:19:45,665 DEBUG [c.c.v.VirtualMachineManagerImpl] (AccountChecker-1:ctx-633521d3) Cleaning up hypervisor data s tructures (ex. SRs in XenServer) for managed storage 2014-04-02 17:19:45,669 WARN [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-633521d3) Failed to cleanup account Acct[10b43 b95-f6e0-445f-acff-9c5cc450f59b-test-TestBaseImageUpdate-6JJ7ST] due to java.lang.NullPointerException at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.disconnectVolumesFromHost(VolumeOrchestrator.java:867) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:527) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:463) at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1654) at sun.reflect.GeneratedMethodAccessor555.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy205.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:651) at com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1575) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6333) [Automation] NPE observed while deleting account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle reassigned CLOUDSTACK-6333: Assignee: (was: Prachi Damle) [Automation] NPE observed while deleting account Key: CLOUDSTACK-6333 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6333 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: KVM Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.4.0 Attachments: management-server.rar This issue observed in automation run, there are many account clean up failures with NPE Also In Log observed VM state transitted from :Expunging to Expunging, why we are changing state Expunging to Expunging 2014-04-02 17:19:45,664 DEBUG [c.c.v.VirtualMachineManagerImpl] (AccountChecker-1:ctx-633521d3) Cleaning up NICS 2014-04-02 17:19:45,664 DEBUG [o.a.c.e.o.NetworkOrchestrator] (AccountChecker-1:ctx-633521d3) Cleaning network for vm: 455 2014-04-02 17:19:45,665 DEBUG [c.c.v.VirtualMachineManagerImpl] (AccountChecker-1:ctx-633521d3) Cleaning up hypervisor data s tructures (ex. SRs in XenServer) for managed storage 2014-04-02 17:19:45,669 WARN [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-633521d3) Failed to cleanup account Acct[10b43 b95-f6e0-445f-acff-9c5cc450f59b-test-TestBaseImageUpdate-6JJ7ST] due to java.lang.NullPointerException at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.disconnectVolumesFromHost(VolumeOrchestrator.java:867) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:527) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:463) at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1654) at sun.reflect.GeneratedMethodAccessor555.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy205.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:651) at com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1575) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6443) [Automation] Two Test Cases failed on test_volumes.py - AttributeError: VirtualMachine instance has no attribute 'hostid'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle reassigned CLOUDSTACK-6443:
Assignee: Min Chen (was: Prachi Damle)
[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] [Commented] (CLOUDSTACK-6502) IAMGroup.list and IAMPolicy.list in marvin base.py are not working.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985775#comment-13985775 ] ASF subversion and git services commented on CLOUDSTACK-6502: - Commit 42b803dd4b6e01107cbcf08d87f17c47934e8ae7 in cloudstack's branch refs/heads/4.4-forward from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=42b803d ] CLOUDSTACK-6502:Remove trailing whitespaces. IAMGroup.list and IAMPolicy.list in marvin base.py are not working. --- Key: CLOUDSTACK-6502 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6502 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Min Chen Assignee: Min Chen Priority: Critical Fix For: 4.4.0 IAMGroup.list and IAMPolicy.list in marvin base.py library have typo bugs, which blocks folks from writing IAM group and policy list related automation test. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6545) IAM - Fix IAM to not do ordering of AccessTypes
Prachi Damle created CLOUDSTACK-6545: Summary: IAM - Fix IAM to not do ordering of AccessTypes Key: CLOUDSTACK-6545 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6545 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0 This is a subtask of CLOUDSTACK-6517 Logged so that we track the change. The issue will be fixed as a whole and so commits for CLOUDSTACK-6517 will solve this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6546) CS should allow all operations for RootAdmin and DomainAdmin(within domain)
Prachi Damle created CLOUDSTACK-6546: Summary: CS should allow all operations for RootAdmin and DomainAdmin(within domain) Key: CLOUDSTACK-6546 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6546 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: IAM, Management Server Affects Versions: 4.4.0 Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0 This is a subtask of CLOUDSTACK-6517 Logged so that we track the change. The issue will be fixed as a whole and so commits for CLOUDSTACK-6517 will solve this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6517) IAM - Admin is allowed to create PortFowarding rule for a regular user, when admin does not have UseEntry permission for IpAddress.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985818#comment-13985818 ] Prachi Damle commented on CLOUDSTACK-6517: -- Analysis Subtask- CLOUDSTACK-6545 - IAM was applying ordering on accessTypes. Thus if an account had OperateEntry access, he got USEEntry access as well. - So even if IAM schema did not have 'UseEntry permission for IpAddress, some other 'OperateEntry' permission on IpAddress was letting this operation go through. - Upon analysis, this should not be done at the IAM level. Reason being, due to AccessType ordering, admin policy gets permission to USE resources from other account just because he has OPERATE access on those resources due to some other APIs. - So we should fix IAM to NOT do ordering of access types anymore. IAM will perform strict accessType check only. - Subtask is logged for this fix Subtask- CLOUDSTACK-6546 - Now due to this fix, we break backwards compatibilty with CS 4.3. - CS 4.3 allowed root admin to do the createPF operation for a user by passing in networkId of the user. - Same was the case for domain admins within their domains - Why this worked in CS 4.3 because in CS 4.3 no IAM checks happen for admins. It simply returns true for root admin/domain admin(within his domain) - So to maintain backwards compatibilty, we need to add the logic to return true for root admin and domain admin just like CS 4.3 in CS 4.4 - This logic will be part of CloudStack core and not IAM. Per IAM these operation will not be allowed. But CS needs this logic to override that decision inorder to maintain backwards compatibility. - Exception is: For Network, AffinityGroup and Templates, we still will respect IAM even for root admin/domain admin, since CS 4.3 did access checks for these resource_types. - So just for these 3 resource_types, it used to perform access checks even for root admin/domain admin and Cs 4.4 IAM will do that. - True way to let IAM handle this is to refactor CloudStack code to handle Impersonation at every API consistently. IAM - Admin is allowed to create PortFowarding rule for a regular user, when admin does not have UseEntry permission for IpAddress. --- Key: CLOUDSTACK-6517 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6517 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Environment: Build from 4.4 Reporter: Sangeetha Hariharan Assignee: Prachi Damle Fix For: 4.4.0 IAM - Admin is allowed to create PortFowarding rule for a regular user, when admin does not have UseEntry permission for IpAddress. Steps to reproduce the problem: As regular user , on a network he owns , acquire an ip address. As admin , try to create a PF rule on this ip address without passing account and domainId. Creating PF rule succeeds. Since Admin has only ListEntry permission for IpAddress owned by other users , we expect this api call to fail. mysql select * from iam_policy_permission where resource_type = 'IpAddress' and policy_id=2; +--+---+---+---+--+-+--++---+-+-+ | id | policy_id | action| resource_type | scope_id | scope | access_type | permission | recursive | removed | created | +--+---+---+---+--+-+--++---+-+-+ | 1840 | 2 | listPublicIpAddresses | IpAddress | -1 | ALL | ListEntry| Allow | 0 | NULL| 2014-04-22 18:31:03 | | 1841 | 2 | listPublicIpAddresses | IpAddress | -1 | ACCOUNT | UseEntry | Allow | 0 | NULL| 2014-04-22 18:31:03 | Admin should be allowed to do this only , when he passes account and domainId of the regular user is passed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6547) [Automation] Failed to download volume in Xen with error Failed to copy the volume from pri stor pool to sec stor pool
Rayees Namathponnan created CLOUDSTACK-6547:
---
Summary: [Automation] Failed to download volume in Xen with error
Failed to copy the volume from pri stor pool to sec stor pool
Key: CLOUDSTACK-6547
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6547
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes, XenServer
Affects Versions: 4.4.0
Environment: Branch 4.4-forward
env xen 6.2
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Steps to reproduce
1) Create advanced zone in xen
2) Deploy a VM
3) Stoped the vm and download the root volume
Result
Failed to download root volume with below error
2014-05-01 04:40:03,160 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(API-Job-Executor-38:job-490 ctx-4880d846) Unsupported data object (VO
LUME, org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@2f9161ed),
no need to delete from object in store ref table
2014-05-01 04:40:03,162 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-5:job-488/job-489 ctx-46360720) Execute VM work job:
com.cloud
.vm.VmWorkStart{dcId:1,podId:1,clusterId:1,hostId:1,rawParams:{VmPassword:rO0ABXQADnNhdmVkX3Bhc3N3b3Jk},userId:2,accountId:2,vmId:70,handlerName:VirtualMachineManagerImpl}
2014-05-01 04:40:03,189 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-38:job-490) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume from
the source primary storage pool to secondary storage.
at
com.cloud.storage.VolumeApiServiceImpl.extractVolume(VolumeApiServiceImpl.java:1897)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy181.extractVolume(Unknown Source)
at
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:137)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:119)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:495)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:452)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2014-05-01 04:40:03,194 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-38:job-490) Complete async job-490, jobStatus: FAILED,
resultCode: 530, result:
[jira] [Updated] (CLOUDSTACK-6547) [Automation] Failed to download volume in Xen with error Failed to copy the volume from pri stor pool to sec stor pool
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6547:
Attachment: management-server.rar
[Automation] Failed to download volume in Xen with error Failed to copy the
volume from pri stor pool to sec stor pool
Key: CLOUDSTACK-6547
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6547
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes, XenServer
Affects Versions: 4.4.0
Environment: Branch 4.4-forward
env xen 6.2
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.rar
Steps to reproduce
1) Create advanced zone in xen
2) Deploy a VM
3) Stoped the vm and download the root volume
Result
Failed to download root volume with below error
2014-05-01 04:40:03,160 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(API-Job-Executor-38:job-490 ctx-4880d846) Unsupported data object (VO
LUME, org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@2f9161ed),
no need to delete from object in store ref table
2014-05-01 04:40:03,162 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-5:job-488/job-489 ctx-46360720) Execute VM work job:
com.cloud
.vm.VmWorkStart{dcId:1,podId:1,clusterId:1,hostId:1,rawParams:{VmPassword:rO0ABXQADnNhdmVkX3Bhc3N3b3Jk},userId:2,accountId:2,vmId:70,handlerName:VirtualMachineManagerImpl}
2014-05-01 04:40:03,189 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-38:job-490) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume
from the source primary storage pool to secondary storage.
at
com.cloud.storage.VolumeApiServiceImpl.extractVolume(VolumeApiServiceImpl.java:1897)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy181.extractVolume(Unknown Source)
at
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:137)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:119)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:495)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:452)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at
[jira] [Created] (CLOUDSTACK-6549) 4.4-forward: Management Server fails to start
Prachi Damle created CLOUDSTACK-6549: Summary: 4.4-forward: Management Server fails to start Key: CLOUDSTACK-6549 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6549 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: Prachi Damle Priority: Blocker Fix For: 4.4.0 4.4-forward: Management Server fails to start Commit 3852afa717dc147ef9dc19d7b3801c341f321e77 that broke it. NetworkACLItemCidrsDao out of NetworkACLItemDao, but you forgot to add that into spring context xml file. You may need to add that into cloud-engine/schema/resources/META-INF/cloudstack/core/spring-engine-schema-core-daos-context.xml. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6548) [Automation] createPrivateNetwork API failed with NullPointer exception
Rayees Namathponnan created CLOUDSTACK-6548: --- Summary: [Automation] createPrivateNetwork API failed with NullPointer exception Key: CLOUDSTACK-6548 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6548 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Environment: Xen 6.2 build 4.4-forward Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 This issue observed with BVT, test cases integration.smoke.test_privategw_acl.TestPrivateGwACL.test_privategw_acl failed with BVT, observed below NPE in ms log 2014-04-30 21:38:37,417 DEBUG [c.c.n.NetworkServiceImpl] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) Created private network Nt wk[cf4d60e1-9d4a-46de-85bc-910a6ea44024|Guest|5] 2014-04-30 21:38:37,433 DEBUG [c.c.u.d.T.Transaction] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) Rolling back the transaction: Time = 209 Name = catalina-exec-17; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670- Transaction.execute:41-NetworkServiceImpl.createPrivateNetwork:3964-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:-1-De legatingMethodAccessorImpl.invoke:-1-Method.invoke:-1-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint: 183-ReflectiveMethodInvocation.proceed:150 2014-04-30 21:38:37,452 ERROR [c.c.a.ApiServer] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) unhandled exception executing api c ommand: [Ljava.lang.String;@1925edc3 java.lang.NullPointerException at com.cloud.network.NetworkServiceImpl$11.doInTransaction(NetworkServiceImpl.java:3987) at com.cloud.network.NetworkServiceImpl$11.doInTransaction(NetworkServiceImpl.java:3964) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.NetworkServiceImpl.createPrivateNetwork(NetworkServiceImpl.java:3964) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy154.createPrivateNetwork(Unknown Source) at com.cloud.network.vpc.VpcManagerImpl$6.doInTransaction(VpcManagerImpl.java:1594) at com.cloud.network.vpc.VpcManagerImpl$6.doInTransaction(VpcManagerImpl.java:1578) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.vpc.VpcManagerImpl.createVpcPrivateGateway(VpcManagerImpl.java:1578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
[jira] [Updated] (CLOUDSTACK-6548) [Automation] createPrivateNetwork API failed with NullPointer exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6548: Attachment: management-server.log.2014-04-30.gz [Automation] createPrivateNetwork API failed with NullPointer exception Key: CLOUDSTACK-6548 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6548 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Environment: Xen 6.2 build 4.4-forward Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Attachments: management-server.log.2014-04-30.gz This issue observed with BVT, test cases integration.smoke.test_privategw_acl.TestPrivateGwACL.test_privategw_acl failed with BVT, observed below NPE in ms log 2014-04-30 21:38:37,417 DEBUG [c.c.n.NetworkServiceImpl] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) Created private network Nt wk[cf4d60e1-9d4a-46de-85bc-910a6ea44024|Guest|5] 2014-04-30 21:38:37,433 DEBUG [c.c.u.d.T.Transaction] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) Rolling back the transaction: Time = 209 Name = catalina-exec-17; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670- Transaction.execute:41-NetworkServiceImpl.createPrivateNetwork:3964-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:-1-De legatingMethodAccessorImpl.invoke:-1-Method.invoke:-1-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint: 183-ReflectiveMethodInvocation.proceed:150 2014-04-30 21:38:37,452 ERROR [c.c.a.ApiServer] (catalina-exec-17:ctx-d1365378 ctx-664fada1 ctx-e0adfbee) unhandled exception executing api c ommand: [Ljava.lang.String;@1925edc3 java.lang.NullPointerException at com.cloud.network.NetworkServiceImpl$11.doInTransaction(NetworkServiceImpl.java:3987) at com.cloud.network.NetworkServiceImpl$11.doInTransaction(NetworkServiceImpl.java:3964) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.NetworkServiceImpl.createPrivateNetwork(NetworkServiceImpl.java:3964) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy154.createPrivateNetwork(Unknown Source) at com.cloud.network.vpc.VpcManagerImpl$6.doInTransaction(VpcManagerImpl.java:1594) at com.cloud.network.vpc.VpcManagerImpl$6.doInTransaction(VpcManagerImpl.java:1578) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.network.vpc.VpcManagerImpl.createVpcPrivateGateway(VpcManagerImpl.java:1578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at
[jira] [Created] (CLOUDSTACK-6550) [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this
Rayees Namathponnan created CLOUDSTACK-6550: --- Summary: [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this Key: CLOUDSTACK-6550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, Virtual Router Affects Versions: 4.4.0 Environment: Xen 6.2 build : 4.4-forward Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Currently test cases are using below command to listrouter (without listall=true), http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6550) [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6550: Description: Currently test cases are using below command to listrouter (without listall=true), passing accountID and domain ID http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, was: Currently test cases are using below command to listrouter (without listall=true), http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this - Key: CLOUDSTACK-6550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Virtual Router Affects Versions: 4.4.0 Environment: Xen 6.2 build : 4.4-forward Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Currently test cases are using below command to listrouter (without listall=true), passing accountID and domain ID http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6517) IAM - Admin is allowed to create PortFowarding rule for a regular user, when admin does not have UseEntry permission for IpAddress.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle resolved CLOUDSTACK-6517. -- Resolution: Fixed Fixed in 4.4-forward branch IAM - Admin is allowed to create PortFowarding rule for a regular user, when admin does not have UseEntry permission for IpAddress. --- Key: CLOUDSTACK-6517 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6517 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Environment: Build from 4.4 Reporter: Sangeetha Hariharan Assignee: Prachi Damle Fix For: 4.4.0 IAM - Admin is allowed to create PortFowarding rule for a regular user, when admin does not have UseEntry permission for IpAddress. Steps to reproduce the problem: As regular user , on a network he owns , acquire an ip address. As admin , try to create a PF rule on this ip address without passing account and domainId. Creating PF rule succeeds. Since Admin has only ListEntry permission for IpAddress owned by other users , we expect this api call to fail. mysql select * from iam_policy_permission where resource_type = 'IpAddress' and policy_id=2; +--+---+---+---+--+-+--++---+-+-+ | id | policy_id | action| resource_type | scope_id | scope | access_type | permission | recursive | removed | created | +--+---+---+---+--+-+--++---+-+-+ | 1840 | 2 | listPublicIpAddresses | IpAddress | -1 | ALL | ListEntry| Allow | 0 | NULL| 2014-04-22 18:31:03 | | 1841 | 2 | listPublicIpAddresses | IpAddress | -1 | ACCOUNT | UseEntry | Allow | 0 | NULL| 2014-04-22 18:31:03 | Admin should be allowed to do this only , when he passes account and domainId of the regular user is passed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6546) CS should allow all operations for RootAdmin and DomainAdmin(within domain)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle resolved CLOUDSTACK-6546. -- Resolution: Fixed CS should allow all operations for RootAdmin and DomainAdmin(within domain) --- Key: CLOUDSTACK-6546 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6546 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: IAM, Management Server Affects Versions: 4.4.0 Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0 This is a subtask of CLOUDSTACK-6517 Logged so that we track the change. The issue will be fixed as a whole and so commits for CLOUDSTACK-6517 will solve this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6545) IAM - Fix IAM to not do ordering of AccessTypes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle resolved CLOUDSTACK-6545. -- Resolution: Fixed IAM - Fix IAM to not do ordering of AccessTypes --- Key: CLOUDSTACK-6545 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6545 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: IAM Affects Versions: 4.4.0 Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0 This is a subtask of CLOUDSTACK-6517 Logged so that we track the change. The issue will be fixed as a whole and so commits for CLOUDSTACK-6517 will solve this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6332) [Automation] Failed to create PFrule with permission error does not have permission to perform this operation on these resources on objs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-6332.
--
Resolution: Fixed
This test is passing now after recet IAM fixes.
So this bug is not present anymore, hence resolving it.
[Automation] Failed to create PFrule with permission error does not have
permission to perform this operation on these resources on objs
--
Key: CLOUDSTACK-6332
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6332
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: Prachi Damle
Priority: Blocker
Fix For: 4.4.0
Attachments: CLOUDSTACK-6329.rar
Test case
integration.component.test_accounts.TestDomainForceRemove.test_forceDeleteDomain
failing with latest build
This test case performing below operations
1540 # Steps for validations
1541 # 1. create a domain DOM
1542 # 2. create 2 users under this domain
1543 # 3. deploy 1 VM into each of these user accounts
1544 # 4. create PF / FW rules for port 22 on these VMs for their
1545 #respective accounts
1546 # 5. delete the domain with force=true option
1547 # Validate the following
1548 # 1. listDomains should list the created domain
1549 # 2. listAccounts should list the created accounts
1550 # 3. listvirtualmachines should show the Running VMs
1551 # 4. PF and FW rules should be shown in listFirewallRules
1552 # 5. domain should delete successfully and above three list calls
1553 #should show all the resources now deleted. listRouters
should
1554 #not return any routers in the deleted accounts/domains
This test case failing while creating PF rule
2014-04-02 17:20:28,092 DEBUG [c.c.a.ApiServlet]
(catalina-exec-6:ctx-fef1201e ctx-1aba7046 ctx-c95b5405) ===END=== 10.223.2
40.194 -- GET
account=test-TestUserLogin-test_forceDeleteDomain-KV543Jdomainid=1503a119-b8b8-4ce8-851c-9af1da80dc59issourc
enat=TrueapiKey=t3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgassociatednetworkid=6
bf99ca0-e6df-40bc-a66f-fe63b57ed8a0signature=X2GGH%2F2eo7oS87z1ObWRUzbnXqQ%3Dcommand=listPublicIpAddressesresponse=jsonli
stall=True
2014-04-02 17:20:28,097 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-f87f0017) ===START=== 10.223.240.194 -- GET apiKey=t
3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgvirtualmachineid=ce01d441-d77f-4b5c-8a2
3-67f959b330bfsignature=pXyBJU73ioZ%2BNZIe%2Fy%2FIA4Ay9cI%3Dipaddressid=8b9f259d-f3a3-4060-ae32-6d5c86bcb346command=create
PortForwardingRuleprivateport=22protocol=TCPpublicport=22response=json
2014-04-02 17:20:28,124 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-f87f0017 ctx-8fe3f5ba ctx-36cd4126) Access to
{Ip[10.223.122.82-1]} granted to
Acct[e77e5066-ddae-4410-8609-4b8e74a984f9-admin] by
RoleBasedEntityAccessChecker
2014-04-02 17:20:28,127 DEBUG [c.c.a.t.Request]
(StatsCollector-1:ctx-44b28c8c) Seq 3-3008686026060202681: Received: { Ans:
, MgmtId: 29066118877352, via: 3, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
2014-04-02 17:20:28,178 INFO [c.c.a.ApiServer]
(catalina-exec-19:ctx-f87f0017 ctx-8fe3f5ba ctx-36cd4126) PermissionDenied:
Acct[e77e5066-ddae-4410-8609-4b8e74a984f9-admin] does not have permission to
perform this operation on these resources on objs: []
2014-04-02 17:20:28,178 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-f87f0017 ctx-8fe3f5ba ctx-36cd4126) ===END===
10.223.240.194 -- GET
apiKey=t3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgvirtualmachineid=ce01d441-d77f-4b5c-8a23-67f959b330bfsignature=pXyBJU73ioZ%2BNZIe%2Fy%2FIA4Ay9cI%3Dipaddressid=8b9f259d-f3a3-4060-ae32-6d5c86bcb346command=createPortForwardingRuleprivateport=22protocol=TCPpublicport=22response=json
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6332) [Automation] Failed to create PFrule with permission error does not have permission to perform this operation on these resources on objs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan closed CLOUDSTACK-6332.
---
Verified with latest automation result
[Automation] Failed to create PFrule with permission error does not have
permission to perform this operation on these resources on objs
--
Key: CLOUDSTACK-6332
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6332
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: Prachi Damle
Priority: Blocker
Fix For: 4.4.0
Attachments: CLOUDSTACK-6329.rar
Test case
integration.component.test_accounts.TestDomainForceRemove.test_forceDeleteDomain
failing with latest build
This test case performing below operations
1540 # Steps for validations
1541 # 1. create a domain DOM
1542 # 2. create 2 users under this domain
1543 # 3. deploy 1 VM into each of these user accounts
1544 # 4. create PF / FW rules for port 22 on these VMs for their
1545 #respective accounts
1546 # 5. delete the domain with force=true option
1547 # Validate the following
1548 # 1. listDomains should list the created domain
1549 # 2. listAccounts should list the created accounts
1550 # 3. listvirtualmachines should show the Running VMs
1551 # 4. PF and FW rules should be shown in listFirewallRules
1552 # 5. domain should delete successfully and above three list calls
1553 #should show all the resources now deleted. listRouters
should
1554 #not return any routers in the deleted accounts/domains
This test case failing while creating PF rule
2014-04-02 17:20:28,092 DEBUG [c.c.a.ApiServlet]
(catalina-exec-6:ctx-fef1201e ctx-1aba7046 ctx-c95b5405) ===END=== 10.223.2
40.194 -- GET
account=test-TestUserLogin-test_forceDeleteDomain-KV543Jdomainid=1503a119-b8b8-4ce8-851c-9af1da80dc59issourc
enat=TrueapiKey=t3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgassociatednetworkid=6
bf99ca0-e6df-40bc-a66f-fe63b57ed8a0signature=X2GGH%2F2eo7oS87z1ObWRUzbnXqQ%3Dcommand=listPublicIpAddressesresponse=jsonli
stall=True
2014-04-02 17:20:28,097 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-f87f0017) ===START=== 10.223.240.194 -- GET apiKey=t
3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgvirtualmachineid=ce01d441-d77f-4b5c-8a2
3-67f959b330bfsignature=pXyBJU73ioZ%2BNZIe%2Fy%2FIA4Ay9cI%3Dipaddressid=8b9f259d-f3a3-4060-ae32-6d5c86bcb346command=create
PortForwardingRuleprivateport=22protocol=TCPpublicport=22response=json
2014-04-02 17:20:28,124 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-f87f0017 ctx-8fe3f5ba ctx-36cd4126) Access to
{Ip[10.223.122.82-1]} granted to
Acct[e77e5066-ddae-4410-8609-4b8e74a984f9-admin] by
RoleBasedEntityAccessChecker
2014-04-02 17:20:28,127 DEBUG [c.c.a.t.Request]
(StatsCollector-1:ctx-44b28c8c) Seq 3-3008686026060202681: Received: { Ans:
, MgmtId: 29066118877352, via: 3, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
2014-04-02 17:20:28,178 INFO [c.c.a.ApiServer]
(catalina-exec-19:ctx-f87f0017 ctx-8fe3f5ba ctx-36cd4126) PermissionDenied:
Acct[e77e5066-ddae-4410-8609-4b8e74a984f9-admin] does not have permission to
perform this operation on these resources on objs: []
2014-04-02 17:20:28,178 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-f87f0017 ctx-8fe3f5ba ctx-36cd4126) ===END===
10.223.240.194 -- GET
apiKey=t3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgvirtualmachineid=ce01d441-d77f-4b5c-8a23-67f959b330bfsignature=pXyBJU73ioZ%2BNZIe%2Fy%2FIA4Ay9cI%3Dipaddressid=8b9f259d-f3a3-4060-ae32-6d5c86bcb346command=createPortForwardingRuleprivateport=22protocol=TCPpublicport=22response=json
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6550) [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985956#comment-13985956 ] Rayees Namathponnan commented on CLOUDSTACK-6550: - All below test cases need to be fixed Test Name Duration Age integration.smoke.test_routers.TestRouterServices.test_01_router_internal_basic 0.41 sec1 integration.smoke.test_routers.TestRouterServices.test_02_router_internal_adv 0.41 sec1 integration.smoke.test_routers.TestRouterServices.test_03_restart_network_cleanup 0.32 sec1 integration.smoke.test_routers.TestRouterServices.test_04_restart_network_wo_cleanup 8.8 sec 1 integration.smoke.test_routers.TestRouterServices.test_05_router_basic 0.39 sec1 integration.smoke.test_routers.TestRouterServices.test_06_router_advanced 0.3 sec 1 integration.smoke.test_routers.TestRouterServices.test_07_stop_router 0.31 sec1 integration.smoke.test_routers.TestRouterServices.test_08_start_router 0.39 sec1 integration.smoke.test_routers.TestRouterServices.test_09_reboot_router 0.35 sec1 [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this - Key: CLOUDSTACK-6550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Virtual Router Affects Versions: 4.4.0 Environment: Xen 6.2 build : 4.4-forward Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Currently test cases are using below command to listrouter (without listall=true), passing accountID and domain ID http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6550) [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6550: Assignee: Girish Shilamkar [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this - Key: CLOUDSTACK-6550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Virtual Router Affects Versions: 4.4.0 Environment: Xen 6.2 build : 4.4-forward Reporter: Rayees Namathponnan Assignee: Girish Shilamkar Priority: Blocker Fix For: 4.4.0 Currently test cases are using below command to listrouter (without listall=true), passing accountID and domain ID http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6550) [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6550: Issue Type: Test (was: Bug) [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this - Key: CLOUDSTACK-6550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: API, Virtual Router Affects Versions: 4.4.0 Environment: Xen 6.2 build : 4.4-forward Reporter: Rayees Namathponnan Assignee: Girish Shilamkar Priority: Blocker Fix For: 4.4.0 Currently test cases are using below command to listrouter (without listall=true), passing accountID and domain ID http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6551) [Automation] Failed to revert vm snapshot in xen
Rayees Namathponnan created CLOUDSTACK-6551:
---
Summary: [Automation] Failed to revert vm snapshot in xen
Key: CLOUDSTACK-6551
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6551
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Snapshot, XenServer
Affects Versions: 4.4.0
Environment: Xen 6.2
build 4.4-forward
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Steps to reproduce
Step 1) Create advanced zone on xen
Step 2) Deploy a vm
Step 3) create vm snapshot without memory
step 4) revert the snapshot
Result
Revert snapshot failed with below exception
2014-05-01 06:22:19,439 DEBUG [c.c.n.NetworkModelImpl]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Service SecurityGroup is
not supported in the network id=241
2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq 2-5867345889533626796:
Sending { Cmd , MgmtId: 6631563722783, via: 2(Rack1Pod1Host15), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.RevertToVMSnapshotCommand:{reloadVm:false,volumeTOs:[{uuid:ee4093bf-e6f0-49e3-be37-3b5c05fd6845,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cb8c6c62-71ea-3269-94b9-b1c0a4055d45,id:3,poolType:NetworkFilesystem,host:10.147.28.8,path:/vol/dgVol/automation/adv/pri_3,port:2049,url:NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=PrimarySTOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45}},name:ROOT-77,size:21474836480,path:75f283c8-db97-4b95-96c2-72d981bc7f0c,volumeId:83,vmName:i-2-77-VM,accountId:2,format:VHD,id:83,deviceId:0,hypervisorType:XenServer}],target:{id:3,snapshotName:i-2-77-VM_VS_20140501005100,type:Disk,createTime:139890546,current:true,description:Test
,quiescevm:true},vmName:i-2-77-VM,guestOSType:CentOS 5.6
(64-bit),wait:0}}] }
2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq 2-5867345889533626796:
Executing: { Cmd , MgmtId: 6631563722783, via: 2(Rack1Pod1Host15), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.RevertToVMSnapshotCommand:{reloadVm:false,volumeTOs:[{uuid:ee4093bf-e6f0-49e3-be37-3b5c05fd6845,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cb8c6c62-71ea-3269-94b9-b1c0a4055d45,id:3,poolType:NetworkFilesystem,host:10.147.28.8,path:/vol/dgVol/automation/adv/pri_3,port:2049,url:NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=PrimarySTOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45}},name:ROOT-77,size:21474836480,path:75f283c8-db97-4b95-96c2-72d981bc7f0c,volumeId:83,vmName:i-2-77-VM,accountId:2,format:VHD,id:83,deviceId:0,hypervisorType:XenServer}],target:{id:3,snapshotName:i-2-77-VM_VS_20140501005100,type:Disk,createTime:139890546,current:true,description:Test
,quiescevm:true},vmName:i-2-77-VM,guestOSType:CentOS 5.6
(64-bit),wait:0}}] }
2014-05-01 06:22:19,465 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-233:ctx-acc9e792) Seq 2-5867345889533626796: Executing request
2014-05-01 06:22:20,084 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 8-4288: Processing Seq 8-4288: { Cmd ,
MgmtId: -1, via: 8, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:3,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-05-01 06:22:20,089 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 8-4288: Sending Seq 8-4288: { Ans: ,
MgmtId: 6631563722783, via: 8, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-05-01 06:22:20,524 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-233:ctx-acc9e792) Task failed! Task record: uuid:
1affb5ba-5bcf-4e86-f866-c3cbba89dff8
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Wed Apr 30 20:08:59 IST 2014
finished: Wed Apr 30 20:08:59 IST 2014
status: failure
residentOn: com.xensource.xenapi.Host@e88e6ba5
progress: 1.0
type: none/
result:
errorInfo: [UNKNOWN_XENAPI_PLUGIN_FUNCTION, revert_memory_snapshot]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-05-01 06:22:20,528 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-233:ctx-acc9e792) callHostPlugin failed for cmd:
revert_memory_snapshot with args hostUUID:
71567ecf-6bae-4aaf-8040-863d3175b885, snapshotUUID:
ca1506e7-63ca-8bcb-c920-3242b7f98d5d, oldVmUuid:
79cc862a-078e-df77-8e28-ffbccd3df635, snapshotMemory: false, vmName: i-2-77-VM,
due to Task failed! Task record: uuid:
[jira] [Commented] (CLOUDSTACK-6550) [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985980#comment-13985980 ] Rayees Namathponnan commented on CLOUDSTACK-6550: - integration.smoke.test_loadbalance.TestLoadBalance.test_01_create_lb_rule_src_nat - also need to be fixed [Automation] listRouters API return empty list if you are not passing listall=true, many testcases failed due to this - Key: CLOUDSTACK-6550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: API, Virtual Router Affects Versions: 4.4.0 Environment: Xen 6.2 build : 4.4-forward Reporter: Rayees Namathponnan Assignee: Girish Shilamkar Priority: Blocker Fix For: 4.4.0 Currently test cases are using below command to listrouter (without listall=true), passing accountID and domain ID http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0domainid=22feae40-d076-11e3-8dca-0608081fcommand=listRouters this API call return empty list in 4.4, -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6552) Cloudstack-Management rpm create log directory that is never use
David Bierce created CLOUDSTACK-6552: Summary: Cloudstack-Management rpm create log directory that is never use Key: CLOUDSTACK-6552 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6552 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup, Management Server, Packaging Affects Versions: 4.2.0, 4.3.0, 4.4.0 Environment: CentOS 6.x Reporter: David Bierce Priority: Trivial The RPM generated by packaging/centos63/build.sh creates a directory in /var/log/cloudstack-management that is never used by cloudstack-management -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6552) Cloudstack-Management install package creates log directory that is never used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bierce updated CLOUDSTACK-6552: - Summary: Cloudstack-Management install package creates log directory that is never used (was: Cloudstack-Management rpm create log directory that is never use) Cloudstack-Management install package creates log directory that is never used -- Key: CLOUDSTACK-6552 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6552 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server, Packaging Affects Versions: 4.2.0, 4.3.0, 4.4.0 Environment: CentOS 6.x Reporter: David Bierce Priority: Trivial The RPM generated by packaging/centos63/build.sh creates a directory in /var/log/cloudstack-management that is never used by cloudstack-management -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6551) [Automation] Failed to revert vm snapshot in xen
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6551:
Attachment: management-server.rar
[Automation] Failed to revert vm snapshot in xen
-
Key: CLOUDSTACK-6551
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6551
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Snapshot, XenServer
Affects Versions: 4.4.0
Environment: Xen 6.2
build 4.4-forward
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.rar
Steps to reproduce
Step 1) Create advanced zone on xen
Step 2) Deploy a vm
Step 3) create vm snapshot without memory
step 4) revert the snapshot
Result
Revert snapshot failed with below exception
2014-05-01 06:22:19,439 DEBUG [c.c.n.NetworkModelImpl]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Service SecurityGroup is
not supported in the network id=241
2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq
2-5867345889533626796: Sending { Cmd , MgmtId: 6631563722783, via:
2(Rack1Pod1Host15), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.RevertToVMSnapshotCommand:{reloadVm:false,volumeTOs:[{uuid:ee4093bf-e6f0-49e3-be37-3b5c05fd6845,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cb8c6c62-71ea-3269-94b9-b1c0a4055d45,id:3,poolType:NetworkFilesystem,host:10.147.28.8,path:/vol/dgVol/automation/adv/pri_3,port:2049,url:NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=PrimarySTOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45}},name:ROOT-77,size:21474836480,path:75f283c8-db97-4b95-96c2-72d981bc7f0c,volumeId:83,vmName:i-2-77-VM,accountId:2,format:VHD,id:83,deviceId:0,hypervisorType:XenServer}],target:{id:3,snapshotName:i-2-77-VM_VS_20140501005100,type:Disk,createTime:139890546,current:true,description:Test
,quiescevm:true},vmName:i-2-77-VM,guestOSType:CentOS 5.6
(64-bit),wait:0}}] }
2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq
2-5867345889533626796: Executing: { Cmd , MgmtId: 6631563722783, via:
2(Rack1Pod1Host15), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.RevertToVMSnapshotCommand:{reloadVm:false,volumeTOs:[{uuid:ee4093bf-e6f0-49e3-be37-3b5c05fd6845,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cb8c6c62-71ea-3269-94b9-b1c0a4055d45,id:3,poolType:NetworkFilesystem,host:10.147.28.8,path:/vol/dgVol/automation/adv/pri_3,port:2049,url:NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=PrimarySTOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45}},name:ROOT-77,size:21474836480,path:75f283c8-db97-4b95-96c2-72d981bc7f0c,volumeId:83,vmName:i-2-77-VM,accountId:2,format:VHD,id:83,deviceId:0,hypervisorType:XenServer}],target:{id:3,snapshotName:i-2-77-VM_VS_20140501005100,type:Disk,createTime:139890546,current:true,description:Test
,quiescevm:true},vmName:i-2-77-VM,guestOSType:CentOS 5.6
(64-bit),wait:0}}] }
2014-05-01 06:22:19,465 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-233:ctx-acc9e792) Seq 2-5867345889533626796: Executing request
2014-05-01 06:22:20,084 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 8-4288: Processing Seq 8-4288: { Cmd ,
MgmtId: -1, via: 8, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:3,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-05-01 06:22:20,089 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 8-4288: Sending Seq 8-4288: { Ans: ,
MgmtId: 6631563722783, via: 8, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-05-01 06:22:20,524 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-233:ctx-acc9e792) Task failed! Task record:
uuid: 1affb5ba-5bcf-4e86-f866-c3cbba89dff8
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Wed Apr 30 20:08:59 IST 2014
finished: Wed Apr 30 20:08:59 IST 2014
status: failure
residentOn: com.xensource.xenapi.Host@e88e6ba5
progress: 1.0
type: none/
result:
errorInfo: [UNKNOWN_XENAPI_PLUGIN_FUNCTION, revert_memory_snapshot]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-05-01 06:22:20,528 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-233:ctx-acc9e792) callHostPlugin failed for cmd:
[jira] [Updated] (CLOUDSTACK-6331) [Automation] Template Permissions test cases failing with error Only ROOT admins are allowed to modify this attribute
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Mehta updated CLOUDSTACK-6331:
Assignee: Prachi Damle (was: Nitin Mehta)
[Automation] Template Permissions test cases failing with error Only ROOT
admins are allowed to modify this attribute
---
Key: CLOUDSTACK-6331
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6331
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.4.0
Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: Prachi Damle
Priority: Blocker
Fix For: 4.4.0
Attachments: CLOUDSTACK-6329.rar
Test case
integration.smoke.test_templates.TestTemplates.test_05_template_permissions
failing from BVT
Steps to reproduce
1) Deploy VM
2) Create snapshot and create template from snapshot
3) Updated template permission Update to private
Result
Template update operation fails with error Only ROOT admins are allowed to
modify this attribute
2014-04-02 12:05:57,472 DEBUG [c.c.a.ApiServlet]
(catalina-exec-9:ctx-1ccdf2c1) ===START=== 10.223.240.194 -- GET apiKey=t3
Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgisfeatured=Trueispublic=Trueisextracta
ble=Falseresponse=jsoncommand=updateTemplatePermissionssignature=YxifB0nikFnbYj40J9Koej8P1yk%3Did=efed6582-1e60-4f8e-b9a0
-3c2f6e1fde3c
2014-04-02 12:05:57,476 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-e19a73c2) Found 0 netwo
rks to update RvR status.
2014-04-02 12:05:57,497 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-9:ctx-1ccdf2c1 ctx-cb8d0196 ctx-6eaa1873) Access to {
Tmpl[208-QCOW2-8897aa78-3d38-488c-aba2-e7be5b817705} granted to
Acct[cde317a6-d332-452a-9e78-5ad2e2ce38b0-admin] by RoleBased
EntityAccessChecker
2014-04-02 12:05:57,501 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-9:ctx-1ccdf2c1 ctx-cb8d0196 ctx-6eaa1873) Root Access
granted to Acct[027223ec-ba90-11e3-b505-1a6f7bb0d0a8-admin] by
RoleBasedEntityAccessChecker
2014-04-02 12:05:57,501 INFO [c.c.a.ApiServer] (catalina-exec-9:ctx-1ccdf2c1
ctx-cb8d0196 ctx-6eaa1873) Only ROOT admins are allowed to modify this
attribute.
2014-04-02 12:05:57,502 DEBUG [c.c.a.ApiServlet]
(catalina-exec-9:ctx-1ccdf2c1 ctx-cb8d0196 ctx-6eaa1873) ===END===
10.223.240.194 -- GET
apiKey=t3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgisfeatured=Trueispublic=Trueisextractable=Falseresponse=jsoncommand=updateTemplatePermissionssignature=YxifB0nikFnbYj40J9Koej8P1yk%3Did=efed6582-1e60-4f8e-b9a0-3c2f6e1fde3c
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6331) [Automation] Template Permissions test cases failing with error Only ROOT admins are allowed to modify this attribute
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986137#comment-13986137
]
Nitin Mehta commented on CLOUDSTACK-6331:
-
Assigning it to Prachi since it seems to be IAM related.
[Automation] Template Permissions test cases failing with error Only ROOT
admins are allowed to modify this attribute
---
Key: CLOUDSTACK-6331
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6331
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.4.0
Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: Prachi Damle
Priority: Blocker
Fix For: 4.4.0
Attachments: CLOUDSTACK-6329.rar
Test case
integration.smoke.test_templates.TestTemplates.test_05_template_permissions
failing from BVT
Steps to reproduce
1) Deploy VM
2) Create snapshot and create template from snapshot
3) Updated template permission Update to private
Result
Template update operation fails with error Only ROOT admins are allowed to
modify this attribute
2014-04-02 12:05:57,472 DEBUG [c.c.a.ApiServlet]
(catalina-exec-9:ctx-1ccdf2c1) ===START=== 10.223.240.194 -- GET apiKey=t3
Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgisfeatured=Trueispublic=Trueisextracta
ble=Falseresponse=jsoncommand=updateTemplatePermissionssignature=YxifB0nikFnbYj40J9Koej8P1yk%3Did=efed6582-1e60-4f8e-b9a0
-3c2f6e1fde3c
2014-04-02 12:05:57,476 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-e19a73c2) Found 0 netwo
rks to update RvR status.
2014-04-02 12:05:57,497 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-9:ctx-1ccdf2c1 ctx-cb8d0196 ctx-6eaa1873) Access to {
Tmpl[208-QCOW2-8897aa78-3d38-488c-aba2-e7be5b817705} granted to
Acct[cde317a6-d332-452a-9e78-5ad2e2ce38b0-admin] by RoleBased
EntityAccessChecker
2014-04-02 12:05:57,501 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-9:ctx-1ccdf2c1 ctx-cb8d0196 ctx-6eaa1873) Root Access
granted to Acct[027223ec-ba90-11e3-b505-1a6f7bb0d0a8-admin] by
RoleBasedEntityAccessChecker
2014-04-02 12:05:57,501 INFO [c.c.a.ApiServer] (catalina-exec-9:ctx-1ccdf2c1
ctx-cb8d0196 ctx-6eaa1873) Only ROOT admins are allowed to modify this
attribute.
2014-04-02 12:05:57,502 DEBUG [c.c.a.ApiServlet]
(catalina-exec-9:ctx-1ccdf2c1 ctx-cb8d0196 ctx-6eaa1873) ===END===
10.223.240.194 -- GET
apiKey=t3Wyi-p5OTh1n5J_y-x8QpwEqHpnyde1729HI5LLHvH5Bd4XU5nEg5n7i6xOIhZOECZ3KcKYnakvdI5hkneqrgisfeatured=Trueispublic=Trueisextractable=Falseresponse=jsoncommand=updateTemplatePermissionssignature=YxifB0nikFnbYj40J9Koej8P1yk%3Did=efed6582-1e60-4f8e-b9a0-3c2f6e1fde3c
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6553) [Automation] Resize volume test case failing with error value=invalid id due to incorrect long value format
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6553: Attachment: management-server.rar [Automation] Resize volume test case failing with error value=invalid id due to incorrect long value format - Key: CLOUDSTACK-6553 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6553 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, VMware, Volumes Affects Versions: 4.4.0 Environment: vmware 5.1 build 4.4-forward Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Attachments: management-server.rar this issue is observed with automation run; resize volume test cases failing with error Invalid parameter id value=invalid id due to incorrect long value format, integration.smoke.test_volumes.TestVolumes.test_07_resize_fail This test cases was passing in 4.3, 2014-04-30 07:08:35,580 DEBUG [c.c.a.ApiServlet] (catalina-exec-25:ctx-4c2b55c4 ctx-7cde2cec ctx-709f77de) ===END=== 10.223.240.1 95 -- GET signature=oPeFwi6qo7V1ZDe9yIcbp3foZL8%3DapiKey=hRzPXkvW4WGZJY4i3f_e1T5Fy0oJHErLBXfB63UsMnA7nsbeXPZaPzNiSO9snRgmXlX8oQX KB0pUOoSpgt9ldgcommand=queryAsyncJobResultresponse=jsonjobid=4396e3af-3cef-43ee-9e33-dcdf492826ca 2014-04-30 07:08:35,608 DEBUG [c.c.a.ApiServlet] (catalina-exec-3:ctx-5311d640) ===START=== 10.223.240.195 -- GET apiKey=hRzPXkv W4WGZJY4i3f_e1T5Fy0oJHErLBXfB63UsMnA7nsbeXPZaPzNiSO9snRgmXlX8oQXKB0pUOoSpgt9ldgresponse=jsoncommand=resizeVolumesignature=FIdW1 p%2B09IkXBdomfhmj2HREj7s%3Ddiskofferingid=2a57852e-7765-4e06-adae-be7d32ab871aid=invalid+id 2014-04-30 07:08:35,663 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-3:ctx-5311d640 ctx-f5e33c1f ctx-4fca8abd) Root Access gran ted to Acct[adde0f76-cfed-11e3-ab79-52b2d980df8a-admin] by RoleBasedEntityAccessChecker 2014-04-30 07:08:35,805 DEBUG [c.c.a.d.ParamProcessWorker] (catalina-exec-3:ctx-5311d640 ctx-f5e33c1f ctx-4fca8abd) Object entity uuid = invalid id does not exist in the database. 2014-04-30 07:08:35,807 INFO [c.c.a.ApiServer] (catalina-exec-3:ctx-5311d640 ctx-f5e33c1f ctx-4fca8abd) Unable to execute API com mand resizevolume due to invalid value. Invalid parameter id value=invalid id due to incorrect long value format, or entity does n ot exist or due to incorrect parameter annotation for the field in api cmd class. 2014-04-30 07:08:35,830 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-3:ctx-5311d640 ctx-f5e33c1f ctx-4fca8abd) Root Access gran ted to Acct[adde0f76-cfed-11e3-ab79-52b2d980df8a-admin] by RoleBasedEntityAccessChecker 2014-04-30 07:08:35,835 DEBUG [c.c.a.ApiServlet] (catalina-exec-3:ctx-5311d640 ctx-f5e33c1f ctx-4fca8abd) ===END=== 10.223.240.19 5 -- GET apiKey=hRzPXkvW4WGZJY4i3f_e1T5Fy0oJHErLBXfB63UsMnA7nsbeXPZaPzNiSO9snRgmXlX8oQXKB0pUOoSpgt9ldgresponse=jsoncommand=resi zeVolumesignature=FIdW1p%2B09IkXBdomfhmj2HREj7s%3Ddiskofferingid=2a57852e-7765-4e06-adae-be7d32ab871aid=invalid+id 2014-04-30 07:08:35,844 DEBUG [c.c.a.ApiServlet] (catalina-exec-24:ctx-3847902e) ===START=== 10.223.240.195 -- GET apiKey=hRzPXk vW4WGZJY4i3f_e1T5Fy0oJHErLBXfB63UsMnA7nsbeXPZaPzNiSO9snRgmXlX8oQXKB0pUOoSpgt9ldgresponse=jsoncommand=resizeVolumesignature=1bAE 0RbpWgdYvFlhX6f35CYsvsM%3Ddiskofferingid=invalid+idid=418d4704-2ce9-4c5c-b2a0-e7cdbcb8413b 2014-04-30 07:08:35,898 DEBUG [c.c.u.AccountManagerImpl] (catalina-exec-24:ctx-3847902e ctx-a73f5221 ctx-c96949e3) Root Access gra nted to Acct[adde0f76-cfed-11e3-ab79-52b2d980df8a-admin] by RoleBasedEntityAccessChecker 2014-04-30 07:08:35,920 DEBUG [c.c.a.d.ParamProcessWorker] (catalina-exec-24:ctx-3847902e ctx-a73f5221 ctx-c96949e3) Object entity uuid = invalid id does not exist in the database. 2014-04-30 07:08:35,921 INFO [c.c.a.ApiServer] (catalina-exec-24:ctx-3847902e ctx-a73f5221 ctx-c96949e3) Unable to execute API co mmand 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. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5683) [Automation] - kvm - Live migration fails with java.lang.NullPointerException. But this is reported as success.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986198#comment-13986198
]
Kelven Yang commented on CLOUDSTACK-5683:
-
This should have already been fixed in
13e956a10ca6944cd4a45348e5bccfacd3b889d3
[Automation] - kvm - Live migration fails with
java.lang.NullPointerException. But this is reported as success.
---
Key: CLOUDSTACK-5683
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5683
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Environment: Build from 4.3
Reporter: Sangeetha Hariharan
Assignee: Kelven Yang
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log, management-server.rar
Steps to reproduce the problem:
Advanced zone set up with 2 KVM hosts.
Deploy few Vms in both hosts.
Live migrate vm from 1 host to another.
UI reports success , but the VM migration actually fails.
Following exception seen in management server logs:
013-12-30 17:35:03,451 ERROR [c.c.v.VmWorkJobDispatcher]
(Job-Executor-101:ctx-23e206c0 ctx-4ddc2410) Unable to complete AsyncJobVO
{id:76
, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo: rO0ABXNyABpjb20uY2xvdWQudm0uVm1X
b3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9
MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbW
V0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAA3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAnNyAA5qYXZhLmxhbmcuTG9uZzuL5
JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXEAfgA
JcQB-AAlwcQB-AAk, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0,
resultCode: 0, result: null, initMsid: 82324189320212, completeMsid: null,
lastUpdated: null, lastPolled: null, created: Mon Dec 30 17:35:02 EST 2013}
java.lang.NullPointerException
at
com.cloud.vm.VmWorkMigrate.getDeployDestination(VmWorkMigrate.java:60)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4743)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2013-12-30 17:35:03,452 ERROR [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-101:ctx-23e206c0) Unexpected exception
java.lang.NullPointerException
2013-12-30 17:35:03,452 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-101:ctx-23e206c0) Complete async job-76, jobStatus: FAILED,
resultCode: 530, result: null
2013-12-30 17:35:03,463 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-102:ctx-e541857f) Add job-75 into job monitoring
2013-12-30 17:35:03,463 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-102:ctx-e541857f) Executing AsyncJobVO {id:75, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:4SFVHNVTkNP6Ys+kKkCAVp57j8w\u003d,virtualmachineid:17c74e6c-a39b-4c51-8e76-b75985ea6622,cmdEventType:VM.MIGRATE,hostid:9cc1f4fa-f972-42a1-be2c-213dc1c36504,ctxUserId:2,httpmethod:GET,_:1388442964044,ctxAccountId:2,ctxStartEventId:165},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid:
[jira] [Resolved] (CLOUDSTACK-5683) [Automation] - kvm - Live migration fails with java.lang.NullPointerException. But this is reported as success.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelven Yang resolved CLOUDSTACK-5683.
-
Resolution: Fixed
[Automation] - kvm - Live migration fails with
java.lang.NullPointerException. But this is reported as success.
---
Key: CLOUDSTACK-5683
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5683
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Environment: Build from 4.3
Reporter: Sangeetha Hariharan
Assignee: Kelven Yang
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log, management-server.rar
Steps to reproduce the problem:
Advanced zone set up with 2 KVM hosts.
Deploy few Vms in both hosts.
Live migrate vm from 1 host to another.
UI reports success , but the VM migration actually fails.
Following exception seen in management server logs:
013-12-30 17:35:03,451 ERROR [c.c.v.VmWorkJobDispatcher]
(Job-Executor-101:ctx-23e206c0 ctx-4ddc2410) Unable to complete AsyncJobVO
{id:76
, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo: rO0ABXNyABpjb20uY2xvdWQudm0uVm1X
b3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9
MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbW
V0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAA3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAnNyAA5qYXZhLmxhbmcuTG9uZzuL5
JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXEAfgA
JcQB-AAlwcQB-AAk, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0,
resultCode: 0, result: null, initMsid: 82324189320212, completeMsid: null,
lastUpdated: null, lastPolled: null, created: Mon Dec 30 17:35:02 EST 2013}
java.lang.NullPointerException
at
com.cloud.vm.VmWorkMigrate.getDeployDestination(VmWorkMigrate.java:60)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4743)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2013-12-30 17:35:03,452 ERROR [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-101:ctx-23e206c0) Unexpected exception
java.lang.NullPointerException
2013-12-30 17:35:03,452 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-101:ctx-23e206c0) Complete async job-76, jobStatus: FAILED,
resultCode: 530, result: null
2013-12-30 17:35:03,463 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-102:ctx-e541857f) Add job-75 into job monitoring
2013-12-30 17:35:03,463 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-102:ctx-e541857f) Executing AsyncJobVO {id:75, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:4SFVHNVTkNP6Ys+kKkCAVp57j8w\u003d,virtualmachineid:17c74e6c-a39b-4c51-8e76-b75985ea6622,cmdEventType:VM.MIGRATE,hostid:9cc1f4fa-f972-42a1-be2c-213dc1c36504,ctxUserId:2,httpmethod:GET,_:1388442964044,ctxAccountId:2,ctxStartEventId:165},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 82324189320212, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Mon Dec 30 17:35:02 EST 2013}
--
[jira] [Updated] (CLOUDSTACK-6055) [Automation] Firewall rule creation failing for portable public IP with error Failed to create firewall rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-6055: --- Assignee: Murali Reddy [Automation] Firewall rule creation failing for portable public IP with error Failed to create firewall rule -- Key: CLOUDSTACK-6055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.4.0 Environment: Observed yet on VMWare. Reporter: Gaurav Aradhye Assignee: Murali Reddy Labels: automation Fix For: 4.4.0 Attachments: portableip-Firewall-MgtSrvrLog.txt Steps to reproduce: 1) Add a portable public IP range 2) Create an isolated network 3) Acquire portable IP in the network 4) Try to create firewall rule for the IP address Step 4 Fails. Management Server log attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5632) [Automation] XenServer - Template deletion fails with error Please specify a template that is not currently being downloaded although the template is completely do
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-5632:
---
Assignee: Min Chen
[Automation] XenServer - Template deletion fails with error Please specify a
template that is not currently being downloaded although the template is
completely downloaded, installed and is in ready state
--
Key: CLOUDSTACK-5632
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5632
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.3.0
Environment: xenserver 62
advanced zone
Reporter: Srikanteswararao Talluri
Assignee: Min Chen
Fix For: 4.4.0
Creating this bug as a place holder for the following failures, needs further
analysis,
ContextSuite context=TestTemplateHierarchy:teardown FAILED Warning:
Exception during cleanup : Execute cmd: asyncquery failed, due to: {errorcode
: 530, errortext : u'Please specify a template that is not currently being
downloaded.'}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
