[FOLIO-3877] Add mod-lists to snapshot hosted environments Created: 25/Aug/23  Updated: 13/Sep/23  Resolved: 06/Sep/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Matt Weaver Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File okapi.log.bz2    
Issue links:
Blocks
blocks RANCHER-970 Include FQM modules to rancher pipelines Closed
Cloners
is cloned by FOLIO-3878 Add ui-lists to snapshot hosted envir... Closed
Relates
relates to MODLISTS-12 Investigate/fix mod-list getting OOM ... Closed
Sprint: DevOps Sprint 160
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

Hi DevOps, we'd like a new module (mod-lists. https://github.com/folio-org/mod-lists) added to the hosted environments for testing and demo purposes.



 Comments   
Comment by David Crossley [ 28/Aug/23 ]

For new modules, please follow the steps https://dev.folio.org/guides/install-backend-module/

For one thing, this module has a broken mainline branch build. As said at that document, when "snapshot artifacts are being reliably generated by the continuous integration".

Note that the "testing" reference environment was discontinued long ago.

Comment by Matt Weaver [ 28/Aug/23 ]

Thanks for taking a look David Crossley! I'm working on getting the build issues sorted out ASAP. Not having the testing environment is fine; it was mentioned in the example given for how to request adding new modules to the ref envs, so I included it here

Comment by David Crossley [ 29/Aug/23 ]

Hah, you found the only remaining mention of folio-testing in the docs. I removed it today. Thanks.

Comment by David Crossley [ 05/Sep/23 ]

Today i tried to add mod-lists to the platform-complete snapshot branch. That is Step 1 for adding to the reference environment folio-snapshot. (platform-hourly-build)

However that failed (see Slack channel #hosted-reference-envs). So i needed to remove mod-lists.

See Jenkins build output from one of the failed hourly builds (20787).

(The next hourly run 20788 is successful following my removal of mod-lists. So i presume that that proves that the problem is with mod-lists or mod-fqm-manager, and not with mod-inventory-storage.)

Tenant operation failed for module mod-inventory-storage-26.1.0-SNAPSHOT.887:
SQL error\n WITH item_circnotes ...
... WHERE item.id = item_circnotes.itemId AND item_circnotes.changed;\nERROR: function public.uuid_generate_v4() does not exist (42883)"

See the attachment okapi.log.bz2 obtained from that failed build.

Comment by David Crossley [ 06/Sep/23 ]

The above-mentioned uuid-ossp problem was fixed via MODLISTS-3 Closed .

Comment by David Crossley [ 06/Sep/23 ]

Hooray, success.

The mod-lists is now added to platform-complete snapshot branch, and the subsequent platform-hourly-build (run 20807) was successful.

So it will will be in the folio-snapshot-2 build after today's run (and folio-snapshot 12 hours later).

By the way, similar pieces are missing from the README as explained at FOLIO-3879 Closed .

Comment by Matt Weaver [ 06/Sep/23 ]

Woooooo! Thanks, David Crossley!

(and I created MODLISTS-4 Closed to add the missing items to the README)

Comment by David Crossley [ 13/Sep/23 ]

Matt Weaver – While doing an un-related task today, i noticed on folio-snapshot and folio-snapshot-2 that mod-lists container is being "OOM Killed" some short time after startup.

Dunno if it helps: https://dev.folio.org/faqs/how-to-obtain-refenv-logs/

Comment by Matt Weaver [ 13/Sep/23 ]

Yikes! That's definitely not supposed to happen... Thanks for the heads up!

Comment by Matt Weaver [ 13/Sep/23 ]

David Crossley, I saw in the Rancher environment docs that Spring Boot modules need more resources to run than RMB modules. If that applies to the snapshot environments, too, then we might need to give mod-lists a little more breathing room since it uses Spring Boot

Update: after some searching on slack, I found out that this is configured in the module descriptor, so it's something we can change ourselves easily. In our old dev environment, we bumped its memory up to 3 GiB (the module can get pretty RAM-hungry when exporting lists), so we're going to make that same change in the MD

Generated at Thu Feb 08 23:31:27 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.