use cli success but call restApi return 404

[jindengke]

when I call restApi to grant access,it returns 404,but cli can grant access success,my api version is 2.4.2
check manila-api.log,two urls are same.

[Goutham Pacha Ravi (gouthamr)]

Hi,

Thanks for filing this bug. A couple of questions for you:

1) Our API versions are of the form X.Y, so, can you please check if you were requesting API version 2.42 and not 2.4.2?
2) Can you share the Manila API log file, and the rest API call you are making?

[jindengke (lmgdlmgd)]

1) sorry,API version is 2.42

2) when I call api,the MANILA API log is:

2019-05-23 09:07:18.266 1598 INFO manila.api.openstack.wsgi [req-72e6f906-97d4-4a56-8359-b1eff757eb19 a95585496e834d7f8fd11b74d6ca3da9 a4e949be795048c39143c545b35d0836 - - -] POST http://10.110.28.66:8786/v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e/action
2019-05-23 09:07:18.268 1598 INFO manila.api.openstack.wsgi [req-72e6f906-97d4-4a56-8359-b1eff757eb19 a95585496e834d7f8fd11b74d6ca3da9 a4e949be795048c39143c545b35d0836 - - -] http://10.110.28.66:8786/v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e/action returned with HTTP 404
2019-05-23 09:07:18.269 1598 INFO eventlet.wsgi.server [req-72e6f906-97d4-4a56-8359-b1eff757eb19 a95585496e834d7f8fd11b74d6ca3da9 a4e949be795048c39143c545b35d0836 - - -] ::ffff:10.72.199.98 "POST /v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e/action HTTP/1.1" status: 404 len: 356 time: 0.0065432

when I call cli,the log is:

9-05-23 09:12:00.280 1598 INFO manila.api.openstack.wsgi [-] GET http://10.110.28.66:8786/
2019-05-23 09:12:00.282 1598 INFO manila.api.openstack.wsgi [-] http://10.110.28.66:8786/ returned with HTTP 300
2019-05-23 09:12:00.283 1598 INFO eventlet.wsgi.server [-] ::ffff:10.110.28.21 "GET / HTTP/1.1" status: 300 len: 895 time: 0.0046918
2019-05-23 09:12:00.932 1598 INFO manila.api.openstack.wsgi [req-721616f8-1b49-41d6-863f-7f8057923fe3 f2cde4d9bfe44f689fbf76fb47aac417 a4e949be795048c39143c545b35d0836 - - -] GET http://10.110.28.66:8786/v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e
2019-05-23 09:12:00.967 1598 INFO manila.api.openstack.wsgi [req-721616f8-1b49-41d6-863f-7f8057923fe3 f2cde4d9bfe44f689fbf76fb47aac417 a4e949be795048c39143c545b35d0836 - - -] http://10.110.28.66:8786/v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e returned with HTTP 200
2019-05-23 09:12:00.968 1598 INFO eventlet.wsgi.server [req-721616f8-1b49-41d6-863f-7f8057923fe3 f2cde4d9bfe44f689fbf76fb47aac417 a4e949be795048c39143c545b35d0836 - - -] ::ffff:10.110.28.21 "GET /v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e HTTP/1.1" status: 200 len: 1493 time: 0.1257150
2019-05-23 09:12:00.978 1598 INFO manila.api.openstack.wsgi [req-b6205b15-fe72-4962-bac0-a65b6eea91b5 f2cde4d9bfe44f689fbf76fb47aac417 a4e949be795048c39143c545b35d0836 - - -] POST http://10.110.28.66:8786/v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e/action
2019-05-23 09:12:01.104 1598 INFO manila.api.openstack.wsgi [req-b6205b15-fe72-4962-bac0-a65b6eea91b5 f2cde4d9bfe44f689fbf76fb47aac417 a4e949be795048c39143c545b35d0836 - - -] http://10.110.28.66:8786/v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e/action returned with HTTP 200
2019-05-23 09:12:01.105 1598 INFO eventlet.wsgi.server [req-b6205b15-fe72-4962-bac0-a65b6eea91b5 f2cde4d9bfe44f689fbf76fb47aac417 a4e949be795048c39143c545b35d0836 - - -] ::ffff:10.110.28.21 "POST /v2/a4e949be795048c39143c545b35d0836/shares/45a94d4d-e3d8-4b7b-a21f-200c1e2a1f3e/action HTTP/1.1" status: 200 le...

[Goutham Pacha Ravi (gouthamr)]

Wow, sorry - I didn't notice that you had reported back with the log from your experiment.
I see that your URLs are the same as you noted. You're invoking a shares "action" API. There are several of these, and they require a unique body element to route your call to the correct API action. Perhaps the body of your JSON request was incorrect or had the wrong "action" key. Please check the available actions here: https://docs.openstack.org/api-ref/shared-file-system/#share-actions

[Launchpad Janitor (janitor)]

[Expired for OpenStack Shared File Systems Service (Manila) because there has been no activity for 60 days.]