Comment 1 for bug 1721558

The command ran is of this form:

autopkgtest [19:55:28]: host juju-prod-ues-proposed-migration-machine-3; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.iw5t9p35/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --setup-commands /home/ubuntu/autopkgtest/setup-commands/setup-testbed --apt-pocket=proposed --apt-upgrade linux-aws --env=ADT_TEST_TRIGGERS=systemd/229-4ubuntu20 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --name adt-xenial-amd64-linux-aws-20170919-195523 --image 'ubuntu/ubuntu-xenial-.*-amd64-server' --keyname testbed-juju-prod-ues-proposed-migration-machine-3 --net-id=net_ues_proposed_migration -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,ppa.launchpad.net'"'"'' --mirror=http://ftpmaster.internal/ubuntu

I guess the crutial bit is that it is a test of: linux-aws with ADT_TEST_TRIGGERS=systemd/229-4ubuntu20

meaning some of the adt magic w.r.t. kernel setup does not kick in, i think.