[jira] [Commented] (CLOUDSTACK-6169) assignVirtualMachine leaves associated tags assigned to old account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100500#comment-14100500 ] Namita Chaudhari commented on CLOUDSTACK-6169: -- I have uploaded the review patch a https://reviews.apache.org/r/24794/ assignVirtualMachine leaves associated tags assigned to old account --- Key: CLOUDSTACK-6169 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6169 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Prachi Damle Fix For: 4.4.0 I'm not 100% sure this is a bug, but it seems so. If you move a virtual machine between accounts via 'assignVirtualMachine', then list the virtual machine, any associated resource tags show the old account/domainid. This is confusing, but could also be a bad information leak -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6169) assignVirtualMachine leaves associated tags assigned to old account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100500#comment-14100500 ] Namita Chaudhari edited comment on CLOUDSTACK-6169 at 8/18/14 9:58 AM: --- I have uploaded the review patch at https://reviews.apache.org/r/24794/ was (Author: namita.chaudh...@sungard.com): I have uploaded the review patch a https://reviews.apache.org/r/24794/ assignVirtualMachine leaves associated tags assigned to old account --- Key: CLOUDSTACK-6169 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6169 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Namita Chaudhari Fix For: 4.4.0 I'm not 100% sure this is a bug, but it seems so. If you move a virtual machine between accounts via 'assignVirtualMachine', then list the virtual machine, any associated resource tags show the old account/domainid. This is confusing, but could also be a bad information leak -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6169) assignVirtualMachine leaves associated tags assigned to old account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari reassigned CLOUDSTACK-6169: Assignee: Namita Chaudhari (was: Prachi Damle) assignVirtualMachine leaves associated tags assigned to old account --- Key: CLOUDSTACK-6169 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6169 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Namita Chaudhari Fix For: 4.4.0 I'm not 100% sure this is a bug, but it seems so. If you move a virtual machine between accounts via 'assignVirtualMachine', then list the virtual machine, any associated resource tags show the old account/domainid. This is confusing, but could also be a bad information leak -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6851) ResourceTagResponse does not have id field due to which resource level permission cannot be granted to any specific resource
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-6851: - Assignee: (was: Namita Chaudhari) ResourceTagResponse does not have id field due to which resource level permission cannot be granted to any specific resource -- Key: CLOUDSTACK-6851 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6851 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Reporter: Namita Chaudhari Labels: None Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5464) VM Deployment Fails
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090463#comment-14090463 ] Namita Chaudhari commented on CLOUDSTACK-5464: -- This bug is already handled in 4.4 and now the VM deployment does not fail. VM Deployment Fails --- Key: CLOUDSTACK-5464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5464 Project: CloudStack Issue Type: Bug Components: API, Management Server Affects Versions: 4.2.0 Environment: ESXi 5.1 Reporter: Rajendra Labels: build Attachments: management-server.zip Original Estimate: 120h Remaining Estimate: 120h I'm not able to create the VM Instance as the VM instance creation fails with the error: Unable to create a deployment for VM and this occurs at around 38 to 40 % (when I check the vm creation in vsphere). attached the Management logs. Please help at the earliest. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-231) Tag creation using special characters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-231: Summary: Tag creation using special characters (was: Tag creation using special charecters ) Tag creation using special characters -- Key: CLOUDSTACK-231 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-231 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: pre-4.0.0 Environment: MS(rhel6.3) Git Revision: 046e916fcf6d847e2cdf281233d2e68a8e6500f8 Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git Reporter: prashant kumar mishra Priority: Minor Fix For: 4.4.0 Tag creation - - steps to reproduce 1-create tag on any resource(vm/template/PF/FW) 2-provide detail key=value=some special character EXPECTED -- -- Tag creation shouldn't be happening with message special character's are not allowed ACTUAL --- -- Tag creation is happening properly using special characters -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6169) assignVirtualMachine leaves associated tags assigned to old account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090535#comment-14090535 ] Namita Chaudhari commented on CLOUDSTACK-6169: -- Hi Marcus, I tried reproducing the issue and moved a VM between accounts via 'assignVirtualMachine' and observed that the resource_tags table in the database is not updated. The tags points to the old account/domainid. Is there any other place where the associated resource tags shows the old account/domainid other than database? Thanks, Namita assignVirtualMachine leaves associated tags assigned to old account --- Key: CLOUDSTACK-6169 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6169 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Prachi Damle Fix For: 4.4.0 I'm not 100% sure this is a bug, but it seems so. If you move a virtual machine between accounts via 'assignVirtualMachine', then list the virtual machine, any associated resource tags show the old account/domainid. This is confusing, but could also be a bad information leak -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085850#comment-14085850 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- Hi Jayapal, Yes sure I will upload the patch soon to review board. Thanks, Namita [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086052#comment-14086052 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- I have uploaded the review patch at https://reviews.apache.org/r/24306/ [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari resolved CLOUDSTACK-2694. -- Resolution: Fixed Assignee: Namita Chaudhari [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Namita Chaudhari 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086193#comment-14086193 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- The patch is applied on master and hence closing the ticket. [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Namita Chaudhari 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari closed CLOUDSTACK-2694. [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Namita Chaudhari 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085804#comment-14085804 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- There is no validation added to check whether there already exists a firewall rule with cidr 0.0.0.0/0 and no ports. [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085806#comment-14085806 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- Made required changes in the code and tested it based on following testcases: 1) Create firewall rules by providing cidr, protocol and ports : a) diff cidr and diff ports with diff protocol b) diff cidr with same ports with diff protocol c) same cidr with diff ports with diff protocol d) same cidr with same ports with diff protocol e) diff cidr and diff ports with same protocol f) diff cidr with same ports with same protocol g) same cidr with diff ports with same protocol h) same cidr with same ports with same protocol 2) Create firewall rules only with cidr,protocol and no ports : a) diff cidr with no ports with diff protocol b) same cidr with no ports with diff protocol b) diff cidr with no ports with same protocol d) same cidr with no ports with same protocol 3) Create various firewall rules and the duplicate Fw rule should not get created [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14062002#comment-14062002 ] Namita Chaudhari commented on CLOUDSTACK-4819: -- So the issue basically is while listing templates or Iso a parameter projectid is passed and based on that a list of permittedaccounts is obtanined whose ISOs or templates should be listed. But during the ListIsoCmd / ListtemplateCmd, it is observed that the parameter projectId has null value as it is not obtained from UI and hence the templates and isos are not listed in project's template list. I have verified that when value is passed for param projectId, the api works fine and gives the expected result due to which the templates/iso under projects are listed. Hence this is an UI issue. Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 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 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-4819: - Comment: was deleted (was: The issue basically is the associated account (newly created account) to the project. When a template is registered in the project, the template by default points to this associated account and hence its not viewed in any template list. Instead of associating new account to the project, we can associate the account through which we have logged into UI. This could solve the issue.) Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 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 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056182#comment-14056182 ] Namita Chaudhari edited comment on CLOUDSTACK-4819 at 7/10/14 11:23 AM: The issue basically is the associated account (newly created account) to the project. When a template is registered in the project, the template by default points to this associated account and hence its not viewed in any template list. Instead of associating new account to the project, we can associate the account through which we have logged into UI. This could solve the issue. was (Author: namita.chaudh...@sungard.com): The issue basically is the associated account (newly created account) to the project. When a template is registered in the project, the template by default points to this associated account and hence its not viewed in any template list. Instead of associating new account to the project, we can associate the account through which we have logged into UI. This solves the issue. Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 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 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056180#comment-14056180 ] Namita Chaudhari edited comment on CLOUDSTACK-4819 at 7/9/14 12:40 PM: --- Registered a template with Acct-Test account. But in database the Ubuntu12.04 template points to ProjAcct-CENIK-598-1 account and that is the reason for template not getting displayed in project. The problem exists for template as well as for isos that are registered in project. was (Author: namita.chaudh...@sungard.com): Registered a template with Acct-Test account. But in database the Ubuntu12.04 template points to ProjAcct-CENIK-598-1 accounts and thats the reason for template not getting displayed in project. The problem exists for template as well as for isos that are registered in project. Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 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 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056182#comment-14056182 ] Namita Chaudhari commented on CLOUDSTACK-4819: -- The issue basically is the associated account (newly created account) to the project. When a template is registered in the project, the template by default points to this associated account and hence its not viewed in any template list. Instead of associating new account to the project, we can associate the account through which we have logged into UI. This solves the issue. Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 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 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056179#comment-14056179 ] Namita Chaudhari commented on CLOUDSTACK-4819: -- I could reproduce the issue. Created a project named CENIK-598 and registered a template(Ubuntu 12.04) in project. It downloaded successfully but did not appear in the project's template list and default view template list. Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 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 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056180#comment-14056180 ] Namita Chaudhari commented on CLOUDSTACK-4819: -- Registered a template with Acct-Test account. But in database the Ubuntu12.04 template points to ProjAcct-CENIK-598-1 accounts and thats the reason for template not getting displayed in project. The problem exists for template as well as for isos that are registered in project. Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 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 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4751) Can't add a single network multiple times to a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052310#comment-14052310 ] Namita Chaudhari commented on CLOUDSTACK-4751: -- There is a CS bug reporting the same issue, which specifies that adding a single network multiple times to a VM is not supported now but it was supported in 4.2 Hence marking the bug as duplicate. Can't add a single network multiple times to a VM - Key: CLOUDSTACK-4751 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4751 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: John Beredimas Assignee: Namita Chaudhari Trying to add a network multiple times to a single VM fails with release 4.2. This worked OK with release 4.1. This should be fairly easy to reproduce. Here is my cloudmonkey output: cloudmonkey add nictovirtualmachine virtualmachineid=a8d35e16-cb65-46c5-aa8d-d07e533326ee networkid=5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 Async job 115feb72-0abf-4cea-8e67-8d61d768e51e failed Error 530, A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 accountid = 2e64c73f-a173-419a-8dc8-6739aa4e4f9d cmd = org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd created = 2013-09-27T15:44:21+0300 jobid = 115feb72-0abf-4cea-8e67-8d61d768e51e jobprocstatus = 0 jobresult: errorcode = 530 errortext = A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 jobresultcode = 530 jobresulttype = object jobstatus = 2 userid = 59322c02-abf9-4be2-a7c5-a67947a257fb -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-4751) Can't add a single network multiple times to a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari resolved CLOUDSTACK-4751. -- Resolution: Duplicate Can't add a single network multiple times to a VM - Key: CLOUDSTACK-4751 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4751 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: John Beredimas Assignee: Namita Chaudhari Trying to add a network multiple times to a single VM fails with release 4.2. This worked OK with release 4.1. This should be fairly easy to reproduce. Here is my cloudmonkey output: cloudmonkey add nictovirtualmachine virtualmachineid=a8d35e16-cb65-46c5-aa8d-d07e533326ee networkid=5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 Async job 115feb72-0abf-4cea-8e67-8d61d768e51e failed Error 530, A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 accountid = 2e64c73f-a173-419a-8dc8-6739aa4e4f9d cmd = org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd created = 2013-09-27T15:44:21+0300 jobid = 115feb72-0abf-4cea-8e67-8d61d768e51e jobprocstatus = 0 jobresult: errorcode = 530 errortext = A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 jobresultcode = 530 jobresulttype = object jobstatus = 2 userid = 59322c02-abf9-4be2-a7c5-a67947a257fb -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-4751) Can't add a single network multiple times to a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052310#comment-14052310 ] Namita Chaudhari edited comment on CLOUDSTACK-4751 at 7/4/14 9:49 AM: -- There is a CS bug (linked above) reporting the same issue, which specifies that adding a single network multiple times to a VM is not supported now but it was supported in 4.2 Hence marking the bug as duplicate. was (Author: namita.chaudh...@sungard.com): There is a CS bug reporting the same issue, which specifies that adding a single network multiple times to a VM is not supported now but it was supported in 4.2 Hence marking the bug as duplicate. Can't add a single network multiple times to a VM - Key: CLOUDSTACK-4751 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4751 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: John Beredimas Assignee: Namita Chaudhari Trying to add a network multiple times to a single VM fails with release 4.2. This worked OK with release 4.1. This should be fairly easy to reproduce. Here is my cloudmonkey output: cloudmonkey add nictovirtualmachine virtualmachineid=a8d35e16-cb65-46c5-aa8d-d07e533326ee networkid=5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 Async job 115feb72-0abf-4cea-8e67-8d61d768e51e failed Error 530, A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 accountid = 2e64c73f-a173-419a-8dc8-6739aa4e4f9d cmd = org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd created = 2013-09-27T15:44:21+0300 jobid = 115feb72-0abf-4cea-8e67-8d61d768e51e jobprocstatus = 0 jobresult: errorcode = 530 errortext = A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 jobresultcode = 530 jobresulttype = object jobstatus = 2 userid = 59322c02-abf9-4be2-a7c5-a67947a257fb -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4751) Can't add a single network multiple times to a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048617#comment-14048617 ] Namita Chaudhari commented on CLOUDSTACK-4751: -- I am working on this bug and had a query regarding it. If a network is already configured on VM, then why do we have to add same network again to the VM? Is there any specific purpose behind doing so? Can anyone please help me in this? Can't add a single network multiple times to a VM - Key: CLOUDSTACK-4751 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4751 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: John Beredimas Assignee: Namita Chaudhari Trying to add a network multiple times to a single VM fails with release 4.2. This worked OK with release 4.1. This should be fairly easy to reproduce. Here is my cloudmonkey output: cloudmonkey add nictovirtualmachine virtualmachineid=a8d35e16-cb65-46c5-aa8d-d07e533326ee networkid=5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 Async job 115feb72-0abf-4cea-8e67-8d61d768e51e failed Error 530, A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 accountid = 2e64c73f-a173-419a-8dc8-6739aa4e4f9d cmd = org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd created = 2013-09-27T15:44:21+0300 jobid = 115feb72-0abf-4cea-8e67-8d61d768e51e jobprocstatus = 0 jobresult: errorcode = 530 errortext = A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 jobresultcode = 530 jobresulttype = object jobstatus = 2 userid = 59322c02-abf9-4be2-a7c5-a67947a257fb -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-4751) Can't add a single network multiple times to a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari reassigned CLOUDSTACK-4751: Assignee: Namita Chaudhari Can't add a single network multiple times to a VM - Key: CLOUDSTACK-4751 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4751 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: John Beredimas Assignee: Namita Chaudhari Trying to add a network multiple times to a single VM fails with release 4.2. This worked OK with release 4.1. This should be fairly easy to reproduce. Here is my cloudmonkey output: cloudmonkey add nictovirtualmachine virtualmachineid=a8d35e16-cb65-46c5-aa8d-d07e533326ee networkid=5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 Async job 115feb72-0abf-4cea-8e67-8d61d768e51e failed Error 530, A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 accountid = 2e64c73f-a173-419a-8dc8-6739aa4e4f9d cmd = org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd created = 2013-09-27T15:44:21+0300 jobid = 115feb72-0abf-4cea-8e67-8d61d768e51e jobprocstatus = 0 jobresult: errorcode = 530 errortext = A NIC already exists for VM:i-34-1015-VM in network: 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5 jobresultcode = 530 jobresulttype = object jobstatus = 2 userid = 59322c02-abf9-4be2-a7c5-a67947a257fb -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6851) ResourceTagResponse does not have id field due to which resource level permission cannot be granted to any specific resource
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari reassigned CLOUDSTACK-6851: Assignee: Namita Chaudhari ResourceTagResponse does not have id field due to which resource level permission cannot be granted to any specific resource -- Key: CLOUDSTACK-6851 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6851 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Reporter: Namita Chaudhari Assignee: Namita Chaudhari Labels: None Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6851) ResourceTagResponse does not have id field due to which resource level permission cannot be granted to any specific resource
Namita Chaudhari created CLOUDSTACK-6851: Summary: ResourceTagResponse does not have id field due to which resource level permission cannot be granted to any specific resource Key: CLOUDSTACK-6851 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6851 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Reporter: Namita Chaudhari Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932868#comment-13932868 ] Namita Chaudhari commented on CLOUDSTACK-4322: -- When a domain is deleted with force option, failed is returned as response incase if there are accounts under that domain that needs cleanup. I have attached the logs(DomainDeleteFailed_logs.txt) and screenshot (del_domain_fail.jpg) for the same. Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup. --- Key: CLOUDSTACK-4322 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.1.0, 4.2.0 Reporter: Sanjay Tripathi Fix For: Future deleteDomain with cleanup = true, CS is not allowing deletion of domain if there is any account under that domain needs clean up; though these accounts are removed and admin can't see them in the listaccounts call. From the end user perspective, CS should return success in case of force delete domain and handle the cleanup of sub-domains/accounts internally. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932869#comment-13932869 ] Namita Chaudhari commented on CLOUDSTACK-4322: -- I tried to delete a domain with force option: 1) The domain gets deleted successfully when the accounts under that domain does not need cleanup. 2) The domain does not get deleted, when the accounts under that domain needs cleanup. It throws an exception saying Failed to clean up domain resources and sub domains, delete failed on domain. I traversed through the code and the flow of the code is such that when a request is sent to delete a domain it first changes the state of domain to Inactive, cleanup the accounts under those domain and then delete the domain. But if the resources of those accounts are referenced elsewhere, then the accounts and domain are not deleted and the domain is reverted back to Active state. Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup. --- Key: CLOUDSTACK-4322 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.1.0, 4.2.0 Reporter: Sanjay Tripathi Fix For: Future deleteDomain with cleanup = true, CS is not allowing deletion of domain if there is any account under that domain needs clean up; though these accounts are removed and admin can't see them in the listaccounts call. From the end user perspective, CS should return success in case of force delete domain and handle the cleanup of sub-domains/accounts internally. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-4322: - Attachment: DomainDeleteFailed_logs.txt del_domain_fail.JPG Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup. --- Key: CLOUDSTACK-4322 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.1.0, 4.2.0 Reporter: Sanjay Tripathi Fix For: Future Attachments: DomainDeleteFailed_logs.txt, del_domain_fail.JPG deleteDomain with cleanup = true, CS is not allowing deletion of domain if there is any account under that domain needs clean up; though these accounts are removed and admin can't see them in the listaccounts call. From the end user perspective, CS should return success in case of force delete domain and handle the cleanup of sub-domains/accounts internally. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-4322: - Summary: Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup. (was: Delete domain with force option is not returning failed as responce incase of accounts under that domain needs cleanup.) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup. --- Key: CLOUDSTACK-4322 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.1.0, 4.2.0 Reporter: Sanjay Tripathi Fix For: Future deleteDomain with cleanup = true, CS is not allowing deletion of domain if there is any account under that domain needs clean up; though these accounts are removed and admin can't see them in the listaccounts call. From the end user perspective, CS should return success in case of force delete domain and handle the cleanup of sub-domains/accounts internally. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5825) Create snapshot API always returns success
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-5825: - Attachment: Snapshot_Logs.txt Create snapshot API always returns success -- Key: CLOUDSTACK-5825 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5825 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: Chris Suich Priority: Critical Labels: api, create, snapshot Attachments: Snapshot_Logs.txt, snapshot_failure.JPG VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot() to VolumeServiceImpl.takeSnapshot(), you’ll notice that ANY exception that is thrown inside of SnapshotManager.takeSnapshot() is simply caught and ignored. Back up in VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(), JobInfo.Status.SUCCEEDED is ALWAYS returned, regardless of the snapshot result. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5825) Create snapshot API always returns success
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-5825: - Attachment: snapshot_failure.JPG Create snapshot API always returns success -- Key: CLOUDSTACK-5825 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5825 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: Chris Suich Priority: Critical Labels: api, create, snapshot Attachments: Snapshot_Logs.txt, snapshot_failure.JPG VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot() to VolumeServiceImpl.takeSnapshot(), you’ll notice that ANY exception that is thrown inside of SnapshotManager.takeSnapshot() is simply caught and ignored. Back up in VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(), JobInfo.Status.SUCCEEDED is ALWAYS returned, regardless of the snapshot result. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari closed CLOUDSTACK-5641. Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_4.2_5641.JPG, CS_master_5641.JPG Local disk usage on storage pool view don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5825) Create snapshot API always returns success
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925474#comment-13925474 ] Namita Chaudhari commented on CLOUDSTACK-5825: -- I tried to create the volume snapshot. When the volume snapshot creation failed, the API threw an exception saying Failed to create the snapshot due to an internal error for volume x. I have attached the log (Snapshot_Logs.txt) and snapshot (snapshot_failure.jpg) for the same. Create snapshot API always returns success -- Key: CLOUDSTACK-5825 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5825 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: Chris Suich Priority: Critical Labels: api, create, snapshot Attachments: Snapshot_Logs.txt, snapshot_failure.JPG VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot() to VolumeServiceImpl.takeSnapshot(), you’ll notice that ANY exception that is thrown inside of SnapshotManager.takeSnapshot() is simply caught and ignored. Back up in VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(), JobInfo.Status.SUCCEEDED is ALWAYS returned, regardless of the snapshot result. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-5641: - Attachment: CS_4.2_5641.JPG Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_4.2_5641.JPG, CS_master_5641.JPG Local disk usage on storage pool view don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923733#comment-13923733 ] Namita Chaudhari commented on CLOUDSTACK-5641: -- Hi Nitin, I tried this with 4.2 and 4.4 versions. I referred the storage pool details as you mentioned above. I can see the Disk Total and Disk Allocated. Please find the attached snapshot (CS_4.2_5641.jpg) Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_4.2_5641.JPG, CS_master_5641.JPG Local disk usage on storage pool view don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari resolved CLOUDSTACK-5641. -- Resolution: Cannot Reproduce Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_4.2_5641.JPG, CS_master_5641.JPG Local disk usage on storage pool view don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6035) error when displaying firewall rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-6035: - Assignee: (was: Namita Chaudhari) error when displaying firewall rules Key: CLOUDSTACK-6035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6035 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Environment: ACS 4.2.1 after upgrade from 3.0.2 Reporter: Tomasz Zieba Attachments: CS_firewall_4.2.JPG, cloudstack_ui_firewall_error.JPG After upgrade from 3.0.2 to 4.2.1. In version 4.2.1 there was an error when displaying firewall rules. If the number of rules is too high UI displays an error (screenshot attached). In the illustrated case it is 26 rules. There wasn't this bug in 3.0.2 version. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912790#comment-13912790 ] Namita Chaudhari commented on CLOUDSTACK-5641: -- Mail to Nitin: I tried this issue on master and I see the local storage is displayed in the admin's webui. In the storage pool view, though the capacity_type = 3, it does not affect the local storage that is displayed in the UI as shown in the screenshot attached to the jira. I was trying to figure out that is there any other view from which we get this data. Can you please verify the screenshot and let me know is it the same local storage you are looking for in UI? Please let me know your comments. Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-5641: - Attachment: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911575#comment-13911575 ] Namita Chaudhari commented on CLOUDSTACK-5641: -- In storage pool view, when the capacity_type = 3, the disk_used_capacity is NULL, but the local storage displayed on the UI is not affected. mysql select * from storage_pool_view \G; *** 1. row *** id: 1 uuid: 9f3f9262-3f77-09cc-2df7-0d8475676260 name: devcloud Local Storage status: Up path: ext pool_type: EXT host_address: 192.168.56.10 created: 2013-10-30 13:11:02 removed: NULL capacity_bytes: 158533136384 capacity_iops: NULL scope: HOST hypervisor: NULL storage_provider_name: DefaultPrimary cluster_id: 1 cluster_uuid: a07d10c6-8108-4aa5-b5b7-cb455589e815 cluster_name: test000 cluster_type: CloudManaged data_center_id: 1 data_center_uuid: eb093781-6728-470a-89e9-1b2ba0d99742 data_center_name: DevCloud0 data_center_type: Basic pod_id: 1 pod_uuid: db4ed361-cc29-480c-a57a-d2490ee74ce2 pod_name: test00 tag: NULL disk_used_capacity: null disk_reserved_capacity: NULL job_id: NULL job_uuid: NULL job_status: NULL job_account_id: NULL 1 row in set (0.00 sec) Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Issue Comment Deleted] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-5641: - Comment: was deleted (was: In storage pool view, when the capacity_type = 3, the disk_used_capacity is NULL, but the local storage displayed on the UI is not affected. mysql select * from storage_pool_view \G; *** 1. row *** id: 1 uuid: 9f3f9262-3f77-09cc-2df7-0d8475676260 name: devcloud Local Storage status: Up path: ext pool_type: EXT host_address: 192.168.56.10 created: 2013-10-30 13:11:02 removed: NULL capacity_bytes: 158533136384 capacity_iops: NULL scope: HOST hypervisor: NULL storage_provider_name: DefaultPrimary cluster_id: 1 cluster_uuid: a07d10c6-8108-4aa5-b5b7-cb455589e815 cluster_name: test000 cluster_type: CloudManaged data_center_id: 1 data_center_uuid: eb093781-6728-470a-89e9-1b2ba0d99742 data_center_name: DevCloud0 data_center_type: Basic pod_id: 1 pod_uuid: db4ed361-cc29-480c-a57a-d2490ee74ce2 pod_name: test00 tag: NULL disk_used_capacity: null disk_reserved_capacity: NULL job_id: NULL job_uuid: NULL job_status: NULL job_account_id: NULL 1 row in set (0.00 sec)) Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911586#comment-13911586 ] Namita Chaudhari commented on CLOUDSTACK-5641: -- In storage pool view, when the capacity_type = 3, the disk_used_capacity is NULL, but the local storage displayed on the UI is not affected. mysql select * from storage_pool_view \G; id: 1 uuid: 9f3f9262-3f77-09cc-2df7-0d8475676260 name: devcloud Local Storage status: Up path: ext pool_type: EXT host_address: 192.168.56.10 created: 2013-10-30 13:11:02 removed: NULL capacity_bytes: 158533136384 capacity_iops: NULL scope: HOST hypervisor: NULL storage_provider_name: DefaultPrimary cluster_id: 1 cluster_uuid: a07d10c6-8108-4aa5-b5b7-cb455589e815 cluster_name: test000 cluster_type: CloudManaged data_center_id: 1 data_center_uuid: eb093781-6728-470a-89e9-1b2ba0d99742 data_center_name: DevCloud0 data_center_type: Basic pod_id: 1 pod_uuid: db4ed361-cc29-480c-a57a-d2490ee74ce2 pod_name: test00 tag: NULL disk_used_capacity: NULL disk_reserved_capacity: NULL job_id: NULL job_uuid: NULL job_status: NULL job_account_id: NULL 1 row in set (0.00 sec) Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911588#comment-13911588 ] Namita Chaudhari commented on CLOUDSTACK-5641: -- In storage pool view, when the capacity_type = 3, the disk_used_capacity is NULL, but the local storage displayed on the UI is not affected. mysql select * from storage_pool_view \G; id: 1 uuid: 9f3f9262-3f77-09cc-2df7-0d8475676260 name: devcloud Local Storage status: Up path: ext pool_type: EXT host_address: 192.168.56.10 created: 2013-10-30 13:11:02 removed: NULL capacity_bytes: 158533136384 capacity_iops: NULL scope: HOST hypervisor: NULL storage_provider_name: DefaultPrimary cluster_id: 1 cluster_uuid: a07d10c6-8108-4aa5-b5b7-cb455589e815 cluster_name: test000 cluster_type: CloudManaged data_center_id: 1 data_center_uuid: eb093781-6728-470a-89e9-1b2ba0d99742 data_center_name: DevCloud0 data_center_type: Basic pod_id: 1 pod_uuid: db4ed361-cc29-480c-a57a-d2490ee74ce2 pod_name: test00 tag: NULL disk_used_capacity: NULL disk_reserved_capacity: NULL job_id: NULL job_uuid: NULL job_status: NULL job_account_id: NULL 1 row in set (0.00 sec) Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911586#comment-13911586 ] Namita Chaudhari edited comment on CLOUDSTACK-5641 at 2/25/14 1:51 PM: --- In storage pool view, when the capacity_type = 3, the disk_used_capacity is NULL, but the local storage displayed on the UI is not affected. mysql select * from storage_pool_view \G;\ *** 1. row *** id: 1 uuid: 9f3f9262-3f77-09cc-2df7-0d8475676260 name: devcloud Local Storage status: Up path: ext pool_type: EXT host_address: 192.168.56.10 created: 2013-10-30 13:11:02 removed: NULL capacity_bytes: 158533136384 capacity_iops: NULL scope: HOST hypervisor: NULL storage_provider_name: DefaultPrimary cluster_id: 1 cluster_uuid: a07d10c6-8108-4aa5-b5b7-cb455589e815 cluster_name: test000 cluster_type: CloudManaged data_center_id: 1 data_center_uuid: eb093781-6728-470a-89e9-1b2ba0d99742 data_center_name: DevCloud0 data_center_type: Basic pod_id: 1 pod_uuid: db4ed361-cc29-480c-a57a-d2490ee74ce2 pod_name: test00 tag: NULL disk_used_capacity: NULL disk_reserved_capacity: NULL job_id: NULL job_uuid: NULL job_status: NULL job_account_id: NULL 1 row in set (0.00 sec) was (Author: namita.chaudh...@sungard.com): In storage pool view, when the capacity_type = 3, the disk_used_capacity is NULL, but the local storage displayed on the UI is not affected. mysql select * from storage_pool_view \G; id: 1 uuid: 9f3f9262-3f77-09cc-2df7-0d8475676260 name: devcloud Local Storage status: Up path: ext pool_type: EXT host_address: 192.168.56.10 created: 2013-10-30 13:11:02 removed: NULL capacity_bytes: 158533136384 capacity_iops: NULL scope: HOST hypervisor: NULL storage_provider_name: DefaultPrimary cluster_id: 1 cluster_uuid: a07d10c6-8108-4aa5-b5b7-cb455589e815 cluster_name: test000 cluster_type: CloudManaged data_center_id: 1 data_center_uuid: eb093781-6728-470a-89e9-1b2ba0d99742 data_center_name: DevCloud0 data_center_type: Basic pod_id: 1 pod_uuid: db4ed361-cc29-480c-a57a-d2490ee74ce2 pod_name: test00 tag: NULL disk_used_capacity: NULL disk_reserved_capacity: NULL job_id: NULL job_uuid: NULL job_status: NULL job_account_id: NULL 1 row in set (0.00 sec) Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Issue Comment Deleted] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-5641: - Comment: was deleted (was: In storage pool view, when the capacity_type = 3, the disk_used_capacity is NULL, but the local storage displayed on the UI is not affected. mysql select * from storage_pool_view \G;\ *** 1. row *** id: 1 uuid: 9f3f9262-3f77-09cc-2df7-0d8475676260 name: devcloud Local Storage status: Up path: ext pool_type: EXT host_address: 192.168.56.10 created: 2013-10-30 13:11:02 removed: NULL capacity_bytes: 158533136384 capacity_iops: NULL scope: HOST hypervisor: NULL storage_provider_name: DefaultPrimary cluster_id: 1 cluster_uuid: a07d10c6-8108-4aa5-b5b7-cb455589e815 cluster_name: test000 cluster_type: CloudManaged data_center_id: 1 data_center_uuid: eb093781-6728-470a-89e9-1b2ba0d99742 data_center_name: DevCloud0 data_center_type: Basic pod_id: 1 pod_uuid: db4ed361-cc29-480c-a57a-d2490ee74ce2 pod_name: test00 tag: NULL disk_used_capacity: NULL disk_reserved_capacity: NULL job_id: NULL job_uuid: NULL job_status: NULL job_account_id: NULL 1 row in set (0.00 sec)) Local disk usage on host don't show up in the admin's webui --- Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Attachments: CS_master_5641.JPG Local disk usage on host don't show up in the admin's webui. I have local storage enabled in the environment. I have VMs on the storage but since upgrading to 4.2 the UI does not show space utilization on the local storage. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-6035) error when displaying firewall rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari updated CLOUDSTACK-6035: - Attachment: CS_firewall_4.2.JPG error when displaying firewall rules Key: CLOUDSTACK-6035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6035 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Environment: ACS 4.2.1 after upgrade from 3.0.2 Reporter: Tomasz Zieba Assignee: Namita Chaudhari Attachments: CS_firewall_4.2.JPG, cloudstack_ui_firewall_error.JPG After upgrade from 3.0.2 to 4.2.1. In version 4.2.1 there was an error when displaying firewall rules. If the number of rules is too high UI displays an error (screenshot attached). In the illustrated case it is 26 rules. There wasn't this bug in 3.0.2 version. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-6035) error when displaying firewall rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906824#comment-13906824 ] Namita Chaudhari commented on CLOUDSTACK-6035: -- I tried reproducing the bug on new deployment of 4.2 version. Following are the steps I followed: 1) Login to UI 2) Go to Network-Select view: Security groups - Select the security group where we want to create the firewall rules - select Ingress Rule tab - added the firewall rules by CIDR. I created 30 firewall rules and UI did not displayed the error popup while displaying the firewall rules. I have attached the screenshot (CS_firewall_4.2.jpg). error when displaying firewall rules Key: CLOUDSTACK-6035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6035 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Environment: ACS 4.2.1 after upgrade from 3.0.2 Reporter: Tomasz Zieba Assignee: Namita Chaudhari Attachments: CS_firewall_4.2.JPG, cloudstack_ui_firewall_error.JPG After upgrade from 3.0.2 to 4.2.1. In version 4.2.1 there was an error when displaying firewall rules. If the number of rules is too high UI displays an error (screenshot attached). In the illustrated case it is 26 rules. There wasn't this bug in 3.0.2 version. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-6035) error when displaying firewall rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906824#comment-13906824 ] Namita Chaudhari edited comment on CLOUDSTACK-6035 at 2/20/14 10:09 AM: -- First approach I tried reproducing the bug on new deployment of 4.2 version. Following are the steps I followed: 1) Login to UI 2) Go to Network-Select view: Security groups - Select the security group where we want to create the firewall rules - select Ingress Rule tab - added the firewall rules by CIDR. I created 30 firewall rules and UI did not displayed the error popup while displaying the firewall rules. I have attached the screenshot (CS_firewall_4.2.jpg). -- The second approach: I am going to try to reproduce this issue by upgrading the version and creating n number of firewall rules. (around 30 rules). was (Author: namita.chaudh...@sungard.com): I tried reproducing the bug on new deployment of 4.2 version. Following are the steps I followed: 1) Login to UI 2) Go to Network-Select view: Security groups - Select the security group where we want to create the firewall rules - select Ingress Rule tab - added the firewall rules by CIDR. I created 30 firewall rules and UI did not displayed the error popup while displaying the firewall rules. I have attached the screenshot (CS_firewall_4.2.jpg). error when displaying firewall rules Key: CLOUDSTACK-6035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6035 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Environment: ACS 4.2.1 after upgrade from 3.0.2 Reporter: Tomasz Zieba Assignee: Namita Chaudhari Attachments: CS_firewall_4.2.JPG, cloudstack_ui_firewall_error.JPG After upgrade from 3.0.2 to 4.2.1. In version 4.2.1 there was an error when displaying firewall rules. If the number of rules is too high UI displays an error (screenshot attached). In the illustrated case it is 26 rules. There wasn't this bug in 3.0.2 version. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-6035) error when displaying firewall rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari reassigned CLOUDSTACK-6035: Assignee: Namita Chaudhari error when displaying firewall rules Key: CLOUDSTACK-6035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6035 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Environment: ACS 4.2.1 after upgrade from 3.0.2 Reporter: Tomasz Zieba Assignee: Namita Chaudhari Attachments: cloudstack_ui_firewall_error.JPG After upgrade from 3.0.2 to 4.2.1. In version 4.2.1 there was an error when displaying firewall rules. If the number of rules is too high UI displays an error (screenshot attached). In the illustrated case it is 26 rules. There wasn't this bug in 3.0.2 version. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
