Skip to content
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

Closed
qinqon opened this issue Dec 22, 2020 · 4 comments · Fixed by #711

Comments

@qinqon
Copy link
Member

qinqon commented Dec 22, 2020

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


[nns] NNS LastSuccessfulUpdateTime when network configuration hasn't change should not be updated expand_less | 15s
-- | --
/tmp/knmstate/kubernetes-nmstate/test/e2e/handler/nns_update_timestamp_test.go:29 Failed after 0.006s. Expected     <string>: NodeNetworkStateStatus to match fields: { .CurrentState: 	Expected 	    <string>: "...on: fd10:24..." 	to equal               \| 	    <string>: "...on: fe80::/..." .LastSuccessfulUpdateTime: 	Expected 	    <v1.Time>: { 	        Time: 2020-12-21T14:32:38Z, 	    } 	to equal 	    <v1.Time>: { 	        Time: 2020-12-21T14:32:33Z, 	    } }


/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 (use kubectl get nodenetworkstate <node_name> -o yaml):
  • Problematic NodeNetworkConfigurationPolicy:
  • kubernetes-nmstate image (use kubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'):
  • NetworkManager version (use nmcli --version)
  • Kubernetes version (use kubectl version):
  • OS (e.g. from /etc/os-release):
  • Others:
@qinqon
Copy link
Member Author

qinqon commented Dec 22, 2020

/kind bug
/triage build-watcher

@qinqon
Copy link
Member Author

qinqon commented Feb 8, 2021

The diff on states
#688

-  - destination: fd10:244::bac0/122
-    metric: 1024
-    next-hop-address: fd00::103
-    next-hop-interface: eth0
-    table-id: 254
   - destination: fe80::/64
     metric: 100
     next-hop-address: ""
     next-hop-interface: eth0
     table-id: 254
   - destination: ff00::/8
     metric: 256
     next-hop-address: ""
     next-hop-interface: eth0
     table-id: 255

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants