Sebastian Scheinkman
Sebastian Scheinkman
Hi @hymgg there is a bug you can see the PR https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/679 in general please check your nodeSelector in the sriovNetworkNodePolicy can you do ``` kubectl -n sriov-network-operator get sriovnetworknodepolicy...
The yaml you shared is from a local file I want you to show me the one that is in the k8s api server. please run `kubectl -n sriov-network-operator get...
yep that was my expectation I think the label you wanted is something like: ```yaml nodeSelector: node-role.kubernetes.io/worker: "" ```
Hi as you can see it's an intel nic and in the status of the sriovNetworkNodeState there is no maxVf that points me out that you didn't enable sriov in...
@hymgg can you please check I think there is on the bios something called 4M memory or something like that
@hymgg can you please run ``` lspci -v -nn -mm -k -s 0000:3b:00.0 lspci -vvv 0000:3b:00.0 ``` and also please check again in the bios configuration about ``` Memory Mapped...
Hi @ns-rlewkowicz any specific issue that the community can help with? we have a large number of users using the operator on large clusters
Hi @e0ne can you please rebase the PR?
/hold this doesn't work on OCP it puts the node in boot loop because the mode didn't change.
+1 from my side. do you have some bandwidth to open a PR with the doc changes and we can review it? also, we always welcome people to the community...