Issues

Select view

Select search mode

 

Q2 to Q3 upgrade - "POST request for module_version /_/tenant failed with REVOKE ALL PRIVILEGES ON SCHEMA public FROM module_schema;"

Done

Description

Upgrading in-place from Q2-2020 hotfix 4 + patches to Q3 yields the the following errors from Okapi for more than several modules:

This affects the following modules:
mod-orders-storage-11.1.0
mod-inventory-storage-19.4.1
mod-login-7.1.0
mod-circulation-storage-12.1.0
mod-organizations-storage-3.2.0
mod-finance-storage-6.0.0
mod-calendar-1.10.0
mod-template-engine-1.10.0
mod-feesfines-15.9.1
mod-patron-blocks-1.1.0
mod-notes-2.10.0
mod-notify-2.7.0
mod-courses-1.1.0
mod-data-import-converter-storage-1.9.0
mod-source-record-manager-2.4.0
mod-data-import-1.11.0
mod-tags-0.7.0
mod-erm-usage-3.0.0
mod-erm-usage-harvester-2.0.0
mod-invoice-storage-4.1.0
mod-password-validator-1.8.0

The database logs also have the following error:

Module log reflecting the database error:

A full Okapi response error for one of the modules:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1

blocks

Checklist

hide

TestRail: Results

Details

Assignee

Reporter

Priority

Sprint

Development Team

Core: Platform

Fix versions

Release

Q3 2020 Bug Fix

Affected Institution

TAMU

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 26, 2020 at 6:20 PM
Updated October 6, 2022 at 9:35 AM
Resolved November 2, 2020 at 9:59 AM

Activity

Show:

Marc JohnsonNovember 6, 2020 at 9:25 AM

mod-circulation-storage 12.1.2 with RAML Module Builder 31.1.5 has been released.

Julian LadischNovember 5, 2020 at 6:02 PM

In the core platform meeting we decided that we don't release RMB 31.1.6. Instead we would like all database (= storage) modules to upgrade to 31.1.5. After that we test the Q2 to Q3 migration with RMB 31.1.5 (). Therefore we need a mod-circulation-storage release with RMB 31.1.5.

Marc JohnsonNovember 5, 2020 at 5:53 PM

I'm confused. Earlier today, I was told on Slack that the fix included in RAML Module Builder 31.1.5 did not resolve this issue.

As such, new change was being prepared (). That meant that the release of mod-circulation-storage could be deferred until the new fix was verified and a new RAML Module Builder version released.

There is now a conversation about testing the released module versions (including mod-circulation-storage) with RAML Module Builder 31.1.5

Has that situation changed? Does the Core Functional team need to upgrade mod-circulation-storage to RAML Module Builder 31.1.5 and release it before this issue can be verified?

jrootNovember 5, 2020 at 5:47 PM

I think if I do that - I will still hit the problems, as not all modules are upgraded yet.

Julian LadischNovember 5, 2020 at 5:40 PM

If you really want to immediately test with only half of the modules being upgraded to RMB 31.1.5 you may take the module list from https://github.com/folio-org/platform-complete/tree/q3-2020

TestRail: Cases
TestRail: Runs