Closed justaddcoffee closed 2 years ago
@kltm any idea what's happening here?
@justaddcoffee Check slack. The short of it is: https://github.com/geneontology/operations/issues/51
A relevant ticket, h/t Seth: https://github.com/geneontology/operations/issues/51
Removing the ssh-keyscan
in https://github.com/Knowledge-Graph-Hub/kg-covid-19/commit/d047fd7b8dd5593fc06fe3f315c84a753ac4946f looks like it still leaves pan
as the endpoint, and it's definitely unreachable:
15:28:54 + HOME=/var/lib/jenkins/workspace/dge-graph-hub_kg-covid-19_master/ansible
15:28:54 + ansible-playbook update-kg-hub-endpoint.yaml --inventory=hosts.local-rdf-endpoint --private-key=**** -e target_user=bbop --extra-vars=endpoint=internal
15:28:55 [DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
15:28:55 allow bad characters in group names by default, this will change, but still be
15:28:55 user configurable on deprecation. This feature will be removed in version 2.10.
15:28:55 Deprecation warnings can be disabled by setting deprecation_warnings=False in
15:28:55 ansible.cfg.
15:28:55 [WARNING]: Invalid characters were found in group names but not replaced, use
15:28:55 -vvvv to see details
15:28:55
15:28:55 PLAY [pipeline-rdf] ************************************************************
15:28:55
15:28:55 TASK [Gathering Facts] *********************************************************
15:28:55 [WARNING]: Unhandled error in Python interpreter discovery for host
15:28:55 pan.lbl.gov: Failed to connect to the host via ssh: Host key verification
15:28:55 failed.
15:28:55 fatal: [pan.lbl.gov]: UNREACHABLE! => {"changed": false, "msg": "Data could not be sent to remote host \"pan.lbl.gov\". Make sure this host can be reached over ssh: Host key verification failed.\r\n", "unreachable": true}
15:28:55
15:28:55 PLAY RECAP *********************************************************************
15:28:55 pan.lbl.gov : ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
15:28:55
[Pipeline] }
15:28:56 ERROR: script returned exit code 4
@caufieldjh I'd hazard a guess that you need to update the metadata that the playbook is running--the pan instances are no longer running and haven't for some time (https://github.com/geneontology/operations/issues/51).
Here:
https://github.com/Knowledge-Graph-Hub/kg-covid-19/blob/522ebfcd9be4a3e3855151bbad207de942e74f41/Jenkinsfile#L233
Change hosts.local
to hosts.remote
and change user to ubuntu
I believe this is resolved now - the Feb 28 build appears to have completed without issue.
Thanks @caufieldjh!
Describe the bug
Jenkins build is failing at the Blazegraph deploy stage, see here:
To Reproduce
See here
Expected behavior
Jenkins build should complete
Version
https://github.com/Knowledge-Graph-Hub/kg-covid-19/commit/8779f52d7b2e6aff59a6ccc5df069ef1078e37c0