[Bug 1959626] Re: barbican autopkgtests fail with python3.10

[Lukas Märdian]

** Changed in: barbican (Ubuntu)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to barbican in Ubuntu.
https://bugs.launchpad.net/bugs/1959626

Title:
  barbican autopkgtests fail with python3.10

Status in barbican package in Ubuntu:
  Fix Committed

Bug description:
  python3-defaults in jammy-proposed switches python3 to be python3.10.
  This causes barbican's autopkgtests to fail fairly inscrutably:

  autopkgtest [09:11:30]: test barbican-daemons: [-----------------------
  OK
  OK
  autopkgtest [09:16:31]: test barbican-daemons: -----------------------]
  barbican-daemons     FAIL non-zero exit status 22

  The 'OK' messages are confirmations that the daemons are started; the
  actual failing command is the call to curl --fail
  http://localhost:9311, which connects to apache and then expects a
  response from barbican-worker via wsgi.  The apache log shows output
  such as:

  [Mon Jan 31 21:45:54.931993 2022] [wsgi:error] [pid 15857:tid
  139695589144128] [client 127.0.0.1:59380] Timeout when reading
  response headers from daemon process 'barbican-api':
  /usr/share/barbican/app.wsgi

  The worker log, in turn, shows only:

  2022-01-31 21:34:36.092 11378 ERROR
  oslo.messaging._drivers.impl_rabbit [-] Connection failed: [Errno 111]
  ECONNREFUSED (retrying in 2.0 seconds): ConnectionRefusedError: [Errno
  111] ECONNREFUSED

  It's true that the connection is refused, because the autopkgtest
  doesn't install rabbitmq-server?  But this doesn't seem to be a
  problem when running under python3.9?

  If I upgrade to -proposed and then downgrade only python3-defaults,
  the failure is still reproducible, so this may be caused by by some
  other package in -proposed besides python3-defaults.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/barbican/+bug/1959626/+subscriptions