[jira] [Created] (CLOUDSTACK-6120) Order of templates and ISOs not honored by UI or API

["Jessica Wang (JIRA)" <ji...@apache.org>]

Jessica Wang created CLOUDSTACK-6120:
----------------------------------------

             Summary: Order of templates and ISOs not honored by UI or API
                 Key: CLOUDSTACK-6120
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6120
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: UI
            Reporter: Jessica Wang
            Assignee: Jessica Wang


there is a problem with the order of UpdateTemplate/ISO API calls in case of multiple zones.
 If a template is registered on multiple zones while listing we show multiple entries of that template (one entry for each zone), but the UUID of the template is same. 

Say from UI listtemplates looks like this,

T2 -> Zone1 (UUID = yyyy)
 T2 -> Zone2 (UUID = yyyy)
 T3 -> Zone1 (UUID = zzzz)
 T3 -> Zone2 (UUID = zzzz)
 T1 -> Zone1 (UUID = xxxx)
 T1 -> Zone2 (UUID = xxxx)

If I pull T1 -> Zone1 to first position

>From UI updatetemplate APIs are called in this order.

UpdateTemplate API T1 -> Zone1 with sort_key 6 and UUID = xxxx
 UpdateTemplate API T2 -> Zone1 with sort_key 5 and UUID = yyyy
 UpdateTemplate API T2 -> Zone2 with sort_key 4 and UUID = yyyy
 UpdateTemplate API T3 -> Zone1 with sort_key 3 and UUID = zzzz
 UpdateTemplate API T3 -> Zone2 with sort_key 2 and UUID = zzzz
 UpdateTemplate API T1 -> Zone2 with sort_key 1 and UUID = xxxx

Even If I pull T1 to first position the last updateTemplate API call on T1 is with sort_key 1. So it will stay at last position again.

So from UI if we call updateTemplate/ISO only one time (starting from top) by maintaining a HaspMap of UUIDs it may solve the problem.
 Update API looks like this

UpdateTemplate API T1 -> Zone1 with sort_key 6
 UpdateTemplate API T2 -> Zone1 with sort_key 5
 UpdateTemplate API T3 -> Zone1 with sort_key 3




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)