/item-storage/items fails because "module name: netty_parent"

Description

Overview:
/item-storage/items query=barcode=4539876054383 fails with NullPointerException caused by null routingContext.
Steps to Reproduce:
Run target/mod-inventory-storage-fat.jar from master.
POST /_/tenant
to install mod-inventory-storage module for the tenant.
The log shows:

The incorrect module name netty_parent is used to create the database schema diku_netty_parent.

This will also show on every reference environment build when mod-courses fails to retrieve some sample data form mod-inventory-storage. Worth noting that inventory storage was recently updated to java 11.

stacktrace from mod-inventory-storage from folio-snapshot

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Julian Ladisch August 19, 2020 at 3:50 PM

Yes, mod-inventory-storage is completely broken because of the wrong schema name.
I suggest to revert the upgrade to java 11.
There should be an integration test (*IT.java) executed by maven-failsafe-plugin that checks that the jar file works.

Ian Hardy August 19, 2020 at 2:25 PM

one more strange detail. okapi reports mod-inventory-storage is enabled for diku

But, there is no schema diku_mod_inventory_storage in the db

Julian Ladisch August 19, 2020 at 2:23 PM

NullPointerException at PgUtil.streamGet(PgUtil.java:585) means that routingContext is null:

Ian Hardy August 19, 2020 at 2:04 PM

or would either of you have a chance to look at this issue/log? mod-inventory-storage throwing an error while loading sample data after the last snapshot.

Done

Details

Assignee

Reporter

Priority

Development Team

Core: Platform

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 19, 2020 at 2:03 PM
Updated October 8, 2020 at 10:23 AM
Resolved August 25, 2020 at 1:39 PM
TestRail: Cases
TestRail: Runs