Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Long story short, we ran into a bug in an outdated Python dependency (pyroute2 0.5.9) installed through apt. (see below for precise exception)
Let's decouple the wgkex worker installation a bit, by installing it in a venv, and install the dependencies as specified in the
requirements.txt
, because those versions are the ones the wgkex CI tests against.This will probably be especially important when we merge and deploy the wgkex loadbalancing PR.
We might want to consider splitting the
requirements.txt
for wgkex between broker and worker, so you don't have to install unneeded packages from the respective other; but this needs to be done over there.Another suggestion was to build a static binary using Bazel and deploy that one, which we can also look into (but I'm currently fighting myself with Bazel to get it to run on newer systems with newer Python and Pip versions...), but for now I'm going with this.
(Fixed in svinota/pyroute2#882 and/or svinota/pyroute2@877435b)