Closed yingzhan-msft closed 4 months ago
I found delegateRc.DeviceID was empty so CNIDeviceInfoFile was not generated. The issue was gone upon reverting the changes introduced in this commit https://github.com/k8snetworkplumbingwg/multus-cni/pull/644. I'm looking for guidance on adding DeviceID to delegateRc, or is this possibly a bug? Any assistance with this would be appreciated.
There are no changes to the net-attach-def with the upgrade to 4.0, so that shouldn't have to change.
However, I'm curious if you've discovered anything more about the CNIDeviceInfoFile?
Hi @dougbtv, I haven't identified the root cause yet. As a workaround for this issue, I removed the non-empty condition check for delegateRc.DeviceID introduced in this commit https://github.com/k8snetworkplumbingwg/multus-cni/pull/644/files#diff-668d0a8a613e2738bc66879510daa1c26f605997ce7a393dc1c4da73c9125c34 and built my own Multus image. With this workaround, the CNIDeviceInfoFile was automatically generated and it fixed my issue.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Hello Multus community,
I've been using Multus v3.7 and am now considering an upgrade to the latest release. I used the sample deployment from /multus-cni/deployments/multus-daemonset.yml and kept everything else unchanged. However, I encountered an issue where the CNIDeviceInfoFile was empty in the runtime config when the request was passed down to the delegate CNI. This resulted in the k8s.v1.cni.cncf.io/networks-status not having device-info in the pod annotation.
By reviewing the Multus logs, it appears that the CNIDeviceInfoFile capability was not set, even though I had configured it as true in the network attachment definition. I'm curious if there is a need to make adjustments in the network attachment definition for the current release, as I did not face this issue in v3.7. Any suggestions would be greatly appreciated.
Network Attachment Definition
Multus config
Multus logs