[jira] [Resolved] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7720. -- Resolution: Fixed No IP Address Validation for Acquire new secondary IP - Key: CLOUDSTACK-7720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps: 1. Go to Instances -- NICs tab. 2. Click on the View Secondary IPs 3. Click on Acquire new secondary IP There is No IP address validation for Acquire new secondary IP. Additionally, this field should be a required field. Clicking Ok generates an IP, but it can be confusing to the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy closed CLOUDSTACK-7720. No IP Address Validation for Acquire new secondary IP - Key: CLOUDSTACK-7720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps: 1. Go to Instances -- NICs tab. 2. Click on the View Secondary IPs 3. Click on Acquire new secondary IP There is No IP address validation for Acquire new secondary IP. Additionally, this field should be a required field. Clicking Ok generates an IP, but it can be confusing to the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-3528) [UI]list calls are in the processing state forever with invalid name provided with Account name search filter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-3528. -- Resolution: Fixed [UI]list calls are in the processing state forever with invalid name provided with Account name search filter -- Key: CLOUDSTACK-3528 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3528 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Assignee: Gabor Apati-Nagy Fix For: 4.6.0 Attachments: UIlistevents.png, UIlistinstances.png, UIlistvolumes.png Steps: 1. Access Instances page 2. Click on Search Filter options 3. Provide wrong account name and tried to search instances owned by this account 4. It failed with message saying no instances were found. But UI remains in the processing state forever This behavior is observed with other list calls , EX: List Events, List Volumes ( All with invalid account name in the search filter) Note: Attached snapshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7875) [UI] Wrong format check is being made on Create VPC box - DNS domain Information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206312#comment-14206312 ] Gabor Apati-Nagy commented on CLOUDSTACK-7875: -- This is regression caused by CLOUDSTACK-7765. I am removing the IPv4 validation from the DNS field, so that the original behavior will be restored. (The API validates this field.) [UI] Wrong format check is being made on Create VPC box - DNS domain Information Key: CLOUDSTACK-7875 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7875 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Gabor Apati-Nagy Priority: Blocker Fix For: 4.5.0 Attachments: Capture5.PNG Currently, We are checking the DNS name with IPV4 format which is incorrect. DNS name needs to conform with FQDN format and not with IPV4 format. The User is currently blocked and is not allowed to proceed forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7875) [UI] Wrong format check is being made on Create VPC box - DNS domain Information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7875: - Status: Reviewable (was: In Progress) [UI] Wrong format check is being made on Create VPC box - DNS domain Information Key: CLOUDSTACK-7875 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7875 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Gabor Apati-Nagy Priority: Blocker Fix For: 4.5.0 Attachments: Capture5.PNG Currently, We are checking the DNS name with IPV4 format which is incorrect. DNS name needs to conform with FQDN format and not with IPV4 format. The User is currently blocked and is not allowed to proceed forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7875) [UI] Wrong format check is being made on Create VPC box - DNS domain Information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7875. -- Resolution: Fixed [UI] Wrong format check is being made on Create VPC box - DNS domain Information Key: CLOUDSTACK-7875 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7875 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Gabor Apati-Nagy Priority: Blocker Fix For: 4.5.0 Attachments: Capture5.PNG Currently, We are checking the DNS name with IPV4 format which is incorrect. DNS name needs to conform with FQDN format and not with IPV4 format. The User is currently blocked and is not allowed to proceed forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3528) [UI]list calls are in the processing state forever with invalid name provided with Account name search filter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-3528: - Status: Reviewable (was: In Progress) [UI]list calls are in the processing state forever with invalid name provided with Account name search filter -- Key: CLOUDSTACK-3528 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3528 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Attachments: UIlistevents.png, UIlistinstances.png, UIlistvolumes.png Steps: 1. Access Instances page 2. Click on Search Filter options 3. Provide wrong account name and tried to search instances owned by this account 4. It failed with message saying no instances were found. But UI remains in the processing state forever This behavior is observed with other list calls , EX: List Events, List Volumes ( All with invalid account name in the search filter) Note: Attached snapshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3528) [UI]list calls are in the processing state forever with invalid name provided with Account name search filter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-3528: - Fix Version/s: (was: 4.4.0) 4.6.0 [UI]list calls are in the processing state forever with invalid name provided with Account name search filter -- Key: CLOUDSTACK-3528 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3528 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Assignee: Gabor Apati-Nagy Fix For: 4.6.0 Attachments: UIlistevents.png, UIlistinstances.png, UIlistvolumes.png Steps: 1. Access Instances page 2. Click on Search Filter options 3. Provide wrong account name and tried to search instances owned by this account 4. It failed with message saying no instances were found. But UI remains in the processing state forever This behavior is observed with other list calls , EX: List Events, List Volumes ( All with invalid account name in the search filter) Note: Attached snapshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-3528) [UI]list calls are in the processing state forever with invalid name provided with Account name search filter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reassigned CLOUDSTACK-3528: Assignee: Gabor Apati-Nagy [UI]list calls are in the processing state forever with invalid name provided with Account name search filter -- Key: CLOUDSTACK-3528 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3528 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Attachments: UIlistevents.png, UIlistinstances.png, UIlistvolumes.png Steps: 1. Access Instances page 2. Click on Search Filter options 3. Provide wrong account name and tried to search instances owned by this account 4. It failed with message saying no instances were found. But UI remains in the processing state forever This behavior is observed with other list calls , EX: List Events, List Volumes ( All with invalid account name in the search filter) Note: Attached snapshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7838) UI - Dashboard should be more clear in representing what storage and Primary storage allocated capacities mean.
Gabor Apati-Nagy created CLOUDSTACK-7838: Summary: UI - Dashboard should be more clear in representing what storage and Primary storage allocated capacities mean. Key: CLOUDSTACK-7838 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7838 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: pre-4.0.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Make the wordings better on the Resources tab of a Zone. Storage - Primary Storage Used CPU - CPU allocated Memory - Memory Allocated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7838) UI - Dashboard should have more clean category names
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7838: - Summary: UI - Dashboard should have more clean category names (was: UI - Dashboard should be more clear in representing what storage and Primary storage allocated capacities mean.) UI - Dashboard should have more clean category names Key: CLOUDSTACK-7838 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7838 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: pre-4.0.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Make the wordings better on the Resources tab of a Zone. Storage - Primary Storage Used CPU - CPU allocated Memory - Memory Allocated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7838) UI - Update category names on Resources tab of a Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7838: - Summary: UI - Update category names on Resources tab of a Zone (was: UI - Dashboard should have more clean category names) UI - Update category names on Resources tab of a Zone - Key: CLOUDSTACK-7838 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7838 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: pre-4.0.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Make the wordings better on the Resources tab of a Zone. Storage - Primary Storage Used CPU - CPU allocated Memory - Memory Allocated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7838) UI - Update category names on Resources tab of a Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7838: - Component/s: UI UI - Update category names on Resources tab of a Zone - Key: CLOUDSTACK-7838 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7838 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: pre-4.0.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Make the wordings better on the Resources tab of a Zone. Storage - Primary Storage Used CPU - CPU allocated Memory - Memory Allocated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7840) UI control tip for 'Add Primary Storage' - 'Provider' seems wrong
Gabor Apati-Nagy created CLOUDSTACK-7840: Summary: UI control tip for 'Add Primary Storage' - 'Provider' seems wrong Key: CLOUDSTACK-7840 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7840 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 The Control Tip that is displayed when the user opens the 'Add Primary Storage' dialog and then clicks on 'Provider' doesn't seem to be correct - it seems to be the text that is displayed when selecting a Zone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7840) UI control tip for 'Add Primary Storage' - 'Provider' seems wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7840: - Status: Reviewable (was: In Progress) UI control tip for 'Add Primary Storage' - 'Provider' seems wrong -- Key: CLOUDSTACK-7840 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7840 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 The Control Tip that is displayed when the user opens the 'Add Primary Storage' dialog and then clicks on 'Provider' doesn't seem to be correct - it seems to be the text that is displayed when selecting a Zone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7838) UI - Update category names on Resources tab of a Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7838: - Status: Reviewable (was: In Progress) UI - Update category names on Resources tab of a Zone - Key: CLOUDSTACK-7838 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7838 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: pre-4.0.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Make the wordings better on the Resources tab of a Zone. Storage - Primary Storage Used CPU - CPU allocated Memory - Memory Allocated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7402) [UI] no option to delete or copy template across zone for registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7402: - Issue Type: Bug (was: Improvement) [UI] no option to delete or copy template across zone for registered template - Key: CLOUDSTACK-7402 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7402 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: shweta agarwal Fix For: Future Attachments: temp.png Repro steps: Register a template . Once its ready notice there is no command button to delete this template Also there is not command option to copy template across zone Attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7402) [UI] no option to delete or copy template across zone for registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194557#comment-14194557 ] Gabor Apati-Nagy commented on CLOUDSTACK-7402: -- I suggest we close this as By design, because the Delete and Copy Template functions are per-zone and they are no longer on the Details tab, but these are accessible on the Zones tab. This is because of CLOUDSTACK-6565. Shweta, please reopen if the followings does not work when you opened the template details: -Go to Zones tab -Select a Zone -You will see the delete and copy button there. [UI] no option to delete or copy template across zone for registered template - Key: CLOUDSTACK-7402 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7402 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: shweta agarwal Fix For: Future Attachments: temp.png Repro steps: Register a template . Once its ready notice there is no command button to delete this template Also there is not command option to copy template across zone Attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7402) [UI] no option to delete or copy template across zone for registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7402. -- Resolution: Won't Fix [UI] no option to delete or copy template across zone for registered template - Key: CLOUDSTACK-7402 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7402 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: shweta agarwal Fix For: Future Attachments: temp.png Repro steps: Register a template . Once its ready notice there is no command button to delete this template Also there is not command option to copy template across zone Attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7766) Field Validations Missing for Ingress and Egress Rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7766. -- Resolution: Fixed Field Validations Missing for Ingress and Egress Rules -- Key: CLOUDSTACK-7766 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7766 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps- 1. For a Network-Security groups, go to the Ingress Rule (or Egress Rule) tab. There are no Field Validations for the Start Port, End Port and CIDR fields. This issue exists for both: CIDR and Account. Additionally, the same applies for both: Ingress and Egress rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7765) Field Validations Missing for VPC IP Address Fields
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7765. -- Resolution: Fixed Field Validations Missing for VPC IP Address Fields --- Key: CLOUDSTACK-7765 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7765 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps - 1. Go to the Networks section 2. Click on Network-VPC and click Add VPC There are no IP address validations in the VPC creation form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7659) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7659. -- Resolution: Fixed UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. -- Key: CLOUDSTACK-7659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7659 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Update the LICENSE file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7764) No IP Address Validations when Adding Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7764. -- Resolution: Fixed No IP Address Validations when Adding Networks -- Key: CLOUDSTACK-7764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7764 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps - 1. Go to the Network tab under Zones. 2. Click Add guest network to add a new network. There are no field validations for -IPv4 Gateway -IPv4 Netmask -IPv4 Start IP -IPv4 End IP -IPv6 Gateway -IPv6 CIDR -IPv6 Start IP -IPv6 End IP on the form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7718) No Field Validations on Zone Form
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7718. -- Resolution: Fixed No Field Validations on Zone Form - Key: CLOUDSTACK-7718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194699#comment-14194699 ] Gabor Apati-Nagy commented on CLOUDSTACK-7720: -- Hi Jayapal, Good catch. I made it required accidently, I have just submitted a fix to ReviewBoard [1]. That will make it optional, but still validated when something has been entered. Cheers, Gabor No IP Address Validation for Acquire new secondary IP - Key: CLOUDSTACK-7720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps: 1. Go to Instances -- NICs tab. 2. Click on the View Secondary IPs 3. Click on Acquire new secondary IP There is No IP address validation for Acquire new secondary IP. Additionally, this field should be a required field. Clicking Ok generates an IP, but it can be confusing to the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194699#comment-14194699 ] Gabor Apati-Nagy edited comment on CLOUDSTACK-7720 at 11/3/14 4:31 PM: --- Hi Jayapal, Good catch. I made it required accidently, I have just submitted a fix to ReviewBoard [1]. That will make it optional, but still validated when something has been entered. Cheers, Gabor [1] https://reviews.apache.org/r/27527/ was (Author: gabora): Hi Jayapal, Good catch. I made it required accidently, I have just submitted a fix to ReviewBoard [1]. That will make it optional, but still validated when something has been entered. Cheers, Gabor No IP Address Validation for Acquire new secondary IP - Key: CLOUDSTACK-7720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps: 1. Go to Instances -- NICs tab. 2. Click on the View Secondary IPs 3. Click on Acquire new secondary IP There is No IP address validation for Acquire new secondary IP. Additionally, this field should be a required field. Clicking Ok generates an IP, but it can be confusing to the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7782) The 4.4.1 web UI is missing Acquire new IP address buton in NIC section
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190350#comment-14190350 ] Gabor Apati-Nagy commented on CLOUDSTACK-7782: -- I suggest the fix for CLOUDSTACK-6590 to be cherry picked to 4.4. (It is only in master at the moment.) That will fix this issue. The 4.4.1 web UI is missing Acquire new IP address buton in NIC section - Key: CLOUDSTACK-7782 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7782 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.1 Environment: CentOS 6.5 mgmt + HVs, Adv zone + SG Reporter: Nux Priority: Minor Labels: ui, web-ui Hello, In Basic and Adv+SG zone one can acquire new/secondary IPs for his instance, in the NIC section of an instance there used to be a button Acquire new IP or similar (alas I have upgraded and no longer have access to 4.3 UI who still had this). The NIC section was also listing any secondary IPs the instance may have had. The capability remains only in the API at this moment. This feature was useful and in use, please advise how to bring it back. Reported also on the dev mailing list here: http://www.mail-archive.com/dev@cloudstack.apache.org/msg36924.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7808) Typo in Zone Creation Wizard
Gabor Apati-Nagy created CLOUDSTACK-7808: Summary: Typo in Zone Creation Wizard Key: CLOUDSTACK-7808 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7808 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps to reproduce: 1. Go to the New Zone creation wizard 2. In Step 3 (Setup Network, Pod) look at the reference text on the upper part of the box. There is a typo in the text: CloudStack\'s is shown instead of CloudStack's. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7765) Field Validations Missing for VPC IP Address Fields
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7765: - Status: Reviewable (was: In Progress) Field Validations Missing for VPC IP Address Fields --- Key: CLOUDSTACK-7765 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7765 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps - 1. Go to the Networks section 2. Click on Network-VPC and click Add VPC There are no IP address validations in the VPC creation form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7766) Field Validations Missing for Ingress and Egress Rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7766: - Status: Reviewable (was: In Progress) Field Validations Missing for Ingress and Egress Rules -- Key: CLOUDSTACK-7766 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7766 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps- 1. For a Network-Security groups, go to the Ingress Rule (or Egress Rule) tab. There are no Field Validations for the Start Port, End Port and CIDR fields. This issue exists for both: CIDR and Account. Additionally, the same applies for both: Ingress and Egress rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7764) No IP Address Validations when Adding Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7764: - Status: Reviewable (was: In Progress) No IP Address Validations when Adding Networks -- Key: CLOUDSTACK-7764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7764 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps - 1. Go to the Network tab under Zones. 2. Click Add guest network to add a new network. There are no field validations for -IPv4 Gateway -IPv4 Netmask -IPv4 Start IP -IPv4 End IP -IPv6 Gateway -IPv6 CIDR -IPv6 Start IP -IPv6 End IP on the form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7808) Typo in Zone Creation Wizard
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7808: - Status: Reviewable (was: In Progress) Typo in Zone Creation Wizard Key: CLOUDSTACK-7808 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7808 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps to reproduce: 1. Go to the New Zone creation wizard 2. In Step 3 (Setup Network, Pod) look at the reference text on the upper part of the box. There is a typo in the text: CloudStack\'s is shown instead of CloudStack's. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7659) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7659: - Description: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Update the LICENSE file. was: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Update the LICESE file. UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. -- Key: CLOUDSTACK-7659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7659 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Update the LICENSE file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7764) No IP Address Validations when Adding Networks
Gabor Apati-Nagy created CLOUDSTACK-7764: Summary: No IP Address Validations when Adding Networks Key: CLOUDSTACK-7764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7764 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps - 1. Go to the Network tab under Zones. 2. Click Add guest network to add a new network. There are no field validations for -IPv4 Gateway -IPv4 Netmask -IPv4 Start IP -IPv4 End IP -IPv6 Gateway -IPv6 CIDR -IPv6 Start IP -IPv6 End IP on the form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7765) Field Validations Missing for VPC IP Address Fields
Gabor Apati-Nagy created CLOUDSTACK-7765: Summary: Field Validations Missing for VPC IP Address Fields Key: CLOUDSTACK-7765 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7765 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps - 1. Go to the Networks section 2. Click on Network-VPC and click Add VPC There are no IP address validations in the VPC creation form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7766) Field Validations Missing for Ingress and Egress Rules
Gabor Apati-Nagy created CLOUDSTACK-7766: Summary: Field Validations Missing for Ingress and Egress Rules Key: CLOUDSTACK-7766 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7766 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps- 1. For a Network-Security groups, go to the Ingress Rule (or Egress Rule) tab. There are no Field Validations for the Start Port, End Port and CIDR fields. This issue exists for both: CIDR and Account. Additionally, the same applies for both: Ingress and Egress rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7718) No Field Validations on Zone Form
Gabor Apati-Nagy created CLOUDSTACK-7718: Summary: No Field Validations on Zone Form Key: CLOUDSTACK-7718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. Refer to attached snapshot for details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7718) No Field Validations on Zone Form
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7718: - Description: 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. was: 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. Refer to attached snapshot for details. No Field Validations on Zone Form - Key: CLOUDSTACK-7718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP
Gabor Apati-Nagy created CLOUDSTACK-7720: Summary: No IP Address Validation for Acquire new secondary IP Key: CLOUDSTACK-7720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps: 1. Go to Instances -- NICs tab. 2. Click on the View Secondary IPs 3. Click on Acquire new secondary IP There is No IP address validation for Acquire new secondary IP. Additionally, this field should be a required field. Clicking Ok generates an IP, but it can be confusing to the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7718) No Field Validations on Zone Form
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7718: - Status: Reviewable (was: In Progress) No Field Validations on Zone Form - Key: CLOUDSTACK-7718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7659) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included.
Gabor Apati-Nagy created CLOUDSTACK-7659: Summary: UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Key: CLOUDSTACK-7659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7659 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Update the LICESE file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7659) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7659: - Status: Reviewable (was: In Progress) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. -- Key: CLOUDSTACK-7659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7659 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Update the LICESE file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7659) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153332#comment-14153332 ] Gabor Apati-Nagy commented on CLOUDSTACK-7659: -- Submitted to ReviewBoard: https://reviews.apache.org/r/26053/ UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. -- Key: CLOUDSTACK-7659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7659 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included. Update the LICESE file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7561: - Status: Reviewable (was: In Progress) UI: After creating a new account, the Add Account dialog remains open --- Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7561. -- Resolution: Fixed UI: After creating a new account, the Add Account dialog remains open --- Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy closed CLOUDSTACK-7561. UI: After creating a new account, the Add Account dialog remains open --- Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7562) Details page for disk offerings only show details for write performance
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7562. -- Resolution: Fixed Details page for disk offerings only show details for write performance --- Key: CLOUDSTACK-7562 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7562 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Details for disk offerings only show details for write performance Disk Write Rate(BPS) Disk Write Rate(IOPS) are both repeated twice, should be read and write ( see screenshot) REPRO Home - Service Offerings - Disk Offerings - select any storage offering Expected: Disk Write Rate (BPS) Disk Read Rate (BPS) Disk Write Rate (IOPS) Disk Read Rate (IOPS) Actual result: Disk Write Rate (BPS) Disk Write Rate (BPS) Disk Write Rate (IOPS) Disk Write Rate (IOPS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7562) Details page for disk offerings only show details for write performance
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7562: - Status: Reviewable (was: In Progress) Details page for disk offerings only show details for write performance --- Key: CLOUDSTACK-7562 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7562 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Details for disk offerings only show details for write performance Disk Write Rate(BPS) Disk Write Rate(IOPS) are both repeated twice, should be read and write ( see screenshot) REPRO Home - Service Offerings - Disk Offerings - select any storage offering Expected: Disk Write Rate (BPS) Disk Read Rate (BPS) Disk Write Rate (IOPS) Disk Read Rate (IOPS) Actual result: Disk Write Rate (BPS) Disk Write Rate (BPS) Disk Write Rate (IOPS) Disk Write Rate (IOPS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reopened CLOUDSTACK-7561: -- Closed by accident, moving back to Fixed/Resolved now... UI: After creating a new account, the Add Account dialog remains open --- Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7561. -- Resolution: Fixed UI: After creating a new account, the Add Account dialog remains open --- Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7561: - Fix Version/s: 4.5.0 UI: After creating a new account, the Add Account dialog remains open --- Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
Gabor Apati-Nagy created CLOUDSTACK-7561: Summary: UI: After creating a new account, the Add Account dialog remains open Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 (see attached screenshot). Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7561) UI: After creating a new account, the Add Account dialog remains open
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7561: - Description: Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. was: Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 (see attached screenshot). Note: Clicking the Add button again will cause a User already exists error. UI: After creating a new account, the Add Account dialog remains open --- Key: CLOUDSTACK-7561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7561 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Go to HomeAccounts. Click Add Account to add a new account. Fill out the required fields. Then click Add to create a new Account. Result: The account is created, but the Add Account dialog remains open and the Accounts view is not refreshed. Running in Chrome, The following error is observed: Uncaught TypeError: undefined is not a function, accountsWizard.js:260 Note: Clicking the Add button again will cause a User already exists error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7562) Details page for disk offerings only show details for write performance
Gabor Apati-Nagy created CLOUDSTACK-7562: Summary: Details page for disk offerings only show details for write performance Key: CLOUDSTACK-7562 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7562 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Details for disk offerings only show details for write performance Disk Write Rate(BPS) Disk Write Rate(IOPS) are both repeated twice, should be read and write ( see screenshot) REPRO Home - Service Offerings - Disk Offerings - select any storage offering Expected: Disk Write Rate (BPS) Disk Read Rate (BPS) Disk Write Rate (IOPS) Disk Read Rate (IOPS) Actual result: Disk Write Rate (BPS) Disk Write Rate (BPS) Disk Write Rate (IOPS) Disk Write Rate (IOPS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7463) UI: Domain Admin UI shows 'Add LDAP Users' button (should not be shown)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7463: - Status: Reviewable (was: In Progress) UI: Domain Admin UI shows 'Add LDAP Users' button (should not be shown) --- Key: CLOUDSTACK-7463 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7463 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Domain Admin UI shows the 'add ldap users' button. Trying to add LDAP users will show an empty screen (even if LDAP is configured) and an error will be displayed the given command does not exist or it is not available for user. This makes sense as Domain Admin cannot use the importLdapUsers API call, only ROOT Admin. The button should be removed for Domain Admins Steps to reproduce: 1) create LDAP integration 2) access as Domain Admin User of a sub-Domain 3) note the 'Add LDAP users' button 4) Try to add an LDAP user and note the error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7463) UI: Domain Admin UI shows 'Add LDAP Users' button (should not be shown)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-7463. -- Resolution: Fixed UI: Domain Admin UI shows 'Add LDAP Users' button (should not be shown) --- Key: CLOUDSTACK-7463 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7463 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Domain Admin UI shows the 'add ldap users' button. Trying to add LDAP users will show an empty screen (even if LDAP is configured) and an error will be displayed the given command does not exist or it is not available for user. This makes sense as Domain Admin cannot use the importLdapUsers API call, only ROOT Admin. The button should be removed for Domain Admins Steps to reproduce: 1) create LDAP integration 2) access as Domain Admin User of a sub-Domain 3) note the 'Add LDAP users' button 4) Try to add an LDAP user and note the error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-6803: - Status: Reviewable (was: In Progress) UI:QuickView: Unable to render Quick view overlay on VM snapshots - Key: CLOUDSTACK-6803 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Parth Jagirdar Assignee: Gabor Apati-Nagy Priority: Critical Attachments: qv_overlay.jpg Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. *** Click on the snapshot, observe that user is presented with a black screen. (Due to this behavior, raising bug severity to Critical, As this prevents user to perform operations on VM snapshot from the UI)) Screen attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117321#comment-14117321 ] Gabor Apati-Nagy commented on CLOUDSTACK-6803: -- This issue is not present in current version, it has already been fixed on (14t Jul 2014) by commit 36e5cc2b6a87d7d142edac9574e3faa13afb1253. I reproduced the issue by just reverting only this commit on the up-to-date version. UI:QuickView: Unable to render Quick view overlay on VM snapshots - Key: CLOUDSTACK-6803 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Parth Jagirdar Assignee: Gabor Apati-Nagy Priority: Critical Attachments: qv_overlay.jpg Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. *** Click on the snapshot, observe that user is presented with a black screen. (Due to this behavior, raising bug severity to Critical, As this prevents user to perform operations on VM snapshot from the UI)) Screen attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-6803. -- Resolution: Fixed UI:QuickView: Unable to render Quick view overlay on VM snapshots - Key: CLOUDSTACK-6803 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Parth Jagirdar Assignee: Gabor Apati-Nagy Priority: Critical Attachments: qv_overlay.jpg Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. *** Click on the snapshot, observe that user is presented with a black screen. (Due to this behavior, raising bug severity to Critical, As this prevents user to perform operations on VM snapshot from the UI)) Screen attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117321#comment-14117321 ] Gabor Apati-Nagy edited comment on CLOUDSTACK-6803 at 9/1/14 11:25 AM: --- This issue is not present in current version, it has already been fixed on (14t Jul 2014) by commit 36e5cc2b6a87d7d142edac9574e3faa13afb1253. I reproduced the issue by reverting only this commit on the up-to-date version. was (Author: gabora): This issue is not present in current version, it has already been fixed on (14t Jul 2014) by commit 36e5cc2b6a87d7d142edac9574e3faa13afb1253. I reproduced the issue by just reverting only this commit on the up-to-date version. UI:QuickView: Unable to render Quick view overlay on VM snapshots - Key: CLOUDSTACK-6803 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Parth Jagirdar Assignee: Gabor Apati-Nagy Priority: Critical Attachments: qv_overlay.jpg Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. *** Click on the snapshot, observe that user is presented with a black screen. (Due to this behavior, raising bug severity to Critical, As this prevents user to perform operations on VM snapshot from the UI)) Screen attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-1152) Missing tag in host-add.xml
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reassigned CLOUDSTACK-1152: Assignee: Gabor Apati-Nagy Missing tag in host-add.xml --- Key: CLOUDSTACK-1152 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1152 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Logan McNaughton Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.1.0 docs/en-US/host-add.xml is missing a closing /para, it is present in master and prevents docs from building -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1152) Missing tag in host-add.xml
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-1152: - Assignee: Jessica Tomechak (was: Gabor Apati-Nagy) Missing tag in host-add.xml --- Key: CLOUDSTACK-1152 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1152 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Logan McNaughton Assignee: Jessica Tomechak Priority: Minor Fix For: 4.1.0 docs/en-US/host-add.xml is missing a closing /para, it is present in master and prevents docs from building -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-1152) Missing tag in host-add.xml
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117475#comment-14117475 ] Gabor Apati-Nagy commented on CLOUDSTACK-1152: -- Assigned accidentally. Missing tag in host-add.xml --- Key: CLOUDSTACK-1152 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1152 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Logan McNaughton Assignee: Jessica Tomechak Priority: Minor Fix For: 4.1.0 docs/en-US/host-add.xml is missing a closing /para, it is present in master and prevents docs from building -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7462) UI: Tags buttons do not work on ACL List tab
Gabor Apati-Nagy created CLOUDSTACK-7462: Summary: UI: Tags buttons do not work on ACL List tab Key: CLOUDSTACK-7462 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7462 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Gabor Apati-Nagy Steps to reproduce: -Go to Network -Select VPC view from the dropdown -Create a VPC if there is none present -On a VPC, click on Configure button -If needed, proceed and set the minimal required settings (eg. tier) -Click on the Routers Network ACL Lists button, the ACLs are now listed -Click on any item to open its detail view -Select the ACL List Rules tab Click on the Edit tags button of any the existing entries in the grid Expected result: -Tag editor should appear and tags should be editable Actual result: -Tag editor appears, but empty. Missing features: list, add, remove tags. Note: -Tag editor has a Done button, so it can be closed and the user can proceed using the UI, however tags are not listable and editable. Loss of tags functionality. -The issue is seems to be related to CLOUDSTACK-5486. -Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7462) UI: Tags buttons do not work on ACL List tab
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7462: - Attachment: tags_jsonobj_empty.jpg TypeError: args.jsonObj is undefined data: args.jsonObj.tags UI: Tags buttons do not work on ACL List tab Key: CLOUDSTACK-7462 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7462 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Gabor Apati-Nagy Attachments: tags_jsonobj_empty.jpg Steps to reproduce: -Go to Network -Select VPC view from the dropdown -Create a VPC if there is none present -On a VPC, click on Configure button -If needed, proceed and set the minimal required settings (eg. tier) -Click on the Routers Network ACL Lists button, the ACLs are now listed -Click on any item to open its detail view -Select the ACL List Rules tab Click on the Edit tags button of any the existing entries in the grid Expected result: -Tag editor should appear and tags should be editable Actual result: -Tag editor appears, but empty. Missing features: list, add, remove tags. Note: -Tag editor has a Done button, so it can be closed and the user can proceed using the UI, however tags are not listable and editable. Loss of tags functionality. -The issue is seems to be related to CLOUDSTACK-5486. -Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7462) UI: Edit tags buttons do not work on ACL List tab
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7462: - Summary: UI: Edit tags buttons do not work on ACL List tab (was: UI: Tags buttons do not work on ACL List tab) UI: Edit tags buttons do not work on ACL List tab - Key: CLOUDSTACK-7462 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7462 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Gabor Apati-Nagy Attachments: tags_jsonobj_empty.jpg Steps to reproduce: -Go to Network -Select VPC view from the dropdown -Create a VPC if there is none present -On a VPC, click on Configure button -If needed, proceed and set the minimal required settings (eg. tier) -Click on the Routers Network ACL Lists button, the ACLs are now listed -Click on any item to open its detail view -Select the ACL List Rules tab Click on the Edit tags button of any the existing entries in the grid Expected result: -Tag editor should appear and tags should be editable Actual result: -Tag editor appears, but empty. Missing features: list, add, remove tags. Note: -Tag editor has a Done button, so it can be closed and the user can proceed using the UI, however tags are not listable and editable. Loss of tags functionality. -The issue is seems to be related to CLOUDSTACK-5486. -Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7463) UI: Domain Admin UI shows 'Add LDAP Users' button (should not be shown)
Gabor Apati-Nagy created CLOUDSTACK-7463: Summary: UI: Domain Admin UI shows 'Add LDAP Users' button (should not be shown) Key: CLOUDSTACK-7463 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7463 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: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.5.0 Domain Admin UI shows the 'add ldap users' button. Trying to add LDAP users will show an empty screen (even if LDAP is configured) and an error will be displayed the given command does not exist or it is not available for user. This makes sense as Domain Admin cannot use the importLdapUsers API call, only ROOT Admin. The button should be removed for Domain Admins Steps to reproduce: 1) create LDAP integration 2) access as Domain Admin User of a sub-Domain 3) note the 'Add LDAP users' button 4) Try to add an LDAP user and note the error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reassigned CLOUDSTACK-6803: Assignee: Gabor Apati-Nagy (was: Stephen Turner) UI:QuickView: Unable to render Quick view overlay on VM snapshots - Key: CLOUDSTACK-6803 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Parth Jagirdar Assignee: Gabor Apati-Nagy Priority: Critical Attachments: qv_overlay.jpg Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. *** Click on the snapshot, observe that user is presented with a black screen. (Due to this behavior, raising bug severity to Critical, As this prevents user to perform operations on VM snapshot from the UI)) Screen attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6732) [OVS][UI] Network Service Providers page displays two ovs providers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-6732: - Description: [OVS][UI] Network Service Providers page displays two ovs providers if there two zones and physical networks created with GRE isolation in both the zones. Steps to reproduce: 1.Bring up CS with two advanced zones using xen clusters 2.Create physical networks in both the zones using GRE isolation 3.From UI naviagate to Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers UI displays two OVS providers in enabled state one with name Ovs and another one with name OVS. Clicking on Ovs provider shows details of it whereas clicking on provider with name OVS gives java script issue and UI becomes unresponsive: TypeError: listViewArgs.onActionComplete is undefined detailViewArgs.data.onActionComplete = listViewArgs.onActionComplete; Attaching screen shots to describe both the issues. --- Problem (refined): --- Two OVS providers are displayed at Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers. The difference in the two OVS entries is only in capitalization. Clicking on the extra OVS causes exception. --- Root Cause Analysis: --- The code was not consistent in capitalization of the word OVS and that made some checks like Ovs==OVS failing. In consequence the OVS with different capitalization has been added and rendered to the UI as well. --- Proposed Solution: --- Reconciled capitalization issue, not adding Ovs twice. Notes for QA: The problem is more general than the above test case. In general, having one Advanced Zone with a Physical network with GRE isolation is enough to reproduce. was: [OVS][UI] Network Service Providers page displays two ovs providers if there two zones and physical networks created with GRE isolation in both the zones. Steps to reproduce: 1.Bring up CS with two advanced zones using xen clusters 2.Create physical networks in both the zones using GRE isolation 3.From UI naviagate to Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers UI displays two OVS providers in enabled state one with name Ovs and another one with name OVS. Clicking on Ovs provider shows details of it whereas clicking on provider with name OVS gives java script issue and UI becomes unresponsive: TypeError: listViewArgs.onActionComplete is undefined detailViewArgs.data.onActionComplete = listViewArgs.onActionComplete; Attaching screen shots to describe both the issues. [OVS][UI] Network Service Providers page displays two ovs providers --- Key: CLOUDSTACK-6732 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6732 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Assignee: Gabor Apati-Nagy Labels: ovs, ui Fix For: 4.4.0 Attachments: issue1.PNG, issue2.PNG [OVS][UI] Network Service Providers page displays two ovs providers if there two zones and physical networks created with GRE isolation in both the zones. Steps to reproduce: 1.Bring up CS with two advanced zones using xen clusters 2.Create physical networks in both the zones using GRE isolation 3.From UI naviagate to Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers UI displays two OVS providers in enabled state one with name Ovs and another one with name OVS. Clicking on Ovs provider shows details of it whereas clicking on provider with name OVS gives java script issue and UI becomes unresponsive: TypeError: listViewArgs.onActionComplete is undefined detailViewArgs.data.onActionComplete = listViewArgs.onActionComplete; Attaching screen shots to describe both the issues. --- Problem (refined): --- Two OVS providers are displayed at Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers. The difference in the two OVS entries is only in capitalization. Clicking on the extra OVS causes exception. --- Root Cause Analysis: --- The code was not consistent in capitalization of the word OVS and that made some checks like Ovs==OVS failing. In consequence the OVS with different capitalization has been added and rendered to the UI as well. --- Proposed Solution:
[jira] [Updated] (CLOUDSTACK-6732) [OVS][UI] Network Service Providers page displays two ovs providers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-6732: - Description: [OVS][UI] Network Service Providers page displays two ovs providers if there two zones and physical networks created with GRE isolation in both the zones. Steps to reproduce: 1.Bring up CS with two advanced zones using xen clusters 2.Create physical networks in both the zones using GRE isolation 3.From UI naviagate to Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers UI displays two OVS providers in enabled state one with name Ovs and another one with name OVS. Clicking on Ovs provider shows details of it whereas clicking on provider with name OVS gives java script issue and UI becomes unresponsive: TypeError: listViewArgs.onActionComplete is undefined detailViewArgs.data.onActionComplete = listViewArgs.onActionComplete; Attaching screen shots to describe both the issues. === Developer review section: === Problem (refined): --- Two OVS providers are displayed at Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers. The difference in the two OVS entries is only in capitalization. Clicking on the extra OVS causes exception. Root Cause Analysis: --- The code was not consistent in capitalization of the word OVS and that made some checks like Ovs==OVS failing. In consequence the OVS with different capitalization has been added and rendered to the UI as well. Proposed Solution: --- Reconciled capitalization issue, not adding Ovs twice. Notes for QA: --- The problem is more general than the above test case. This means that it is easier to reproduce. In general, to be able to reproduce the issue the following setup is needed: - Advanced Zone with a Physical network with GRE isolation was: [OVS][UI] Network Service Providers page displays two ovs providers if there two zones and physical networks created with GRE isolation in both the zones. Steps to reproduce: 1.Bring up CS with two advanced zones using xen clusters 2.Create physical networks in both the zones using GRE isolation 3.From UI naviagate to Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers UI displays two OVS providers in enabled state one with name Ovs and another one with name OVS. Clicking on Ovs provider shows details of it whereas clicking on provider with name OVS gives java script issue and UI becomes unresponsive: TypeError: listViewArgs.onActionComplete is undefined detailViewArgs.data.onActionComplete = listViewArgs.onActionComplete; Attaching screen shots to describe both the issues. --- Problem (refined): --- Two OVS providers are displayed at Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers. The difference in the two OVS entries is only in capitalization. Clicking on the extra OVS causes exception. --- Root Cause Analysis: --- The code was not consistent in capitalization of the word OVS and that made some checks like Ovs==OVS failing. In consequence the OVS with different capitalization has been added and rendered to the UI as well. --- Proposed Solution: --- Reconciled capitalization issue, not adding Ovs twice. Notes for QA: The problem is more general than the above test case. In general, having one Advanced Zone with a Physical network with GRE isolation is enough to reproduce. [OVS][UI] Network Service Providers page displays two ovs providers --- Key: CLOUDSTACK-6732 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6732 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Assignee: Gabor Apati-Nagy Labels: ovs, ui Fix For: 4.4.0 Attachments: issue1.PNG, issue2.PNG [OVS][UI] Network Service Providers page displays two ovs providers if there two zones and physical networks created with GRE isolation in both the zones. Steps to reproduce: 1.Bring up CS with two advanced zones using xen clusters 2.Create physical networks in both the zones using GRE
[jira] [Updated] (CLOUDSTACK-6732) [OVS][UI] Network Service Providers page displays two ovs providers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-6732: - Labels: DEVREV ovs ui (was: ovs ui) [OVS][UI] Network Service Providers page displays two ovs providers --- Key: CLOUDSTACK-6732 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6732 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Assignee: Gabor Apati-Nagy Labels: DEVREV, ovs, ui Fix For: 4.4.0 Attachments: issue1.PNG, issue2.PNG [OVS][UI] Network Service Providers page displays two ovs providers if there two zones and physical networks created with GRE isolation in both the zones. Steps to reproduce: 1.Bring up CS with two advanced zones using xen clusters 2.Create physical networks in both the zones using GRE isolation 3.From UI naviagate to Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers UI displays two OVS providers in enabled state one with name Ovs and another one with name OVS. Clicking on Ovs provider shows details of it whereas clicking on provider with name OVS gives java script issue and UI becomes unresponsive: TypeError: listViewArgs.onActionComplete is undefined detailViewArgs.data.onActionComplete = listViewArgs.onActionComplete; Attaching screen shots to describe both the issues. === Developer review section: === Problem (refined): --- Two OVS providers are displayed at Home-Infrastructure- Zones-Adv-Physical Network 1-Network Service Providers. The difference in the two OVS entries is only in capitalization. Clicking on the extra OVS causes exception. Root Cause Analysis: --- The code was not consistent in capitalization of the word OVS and that made some checks like Ovs==OVS failing. In consequence the OVS with different capitalization has been added and rendered to the UI as well. Proposed Solution: --- Reconciled capitalization issue, not adding Ovs twice. Notes for QA: --- The problem is more general than the above test case. This means that it is easier to reproduce. In general, to be able to reproduce the issue the following setup is needed: - Advanced Zone with a Physical network with GRE isolation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6717) [OVS][UI]VPC network creation page does not display custom network offering created for vpc
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reassigned CLOUDSTACK-6717: Assignee: Sanjeev N (was: Gabor Apati-Nagy) Could you please provide the database dump for this issue? Thanks [OVS][UI]VPC network creation page does not display custom network offering created for vpc --- Key: CLOUDSTACK-6717 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6717 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072 Reporter: Sanjeev N Assignee: Sanjeev N Priority: Critical Fix For: 4.4.0 Attachments: vpc_tier.PNG [SDN][UI]VPC network creation page does not display custom network offering created for vpc Steps to Reproduce: 1.Bring up CS in advanced zone with xen cluster 2.Create physical network with GRE isolation 3.Create Region level vpc 4.Create isolated network offering for vpc with virtualnetworking service and ovs as the service provider 5.Enable the network offering 6.In region level vpc try to create tier with above created network offering Result: == Add tier in VPC page does not display the custom vpc offering created with ovs provider. It only shows the default vpc offerings in the drop down list. Attaching screen shot to describe the issue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6840) [OVS][UI] Ovs provider should not be displayed in NetworkServiceProviders if the physical network isolation type is VLAN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reassigned CLOUDSTACK-6840: Assignee: Jessica Wang (was: Gabor Apati-Nagy) I am assigning to Jessica as this is related to CS-6162. [OVS][UI] Ovs provider should not be displayed in NetworkServiceProviders if the physical network isolation type is VLAN Key: CLOUDSTACK-6840 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6840 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Environment: Latest build from 4.4. with commit 32bbc84db99d0e5f7f9b2a3fb41e4e783a2de350 Reporter: Sanjeev N Assignee: Jessica Wang Priority: Critical Labels: ovs Fix For: 4.4.0 Attachments: ovs_vlan.PNG [OVS][UI] Ovs provider should not be displayed in NetworkServiceProviders if the physical network isolation type is VLAN Steps to reproduce: == 1.Bring up CS in advanced zone with xen cluster 2.While creating physical network during zone creation choose VLAN as the isolation type 3.From UI navigate to Home-Infrastructure-Zones-CS-GRE-Physical Network 1-Network Service Providers Result: == NetworkServiceProviders page shows OVS as one of the providers and by default is in disabled state. Whereas API does not show OVS as one of the providers. Following is the API response: http://10.147.59.119:8096/client/api?command=listNetworkServiceProvidersphysicalnetworkid=e58d6d73-cd77-4917-875a-695f56a4b968 listnetworkserviceprovidersresponse cloud-stack-version=4.4.0-SNAPSHOTcount4/countnetworkserviceprovidernameInternalLbVm/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateEnabled/stateid223a1a51-c6a0-4239-ac82-f96290520669/idservicelistLb/servicelistcanenableindividualservicetrue/canenableindividualservice/networkserviceprovidernetworkserviceprovidernameVpcVirtualRouter/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateEnabled/stateid641ae03f-861b-4e20-8b59-333f0848207e/idservicelistVpn/servicelistservicelistDhcp/servicelistservicelistDns/servicelistservicelistGateway/servicelistservicelistLb/servicelistservicelistSourceNat/servicelistservicelistStaticNat/servicelistservicelistPortForwarding/servicelistservicelistUserData/servicelistcanenableindividualservicetrue/canenableindividualservice/networkserviceprovidernetworkserviceprovidernameSecurityGroupProvider/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateDisabled/stateid2414d618-ec08-4624-b16e-fd22e2326f24/idservicelistSecurityGroup/servicelistcanenableindividualservicefalse/canenableindividualservice/networkserviceprovidernetworkserviceprovidernameVirtualRouter/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateEnabled/stateiddae0a4b6-24a7-4d56-91bd-8f0f4919938e/idservicelistVpn/servicelistservicelistDhcp/servicelistservicelistDns/servicelistservicelistGateway/servicelistservicelistFirewall/servicelistservicelistLb/servicelistservicelistSourceNat/servicelistservicelistStaticNat/servicelistservicelistPortForwarding/servicelistservicelistUserData/servicelistcanenableindividualservicetrue/canenableindividualservice/networkserviceprovider/listnetworkserviceprovidersresponse DB entries from cloud db are as follows: mysql select * from physical_network_service_providers where physical_network_id=202; ++--+-+---+--+-+--+---+--+--+---+-+---+-+--++-+-+-+ | id | uuid | physical_network_id | provider_name | state| destination_physical_network_id | vpn_service_provided | dhcp_service_provided | dns_service_provided | gateway_service_provided | firewall_service_provided | source_nat_service_provided | load_balance_service_provided | static_nat_service_provided | port_forwarding_service_provided | user_data_service_provided | security_group_service_provided | networkacl_service_provided | removed |
[jira] [Commented] (CLOUDSTACK-6840) [OVS][UI] Ovs provider should not be displayed in NetworkServiceProviders if the physical network isolation type is VLAN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017616#comment-14017616 ] Gabor Apati-Nagy commented on CLOUDSTACK-6840: -- I have checked the UI code to make sure how it works currently. Yes, there is code to intentionally show Ovs (as disabled) even when there is no Ovs in the response. Could you tell me what is the expected behavior exactly? Are we supposed to show Ovs only when it is in the response? It seems that the current code to always show is there because of CLOUDSTACK-6162, [~jessicawang] or [~murali.reddy] could you please advise if I should change this or not? [OVS][UI] Ovs provider should not be displayed in NetworkServiceProviders if the physical network isolation type is VLAN Key: CLOUDSTACK-6840 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6840 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Environment: Latest build from 4.4. with commit 32bbc84db99d0e5f7f9b2a3fb41e4e783a2de350 Reporter: Sanjeev N Assignee: Gabor Apati-Nagy Priority: Critical Labels: ovs Fix For: 4.4.0 Attachments: ovs_vlan.PNG [OVS][UI] Ovs provider should not be displayed in NetworkServiceProviders if the physical network isolation type is VLAN Steps to reproduce: == 1.Bring up CS in advanced zone with xen cluster 2.While creating physical network during zone creation choose VLAN as the isolation type 3.From UI navigate to Home-Infrastructure-Zones-CS-GRE-Physical Network 1-Network Service Providers Result: == NetworkServiceProviders page shows OVS as one of the providers and by default is in disabled state. Whereas API does not show OVS as one of the providers. Following is the API response: http://10.147.59.119:8096/client/api?command=listNetworkServiceProvidersphysicalnetworkid=e58d6d73-cd77-4917-875a-695f56a4b968 listnetworkserviceprovidersresponse cloud-stack-version=4.4.0-SNAPSHOTcount4/countnetworkserviceprovidernameInternalLbVm/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateEnabled/stateid223a1a51-c6a0-4239-ac82-f96290520669/idservicelistLb/servicelistcanenableindividualservicetrue/canenableindividualservice/networkserviceprovidernetworkserviceprovidernameVpcVirtualRouter/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateEnabled/stateid641ae03f-861b-4e20-8b59-333f0848207e/idservicelistVpn/servicelistservicelistDhcp/servicelistservicelistDns/servicelistservicelistGateway/servicelistservicelistLb/servicelistservicelistSourceNat/servicelistservicelistStaticNat/servicelistservicelistPortForwarding/servicelistservicelistUserData/servicelistcanenableindividualservicetrue/canenableindividualservice/networkserviceprovidernetworkserviceprovidernameSecurityGroupProvider/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateDisabled/stateid2414d618-ec08-4624-b16e-fd22e2326f24/idservicelistSecurityGroup/servicelistcanenableindividualservicefalse/canenableindividualservice/networkserviceprovidernetworkserviceprovidernameVirtualRouter/namephysicalnetworkide58d6d73-cd77-4917-875a-695f56a4b968/physicalnetworkidstateEnabled/stateiddae0a4b6-24a7-4d56-91bd-8f0f4919938e/idservicelistVpn/servicelistservicelistDhcp/servicelistservicelistDns/servicelistservicelistGateway/servicelistservicelistFirewall/servicelistservicelistLb/servicelistservicelistSourceNat/servicelistservicelistStaticNat/servicelistservicelistPortForwarding/servicelistservicelistUserData/servicelistcanenableindividualservicetrue/canenableindividualservice/networkserviceprovider/listnetworkserviceprovidersresponse DB entries from cloud db are as follows: mysql select * from physical_network_service_providers where physical_network_id=202; ++--+-+---+--+-+--+---+--+--+---+-+---+-+--++-+-+-+ | id | uuid | physical_network_id | provider_name | state| destination_physical_network_id | vpn_service_provided | dhcp_service_provided | dns_service_provided | gateway_service_provided | firewall_service_provided |
[jira] [Updated] (CLOUDSTACK-6565) [UI] New Zones tab for Templates and ISOs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-6565: - Description: Display templates and ISOs only once, even if they are for multiple zones. Display the zone data in a new tab. (Current UI shows templates and ISOs as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show per-zone related user actions (action buttons) in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. This feature does not need API changes. was: Display templates and ISOs only once, even if they are for multiple zones. Display the zone data in a new tab. (Current UI shows them as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show per-zone related user actions (action buttons) in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. [UI] New Zones tab for Templates and ISOs - Key: CLOUDSTACK-6565 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6565 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Display templates and ISOs only once, even if they are for multiple zones. Display the zone data in a new tab. (Current UI shows templates and ISOs as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show per-zone related user actions (action buttons) in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. This feature does not need API changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6565) [UI] New Zones tab for Templates and ISOs
Gabor Apati-Nagy created CLOUDSTACK-6565: Summary: [UI] New Zones tab for Templates and ISOs Key: CLOUDSTACK-6565 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6565 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Display templates and ISOs only once, even if they are for multiple zones. Display the zone data in a new tab. (Current UI shows them as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show per-zone related user actions (action buttons) in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6565) [UI] New Zones tab for Templates and ISOs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-6565: - Description: Display templates and ISOs only once, even if they are for multiple zones. Instead of showing redundant list, one item for each zone, show zone list in a new tab. (Current UI shows templates and ISOs as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show the per-zone related user actions in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. This feature does not need API changes. was: Display templates and ISOs only once, even if they are for multiple zones. Display the zone data in a new tab. (Current UI shows templates and ISOs as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show per-zone related user actions (action buttons) in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. This feature does not need API changes. [UI] New Zones tab for Templates and ISOs - Key: CLOUDSTACK-6565 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6565 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Display templates and ISOs only once, even if they are for multiple zones. Instead of showing redundant list, one item for each zone, show zone list in a new tab. (Current UI shows templates and ISOs as many times as many zones they are in.) Show the new Zones tab right next to the currently existing Details tab, show the per-zone related user actions in the Zones list. Having this view would eliminate the long list of Templates and ISOs when there are many zones available. This feature does not need API changes. -- 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] [Resolved] (CLOUDSTACK-6227) Add copy-paste support for detail view fields
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-6227. -- Resolution: Fixed Add copy-paste support for detail view fields - Key: CLOUDSTACK-6227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6227 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: Brian Federle Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Attachments: copy-paste-concept.png Right now long value fields are displayed in a scrollbox to prevent overflow, examples being the API and secret key fields. Visually, this is not an optimal solution and can also make copy-pasting the values hard. There should be a new option in the detailView to provide a 'copy' button next to long fields, which would copy the entire field's contents to the clipboard. The displayed value field can then be truncated via ellipses '...' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5962) Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy resolved CLOUDSTACK-5962. -- Resolution: Fixed Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation. -- Key: CLOUDSTACK-5962 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5962 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.3.0 Reporter: Pradeep S Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Attachments: Disk_size.jpg Steps to Reproduce: -- 1. Set the value of Global parameters custom.diskoffering.size.min to 50, custom.diskoffering.size.max to 100 and restart the management service. 2. Start creating a new instance, select Custom option for Disk Offering. Observation: In the Slider option for Custom Disk Offering, the minimum value of Disk size is not updated to 50. It still displays as 1. Maximum value of Disk size is updated correctly to 100. Expected Result: -- In the Slider option for Custom Disk Offering, the minimum value of Disk size should be updated to the value set in Global parameter custom.diskoffering.size.min. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5962) Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-5962: - Fix Version/s: (was: 4.3.0) 4.4.0 Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation. -- Key: CLOUDSTACK-5962 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5962 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.3.0 Reporter: Pradeep S Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Attachments: Disk_size.jpg Steps to Reproduce: -- 1. Set the value of Global parameters custom.diskoffering.size.min to 50, custom.diskoffering.size.max to 100 and restart the management service. 2. Start creating a new instance, select Custom option for Disk Offering. Observation: In the Slider option for Custom Disk Offering, the minimum value of Disk size is not updated to 50. It still displays as 1. Maximum value of Disk size is updated correctly to 100. Expected Result: -- In the Slider option for Custom Disk Offering, the minimum value of Disk size should be updated to the value set in Global parameter custom.diskoffering.size.min. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5962) Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13956863#comment-13956863 ] Gabor Apati-Nagy commented on CLOUDSTACK-5962: -- committed to master: 883d7f17f78433b37e4f20103b532b3b20582014 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=883d7f17f78433b37e4f20103b532b3b20582014 4.4: eb86ed60bd30afcb660c7a05ad46ac0977c019f0 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=eb86ed60bd30afcb660c7a05ad46ac0977c019f0 Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation. -- Key: CLOUDSTACK-5962 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5962 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.3.0 Reporter: Pradeep S Assignee: Gabor Apati-Nagy Fix For: 4.3.0 Attachments: Disk_size.jpg Steps to Reproduce: -- 1. Set the value of Global parameters custom.diskoffering.size.min to 50, custom.diskoffering.size.max to 100 and restart the management service. 2. Start creating a new instance, select Custom option for Disk Offering. Observation: In the Slider option for Custom Disk Offering, the minimum value of Disk size is not updated to 50. It still displays as 1. Maximum value of Disk size is updated correctly to 100. Expected Result: -- In the Slider option for Custom Disk Offering, the minimum value of Disk size should be updated to the value set in Global parameter custom.diskoffering.size.min. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-5962) Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reassigned CLOUDSTACK-5962: Assignee: Gabor Apati-Nagy Value of Global parameter custom.diskoffering.size.min is not reflected in UI during new instance creation. -- Key: CLOUDSTACK-5962 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5962 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.3.0 Reporter: Pradeep S Assignee: Gabor Apati-Nagy Fix For: 4.3.0 Attachments: Disk_size.jpg Steps to Reproduce: -- 1. Set the value of Global parameters custom.diskoffering.size.min to 50, custom.diskoffering.size.max to 100 and restart the management service. 2. Start creating a new instance, select Custom option for Disk Offering. Observation: In the Slider option for Custom Disk Offering, the minimum value of Disk size is not updated to 50. It still displays as 1. Maximum value of Disk size is updated correctly to 100. Expected Result: -- In the Slider option for Custom Disk Offering, the minimum value of Disk size should be updated to the value set in Global parameter custom.diskoffering.size.min. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (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 reassigned CLOUDSTACK-6255: Assignee: Gabor Apati-Nagy 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-6227) Add copy-paste support for detail view fields
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy reassigned CLOUDSTACK-6227: Assignee: Gabor Apati-Nagy Add copy-paste support for detail view fields - Key: CLOUDSTACK-6227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6227 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: Brian Federle Assignee: Gabor Apati-Nagy Fix For: 4.4.0 Attachments: copy-paste-concept.png Right now long value fields are displayed in a scrollbox to prevent overflow, examples being the API and secret key fields. Visually, this is not an optimal solution and can also make copy-pasting the values hard. There should be a new option in the detailView to provide a 'copy' button next to long fields, which would copy the entire field's contents to the clipboard. The displayed value field can then be truncated via ellipses '...' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4563) Initial zone wizard UI label issue
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918243#comment-13918243 ] Gabor Apati-Nagy commented on CLOUDSTACK-4563: -- I submitted the fix to ReviewBoard, please see at https://reviews.apache.org/r/18695 Initial zone wizard UI label issue -- Key: CLOUDSTACK-4563 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4563 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Chiradeep Vittal On the 'add secondary storage' wizard step, the label for the dropdown shows 'label.provider' -- This message was sent by Atlassian JIRA (v6.2#6252)
