[FOLIO-2180] Snapshot builds fail due to orders interface dependency mismatch Created: 22/Jul/19  Updated: 03/Jun/20  Resolved: 23/Jul/19

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

Type: Bug Priority: P2
Reporter: Marc Johnson Assignee: David Crossley
Resolution: Done Votes: 0
Labels: ci, compatibility-breaking, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by ERM-350 Supports orders interface 7.0 Closed
Relates
relates to FOLIO-2181 Platform complete build fails due to ... Closed
Sprint: CP: sprint 68
Story Points: 0.5
Development Team: Core: Platform

 Description   

As reported by Aliaksei Chumakou on slack on Saturday the snapshot environment build failed due to a mismatch between major versions of the orders interface expected.

The Jenkins build fails with the following error

fatal: [10.36.1.58]: FAILED! => {"changed": false, "connection": "close", "content": "Incompatible version for module mod-erm-usage-2.4.0-SNAPSHOT.56 interface organizations-storage.organizations. Need 1.0. Have 2.0/mod-orders-7.1.0-SNAPSHOT.196/mod-gobi-1.7.0-SNAPSHOT.90/folio_invoice-1.0.100044/folio_plugin-find-po-line-1.0.100016/folio_orders-1.5.1000442/folio_organizations-1.2.100087. Incompatible version for module folio_agreements-3.0.1000173 interface orders. Need 6.0. Have 7.0/mod-gobi-1.7.0-SNAPSHOT.90/folio_plugin-find-po-line-1.0.100016/mod-invoice-1.1.0-SNAPSHOT.47/folio_orders-1.5.1000442", "content_length": "522", "content_type": "text/plain", "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.36.1.58:9130/_/proxy/tenants/diku/install?simulate=true"}

Mod-gobi forces the need for orders 7.0 and ui-agreements only supports orders 6.0 meaning that a congruent backend cannot be built.

This also includes an error about mod-ermusage and the organizations-storage.organizations interface version, indicating that there might be multiple mismatches here (and separate issues might be needed for these).



 Comments   
Comment by Jakub Skoczen [ 22/Jul/19 ]

Marc Johnson Guys, I am assigning this to David and blocking on ERM-350 Closed .

Comment by md331 (Inactive) [ 22/Jul/19 ]

I've merged a PR to ui-agreements to support 7.0 and closed ERM-350: https://github.com/folio-org/ui-agreements/pull/245

Comment by Marc Johnson [ 22/Jul/19 ]

It appears that a fix for the mod-ermusage dependency has already been merged (Jag Goraya I don't know the process that led to that, so maybe you can investigate)

And md331 appears to have merged a change for UI agreements.

I am going to kick off a snapshot environment build to see if that resolves the issues (right after the platform build finishes).

Comment by David Crossley [ 23/Jul/19 ]

The regular automated builds of folio-snapshot and folio-testing related Jenkins jobs are okay today.

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