[FOLIO-2288] Inconsistent backend ModuleDescriptors in folio-registry for some modules Created: 26/Sep/19  Updated: 03/Jun/20  Resolved: 27/Sep/19

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

Type: Bug Priority: TBD
Reporter: David Crossley Assignee: Kostyantyn Khodarev
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: EPAM-Veg Sprint 25
Development Team: Vega

 Description   

While investigating Docker container memory allocation in some VMs and reference environments, i found that some containers are missing the memory "limit" as specified in the new LaunchDescriptors. The three erroneous one are mod-password-validator, mod-event-config, mod-calendar.

Investigating their "latest" MD in the "folio-registry" shows that there are older ones, which are using a higher version number than the current master branch's POM version.

Investigating the git history of their POM:

For example, mod-password-validator:
was 1.5.0-SNAPSHOT
then prepared for recent 1.4.1 release
then moved the POM in master to 1.4.2-SNAPSHOT

So now the "latest" MD in the registry (1.5.0-SNAPSHOT) is actually older than the current master. (Hence missing the new LaunchDescriptor.)

This means that the module that is available in the VMs and the "snapshot" and "testing" environments is actually an older version.

The Release Procedures do have a note about this:
https://dev.folio.org/guidelines/release-procedures/#prepare-and-perform-the-source-release
Search for: next post-release “new development version”



 Comments   
Comment by David Crossley [ 27/Sep/19 ]

The "version" in those POMs are now updated. I verified the "latest" MDs in folio-registry is now proper. Today's "folio-testing" reference environment now has the latest snapshot of each.

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