-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add custom metalk8s_network.routes execution module #3352
Conversation
Hello alexandre-allard-scality,My role is to assist you with the merge of this Status report is not available. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
335e63b
to
985f87b
Compare
History mismatchMerge commit #ec287557a01076cc2790dd2ae5bb8b67af39828e on the integration branch It is likely due to a rebase of the branch Please use the |
This module is a simplified version of Salt network.routes, only handling IPv4 routes for Linux dists using `ip` utility. The goal of the module is to workaround a bug in the original one when there is a blackhole route defined (see: saltstack/salt#60126) Once this bug is fixed upstream, we can remove it. Refs: #3349
We use a custom module because the upstream one is bugged. Refs: #3349
985f87b
to
06afdf9
Compare
/reset |
Reset completeI have successfully deleted this pull request's integration branches. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
/approve |
Also fix metalk8s_checks.routes_exists test since it was mocking network.routes module. Refs: #3349
aefb577
06afdf9
to
aefb577
Compare
History mismatchMerge commit #06afdf92deaea6a57f45412458e7992cb84c1602 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: approve |
@gdemonet @TeddyAndrieux Forgot to update the tests according to the changes requested... you can re-approve now :) |
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: approve |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
The following options are set: approve |
result: [] | ||
# 5. Unsupported type or format | ||
- ip_route_output: |- | ||
banana route via foo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤣
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been greatly inspired by your tests. :)
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye alexandre-allard-scality. |
Component: salt, tests
Context:
We rely on the Salt
network.routes
execution module to retrieve the routes during pre-check to ensure a route exists for a specific destination (or at least a default route).The issue is that this module is bugged and fails when there is a blackhole route defined, which is our case, since Calico defines one.
Summary:
We implement a basic version of the
network.routes
module, fixing the blackhole issue and only keeping what we really need.Acceptance criteria:
Unit tests are OK and
salt-call metalk8s_network.routes
returns the list of routes without crashing when a blackhole route is defined and there is nonet-tools
package installedCloses: #3349