[FOLIO-2655] Upgrade fails on failure to update reference data Created: 22/Jun/20 Updated: 24/Mar/23 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P2 |
| Reporter: | Wayne Schneider | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | keep-bug, platform-backlog, platform-core | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | CP: Roadmap backlog | ||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||
| Description |
|
By using the UI or the APIs (that is, in sanctioned ways) it is possible to create user data that conflicts with incoming reference data on module upgrade. This conflict causes loading reference data to fail. This failure aborts the entire upgrade. Okapi continues to route to the original (un-upgraded) module set for the tenant. The storage module schemas, however, may have been fully or partially upgraded, so system storage may be left in an inconsistent state. It is likely impossible to know the state of the system storage without Okapi logfile analysis and module code inspection. There are a few ways to address this, from fairly simple to quite complex:
This issue was created to address the immediate concern of upgrade failure leaving a system in an inconsistent state. See also
|