[FOLIO-3357] folio-testing-stripes Jenkins build failing Created: 06/Dec/21 Updated: 06/Dec/21 Resolved: 06/Dec/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | DevOps Sprint 129 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
The folio-testing-stripes Jenkins build is failing as it is trying to assign new permissions to the admin user. See the job log for details. Error is (for example): Cannot add immutable permission calendar.all not owned by operating user 231e1468-3e9b-5d9f-8e9b-612733423d2f This may simply be the result of someone editing the diku_admin user in the environment (see open issue
|
| Comments |
| Comment by Wayne Schneider [ 06/Dec/21 ] |
|
Indeed, the perms.users.assign.immutable and perms.users.assign.mutable permissions were removed from diku_admin, most likely as a result of someone editing the user and the side effect documented in
By disabling mod-authtoken temporarily for the diku tenant, I was able to manually assign the missing permissions, and then the tenant-admin-permissions role that is run by that Jenkins job is able to run without errors. The reason that the environment remained available (and indeed, the frontend was updated) is because the tenant-admin-permissions role runs after the stripes build. |