Race Condition: setIntfIp Fails Due to PortChannel Initialization Delay #21998
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Description:
An error occurs when setIntfIp attempts to assign an IP address to a PortChannel before its initialization is complete. This indicates a race condition between swss (which assigns the IP) and teamd (which creates the PortChannel).
Observed Behavior:
In the logs, we see that setIntfIp fails when trying to assign an IP to PortChannel108:
Subsequent log entries confirm that PortChannel108 had not been fully initialized when setIntfIp was executed:
These logs indicate that PortChannel108 was still in the process of being created when setIntfIp was executed.
Later, we see that PortChannel108 becomes fully initialized only after setIntfIp had already failed:
Root Cause:
There is a timing issue where setIntfIp executes before teamd has fully initialized the PortChannel.
Reproduction Frequency:
This issue reproduces very rarely. It was observed only once in our setup (SN2700) and occurred on a system with a weak CPU, suggesting that timing variations due to system performance may contribute to the issue.
Expected Behavior:
setIntfIp should only attempt to assign an IP address after the PortChannel has been fully initialized by teamd.
The text was updated successfully, but these errors were encountered: