[FOLIO-3624] Vagrant box build failure Created: 02/Nov/22  Updated: 09/Nov/22  Resolved: 08/Nov/22

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

Type: Bug Priority: TBD
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-3597 Vagrant box: mod-data-export-worker c... Closed
Relates
relates to MODELINKS-16 Link update: Implement mechanism of s... Closed
relates to FOLIO-3568 Add ui-serials-management and mod-ser... Closed
Sprint: DevOps Sprint 151, DevOps Sprint 152
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

The folio/snapshot Vagrant box has not built successfully for the last several days. A typical failed run:

https://jenkins-aws.indexdata.com/job/Automation/job/folio-blackbox/7840/



 Comments   
Comment by Wayne Schneider [ 04/Nov/22 ]

Confirmed that same failure happens with local build.

Comment by Wayne Schneider [ 07/Nov/22 ]

The work for MODELINKS-16 Closed (creating a system user for mod-entities-links) did not include necessary updates to mod-entity-links' module descriptor to require the necessary interfaces. This causes the Vagrant build to fail, since it enables modules in order according to dependency resolution (so there is no guarantee that the necessary interfaces for system user creation will be available to the tenant when mod-entity-links is enabled).

Chances are pretty good that the EC2 reference builds are succeeding only by accident.

Comment by Wayne Schneider [ 08/Nov/22 ]

A second issue surfaced once the problem with MODELINKS-16 Closed was resolved. When mod-serials-management was added to the platform, an additional entry needed to be made in the group_vars/snapshot file of folio-ansible to ensure that the module is deployed in the Vagrant build (this is not required by the build for folio-snapshot, which uses the okapi-install.json file of platform-complete directly rather than building from dependencies). This was likely the original cause of the failure, as the problem with mod-entities-links was introduced only later.

Comment by David Crossley [ 09/Nov/22 ]

Erk sorry Wayne. I missed a step with mod-serials-management FOLIO-3568 Closed

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