UI service offering sorting order not working

[PPisz]

What could be the reason that changing places on the list (service offering sorting order) does not work in the UI?
If I click on change position then the offering changes position and then goes back.

[Pearl1594]

@PPisz which version of CloudStack do you see this behaviour? Because, I do not see this happening on the current main branch

[PPisz]

In version 4.19.3, it was working before, unfortunately I don't know when it stopped.
I see such entries in the log:

2025-01-15 19:07:56,387 DEBUG [c.c.a.ApiServer] (qtp364604394-12130:ctx-c3ff9823 ctx-ac0be77c) (logid:404bc8b6) CIDRs from which account 'Account [{"accountName":"admin","id":2,"uuid":"ca0651fe-40f4-11ef-8273-0242ac120002"}]' is allowed to perform API calls: 0.0.0.0/0,::/0 2025-01-15 19:07:56,396 DEBUG [o.a.c.a.StaticRoleBasedAPIAccessChecker] (qtp364604394-12130:ctx-c3ff9823 ctx-ac0be77c) (logid:404bc8b6) RoleService is enabled. We will use it instead of StaticRoleBasedAPIAccessChecker. 2025-01-15 19:07:56,398 DEBUG [o.a.c.r.ApiRateLimitServiceImpl] (qtp364604394-12130:ctx-c3ff9823 ctx-ac0be77c) (logid:404bc8b6) API rate limiting is disabled. We will not use ApiRateLimitService. 2025-01-15 19:07:56,443 DEBUG [c.c.a.ApiServlet] (qtp364604394-12134:ctx-dc0eac18 ctx-71a28644) (logid:78ba60d8) ===END=== 10.10.101.11 -- GET id=3a3f1232-7055-45cf-b47c-8205aa3c7c0e&sortKey=3&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,448 DEBUG [c.c.a.ApiServlet] (qtp364604394-12106:ctx-fd81561f ctx-c2bfacc5) (logid:72d69b18) ===END=== 10.10.101.11 -- GET id=bd1de9e2-1019-43b6-a512-8952b8a550c5&sortKey=1&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,448 DEBUG [c.c.a.ApiServlet] (qtp364604394-12102:ctx-b59ef648 ctx-04224485) (logid:177042b9) ===END=== 10.10.101.11 -- GET id=7729006c-c6f6-444e-a6f7-5d44c9ff2686&sortKey=2&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,453 DEBUG [c.c.a.ApiServlet] (qtp364604394-12062:ctx-96567063 ctx-c2be7c7b) (logid:6f9d56df) ===END=== 10.10.101.11 -- GET id=afe9c053-c890-458e-8209-8f9be1d67f94&sortKey=10&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,459 DEBUG [c.c.a.ApiServlet] (qtp364604394-12076:ctx-1b69ccb5 ctx-b749ab9e) (logid:bcaecf73) ===END=== 10.10.101.11 -- GET id=74b09c93-4e43-46ae-8961-dd3b71a998b0&sortKey=8&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,463 DEBUG [c.c.a.ApiServlet] (qtp364604394-12120:ctx-a44b520d ctx-abc0fd4c) (logid:c1f991ed) ===END=== 10.10.101.11 -- GET id=c61b50f2-360b-4e1f-8757-c8959be38d36&sortKey=13&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,489 DEBUG [c.c.a.ApiServlet] (qtp364604394-11845:ctx-baca1ac0 ctx-6916941e) (logid:43f50a9c) ===END=== 10.10.101.11 -- GET id=b511465a-dd7b-4a10-951e-4b991117f11b&sortKey=7&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,489 DEBUG [c.c.a.ApiServlet] (qtp364604394-11988:ctx-4de6544f ctx-d95821e0) (logid:ca36ccf5) ===END=== 10.10.101.11 -- GET id=1ad3892c-ce5c-4f62-bcf5-2a352c9a51de&sortKey=12&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,489 DEBUG [c.c.a.ApiServlet] (qtp364604394-11940:ctx-29628289 ctx-3b12168d) (logid:3c3621b4) ===END=== 10.10.101.11 -- GET id=95e9f396-aa89-4f0e-9e22-17e5a36ea51e&sortKey=6&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,489 DEBUG [c.c.a.ApiServlet] (qtp364604394-12074:ctx-1c7c0420 ctx-c8952184) (logid:b3d96e5f) ===END=== 10.10.101.11 -- GET id=a7ab2868-0857-40b9-9fac-8897e3db3dbf&sortKey=4&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,489 DEBUG [c.c.a.ApiServlet] (qtp364604394-12040:ctx-b60f146e ctx-d243e949) (logid:b5521fd3) ===END=== 10.10.101.11 -- GET id=80cecee5-b8ed-4d40-a17f-23138b251ec0&sortKey=5&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,492 DEBUG [c.c.a.ApiServlet] (qtp364604394-11889:ctx-b8b337e6 ctx-a9304058) (logid:85e8ebd9) ===END=== 10.10.101.11 -- GET id=f8fb8d29-c0c5-4156-9e4c-15225df5cdef&sortKey=9&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,492 DEBUG [c.c.a.ApiServlet] (qtp364604394-12121:ctx-0a715d52 ctx-a354f46e) (logid:cb9c9bdc) ===END=== 10.10.101.11 -- GET id=5f75b587-baf9-4da5-8e0a-18001e97060e&sortKey=14&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,492 DEBUG [c.c.a.ApiServlet] (qtp364604394-11954:ctx-1f8d3275 ctx-eca62b95) (logid:0454941b) ===END=== 10.10.101.11 -- GET id=ec82227d-7670-4798-9018-f5c6e8f5b5d7&sortKey=11&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,493 DEBUG [c.c.a.ApiServlet] (qtp364604394-12130:ctx-c3ff9823 ctx-ac0be77c) (logid:404bc8b6) ===END=== 10.10.101.11 -- GET id=4bc274c4-961a-4bb9-9d63-9757c4e89b5f&sortKey=15&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,583 DEBUG [c.c.a.ApiServlet] (qtp364604394-12132:ctx-959f8348) (logid:a3da3ce7) ===START=== 10.10.101.11 -- GET listall=true&isrecursive=true&page=1&pagesize=20&command=listServiceOfferings&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0 2025-01-15 19:07:56,583 DEBUG [c.c.a.ApiServlet] (qtp364604394-12132:ctx-959f8348) (logid:a3da3ce7) Two factor authentication is already verified for the user 2, so skipping 2025-01-15 19:07:56,603 DEBUG [c.c.a.ApiServer] (qtp364604394-12132:ctx-959f8348 ctx-bed0e3ca) (logid:a3da3ce7) CIDRs from which account 'Account [{"accountName":"admin","id":2,"uuid":"ca0651fe-40f4-11ef-8273-0242ac120002"}]' is allowed to perform API calls: 0.0.0.0/0,::/0 2025-01-15 19:07:56,612 DEBUG [o.a.c.a.StaticRoleBasedAPIAccessChecker] (qtp364604394-12132:ctx-959f8348 ctx-bed0e3ca) (logid:a3da3ce7) RoleService is enabled. We will use it instead of StaticRoleBasedAPIAccessChecker. 2025-01-15 19:07:56,613 DEBUG [o.a.c.r.ApiRateLimitServiceImpl] (qtp364604394-12132:ctx-959f8348 ctx-bed0e3ca) (logid:a3da3ce7) API rate limiting is disabled. We will not use ApiRateLimitService. 2025-01-15 19:07:56,638 DEBUG [o.a.c.h.HAManagerImpl] (BackgroundTaskPollManager-4:ctx-6f4ae7cd) (logid:405f5999) HA health check task is running...

