You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multi-NIC IPAM CNI allocates the address that is already in use to Pod.
Expected Behavior
The IP address should be successfully add to the interface.
Current Behavior
error adding pod <pod name> to CNI network "multus-cni-network":
plugin type="multus" name="multus-cni-network"
failed (add): [default/..:multinic-ipvlanl3]: error adding container to network "multinic-ipvlanl3":
failed to add IP addr <IP> to "net1-0": address already in use
Check IP in-use before allocation --> Is there any way we can check without try assigning to network device?
Detect anomaly request by daemon (request from same pod for multiple times)
Report failure by CNI
Considering current practicality, I will work on the second choice.
However, if we can find a way to do the first choice, it will be more straightforward.
The text was updated successfully, but these errors were encountered:
Multi-NIC IPAM CNI allocates the address that is already in use to Pod.
Expected Behavior
The IP address should be successfully add to the interface.
Current Behavior
Troubleshooting Steps
Steps to Reproduce
(not trivial)
Context (Environment)
res-cpe-team-docker-local.artifactory.swg-devops.com/multi-nic-cni-operator/controller:v1.0.2-alpha
res-cpe-team-docker-local.artifactory.swg-devops.com/net/multi-nic-cni-daemon:v1.0.1-alpha
Possible Implementation
Considering current practicality, I will work on the second choice.
However, if we can find a way to do the first choice, it will be more straightforward.
The text was updated successfully, but these errors were encountered: