[FOLIO-1313] Convert folio-ansible to use module-sample-data for loading inventory data Created: 26/Jun/18  Updated: 12/Nov/18  Resolved: 09/Jul/18

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

Type: Task Priority: P2
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, sprint41, sprint42
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1221 Bootstrap Resource types from RDA Con... Closed
blocks FOLIO-1222 Bootstrap Format from RDA Carrier list Closed
Relates
relates to MODAT-27 Add creation timestamp to token on cr... Closed
relates to FOLIO-1085 Add static user and item data each ti... Open
relates to FOLIO-1203 Bootstrap Contributor types from MARC... Closed
relates to FOLIO-1234 Need Better Bootstrap Data for Loans Closed
relates to FOLIO-1323 Merge Inventory reference changes - m... Closed
Sprint:

 Description   

The module-sample-data role allows us to use sample data stored in the module repo, rather than duplicating sample data in folio-ansible



 Comments   
Comment by Wayne Schneider [ 09/Jul/18 ]

This is working for all builds except folio-testing-backend01 on AWS, which reports:

TASK [folio-ansible/roles/module-sample-data : Load module data to /classification-types] ***
failed: [10.36.1.78] (item=/tmp/module-sample-data/mod-inventory-storage/reference-data/classification-types/UDC.json) => {"changed": false, "connection": "close", "content": "Access requires permission: inventory-storage.classification-types.item.post", "data_file": "/tmp/module-sample-data/mod-inventory-storage/reference-data/classification-types/UDC.json", "failed": true, "msg": "Status code was not [201, 400]: HTTP Error 403: Forbidden", "redirected": false, "status": 403, "transfer_encoding": "chunked", "url": "http://ip-10-36-1-78.ec2.internal:9130/classification-types", "x_okapi_trace": "POST mod-authtoken-1.4.1-SNAPSHOT.21 http://10.36.1.78:9131/classification-types : 403 2755us"}

The diku_admin user does have the appropriate permissions, and outside of the build process, can create classification-types.

Comment by John Malconian [ 09/Jul/18 ]

I wonder if this is related at all to https://folio-org.atlassian.net/browse/FOLIO-1312

Comment by Wayne Schneider [ 09/Jul/18 ]

It does seem very similar. By introducing a 10 second delay at the end of the tenant-admin-permissions role, I was able to get the build to proceed. I've pulled in Kurt Nordstrom to take a look – Kurt Nordstrom, if you find an issue with mod-permissions, please feel free to just file a bug there. I will close this one.

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