Comment 9 for bug 1826644

Hi,

Sorry for so late answer but I was busy recently.
Can You also check for router 6e84cf52-ef66-455c-b89c-d9725057e131 on ctrl1, ctrl2 and ctrl3 if there is VIP address configured in router's namespace on one of hosts?
Also, please check (and paste here) config files from keepalived processes for this router from each of controller nodes and check journal logs if there are maybe any errors/warnings coming from keepalived or neutron-keepalived-state-change related to this router.

Can You also tell me if restart of L3 agents or restart of keepalived processes and L3 agents after that fixes this issue?