Any updates to this defect?
I see similar symptoms in my deployment which is kilo based?
The bridge fdb entries have several entries for the same host (00:00:00:00:00:00 MAC address)
and bridge process occupies close to 90% of the system resources when linuxbridge agent tries to dump the fdb table.
Any updates to this defect?
I see similar symptoms in my deployment which is kilo based?
The bridge fdb entries have several entries for the same host (00:00:00:00:00:00 MAC address)
and bridge process occupies close to 90% of the system resources when linuxbridge agent tries to dump the fdb table.