[DaanHoogland]

@PPisz , assuming you mean

2025-01-15 19:07:56,583 DEBUG [c.c.a.ApiServlet] (qtp364604394-12132:ctx-959f8348) (logid:a3da3ce7) ===START===  10.10.101.11 -- GET listall=true&isrecursive=true&page=1&pagesize=20&command=listServiceOfferings&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0

and

2025-01-15 19:07:56,493 DEBUG [c.c.a.ApiServlet] (qtp364604394-12130:ctx-c3ff9823 ctx-ac0be77c) (logid:404bc8b6) ===END===  10.10.101.11 -- GET  id=4bc274c4-961a-4bb9-9d63-9757c4e89b5f&sortKey=15&command=updateServiceOffering&response=json&sessionkey=YhbX4owxRt3_V_23DFXi25_kJQ0

these lines mean nothing but the start and end of processing of an API. You can ignore those.

after ===START=== ... &command=listServiceOfferings&, there must be a ===END===...&command=listServiceOfferings& line. Btween those two lines you would find relevant information about the retrieval of the offerings to list.

That all said, I suspect you are hitting the issue #9595 and if so it will be fixed in 4.19,2 and later by #9624

If that is not the case look between a ===START===....command=updateServiceOffering and a ===END===....command=updateServiceOffering line.

