We just encountered this same bug in a multi-controller deployment (3 controllers) and the fix proposed by Vladimir seems to work. Is there a reason it was abandoned?
We just encountered this same bug in a multi-controller deployment (3 controllers) and the fix proposed by Vladimir seems to work. Is there a reason it was abandoned?