[
https://issues.apache.org/jira/browse/CLOUDSTACK-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle reassigned CLOUDSTACK-3153:
-----------------------------------------
Assignee: Kishan Kavala (was: Brian Federle)
Kishan, though I am now using 1 api call to update the target ACL rule, I'm
still getting an error due to overlapping rule numbers:
'ACL item with number 1 already exists in ACL:
43c58857-85b8-4985-987c-2cf587018bea'
Since we only want 1 API call per reorder, I'm not sure if I can fix this issue
in the UI, since I would need to do an update call for *every* row that is
conflicting. Ideally, the backend should handle conflicting row numbers and
automatically re-number those rows.
> [UI] Network ACL : Incorrect API calls when changing the rule number
> --------------------------------------------------------------------
>
> Key: CLOUDSTACK-3153
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3153
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Reporter: Kishan Kavala
> Assignee: Kishan Kavala
> Priority: Critical
>
> After creating Network ACL rules, UI for changing the number is not correct.
> UI should just update the number of rule that is moved. It should be a single
> updateNetworkACL API call.
> UI currently fires 2 APIs and both of them fail. UI should not try to swap
> the numbers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
