[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: |
|
||||||||
| 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 |
| 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: |
| Comment by Marc Johnson [ 11/Apr/22 ] |
|
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. |