Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
None
-
CP: sprint 130
-
1
-
Core: Platform
Description
https://jenkins-aws.indexdata.com/job/FOLIO_Reference_Builds/job/folio-testing-backend/1210/console
fatal: [10.36.1.224]: FAILED! => {"changed": false, "connection": "close", "content": "POST request for mod-inn-reach-1.1.0-SNAPSHOT.159 /_/tenant failed with 500: {\"message\":\"[403 Forbidden] during [POST] to [http://perms/users] [PermissionsClient#assignPermissionsToUser(Permissions)]: [Cannot add immutable permissions inventory-storage.inventory-view.instances.collection.get, inventory-storage.instances.collection.get, inventory-storage.instances.item.get, inventory-storage.items.co... (837 bytes)]\",\"code\":\"500\"}", "content_length": "433", "content_type": "text/plain", "elapsed": 339, "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.36.1.224:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadSample%3Dtrue%2CloadReference%3Dtrue%2CrunReindex%3Dtrue", "vary": "origin"}
This can be fixed by either adding perms.users.assign.immutable or all permissions that the created user is going to use.
Like in MODEXPS-61
TestRail: Results
Attachments
Issue Links
- is cloned by
-
MSEARCH-395 Cannot enable module due to lack of permissions
-
- Closed
-
- relates to
-
MODEXPS-61 User creation fails due to lack of permissions
-
- Closed
-
-
MODPERMS-157 Check assignment permissions for operating user
-
- Closed
-