extra ipv6 controller incorrectly configured

While testing fix for OVSDB-466 in a proper deployment, it was noticed that an extra controller is being configured.

Manager "tcp:[fd00:fd00:fd00:2000::20]:6640"
is_connected: true
Manager "tcp:[fd00:fd00:fd00:2000::28]:6640"
is_connected: true
Manager "tcp:[fd00:fd00:fd00:2000::1e]:6640"
is_connected: true
Manager "ptcp:6639:[::1]"
Bridge br-int
Controller "tcp:[fd00:fd00:fd00:2000::1e]:6653"
is_connected: true
Controller "tcp:[fd00:fd00:fd00:2000::20]:6653"
is_connected: true
Controller "tcp:fd00:fd00:fd00:2000:0:0:0:20:6653"
Controller "tcp:[fd00:fd00:fd00:2000::28]:6653"
is_connected: true
fail_mode: secure

There is a correct entry for this IP already present and everything works fine. But this wrong entry fills up OVS logs with repeated connection attempts and failures which makes troubleshooting difficult.