kubernetes-nmstate
kubernetes-nmstate copied to clipboard
nmstate
Use nmstatectl rust
Is this a BUG FIX or a FEATURE ?:
Uncomment only one, leave it on its own line:
/kind bug /kind enhancement
What this PR does / why we need it: This PR use the rust version of nmstatectl to check for issues there, tt also remove error stripping since it's not needed at rust version.
the normal handler lane is pointing to stream9 nmstate while futur is pointing to stream9 copr nmstate-git
Depends on:
- BZs:
- ~~https://bugzilla.redhat.com/show_bug.cgi?id=2079420~~
- ~~https://bugzilla.redhat.com/show_bug.cgi?id=2081277~~
- ~~https://bugzilla.redhat.com/show_bug.cgi?id=2081286~~
- ~~https://bugzilla.redhat.com/show_bug.cgi?id=2081356~~
- https://bugzilla.redhat.com/show_bug.cgi?id=2089791
- PRs:
- https://github.com/nmstate/nmstate/pull/1881
- https://github.com/nmstate/kubernetes-nmstate/pull/969
- https://github.com/nmstate/nmstate/pull/1792
- https://github.com/nmstate/nmstate/pull/1789
- https://github.com/nmstate/nmstate/pull/1794
- https://github.com/nmstate/nmstate/pull/1821
- https://github.com/nmstate/nmstate/pull/1830
- https://github.com/nmstate/nmstate/pull/1839
- https://github.com/nmstate/nmstate/pull/1868
- https://github.com/nmstate/nmstate/pull/1883
Release note:
Remove error stripping.
Looks like copr is broken and https://github.com/nmstate/nmstate/pull/1868 is not reaching nmstate-git
Looks like copr nmstate-git is not able to put eth1 down at setup/teardown
message: |-
error reconciling NodeNetworkConfigurationPolicy at desired state apply: ,
failed to execute nmstatectl set --no-commit --timeout 480: 'exit status 65' '' 'Using 'set' is deprecated, use 'apply' instead.
NmstateError: VerificationError: Verification failure: eth1.interface.state desire '"down"', current '"up"'
'
After removing the bond of eth0 and eth1 (eth1 is up there) and checked that bond0 is going we have to add a 15 seconds sleep so we canreset the eth1 to down (looks like it's still trapped by the bond?).
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from qinqon by writing /assign @qinqon in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@qinqon: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-kubernetes-nmstate-e2e-handler-k8s-future | 8180d7cfa9094cb707cab0d6590821508554f4cc | link | false | /test pull-kubernetes-nmstate-e2e-handler-k8s-future |
| pull-kubernetes-nmstate-e2e-handler-k8s | 8180d7cfa9094cb707cab0d6590821508554f4cc | link | true | /test pull-kubernetes-nmstate-e2e-handler-k8s |
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/test pull-kubernetes-nmstate-e2e-handler-k8s
NNCP with maxUnavailable when applying a policy to matching nodes
should be progressing on multiple nodes
/tmp/knmstate/kubernetes-nmstate/test/e2e/handler/nncp_parallel_test.go:60
[38;5;11mGinkgo received an interrupt signal but is currently running a ReportAfterEach
node. To avoid an invalid report the ReportAfterEach node will not be
interrupted however subsequent tests will be skipped.[0m
Let's check if the ovs test failures are deterministic /retest pull-kubernetes-nmstate-e2e-handler-k8s
@qinqon: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:
-
/test pull-kubernetes-nmstate-docs -
/test pull-kubernetes-nmstate-e2e-handler-k8s -
/test pull-kubernetes-nmstate-e2e-operator-k8s -
/test pull-kubernetes-nmstate-unit-test
The following commands are available to trigger optional jobs:
-
/test pull-kubernetes-nmstate-e2e-handler-k8s-future -
/test pull-kubernetes-nmstate-e2e-upgrade-k8s
Use /test all to run all jobs.
In response to this:
Let's check if the ovs test failures are deterministic /retest pull-kubernetes-nmstate-e2e-handler-k8s
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Looks like we are breaking default gw when we use a ovs-bridge + ovs-interface to replace the primary interface
{"level":"info","ts":"2023-01-18T14:26:03.948Z","logger":"probe","msg":"default gw missing","path":"routes.running.#(destination==\"0.0.0.0/0\").next-hop-address"}
{"level":"error","ts":"2023-01-18T14:26:03.948Z","logger":"probe","msg":"failed to retrieve default gw","error":"default gw missing","errorVerbose":"default gw missing