barbican autopkgtests fail with python3.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
barbican (Ubuntu) |
Fix Released
|
Undecided
|
Lukas Märdian |
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://
[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/
The worker log, in turn, shows only:
2022-01-31 21:34:36.092 11378 ERROR oslo.messaging.
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.
Related branches
- Chris MacNaughton (community): Approve
-
Diff: 35 lines (+9/-0)2 files modifieddebian/barbican-api.conf (+2/-0)
debian/changelog (+7/-0)
tags: | added: fr-2040 |
Changed in barbican (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Lukas Märdian (slyon) |
Changed in barbican (Ubuntu): | |
status: | In Progress → Fix Committed |
except the autopkgtest log clearly shows only python3-defaults being pulled from -proposed, so it looks like more analysis is needed.