Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

folio-snapshot and folio-testing failures 24.1.2021

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"

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

David CrossleyJanuary 25, 2022 at 3:38 AM

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

David CrossleyJanuary 25, 2022 at 1:47 AM

Now that 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.

Done

Details

Assignee

Reporter

Priority

Sprint

Development Team

FOLIO DevOps

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 24, 2022 at 10:32 AM
Updated January 25, 2022 at 3:38 AM
Resolved January 25, 2022 at 3:38 AM
TestRail: Cases
TestRail: Runs