drop geth-peer-fix which appears to be unnecesary

Signed-off-by: Jakub Sokołowski <jakub@status.im>
This commit is contained in:
Jakub Sokołowski 2021-03-25 12:29:15 +01:00
parent a6849196f9
commit 88d2afa61c
No known key found for this signature in database
GPG Key ID: 4EF064D0E6D63020
3 changed files with 0 additions and 15 deletions

View File

@ -15,7 +15,6 @@
- { role: infra-role-geth, tags: infra-role-geth }
- { role: infra-role-geth-exporter, tags: infra-role-geth-exporter }
- { role: faucet-api, tags: faucet-api }
- { role: geth-peer-fix, tags: geth-peer-fix }
vars:
faucet_network: ropsten
faucet_http_port: 3000
@ -34,7 +33,6 @@
- { role: infra-role-geth, tags: infra-role-geth }
- { role: infra-role-geth-exporter, tags: infra-role-geth-exporter }
- { role: faucet-api, tags: faucet-api }
- { role: geth-peer-fix, tags: geth-peer-fix }
vars:
faucet_network: rinkeby
faucet_http_port: 3001
@ -51,7 +49,6 @@
- { role: infra-role-geth, tags: infra-role-geth }
- { role: infra-role-geth-exporter, tags: infra-role-geth-exporter }
- { role: faucet-api, tags: faucet-api }
- { role: geth-peer-fix, tags: geth-peer-fix }
vars:
faucet_network: goerli
faucet_http_port: 3002

View File

@ -1,5 +0,0 @@
# Description
This tiny role simply adds a cronjob to restart the geth container on faucet master host daily to avoid the `no suitable peers available` error which keeps messing with the faucet API.
For more details read: https://github.com/status-im/infra-faucet/issues/1

View File

@ -1,7 +0,0 @@
---
# This an UGLY way of "fixing" the `no suitable peers available` error
- name: Add cronjob to restart geth container
cron:
name: 'HACK: Restart {{ geth_cont_name }} to avoid peers errors'
job: 'docker restart {{ geth_cont_name }}'
special_time: 'daily'