(FSE Dry run 1) Cannot import MARC records
Description
Environment
CSP Request Details
CSP Rejection Details
Potential Workaround
Estimation Notes and Assumptions
RCA Group Details
Attachments
- 26 Aug 2024, 07:59 AM
- 16 Aug 2024, 08:05 AM
- 16 Aug 2024, 08:02 AM
- 01 Aug 2024, 08:31 AM
- 01 Aug 2024, 08:31 AM
- 24 Jul 2024, 12:27 PM
- 24 Jul 2024, 12:13 PM
Checklist
hideActivity
Yauhen Viazau August 26, 2024 at 8:02 AM
Issue is not reproducible on evrk2 (diku4 - https://diku4.int.aws.folio.org/ , ECS Central - https://eureka-central-tenant.int.aws.folio.org ), and on FSE Dry run 1 (non-ECS - https://crs-sandbox2.int.aws.folio.org/ , ECS - https://lcsg-sandbox2.int.aws.folio.org/ ) 
See example for evrk2 diku4:
@Danylo Vazhynskyi - FYI
Danylo Vazhynskyi August 21, 2024 at 10:02 AM
Can be reproduced on evrk2 diku4. Can’t be reproduced on Snapshot
Yauhen Viazau August 16, 2024 at 8:07 AM
Re-tested on FSE Dry run 1 (https://crs-sandbox2.int.aws.folio.org/ ) after Q CSP2 updates - issue is no longer active
MARC bib record can be successfully imported. See example:
Note: Import of MARC authority and MARC holdings records can be performed, but ends with errors due to https://folio-org.atlassian.net/browse/EUREKA-224
Yauhen Viazau August 1, 2024 at 8:38 AMEdited
Tested on evrk2 - works as expected
MARC files can be imported without issues on non-ECS, ECS Central tenants. See examples:
Still reproducible on FSE Dry run 1 
Note: I have updated the description and labels for this ticket to only mention Dry run 1
cc: @Craig McNally
Craig McNally July 31, 2024 at 9:19 PMEdited
on evrk2 I see similar behavior, but here I see different errors in the logs and the service is more stable…
21:14:42 [979744/mod-data-import] [diku2] [2453fcff-fe2c-450c-a9e8-7be93caf16cd] [mod_data_import] ERROR FileSplitWriter Failed uploading file data-import/diku2/1722369489428-testMarcFile.102.6021051145315426_1.mrc:
software.amazon.awssdk.services.s3.model.S3Exception: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. (Service: S3, Status Code: 301, Request ID: 352B834FBYJCQVGE, Extended Request ID: tMCQUVRHOUbmzBFxojqhGOOY1BfvHvAFUztXuzH1oG2cDMi7FV7R5zx7ZO5bEt+o98IV0CHVHec=)This looks to me like it could be a configuration problem.
*** UPDATE ***
I fixed the problem above by correcting the AWS_URL in evrk2’s mod-data-import. After that, I was unable to reproduce this problem. @Yauhen Viazau can you please retest in evrk2? It appears there is something else going on on dryrun which is causing the service to continuously crash.
Details
Details
Assignee
Reporter
Development Team
RCA Group
Priority
P2
Overview:
Cannot import any MARC records (bib, authority, holdings)
Steps to reproduce:
Login to FSE Dry run 1
Go to “Data import” app
Click on “or choose files“ button
Select .mrc file (you can use the attached MARC bib file)
Select the appropriate job profile (click on it) (for MAR bib you can use “Default - Create instance and SRS MARC Bib“)
Click on “Actions“ → Select “Run“
Click on “Run“ button in appeared modal
Expected result:
Import job is shown in the first pane in “Running“ accordion. After some time, a row for imported record appears in the second pane with “Completed“ status
Actual result:
Import job is NOT shown in the first pane in “Running“ accordion. Import job is never finished.
Additional information:
Currently NOT reproducible on evrk2
Importing MARC records using API calls is not possible as well (job is never finished; the same is shown in UI)
See example: