canonical-ubuntu-qa team mailing list archive

[Brian Murray <2045578@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: auto-package-testing
     Importance: Critical
         Status: New

** Changed in: auto-package-testing
   Importance: Undecided => Critical

-- 
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