Comment 13 for bug 1759971

Yes, neither address scope information, nor fixed IP address assignment because the port is still unbound during the first call to list_active_sync_routers_on_active_l3_agent (_build_routers_list is called after some nested calls).

Fixed address allocation is used to include address scope information to the gateway port dict.

So, after we ensure that the gateway port is bound via _ensure_host_set_on_ports (which relies on neutron ML2 core plugin code base) we need to rebuild the list of routers again because router info dicts include external gateway port information and it needs to be refreshed with post-binding data persisted to the neutron DB by ML2.