Failed to fetch ECS TLR settings from mod-tlr in Ramsons release
Description
FSE reported an issue while testing internal environment that is on Ramsons okapi version. Investigate the issue with the Ramsons environment. Based on the errors listed below, it appears that the feature toggle isn't functioning, and mod-patron is making calls to mod-tlr:
Yes, there was a problem with the feature toggle while checking the environment configuration. Mod-patron determines if it's operating in a consortia environment and encountered a failure because mod-tlr was missing. This issue was only reproducible in non-consortia environments
Additionally, the RRT thread related to this issue was closed after deploying mod-patron v6.2.8, which resolved the problem. Requests from Locate are now being created without any issues. I believe this ticket can also be closed
Stephanie Buck February 13, 2025 at 4:03 PM
Sorry if I’m not catching on, . Is it a single tenant only issue because it’s to do with the feature toggle? I have this memory of someone saying “mod-tlr is only deployed in ECS/multitenant environments”. I just want to make sure I’ve got the proper understanding. Thank you!
Roman Barannyk February 12, 2025 at 1:45 PM
Edited
The RRT reporter confirmed that the instance hold request was successful in a single tenant environment, and the provided logs indicate that the feature toggle fix is functioning as expected:
The reporter also mentioned another issue related to item level requests in a multi-tenant environment, which will be addressed as part of BF-1036
FSE reported an issue while testing internal environment that is on Ramsons okapi version.
Investigate the issue with the Ramsons environment. Based on the errors listed below, it appears that the feature toggle isn't functioning, and mod-patron is making calls to mod-tlr: