Cannot add holdings to shared instances in Member tenant

Description

Scenario 1 - MARC holdings

Steps to Reproduce:

  1. Login to evrk2 ECS tenant as an admin user

  2. Switch affiliations to a Member tenant

  3. Go to "Inventory" app

  4. Fill search input field with query which will return records (f.e. “*“)

  5. Click “Search“ button

  6. Click on the title of any shared MARC record in the second pane

  7. Click on "Actions" button in second pane → Select"Add MARC holdings record" option

Expected Results: QuickMARC editor window is opened for creating a new MARC holdings

Actual Results: Error toast notification is shown - “Record cannot be found or loaded“. In DevTools, multiple GET /perms/users/<UUID>/permissions calls fail with 404 status and following body:

No user found by userId <user UUID>

 

Scenario 2 - FOLIO holdings

Steps to Reproduce:

  1. Login to evrk2 ECS tenant as an admin user

  2. Switch affiliations to a Member tenant

  3. Go to "Inventory" app

  4. Fill search input field with query which will return records (f.e. “*“)

  5. Click “Search“ button

  6. Click on the title of any shared MARC/FOLIO record in the second pane

  7. Click on "Add holdings" button

  8. Fill required fields → Click on “Save“ button

Expected Results: Editor window is opened for creating a new FOLIO holdings

Actual Results: Error pop-up is shown. In DevTools, POST /holdings-storage/holdings call fails with 500 status and following body (the same message as in pop-up):

Error during sharing Instance for sourceTenantId: cs101, targetTenantId: cs101m01, instanceIdentifier: d77c5f6d-72eb-4e10-8976-99b67e88dc72, status code: 201, response message: {"id":"e741de92-8aa4-4a97-8d28-b07f49120618","instanceIdentifier":"d77c5f6d-72eb-4e10-8976-99b67e88dc72","sourceTenantId":"cs101","targetTenantId":"cs101m01","status":"ERROR","error":"Failed to post inventory instance with reason: HRID value already exists in table instance: in00000000001","metadata":{"createdDate":"2024-06-04T14:04:00.869073","createdByUserId":"a3d2fb7a-c200-402f-845e-b79e10afaf72","updatedDate":"2024-06-04T14:04:00.869073","updatedByUserId":"a3d2fb7a-c200-402f-845e-b79e10afaf72"}}

Additional Information:

  • Not reproduced for each instance record (maybe it depends on the HRID)

  • Holdings can be added to local records in Member tenant

  • See attached screencast:

 

Environment

None

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Estimation Notes and Assumptions

None

RCA Group Details

None

Attachments

11
  • 21 Nov 2024, 07:40 AM
  • 14 Nov 2024, 01:20 PM
  • 12 Nov 2024, 03:58 PM
  • 12 Nov 2024, 03:58 PM
  • 05 Nov 2024, 01:39 PM
  • 05 Nov 2024, 01:39 PM
  • 05 Nov 2024, 01:39 PM
  • 05 Nov 2024, 01:39 PM
  • 30 Oct 2024, 03:56 PM
  • 05 Jun 2024, 07:47 AM
  • 04 Jun 2024, 02:23 PM

Checklist

hide

Activity

Show:

Yauhen Viazau November 21, 2024 at 9:07 AM

Scenario 1:
After discussion with Spitfire QA and clarifications from their team it became clear that this scenario is currently not supported and has known issues which will not be solved in Ramsons. At the very least, this is not a Eureka issue and will be addressed separately from this ticket.

It was my mistake to make unnecessary assumptions. At some point this must have worked on Okapi ECS but it does not work right now.

Scenario 2:

This is also a known problem and not in fact an issue. This behavior is caused by HRID settings being the same by default on all tenants. Before testing, they need to be updated manually.

Closing this ticket as “Not a bug“

Yauhen Viazau November 21, 2024 at 7:40 AM

Yauhen Viazau November 14, 2024 at 1:19 PM
Edited

Unfortunately, I was able to reproduce Scenario 2 again on etesting-snapshot. Restored the description to the original form

image-20241114-131946.png

Yauhen Viazau November 12, 2024 at 4:00 PM

Re-tested on https://folio-etesting-snapshot-consortium.ci.folio.org/

Scenario 1 - still active Warning

Scenario 2 - not reproducible Check Mark

 

Zak Burke November 5, 2024 at 4:52 PM

The issue in Scenario 1, where we see an API call to /perms/users/<UUID>/permissions despite this being a Eureka tenant, looks like https://folio-org.atlassian.net/browse/EUREKA-499 to me.

Won't Do

Details

Assignee

Reporter

Development Team

Eureka

RCA Group

Not a bug

Story Points

Sprint

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created June 4, 2024 at 2:19 PM
Updated December 3, 2024 at 5:37 PM
Resolved November 21, 2024 at 9:08 AM
TestRail: Cases
TestRail: Runs

Flag notifications