Wrong metadata url in enlist cloud-config

Hello,

this is single host, rack+region scenario. Version 3.3.3. Metadata url is presented without a specific port and it's unreachable on default 80.

Steps to reproduce:

When visiting url passed on to kernel/initrd by bootloader:

http://192.168.0.234:5248/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed

I receive following cloud-config script

#cloud-config
apt:
  preserve_sources_list: false
  primary:
  - arches:
    - amd64
    - i386
    uri: http://archive.ubuntu.com/ubuntu
  - arches:
    - default
    uri: http://ports.ubuntu.com/ubuntu-ports
  proxy: http://192.168.0.234:8000/
  security:
  - arches:
    - amd64
    - i386
    uri: http://archive.ubuntu.com/ubuntu
  - arches:
    - default
    uri: http://ports.ubuntu.com/ubuntu-ports
  sources_list: 'deb $PRIMARY $RELEASE universe restricted main multiverse

    # deb-src $PRIMARY $RELEASE universe restricted main multiverse

    deb $PRIMARY $RELEASE-updates universe restricted main multiverse

    # deb-src $PRIMARY $RELEASE-updates universe restricted main multiverse

    deb $PRIMARY $RELEASE-backports universe restricted main multiverse

    # deb-src $PRIMARY $RELEASE-backports universe restricted main multiverse

    deb $SECURITY $RELEASE-security universe restricted main multiverse

    # deb-src $SECURITY $RELEASE-security universe restricted main multiverse

    '
datasource:
  MAAS:
    metadata_url: http://192.168.0.234/MAAS/metadata/
manage_etc_hosts: true
packages:
- python3-yaml
- python3-oauthlib
power_state:
  condition: test ! -e /tmp/block-poweroff
  delay: now
  mode: poweroff
  timeout: 1800
rsyslog:
  remotes:
    maas: 192.168.0.234:5247

Please note metadat_url not having a port specified. The enlistment process hangs during ephemeral image startup after

[ OK ] Reached target Host and Netowrka Name Lookups

and then typically times out but with no datasource configured and resulting in failed enlistment.

You can work it around by replacing default /etc/maas/preseed/enlist template:

{{preseed_data}}

with

#cloud-config
apt:
  preserve_sources_list: false
  primary:
  - arches:
    - amd64
    - i386
    uri: http://archive.ubuntu.com/ubuntu
  - arches:
    - default
    uri: http://ports.ubuntu.com/ubuntu-ports
  security:
  - arches:
    - amd64
    - i386
    uri: http://archive.ubuntu.com/ubuntu
  - arches:
    - default
    uri: http://ports.ubuntu.com/ubuntu-ports
  sources_list: 'deb $PRIMARY $RELEASE main restricted multiverse universe

    # deb-src $PRIMARY $RELEASE main restricted multiverse universe

    deb $PRIMARY $RELEASE-updates main restricted multiverse universe

    # deb-src $PRIMARY $RELEASE-updates main restricted multiverse universe

    deb $PRIMARY $RELEASE-backports main restricted multiverse universe

    # deb-src $PRIMARY $RELEASE-backports main restricted multiverse universe

    deb $SECURITY $RELEASE-security main restricted multiverse universe

    # deb-src $SECURITY $RELEASE-security main restricted multiverse universe

    '
datasource:
  MAAS:
    metadata_url: http://10.141.200.9:5248/MAAS/metadata/
manage_etc_hosts: true
packages:
- python3-yaml
- python3-oauthlib
power_state:
  condition: test ! -e /tmp/block-poweroff
  delay: now
  mode: poweroff
  timeout: 1800
rsyslog:
  remotes:
    maas: 10.141.200.9:5247

Commisioning and deployment are not affected.
With regards
Michal K.