[FOLIO-2788] mod-audit failure on Vagrant snapshot build Created: 08/Sep/20  Updated: 15/Sep/20  Resolved: 09/Sep/20

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 FOLIO-2799 Align Vagrant snapshot build with AWS... Open
Sprint: DevOps: Sprint 97
Development Team: FOLIO DevOps

 Description   

It looks like there is a problem with the mod-audit startup in the Vagrant "snapshot" build.

snapshot: TASK [okapi-tenant-deploy : Post install list for enabling modules (no deployment)] ***
snapshot: fatal: [default]: FAILED! => {"changed": false, "connection": "close", "content": "No running instances for module mod-audit-0.0.5-SNAPSHOT.37. Can not invoke /_/tenant", "content_length": "85", "content_type": "text/plain", "elapsed": 4, "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?tenantParameters=loadReference%3Dtrue%2CloadSample%3Dtrue"}


 Comments   
Comment by Wayne Schneider [ 09/Sep/20 ]

mod-audit was not specified in the group_vars/snapshot variable file. I added it to the file and did a little cleanup to align better with the install files on platform-complete.

Comment by Jakub Skoczen [ 10/Sep/20 ]

Wayne Schneider David Crossley we discussed that the Vagrant box should be aligned with the new method of creating ref envs. Wayne Schneider will create a ticket for that.

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