While debugging some issues with systemd-upstream tests I noticed that we had 2 instances created for a test run but only one of them was actually being used.
ubuntu@juju-4d1272-prod-proposed-migration-4:~/autopkgtest-cloud$ ps aux | grep 'runner.*e8ad25b2'
ubuntu 2850558 0.0 0.1 30808 20352 ? S 17:10 0:00 /usr/bin/python3 -u /home/ubuntu/autopkgtest/runner/autopkgtest --output
-dir /tmp/autopkgtest-work.cdg2zji9/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 --setup-commands apt-key adv --keyserver keyserver.ubun
tu.com --recv-key 602DA2D8F03FED90D4ED3090E4A8EEB6317A360E --setup-commands REL=$(sed -rn "/^(deb|deb-src) .*(ubuntu.com|ftpmaster)/ { s/^[
^ ]+ +(\[.*\] *)?[^ ]* +([^ -]+) +.*$/\2/p; q }" /etc/apt/sources.list); echo "deb http://ppa.launchpad.net/upstream-systemd-ci/systemd-ci/
ubuntu $REL main" > /etc/apt/sources.list.d/autopkgtest-upstream-systemd-ci-systemd-ci.list; echo "deb-src http://ppa.launchpad.net/upstrea
m-systemd-ci/systemd-ci/ubuntu $REL main" >> /etc/apt/sources.list.d/autopkgtest-upstream-systemd-ci-systemd-ci.list; --apt-upgrade https:/
/salsa.debian.org/systemd-team/systemd.git#upstream-ci --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=CFLAGS=-O0 --en
v=DEB_BUILD_PROFILES=noudeb --env=TEST_UPSTREAM=1 --env=CONFFLAGS_UPSTREAM=--werror -Dslow-tests=true --env=UPSTREAM_PULL_REQUEST=26332 --e
nv=GITHUB_STATUSES_URL=https://api.github.com/repos/systemd/systemd/statuses/e8ad25b2cea308e1276d42230f6651614d99431b -- ssh -s /home/ubunt
u/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups <email address hidden>
group --name adt-jammy-s390x-systemd-upstream-20230207-160443-juju-4d1272-prod-proposed-migration-4 --image adt/ubuntu-jammy-s390x-server -
-keyname testbed-juju-4d1272-prod-proposed-migration-4 --net-id=net_prod-proposed-migration -e TERM=linux -e 'http_proxy=http://squid.inter
nal:3128' -e 'https_proxy=http://squid.internal:3128' -e 'no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubu
ntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,launchpad.net,10.24.0.0/24' --mirror=http://ftpmaster.i
nternal/ubuntu/
ubuntu@juju-4d1272-prod-proposed-migration-4:~/autopkgtest-cloud$ nova show adt-jammy-s390x-systemd-upstream-20230207-160443-juju-4d1272-prod-proposed-migration-4
ERROR (CommandError): Multiple server matches found for 'adt-jammy-s390x-systemd-upstream-20230207-160443-juju-4d1272-prod-proposed-migration-4', use an ID to be more specific.
ubuntu@juju-4d1272-prod-proposed-migration-4:~/autopkgtest-cloud$ nova list | grep adt-jammy-s390x-systemd-upstream-20230207-160443-juju-4d1272-prod-proposed-migration-4
| 1275fc41-eaac-4fd7-8dce-905803ea5455 | adt-jammy-s390x-systemd-upstream-20230207-160443-juju-4d1272-prod-proposed-migration-4 | ACTIVE | - | Running | net_prod-proposed-migration=10.44.124.192 |
| 41d1fefc-af14-4e98-bbe8-85fe1f1c51b4 | adt-jammy-s390x-systemd-upstream-20230207-160443-juju-4d1272-prod-proposed-migration-4 | ACTIVE | - | Running | net_prod-proposed-migration=10.44.124.142 |
I ssh'ed to the unit's IP addresses and discovered that only one, the "second", instance was actually running tests. While the first instance will get cleaned up eventually by cleanup-test-instances this still seems wasteful.
