Skip to content

contest: remote: retry on connect errors - #122

Merged
matttbe merged 2 commits into
linux-netdev:mainfrom
matttbe:fetcher-retry
Oct 23, 2026
Merged

matttbe merged 2 commits into
linux-netdev:mainfrom
matttbe:fetcher-retry

Conversation

@matttbe

@matttbe matttbe commented Oct 23, 2026

Copy link
Copy Markdown
Member

Recently, after a reboot, most vmksft services failed to start because they failed to resolve the hostname.

Allow them to retry with an exponential backoff, similar to what is done with Patchwork.

Also switch to 'urllib3' instead of 'requests' if it is to use Retry from there.

Recently, after a reboot, most vmksft services failed to start because
they failed to resolve the hostname.

Allow them to retry with an exponential backoff, similar to what is done
with Patchwork.

While at it, switch to 'urllib3' instead of 'requests', and use a
'PoolManager', as recommended on urllib3 doc, to handle both the timeout
and the retries settings. We just need to change the response to get
'data' instead of 'content'. Also catch HTTP errors and issues to decode
the JSON files.

Signed-off-by: Matthieu Baerts <matttbe@kernel.org>
Similar to the parent commit, retry with an exponential backoff in case
of connection issues.

Also switch to 'urllib3' instead of 'requests' if it is to use Retry
from there, and catch errors instead of crashing: that's OK if we don't
have the filters there.

Signed-off-by: Matthieu Baerts <matttbe@kernel.org>
@matttbe

matttbe commented Oct 23, 2026

Copy link
Copy Markdown
Member Author

No need to review I suppose: a small fix that can be deployed.

@matttbe
matttbe merged commit e298906 into linux-netdev:main Oct 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant