Skip to:

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

Holdings process status issue

Description

Environment : Running a single tenant in a single container on an EC2 instance

Uses : Sandbox RM API "apidvgvmt" account

Holdings process triggered as expected and ran successfully(loaded all holdings in DB). However, the holdings_status table does not reflect the correct state. I would expect it to be showing a status of "completed" where as it shows the below:

Logs are attached.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Andrii Paias October 15, 2019 at 11:20 AM

,
There is a pull request that should fix this issue: https://github.com/folio-org/mod-kb-ebsco-java/pull/186

Sobha Duvvuri October 14, 2019 at 5:17 PM

- not sure what's the status of this story? Its "In Review" column - has this issue been fixed in code or a user story written to deal with this?

Sobha Duvvuri October 1, 2019 at 12:35 PM

Ok, yes. From a hosting point of view, it is very much possible that module will be upgraded after its enabled for a given tenant. In this example, we did upgrade this module from a previous version. Could you please add a user story to fix this? Thanks!

Andrii Paias October 1, 2019 at 9:07 AM

The only time we set status to "Not started" is when module is assigned to tenant or module is upgraded for tenant.
This issue probably happens because module is redeployed/upgraded, and the status gets reset to "Not started". This can be fixed by checking if there is already status in datbase, before overriding it.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 27, 2019 at 7:49 PM
Updated October 18, 2019 at 1:13 PM
Resolved October 18, 2019 at 1:13 PM
Configure
TestRail: Cases
TestRail: Runs