-
Notifications
You must be signed in to change notification settings - Fork 114
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
mellanox vendor plugin cannot register under certain conditions #573
Comments
I think that is not the case because we always run the pollNic before we go here no? |
Corrected: the code is from release 1.2.0: https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/v1.2.0/pkg/daemon/daemon.go#L426 It's triggered by SriovNetworkNodeState changed, and handled with nodeStateSyncHandler function. |
will you be able to use a new version of the operator? :) |
https://github.com/k8snetworkplumbingwg/sriov-network-operator/releases The latest release version is v1.2.0, so shall we use master code to deploy to production environment ? |
you are right we are going to do a new release of the operator soon sorry about that |
We plan to use sriov-network-operator 1.3.0 release version in our production environment, and we'll continue watching this bug. |
Hi @qiaoning please check the latest release we did as we fix also a critical issue in the sriov-cni |
https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/master/pkg/daemon/daemon.go#L541C2-L548
if
latestState.status
isnil
, only k8s_plugin and generic_plugin registed, vendor plugin(such as mellanox_plugin) will never be registered in this case, even if generation ofSriovNetworkNodeState
is changed, because only checkdn.enabledPlugins
's count, plugin name is NOT checked.A solution should be like this code template:
The text was updated successfully, but these errors were encountered: