(Dry run) Cannot import/create MARC Authority/Holdings records

Description

Overview:

The issue is reproducible on non-ECS and ECS dryrun1 environments
NOT reproducible on Eureka BF and etesting-snapshot https://folio-etesting-snapshot-diku.ci.folio.org

Preconditions:

Admin user is logged in to dryrun1 environment

Steps to reproduce:

  1. Go to the “Data import”

  2. Click “or choose files” button on “Jobs pane” → Select attached Marc Authority file

  3. Select “Default - Create SRS MARC Authority” job profile

  4. Click “Actions” on the third job profile pane → Select “Run” option → Click “Run” button in appeared modal

Expected Results:

Once import is complete, a new row with "Completed" status is displayed on Logs page. New Marc Authority record is created.

Actual Results:

Once import is complete, a new row with "Completed with error" status is displayed on Logs page. New Marc Authority record is NOT created. The following error message is displayed on Import Log page:
Failed to initialize pool: SSL error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Additional information:

  • Also reproducible when importing MARC Holdings records

  • Also reproducible when creating new MARC Authority or MARC Holdings records via UI/API

  • NOT reproducible for importing Marc Bib record with “Default - Create instance and SRS MARC Bib” job profile

Environment

None

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Estimation Notes and Assumptions

None

RCA Group Details

None

Attachments

3

Checklist

hide

Activity

Show:

Yauhen Viazau March 17, 2025 at 11:23 AM

, - the issue is still active after update of Dry run 1 to Ramsons. For MARC Authority and MARC Holdings records (create and import). Updated ticket description.
Also, please note that the original ticket for this issue was closed before due to the information that CRS will not use such records - .
cc: ,

Denis March 4, 2025 at 8:31 PM

, do you think it makes sense to retest this bug on TLS version with Ramsons code and see if the issue persists? Because if it’s only Quesnelia where the issue could be observed, we might close the ticket unless there is a high priority bug reported from prod instance.

cc

Craig McNally February 14, 2025 at 1:35 PM

, I just assigned this to FSE as it looks hosting related. Note the error message about not being able to find a certificate.

Details

Assignee

Reporter

Development Team

EBSCO - FSE

RCA Group

TBD

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 14, 2025 at 7:36 AM
Updated March 17, 2025 at 11:23 AM
TestRail: Cases
TestRail: Runs