Known issues

[RANCHER-2300] Shift duties - Sprint 216 - FOLIO Jira

mgr-* components deployment issue, 401 error.

Resolved

Check ASG IAM instance profile, if AWS SSM permissions missing, assign to role.

[MSEARCH-750] Mod-search Out Of Memory Error - FOLIO Jira (atlassian.net)

Re-index blocker

Resolved

MODSER-4001505d01-b853-3c2e-90f1-ee9b165564fcSystem Jira

Update modules issue mod-serials-management mod-licenses

Resolved

UILISTS-16801505d01-b853-3c2e-90f1-ee9b165564fcSystem Jira

Yarn lock build issue on folio-lists

Resolved

-

mod-data-import not working with s3 based env if env variable S3_FORCEPATHSTYLE set true

Active

Eureka environment log-in issue

Active
Possible solution: restart the modules mod-login mod-permission mod-users-keycloak mod-roles-keycloak

MSEARCH-956

"errors": [{ "message": "OpenSearch exception [type=search_phase_execution_exception, reason=all shards failed]", "type": "OpenSearchStatusException", "code": "elasticsearch_error", "parameters": [] }], "total_records": 1 }

Resolved
On diku (NonECS tenant), ui-inventory will not work, until mod-search is restarted and reindex re-triggered. Automated workaround on the page: Rancher FAQ - Folio Development Teams - FOLIO Wiki

None

Eureka karate tests mod-agreements (family modules) OOM - source

Resolved

None

API POST https://folio-edev-volaris-2nd-kong.ci.folio.org/users-keycloak/users returns TenantNotEnabledException for test tenants

Active

None

mod-patron-blocks does NOT create or use a system user

📌 Confirmed via community discussion (Slack thread, March 2024):
mod-patron-blocks does not create any system user in Keycloak or in FOLIO upon entitlement. It does not have a system user of its own.

The /patron-block-limits?limit=2147483647 call is made by mod-scheduler using the {tenantId}-system-user (e.g. sul-system-user), which is the Eureka per-tenant system user created by mod-scheduler upon entitlement — not by mod-patron-blocks.

⚠️ Important: Any reference to a "mod-patron-blocks system user" is incorrect. Troubleshooting Access Denied errors on /patron-block-limits should focus on:

• The {tenantId}-system-user capabilities in Keycloak (created by mod-scheduler)

• mod-scheduler sidecar configuration (ROUTING_DYNAMIC_ENABLED=true)

• Timer configuration in mod-scheduler

Active / Documented

Focus troubleshooting on mod-scheduler's {tenantId}-system-user and its capabilities. Do NOT look for a mod-patron-blocks system user — it does not exist.