Project

General

Profile

Actions

Support #11500

closed

Error updating GRSF service with ansible

Added by Luca Frosini about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
High
Assignee:
_InfraScience Systems Engineer
Category:
Application
Start date:
Mar 21, 2018
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Development

Description

I'm trying to update GRSF in dev with the following command:

./run.sh smartgears-node-upgrade.yml -i inventory/hosts.dev -l smart_grsf_dev

and I obtain the followign ansible error:

TASK [disable nagios alerts for this host services] **************************************************
failed: [smart-grsf-d-d4s.d4science.org] (item=monitoring.research-infrastructures.eu) => {"item": "monitoring.research-infrastructures.eu", "msg": "SSH Error: data could not be sent to remote host \"monitoring.research-infrastructures.eu\". Make sure this host can be reached over ssh", "unreachable": true}
fatal: [smart-grsf-d-d4s.d4science.org]: UNREACHABLE! => {"changed": false, "msg": "All items completed", "results": [{"_ansible_ignore_errors": null, "_ansible_item_result": true, "item": "monitoring.research-infrastructures.eu", "msg": "SSH Error: data could not be sent to remote host \"monitoring.research-infrastructures.eu\". Make sure this host can be reached over ssh", "unreachable": true}]}
    to retry, use: --limit @/home/lucafrosini/workspace/ANSIBLE/ansible-playbooks/d4science-ghn-cluster/smartgears-node-upgrade.retryPLAY RECAP *******************************************************************************************
smart-grsf-d-d4s.d4science.org : ok=1    changed=0    unreachable=1    failed=0

Related issues

Blocks StocksAndFisheriesKB - Task #11464: Update stock endpoint for GRSF-Publication-ServiceClosedYannis MarketakisMar 16, 2018

Actions
Actions #1

Updated by Luca Frosini about 7 years ago

  • Blocks Task #11464: Update stock endpoint for GRSF-Publication-Service added
Actions #2

Updated by Andrea Dell'Amico about 7 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Use the smartgears-node.yml playbook, the other one needs a user with root access to the nagios server.

Other than the nagios management, the two playbooks should behave in the same way: all the *_upgrade_* variables have been obsoleted by the use of maven_artifact. If an involved smartgears role does not use maven_artifact, it's buggy and have to be fixed.

Actions #3

Updated by Luca Frosini about 7 years ago

  • Status changed from Feedback to Closed

It works. Thanks you.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)