[FOLIO-3512] folio-snapshot-2 build failure while adding eholdings/EBSCO RMI config Created: 26/May/22  Updated: 17/Aug/22  Resolved: 19/Jul/22

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: back-end, epam-spitfire
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 144, DevOps Sprint 142, DevOps Sprint 140, DevOps Sprint 141
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

The folio-snapshot-2 build has consecutive build failures configuring the EBSCO RMI credentials for eholdings. Ansible generated error message:

TASK [ebsco-rmapi-config : Configure RM API credentials] ***********************
fatal: [10.36.1.203]: FAILED! => {"changed": false, "connection": "close", "content": "{\n  \"errors\" : [ {\n    \"title\" : \"Limit Exceeded\"\n  } ],\n  \"jsonapi\" : {\n    \"version\" : \"1.0\"\n  }\n}", "content_type": "application/vnd.api+json", "elapsed": 0, "json": {"errors": [{"title": "Limit Exceeded"}], "jsonapi": {"version": "1.0"}}, "msg": "Status code was 429 and not [204]: HTTP Error 429: Too Many Requests", "redirected": false, "status": 429, "transfer_encoding": "chunked", "url": "http://10.36.1.203:9130/eholdings/kb-credentials/80898dee-449f-44dd-9c8e-37d5eb469b1d"}


 Comments   
Comment by John Malconian [ 26/May/22 ]

Not sure what has changed here. I don't see any related recent changes to mod-kb-ebsco-java. Perhaps it's related to the credentials themselves. Maybe they are no longer valid or perhaps something has changed so that the credentials can only be configured for one instance of FOLIO?

Comment by John Malconian [ 26/May/22 ]

For now, I've disabled the ebsco-rmapi-config role in the folio-snapshot playbook.

Comment by John Malconian [ 26/May/22 ]
curl -w '\n' -i https://folio-snapshot-2-okapi.dev.folio.org/eholdings/kb-credentials/80898dee-449f-44dd-9c8e-37d5eb469b1d -H 'Accept: application/vnd.api+json' -H 'Content-Type: application/vnd.api+json' -H 'X-Okapi-Tenant: diku' -H "X-Okapi-Token: $OKAPI_TOKEN" -X PUT -d@rmi.json           
HTTP/2 429 
date: Thu, 26 May 2022 19:11:42 GMT
content-type: application/vnd.api+json

{
  "errors" : [ {
    "title" : "Limit Exceeded"
  } ],
  "jsonapi" : {
    "version" : "1.0"
  }
}
Comment by Khalilah Gambrell [ 26/May/22 ]

Hey John Malconian - EBSCO KB team is trying to resolve this issue. Hopefully it will be up and running again soon.

cc: Pavlo Smahin and Natalia Zaitseva

Comment by Khalilah Gambrell [ 03/Jul/22 ]

Issue happens on snapshot too.

Comment by Jakub Skoczen [ 11/Jul/22 ]

Natalia Zaitseva is there a specific issue that this should be blocked on?

Comment by Natalia Zaitseva [ 15/Jul/22 ]

John Malconian could you confirm that issue is still reproducible?

Comment by John Malconian [ 19/Jul/22 ]

Natalia Zaitseva - It looks like this issue has been resolved. I am able to manually post the EBSCO RMI configuration to both folio-snapshot and folio-snapshot-2. I've re-enabled setting this configuration in the daily folio-snapshot and folio-snapshot-2 builds.

Comment by John Malconian [ 19/Jul/22 ]

test build of folio-snapshot is successful. Closing this as resolved.

Comment by David Crossley [ 17/Aug/22 ]

This happened again today with build of [folio-snapshot-2/1436|https://jenkins-aws.indexdata.com/job/FOLIO_Reference_Builds/job/folio-snapshot-2/1436/consoleFull,] but was okay for subsequent builds. So somthing is erratic.

Generated at Thu Feb 08 23:28:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.