Soft-fail on network errors
authorMichael Tremer <michael.tremer@ipfire.org>
Tue, 23 Jun 2015 22:34:33 +0000 (22:34 +0000)
committerStefan Schantl <stefan.schantl@ipfire.org>
Wed, 1 Jul 2015 19:42:23 +0000 (21:42 +0200)
commit29a69850e9e172b5a868e3f2dc0ac63ba08871a8
treec198411ed13b5301a49607964e8851f678949491
parent5d98b00335d8c016c19c884e51c0a48aee2e1692
Soft-fail on network errors

When an update could not be performed because of a network
error (host unreachable/no route to host) we should not
log an error to the database and hold off updates for a
long time.

Those errors are usually caused by local configuration
errors and the servers of the providers should not be
bothered with update requests as those won't reach them
any way.

The client will try to resend the update at the next
update call.

Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Signed-off-by: Stefan Schantl <stefan.schantl@ipfire.org>
src/ddns/providers.py