-
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
NNCP apply takes *very long* time to apply; nmstatectl does not #1242
Comments
kubernetes-nmstate do some probes before commit the changes to ensure that it do not break the cluster, that's where the time goes on. |
@qinqon did you look at the full logs? It's NOT due to the probes. The probes come back extremely quick. Something else is wrong. Edit journalctl -S today -u NetworkManager.service -f (output on the node I see the problem on)
When I look at NNCP for that node, they are constantly going from "Available SuccessfullyConfigured" to blank status then back to "Available SuccessfullyConfigured". When that happens I see the above journalctl output for that particular interface. I really need to figure out why k8s nmstate is behaving this way. This node's nmstate-handler pod restarted this week. The other node's pods have been up for 200+ days. I'm afraid to bound the other node's pods because of this odd behavior. |
@k8scoder192 is this still happening to you ? |
What happened:
Apply of a nncp takes over 60 seconds. If I exec into the node's nmstate-handler pod and use nmstatectl to create an interface (vlan or bridge) it takes seconds.
What you expected to happen:
Apply of nncp to apply quickly
How to reproduce it (as minimally and precisely as possible):
Apply a yaml such as this
Anything else we need to know?:
nmstate version --> kubernetes-nmstate-handler:v0.80.0
Environment:
NodeNetworkState
on affected nodes (usekubectl get nodenetworkstate <node_name> -o yaml
):NodeNetworkConfigurationPolicy
:Any but see above yaml, here is the actual output from the nncp
kubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'
):nmcli --version
)kubectl version
):Kernel
nmstate pod log:
kubectl logs nmstate-handler-9zkz6 -n nmstate
I killed the pod and a new one properly started up. Tried the apply for another vlan interface and it still took > 60s to apply
I attached the full logs of nmstate-handler-9zkz6
logs--svc-uc-v108-apply.txt
The text was updated successfully, but these errors were encountered: