Comment 12 for bug 1851276

I can reproduce it 100% of the time, but I don't know from where you want me to run the `curl`s. Here's the output from the controller:

```
$ curl http://192.168.2.1:5240/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed
#cloud-config
apt:
  preserve_sources_list: false
  primary:
  - arches: [amd64, i386]
    uri: http://apt.cnct.io:8080/ubuntu/
  - arches: [default]
    uri: http://apt.cnct.io:8080/ubuntu-ports/
  proxy: http://192-168-2-0--24.maas-internal:8000/
  security:
  - arches: [amd64, i386]
    uri: http://apt.cnct.io:8080/ubuntu/
  - arches: [default]
    uri: http://apt.cnct.io:8080/ubuntu-ports/
  sources_list: 'deb $PRIMARY $RELEASE main

    # deb-src $PRIMARY $RELEASE main

    '
datasource:
  MAAS: {metadata_url: 'http://192.168.2.1:5240/MAAS/metadata/enlist'}
manage_etc_hosts: true
packages: [python3-yaml, python3-oauthlib, freeipmi-tools, ipmitool, sshpass, archdetect-deb,
  jq]
power_state: {condition: test ! -e /tmp/block-poweroff, delay: now, mode: poweroff,
  timeout: 1800}
rsyslog:
  remotes: {maas: '192.168.2.1:5247'}
```

The packages specified are the packages that fail to install, which I surmise is happening because cloud-init scripts are not running `apt update` before attempting to install.