Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Fix several tenants usage errors for data export process

Description

Purpose/Overview:

Logs for data export process have numerous issues related to tenants usage mostly for SCHEDULED job. The jobs could be not found in one tenant but they exist in another:

The issues could be related to multy-tenancy usage for mod-data-export-spring module.

Actual result:

Issues relates to multy-tenancy usage in the logs

Acceptance criteria:

Multy-tenancy issues do not exist

Notes: the errors are visible at mod-data-export-spring:1.1.3 and mod-data-export-worker:1.1.6.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Aliaksei HarbuzFebruary 4, 2022 at 11:40 AM

The ticket is verified in scope of .

Oleksandr BozhkoFebruary 3, 2022 at 12:13 PM

- this story has been verified in scope of https://folio-org.atlassian.net/browse/MODEXPW-67

Oleksandr BozhkoFebruary 2, 2022 at 1:42 PM
Edited

- second bug (jobs that get stuck in SCHEDULED status) now is reproducible on testing environment and has been fixed in scope of https://folio-org.atlassian.net/browse/MODEXPW-67.

Oleksandr BozhkoJanuary 27, 2022 at 9:28 AM
Edited

- there are two bugs here: 1) ERROR mentioned in the Description, and 2) jobs that get stuck in SCHEDULED status. Both of them are reproducible on production environment, but only the first bug can be seen on testing, snapshot, or bugfest. Hence, only the first bug has been fixed, tested and verified. However, there is a good chance that the second bug will be fixed as well due to the fact that the reason of the second bug is the first bug with a high probability, but actually it cannot be tested properly until the code changes are deployed on production environment (versions of modules are different on prod and bugfest environments). And yet it should be noted that the issue may still appear on production environment after release.

Steps for verification:

  1. Go to Circulation log and apply filter for Loan to have at least a couple of records (for example, Checked out).

  2. Go to Actions -> Export results (CSV).

  3. Repeat Step 2 at least 50 times and wait for the completion of all jobs.

  4. Go to Export manager and make sure all jobs are completed and there are no jobs with SCHEDULED status.

  5. Retrieve logs for mod-data-export-spring and make sure there is no ERROR mentioned in the Description.

Magda ZacharskaJanuary 10, 2022 at 5:36 PM

It is planned for the Lotus release

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Firebird

Fix versions

Release

Lotus R1 2022

Affected Institution

Caltech
Middle Tennessee State University
Skidmore College
University of Tennessee Martin

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 23, 2021 at 8:14 AM
Updated June 14, 2022 at 9:40 AM
Resolved February 4, 2022 at 11:43 AM
TestRail: Cases
TestRail: Runs