[FOLIO-3467] folio-snapshot Vagrant box build failures Created: 06/Apr/22  Updated: 12/Apr/22  Resolved: 07/Apr/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:
Relates
relates to MODEXPS-82 Fix issue with permissions for EDIFAC... Closed
relates to MODEXPS-90 Fix issue with permissions for EDIFAC... Closed
relates to MODEXPS-67 Missing require on circulation-logs Closed
Sprint: DevOps Sprint 137
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

See e.g. this Jenkins job.

Failure is in the task for module deployment/enabling:

snapshot: TASK [okapi-tenant-deploy : Post install list for deployment and enabling] snapshot: fatal: [default]: FAILED! => {"changed": false, "connection": "close", "content_length": "90", "content_type": "text/plain", "elapsed": 223, "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.0.2.15:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadReference%3Dtrue%2CloadSample%3Dtrue%2CrunReindex%3Dtrue"}


 Comments   
Comment by Wayne Schneider [ 06/Apr/22 ]

In my testing, the issue seems to be that mod-data-export-spring cannot assign permissions to its system user. This from the mod-data-export-spring log:

16:42:28 [225626/proxy;830177/tenant] [diku] [] [mod-data-export-spring] ERROR olioTenantController [422 Unprocessable Entity] during [POST] to [http://perms/users] [PermissionsClient#create(PermissionUser)]: [{
  "errors" : [ {
    "message" : "Unable to update derived fields: Attempting to add non-existent permissions orders.item.get to permission user with id 8661ae0d-e838-4b1d-8693-de1897a3d05e",
    "type" : "1",
    "code" : "-1",
    "parameters" : [ {
      "key" : "id",
      "value" : "8661ae0d-e838-4b1d-8693-de1897a3d05e"
    } ]
  } ]
}]
feign.FeignException$UnprocessableEntity: [422 Unprocessable Entity] during [POST] to [http://perms/users] [PermissionsClient#create(PermissionUser)]: [{
  "errors" : [ {
    "message" : "Unable to update derived fields: Attempting to add non-existent permissions orders.item.get to permission user with id 8661ae0d-e838-4b1d-8693-de1897a3d05e",
    "type" : "1",
    "code" : "-1",
    "parameters" : [ {
      "key" : "id",
      "value" : "8661ae0d-e838-4b1d-8693-de1897a3d05e"
    } ]
  } ]
}]

After recording this error, mod-data-export-spring returns a 500 to the _tenant interface call, and Okapi returns a 400 to the tenant install call, failing the build.

It is a bit of a mystery why this should happen in the Vagrant build, but not in the EC2 build. orders.item.get is a permission defined by mod-orders. mod-orders should be initialized before mod-data-export-spring, based on the install.json file of platform-complete, but mod-data-export-spring does not require the orders interface. Adam Dickmeiss, would the work on OKAPI-939 Closed have an impact on this?

Viachaslau Khandramai – is it possible that mod-data-export-spring should have a dependency on the orders interface? I know that permissions are kind of a fuzzy part of an interface definition.

Comment by Viachaslau Khandramai (Inactive) [ 06/Apr/22 ]

Hi Wayne Schneider, I assume it's possible because Thunderjet team can integrate acquisitions functionality with mod-data-export-spring.

Let's ask Andrei Makaranka for additional details.

Thanks,

Slava

 

Comment by Adam Dickmeiss [ 07/Apr/22 ]

This is similar to MODEXPS-67 Closed and and due to OKAPI-662 Closed . See also https://github.com/folio-org/okapi/releases/tag/v4.13.0

Looks like things were broken after MODEXPS-82 Closed work.

Comment by Andrei Makaranka [ 07/Apr/22 ]

Hi Wayne Schneider,

Dependency added to module description.

Thanks

Comment by Wayne Schneider [ 07/Apr/22 ]

Thanks, Andrei Makaranka, Adam Dickmeiss, that seems to have taken care of the problem!

Comment by Marc Johnson [ 11/Apr/22 ]

Adam Dickmeiss Wayne Schneider

As the official version of Okapi for Lotus is 4.13.x, does this issue affect the Lotus release? And thus this change needs to be back ported to a version of mod-data-export-spring for Lotus?

cc: Magda Zacharska Viachaslau Khandramai Andrei Makaranka

Comment by Andrei Makaranka [ 11/Apr/22 ]

Hi Marc Johnson Adam Dickmeiss,

Let me know if bugfix needed and I will release.

Thanks

Comment by Marc Johnson [ 11/Apr/22 ]

Andrei Makaranka

Let me know if bugfix needed and I will release.

Thank you. I think I'll leave that decision to Adam Dickmeiss Jakub Skoczen or Wayne Schneider (it's a bit outside of my area of knowledge)

Comment by Wayne Schneider [ 12/Apr/22 ]

I believe that without backporting this module descriptor patch it may be difficult to build a Lotus system from scratch (it might not be an issue for an upgrade). If possible, I would recommend making a new release.

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