Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Go to all issues
Select view

Select search mode

 
19 of 19

(ECS) 404 errors for a user with an admin role in all tenants in role detailed view in Member tenants

Won't Do

Description

Preconditions:

  1. User is logged in https://folio-etesting-snapshot-consortium.ci.folio.org/ as a user having admin role assigned in all tenants

Steps to reproduce:

  1. Switch affiliation to any Member tenant (f.e., “college“)

  2. Go to “Settings“ → “Authorization roles“

  3. Click on the name of any existing role in the second pane

Expected result:
Role detailed view is opened in the third pane, and contains “Capability sets“, “Capabilities“ accordions. Accordions can be expanded and then capabilities/sets will be shown. No failed requests in DevTools.

Actual result:
Role detailed view is opened in the third pane, and contains “Capability sets“, “Capabilities“ accordions. Accordions can be expanded and then capabilities/sets will be shown.

In DevTools, the following API calls are failing with 404 status (see screencast):

  • GET /roles/bf91ebc1-8ca2-41bb-a71c-427bc8f8e6fc/capability-sets?limit=5000

  • GET /roles/bf91ebc1-8ca2-41bb-a71c-427bc8f8e6fc/capabilities?limit=5000&query=cql.allRecords%3D1+sortby+resource&expand=true

Response body is:

Additional info:

  • NOT reproducible on Central ECS tenant, as well as on non-ECS tenant

  • Also reproducible when viewing Member roles in “Consortium manager” in Central tenant

  • See example:

 

Environment

None

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Estimation Notes and Assumptions

None

RCA Group Details

None

Attachments

5

Checklist

hide

Details

Assignee

Reporter

Labels

Development Team

Eureka

RCA Group

Implementation coding issue

Story Points

Sprint

Priority

Parent

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 3, 2024 at 7:10 AM
Updated November 5, 2024 at 4:23 PM
Resolved November 1, 2024 at 11:05 AM
Configure

Activity

Show:

Dima Tkachenko November 1, 2024 at 11:02 AM

The issue is cloned to and addressed to Thunderjet team

Closing this one..

Serhii_Nosko November 1, 2024 at 10:01 AM

It is interesting why requests to central tenant are sent in this case, probably these requests to central tenant is not needed

Dima Tkachenko October 31, 2024 at 4:56 PM

Summary

404 Not Found error with Unable to find org.folio.roles.domain.entity.RoleEntity with id 345c5cc9-b164-4604-9d0e-bad160cbb852 message is caused by invalid role id in the request to consortia’s DB.

Details

When role details page is being loaded the UI sends similar requests to get capabilities and capability sets assigned to the role from both affiliation and central tenant data:

The first group of requests is successful. It’s addressed to affiliation (x-okapi-tenant = college):

The second group uses the same role id as for affiliation but requests data from central tenant (x-okapi-tenant = consortium) and it fails

Indeed, there are different ids for the role in consortium and college schemas so failed requests for consortium are kind of expected:

please review and decide on further steps to resolve the issue

CC: ,

TestRail: Cases
TestRail: Runs
Loading...