[FOLIO-3470] cannot connect to folio registry Created: 11/Apr/22  Updated: 13/Apr/22

Status: In Progress
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P2
Reporter: Jakub Skoczen Assignee: John Malconian
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by OKAPI-1091 Exception for SemVer with component 4... Closed
Sprint: DevOps Sprint 137
Development Team: None
RCA Group: TBD

 Description   

These failures seem to be caused by a failure to fetch module descriptors from the shared repository:

HttpMethod: POST
URL: http://172.17.0.3:9130/_/proxy/pull/modules
Content-Type: application/json; charset=UTF-8
Accept: application/json
Sending request to url: http://172.17.0.3:9130/_/proxy/pull/modules
Response Code: HTTP/1.1 400 Bad Request



 Comments   
Comment by Marc Johnson [ 11/Apr/22 ]

Julian Ladisch did some further investigation into this (based upon a related issue reported in the DevOps slack channel)

In that investigation, he reports the following request and response:

curl -w"\n" -D - https://folio-registry.dev.folio.org/_/proxy/modules
HTTP/2 500
date: Mon, 11 Apr 2022 10:14:13 GMT
content-type: text/plain
content-length: 30
server: nginx/1.18.0 (Ubuntu)
vary: origin

For input string: "4000001006"

A quick search for the error message (For input string: ...) suggests that this is caused by a NumberFormatException.

Based upon my understanding that Okapi attempts to parse version numbers (in order to sort descriptors). That leads me to the hypothesis:
that we have a module descriptor with part of a version number that is too big for an integer. I imagine this is likely to be a build number appended onto the version.

cc: Pavel Spichonak Stanislau Snapok

Comment by Marc Johnson [ 11/Apr/22 ]

Jakub Skoczen John Malconian

I have disabled the platform-complete-snapshot and platform-complete-snapshot-core builds in order to stop redundant builds and error alerts.

Comment by John Malconian [ 11/Apr/22 ]

Adam Dickmeiss has provided branch 'OKAPI-1091-semver-exception' of Okapi to address this issue. I've got it running on the folio-registry and it appears to resolve the issue. Module descriptors can be successfully POST'ed and pulled from the registry. Will update folio-registry with next Okapi release that includes the fix. In the meantime, folio-registry will run from OKAPI-1091-semver-exception branch.

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