[FOLIO-3398] folio-snapshot and folio-testing failures 24.1.2021 Created: 24/Jan/22  Updated: 25/Jan/22  Resolved: 25/Jan/22

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

Type: Story Priority: TBD
Reporter: Jakub Skoczen Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to MODPUBSUB-211 Replace Future<Boolean> by Future<Void> Closed
relates to MODEXPS-67 Missing require on circulation-logs Closed
relates to MODPUBSUB-210 Incorrect status for tenant init Closed
Sprint: DevOps sprint 132
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

All reference environment builds are broken yesterday and today. So there are no reference environments available.
Perhaps it is compounded by those issues that were not fixed on Friday.
The recent folio-snapshot build 1211 (https://jenkins-aws.indexdata.com/job/FOLIO_Reference_Builds/job/folio-snapshot/1211/consoleFull) reports:

POST request for mod-data-export-spring-1.3.0-SNAPSHOT.138 /_/tenant failed with 500: [422 Unprocessable Entity] during [POST] to http://perms/users PermissionsClient#create(PermissionUser):
... "Unable to update derived fields: Attempting to add non-existent permissions circulation-logs.collection.get to permission user with id 0b16e902-319b-4263-aed8-7719a0ed8427"



 Comments   
Comment by David Crossley [ 25/Jan/22 ]

Now that MODEXPS-67 Closed is fixed for mod-data-export-spring to require mod-audit, the folio-snapshot builds are happy.

The folio-testing refenv is failing due to the module init sequence now needing mod-audit to happen earlier. So research its use and raise mod-audit sequence.

Comment by David Crossley [ 25/Jan/22 ]

Done. The folio-testing is now also back in action.

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