-
Notifications
You must be signed in to change notification settings - Fork 90
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
[flaky CI] [nns] NNS LastSuccessfulUpdateTime when network configuration hasn't change should not be updated #670
Labels
Comments
/kind bug |
This was referenced Jan 5, 2021
The diff on states
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/nmstate_kubernetes-nmstate/661/pull-kubernetes-nmstate-e2e-handler-k8s/1341025954180370432
/kind bug
/triage build-watcher
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
NodeNetworkState
on affected nodes (usekubectl get nodenetworkstate <node_name> -o yaml
):NodeNetworkConfigurationPolicy
:kubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'
):nmcli --version
)kubectl version
):The text was updated successfully, but these errors were encountered: