Hello @bmcnally-uw
I am wondering if thats the same issue as in Cloud-init fails to fetch MAAS datasource from metadata_url missing port
If thats the same in your case, then thats indeed a bug and we are already working on a fix.
You can track the progress at Bug #2022926 “Wrong metadata url in enlist cloud-config” : Bugs : MAAS