(Eureka BF) Cannot export eHoldings package

Description

Steps to Reproduce:

  1. Login to https://eureka-bugfest-ramsons.int.aws.folio.org/ tenant as an admin user

  2. Open detail view page of "Package" record: "/eholdings/packages/22-2163800"

  3. Click on the "Actions" button and select "Export package (CSV)" option from the expanded dropdown >> Click on the "Export" button.

    1. The successful toast notification is displayed with the following message:
      "Your eholdings export (Job ID: <<Job ID>>) is in progress and will be available on the Export manager app. The export may take several minutes to complete."

  4. Go to "Export manager" app and verify that new row with "Job ID" value matched to "Job ID" from previous step are displayed at export jobs list.

  5. Wait for the export is complete (status of the exported job changed from "In progress" to a different status)

    1. For the status to be updated, the page needs to be reloaded

Expected Results: The export is complete and status of the exported job changed to "Successful"

Actual Results: The export is complete and status of the exported job changed to "Failed". When opening a detailed view for a completed export job, one of the following messages is shown:

Additional Information:

 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

9

Checklist

hide

Activity

Show:

Khalilah Gambrell December 10, 2024 at 1:14 PM

Hey - I closed the issue. Thank you.

Valery_Pilko December 10, 2024 at 12:45 PM

Re-tested on Eureka Bugfest (non-ECS and ECS) environments - cannot reproduce this issue:
Packages used for testing are:
/eholdings/packages/53-3457531
/eholdings/packages/125531-2631932

Hey - do you want to review it by yourself, or can we close it?

Mukhiddin Yusupov December 4, 2024 at 1:46 PM

The issue is being reproduced intermittently and mostly for packages with about 9000 titles or more for which the exporting operation takes a long time, about 5 minutes or more.

Validated the defect against and points related to permissions, Capabilities or Capability Sets are fulfilled, so returned errors do not seem to be related to the permission issues.

I think this issue needs to be retested after the or it’s related similar defects are resolved as these defects have same [401 Unauthorized] errors being produced.

Oleksii Petrenko November 27, 2024 at 9:25 AM

Please validate defect based on guideline -

Natalia Zaitseva November 26, 2024 at 6:17 PM

Hey
During our recent internal Scrum of Scrums meeting, various teams raised their concerns about issues that they have in the Eureka BugFest environment.
It became clear that the Eureka team, despite their efforts, couldn't address every issue due to their workload and areas of expertise.

We agreed to continue the process that mirrors the Okapi-based Bugfest triaging model.
This way, we involve multiple teams that can add small, manageable tasks to their backlogs to address and help resolve issues collectively.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Release

Ramsons (R2 2024) Bug Fix

RCA Group

Not a bug

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 15, 2024 at 9:48 AM
Updated December 13, 2024 at 7:01 AM
Resolved December 10, 2024 at 1:14 PM
TestRail: Cases
TestRail: Runs