[FOLIO-560] http://folio-uidemo.aws.indexdata.com/ is down Created: 13/Apr/17 Updated: 12/Nov/18 Resolved: 13/Apr/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P2 |
| Reporter: | Wolfram Schneider | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 4 hours | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Our demo site http://folio-uidemo.aws.indexdata.com/ does not response, and times out. |
| Comments |
| Comment by Wolfram Schneider [ 13/Apr/17 ] |
|
I see that the jenkins job FOLIO_UI_Demo_2 failed last night https://jenkins-aws.indexdata.com/job/FOLIO_UI_Demo_2/30/console TASK [mod-auth-data : Create mod-auth credentials for other users] ************* failed: [uidemo02] (item={u'username': u'auth_test1', u'password': u'diku', u'permissions': [u'module.users.enabled', u'perms.permissions.get', u'perms.users.get', u'users.read', u'usergroups.read']}) => {"changed": false, "connection": "close", "content": "", "failed": true, "item": {"password": "diku", "permissions": ["module.users.enabled", "perms.permissions.get", "perms.users.get", "users.read", "usergroups.read"], "username": "auth_test1"}, "msg": "Status code was not [201, 422]: HTTP Error 403: Forbidden", "redirected": false, "status": 403, "transfer_encoding": "chunked", "url": "http://10.36.1.77:9130/authn/credentials", "x_okapi_trace": "POST authtoken http://10.36.1.77:9136/authn/credentials : 403 28748us"} failed: [uidemo02] (item={u'username': u'auth_test2', u'password': u'diku'}) => {"changed": false, "connection": "close", "content": "", "failed": true, "item": {"password": "diku", "username": "auth_test2"}, "msg": "Status code was not [201, 422]: HTTP Error 403: Forbidden", "redirected": false, "status": 403, "transfer_encoding": "chunked", "url": "http://10.36.1.77:9130/authn/credentials", "x_okapi_trace": "POST authtoken http://10.36.1.77:9136/authn/credentials : 403 33684us"} to retry, use: --limit @/home/jenkins/workspace/FOLIO_UI_Demo_2/CI/ansible/folio-uidemo02.retry PLAY RECAP ********************************************************************* uidemo02 : ok=195 changed=125 unreachable=0 failed=1 FATAL: command execution failed hudson.AbortException: Ansible playbook execution failed at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:226) at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:199) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1730) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405) $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 25741 killed; [ssh-agent] Stopped. ERROR: Ansible playbook execution failed |
| Comment by Wolfram Schneider [ 13/Apr/17 ] |
|
I forced a rebuild of the job. The job is still failing in "TASK [mod-auth-data : Create mod-auth credentials for other users]" Who is in charge of mod-auth? Kurt? |
| Comment by Wolfram Schneider [ 13/Apr/17 ] |
|
I'm wondering if we are monitoring our FOLIO websites or FOLIO API services with nagios/munin? If not, we should file another issue. |
| Comment by Wayne Schneider [ 13/Apr/17 ] |
|
Looking at the error message, it is pretty clear that this is a permissions naming problem – the user that the Ansible script is using to talk to mod-auth doesn't have the correct permissions to do the task. Permission names are still being worked on, I would expect this to be more or less fixed today. |
| Comment by Mike Taylor [ 13/Apr/17 ] |
|
HAR! |
| Comment by Wolfram Schneider [ 13/Apr/17 ] |
|
I’m still wondering why a failed jenkins jobs can break our demo web site? If the update fails, the old instance should still be runnable. Or is this a different story? |
| Comment by John Malconian [ 13/Apr/17 ] |
|
That's the way its supposed to work, however, with all the manual rebuilds occurring recently, the regular job schedule is off a bit. Ultimately, once the back end modules are a little more stable, we'll have a dedicated demo instance which should be more stable and additional instances that consists of the tip of development. |
| Comment by John Malconian [ 13/Apr/17 ] |
|
folio-uidemo.aws.indexdata.com is back up. See
|