Skip to content

temp interface name causes race conditions #321

@anushakad

Description

@anushakad

What happened?

Interface name not getting updated when you have pod with multiple interfaces in the node. Due to which container creation is failing

What did you expect to happen?

Pod should be up with all the interfaces

What are the minimal steps needed to reproduce the bug?

Anything else we need to know?

This issue is similar to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1599
Error seen in multus.log:
[nathan/18-eric-adc-sel-lb-access-fe-deployment-57f686dfbb-tqnts/18244680-1387-4cbb-b1db-cf4faf2c97ad:mellanox_sriov_dpdk1_right]: error adding container to network "mellanox_sriov_dpdk1_right": failed to set up pod interface "rightsriov" from the device "enp75s0f1": error setting up interface in container namespace: "error setting container interface name enp75s13f4 for temp_254"

multus.txt

Attached multus logs for reference

Component Versions

Please fill in the below table with the version numbers of applicable components used.

Component Version
SR-IOV CNI Plugin v2.8.1
Multus v4.1.0
SR-IOV Network Device Plugin v3.7.0

Config Files

Config file locations may be config dependent.

CNI config (Try '/etc/cni/net.d/')
Device pool config file location (Try '/etc/pcidp/config.json')
Multus config (Try '/etc/cni/multus/net.d')
Kubernetes deployment type ( Bare Metal, Kubeadm etc.)
Multus logs (If enabled. Try '/var/log/multus.log' )
Kubelet logs (journalctl -u kubelet)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions