The "500" error appears when user uses import single record

Description

Overview: Import single record failed with "Something went wrong" error.
The issue is reproduced not each time.
Steps to Reproduce:

  1. Log into Nolana BF FOLIO environment as User with following permissions:
    Inventory: All permissions
    Inventory: Import single bibliographic records
    quickMARC: View, edit MARC bibliographic record

  2. Go to "Inventory" app.

  3. Click on the "Actions" >> "Import".

  4. Select "OCLC WorldCat" in the first dropdwon.

  5. Enter the valid "OCLC Number" value (for exmaple: "855491594")

  6. Click on the "Import" button

Expected Results: The new "Instance" record successfully imported.
Actual Results: 
1) From UI side: the error toast notifcation is being displayed with the following message: "Something went wrong: HTTPError: 400: Add record for job execution failed: POST http://pvt.lb.nbf.folio-eis.us-west-2:9130/change-manager/jobExecutions/667e8d20-3e37-4d82-b955-e475b70424fa/records returned 500 (expected 204):Internal Server Error, Please contact System Administrator or try again" 
2) From Back-end side:  the POST request to the "/copycat/imports" failed with the following error message: "Add record for job execution failed: POST http://pvt.lb.nbf.folio-eis.us-west-2:9130/change-manager/jobExecutions/667e8d20-3e37-4d82-b955-e475b70424fa/records returned 500 (expected 204):Internal Server Error, Please contact System Administrator or try again"
Additional Information: see attached screenshots.
Interested parties:  

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Kateryna Senchenko November 28, 2022 at 4:29 PM

Hi , no bugfix is needed. I added a release not for Nolana https://folio-org.atlassian.net/wiki/display/REL/Nolana+%28R3+2022%29+Release+Notes. Related Jira tickets are also linked. Thank you!

Ann-Marie Breaux November 28, 2022 at 7:47 AM

- do we need a bugfix, or is this just a setting that needs to be updated in Nolana SRM? If just a setting, then please make sure there is a note in Nolana release notes, so that the proper thing is done during upgrade from MG to Nolana. We can talk about it or look at it together later this week if necessary.

Roman Chernetskyi November 25, 2022 at 2:51 PM

Reason for the bug is a new feature about adding read-only DB, sometimes read-only instance do not synchronise with the default one, so we decided to turn off this feature for srm

Valery_Pilko November 21, 2022 at 7:14 PM

Hi ,  
I still can reproduce this issue at Nolana BF environment.
See attached screencast:

Ivan Kryzhanovskyi November 21, 2022 at 3:54 PM

or , could you please double check this ticket and confirm that we can close?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Release

Nolana (R3 2022)

RCA Group

Not a bug

Affected releases

Nolana (R3 2022)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 16, 2022 at 12:07 PM
Updated May 22, 2024 at 11:53 AM
Resolved November 28, 2022 at 7:47 AM
TestRail: Cases
TestRail: Runs