Comment 3 for bug 1743005

Can you be more specific about what you mean by "no longer allows explicit configuration of the metadata_url used for cloud-init"? Where were you configuring this before?

The branch you referenced fixed a bug that caused incorrect source address selection, but it does not prevent a MAAS admin for defining the `maas_url` in the rackd.conf file; rather, it intentionally preserves that behavior.

That is, you should be able to edit `/etc/maas/rackd.conf` and define `maas_url: <your-desired-url>`, and the region will use that URL when hosts boot from that rack controller. (If you have done that and it still doesn't work, then this bug is valid and should be fixed, but it's not clear to me from the bug description.)

In `src/maasserver/server_address.py` you can see that `get_maas_facing_server_host(...)` checks if `rack_controller.url` is defined and uses that as a first-priority rather than the new `default_region_ip` determined by source address selection.