I've tried to reproduce this. The "Error: Only running operations can be connected" wasn't an issue for me. Instead it failed like this:
ERROR: "dpkg --print-architecture" failed with stderr "Error: read tcp 10.136.6.103:40086->10.44.124.67:8443: i/o timeout -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2045578 Title: Error: only running operations can be connected Status in Auto Package Testing: New Bug description: This was seen on an armhf test runner with tcl-fitstcl and a trigger of glibc/2.31-0ubuntu9.13. 100s autopkgtest [17:48:52]: rebooting testbed after setup commands that affected boot 140s autopkgtest [17:49:32]: testbed running kernel: Linux 5.4.0-167-generic #184-Ubuntu SMP Tue Oct 31 09:24:51 UTC 2023 157s autopkgtest [17:49:49]: ERROR: "dpkg --print-architecture" failed with stderr "Error: Only running operations can be connected 157s " I've actually seen this in multiple logs so it bears further investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2045578/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
