[FOLIO-1161] Snapshot builds failing due to admin account not present Created: 26/Mar/18  Updated: 12/Nov/18  Resolved: 26/Mar/18

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

Type: Bug Priority: P1
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, sprint35
Remaining Estimate: Not Specified
Time Spent: 1 hour, 45 minutes
Original estimate: Not Specified

Sprint:

 Description   

Report from Marc Johnson:
It looks like the folio-snapshot environment (https://jenkins-aws.indexdata.com/job/Automation/job/folio-snapshot/163/consoleFull) and snapshot VM (https://jenkins-aws.indexdata.com/job/Automation/job/folio-blackbox/516/consoleFull, but not the testing VM oddly) builds failed due to not being able to find the diku_admin

The testing-backend build also failed, but this seemed to be for a different reason, so I’ve re-triggered it.

folio-snapshot environment

fatal: [10.36.1.27]: FAILED! => {"accept": "application/json, text/plain", "accept_encoding": "identity", "changed": false, "connection": "close", "content": "{\n  \"endpoint\" : \"/authn/login\",\n  \"statusCode\" : 500,\n  \"errorMessage\" : \"Error verifying user existence: No user found by username diku_admin\"\n}", "content_type": "text/plain", "failed": true, "host": "folio-snapshot-163.aws.indexdata.com:9130", "msg": "Status code was not [201]: HTTP Error 500: Internal Server Error", "redirected": false, "status": 500, "transfer_encoding": "chunked", "url": "http://folio-snapshot-163.aws.indexdata.com:9130/bl-users/login", "user_agent": "ansible-httpget", "x_okapi_permissions": "[]", "x_okapi_request_id": "553372/bl-users", "x_okapi_tenant": "diku", "x_okapi_token": ...

snapshot VM

    snapshot: fatal: [default]: FAILED! => {"accept": "application/json, text/plain", "accept_encoding": "identity", "changed": false, "connection": "close", "content": "{\n  \"endpoint\" : \"/authn/login\",\n  \"statusCode\" : 500,\n  \"errorMessage\" : \"Error verifying user existence: No user found by username diku_admin\"\n}", "content_type": "text/plain", "host": "10.0.2.15:9130", "msg": "Status code was not [201]: HTTP Error 500: Internal Server Error", "redirected": false, "status": 500, "transfer_encoding": "chunked", "url": "http://10.0.2.15:9130/bl-users/login", "user_agent": "ansible-httpget", "x_okapi_permissions": "[]", "x_okapi_request_id": "010804/bl-users", "x_okapi_tenant": "diku", "x_okapi_token": ...


 Comments   
Comment by Wayne Schneider [ 26/Mar/18 ]

Pretty sure it's this commit that broke it: https://github.com/folio-org/folio-ansible/commit/0d91629d9ff412a36d67fb638558ac916abd38a0

This was needed to prevent the stripes-testing build from attempting to run the mod-auth-data role (which creates the admin user).

Comment by Wayne Schneider [ 26/Mar/18 ]

Will be fixed in next build.

Comment by Wayne Schneider [ 27/Mar/18 ]

Reopening, as the folio-snapshot.aws.indexdata.com build is still broken.

Comment by Wayne Schneider [ 27/Mar/18 ]

Reordered execution of roles in folio-snapshot.yml, build now succeeds.

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