[PPisz]

Thank you, I hope this PR solves the problem. The log only says:

2025-01-16 15:54:14,494 DEBUG [c.c.a.ApiServlet] (qtp364604394-13878:ctx-51824df5) (logid:936dddfa) ===START=== 10.10.101.11 -- GET listall=true&isrecursive=true&page=1&pagesize=20&command=listServiceOfferings&response=json&sessionkey=EgMfJlnpP1EOb74HXzeSejYHYK0 2025-01-16 15:54:14,494 DEBUG [c.c.a.ApiServlet] (qtp364604394-13878:ctx-51824df5) (logid:936dddfa) Two factor authentication is already verified for the user 33, so skipping 2025-01-16 15:54:14,510 DEBUG [c.c.a.ApiServer] (qtp364604394-13878:ctx-51824df5 ctx-2262f0fa) (logid:936dddfa) CIDRs from which account 'Account [{"accountName":"ppisz","id":14,"uuid":"016415f5-344c-4f77-8ae3-f6097845237f"}]' is allowed to perform API calls: 0.0.0.0/0,::/0 2025-01-16 15:54:14,518 DEBUG [o.a.c.a.StaticRoleBasedAPIAccessChecker] (qtp364604394-13878:ctx-51824df5 ctx-2262f0fa) (logid:936dddfa) RoleService is enabled. We will use it instead of StaticRoleBasedAPIAccessChecker. 2025-01-16 15:54:14,520 DEBUG [o.a.c.r.ApiRateLimitServiceImpl] (qtp364604394-13878:ctx-51824df5 ctx-2262f0fa) (logid:936dddfa) API rate limiting is disabled. We will not use ApiRateLimitService. 2025-01-16 15:54:14,652 DEBUG [c.c.a.ApiServlet] (qtp364604394-13878:ctx-51824df5 ctx-2262f0fa) (logid:936dddfa) ===END=== 10.10.101.11 -- GET listall=true&isrecursive=true&page=1&pagesize=20&command=listServiceOfferings&response=json&sessionkey=EgMfJlnpP1EOb74HXzeSejYHYK0

[DaanHoogland]

ok, I see nothing wrong in that fragment. you can check the sequence of updateServiceOffering commands issued.

I analysed the ones you send but also these seem alright:

id	sort-key
3a3f1232-7055-45cf-b47c-8205aa3c7c0e	3
bd1de9e2-1019-43b6-a512-8952b8a550c5	1
7729006c-c6f6-444e-a6f7-5d44c9ff2686	2
afe9c053-c890-458e-8209-8f9be1d67f94	10
74b09c93-4e43-46ae-8961-dd3b71a998b0	8
c61b50f2-360b-4e1f-8757-c8959be38d36	13
b511465a-dd7b-4a10-951e-4b991117f11b	7
1ad3892c-ce5c-4f62-bcf5-2a352c9a51de	12
95e9f396-aa89-4f0e-9e22-17e5a36ea51e	6
a7ab2868-0857-40b9-9fac-8897e3db3dbf	4
80cecee5-b8ed-4d40-a17f-23138b251ec0	5
f8fb8d29-c0c5-4156-9e4c-15225df5cdef	9
5f75b587-baf9-4da5-8e0a-18001e97060e	14
ec82227d-7670-4798-9018-f5c6e8f5b5d7	11
4bc274c4-961a-4bb9-9d63-9757c4e89b5f	15

only if you see multiple reorderings, while you perform only one ordering action in the UI, there is something wrong.