[FOLIO-2676] Unable to build q1-2020 release from platform-complete Created: 02/Jul/20  Updated: 23/Mar/21  Resolved: 23/Mar/21

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

Type: Bug Priority: TBD
Reporter: Wayne Schneider Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: devops, devops-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File response.txt     Text File success.txt    
Sprint:
Development Team: FOLIO DevOps
Affected Institution:
Lehigh

 Description   

Overview:
When attempting to enable the set of modules in install.json of the q1-2020 branch of platform-complete with a fully-populated Okapi module descriptor registry, Okapi claims that mod-inventory-storage-19.2.3 is now required, while 19.1.3 is what's in install.json

Steps to Reproduce:

  1. Set up Okapi 2.40.0 with a tenant
  2. Pull module descriptors from http://folio-registry.aws.indexdata.com
  3. Post install.json file to /_/proxy/tenants/tenantId/install?simulate=true

Expected Results:
Successful response to HTTP request with body containing a JSON structure that matches install.json

Actual Results:
Error as described above

Christopher Creswell can provide more details



 Comments   
Comment by John Malconian [ 02/Jul/20 ]

Is this as simple as upgrading mod-inventory-storage to v19.2.3 in the q1 branch? Although I suppose that might open a whole can of dependency worms.

Comment by Wayne Schneider [ 02/Jul/20 ]

Maybe? But I don't understand why Okapi is not honoring the full install JSON request (which should include a compatible version of mod-inventory-storage) and is instead trying to give us a new version.

Comment by Adam Dickmeiss [ 03/Jul/20 ]

I tried this and NO error. install.json has mod-inventory-storage-19.1.3 in it still. See attachment success.txt with okapi log and response.txt with result of install.

Comment by Wayne Schneider [ 06/Jul/20 ]

I was also unable to replicate this problem. Christopher Creswell, can you verify the reproduction steps? Thanks!

Comment by Christopher Creswell [ 06/Jul/20 ]

I don't actually submit the entire install.json all at once – perhaps that's the difference? My build script submits individual json for each module to enable, enabling them in the order they appeared in install.json, but not all at once. I had it do things this way because of problems I was having in the past, but which may no longer be present, so I could probably just submit one big file of modules to enable if that's in fact the issue.

Comment by Wayne Schneider [ 06/Jul/20 ]

I cannot reproduce the issue posting modules one at a time to /_/proxy/tenants/tenantId/install, nor posting to /_/proxy/tenants/tenantId/modules.

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