Bug#1034361: haveged: autopkgtest fails on bookworm kernel: service fails to start

[Danny van Heumen]

Hi,

I looked into haveged a while back because I ran into some issue. (Don't 
remember exactly what.)

Apparently, the upstream systemd-service contains a conditional to only start 
on old kernels. The strategies that haveged performed are apparently 
incorporated into the kernel. That makes haveged an optional "extra" 
contribution to entropy, but no longer necessary.

A issue on either haveged's github or Qubes-OS's discussed pros/cons for use in 
VMs and IIRC the benefits are doubtful due to depending on healthy input 
entropy and characteristics of VMs (as opposed to actual machines).

Running haveged as userspace tool only has uses because applications/scripts 
can use it as an API to randomness. However, the issue for running haveged 
userspace while the systemd-service is running, was broken for a while. (Not 
sure what the status is now.)

You would need to investigate in detail, as I am not knowledgeable on this 
subject, but from my understanding one would run haveged service on newer 
kernels solely for an overabundance of caution, rather than a necessity to seed 
the entropy pool.

There is an explanation with references on the haveged homepage. The issue 
should be that *if* the service is running, *then* userspace cannot start.

 Original Message 
On Apr 14, 2023, 9:47 PM, Cyril Brulebois < k...@debian.org> wrote:
Paul Gevers (2023-04-13): > The release team has announced [1] that failing 
autopkgtest on amd64 and > arm64 are considered RC in testing. [Release Team 
member hat on] Because > we're currently in the hard freeze for bookworm, I 
have marked this bug as > bookworm-ignore, however, I have a strong suspicion 
that it points out that > the package is broken. Targeted fixes are still 
welcome. The daemon starts just fine in d-i. The daemon starts just fine from 
the service unit on baremetal. I'd like extreme caution to be used before 
considering removing this package. After the 5.4 announce, trying to drop it 
from the installer didn't go quite well[1]. Maybe that's indeed better after 
5.6, but I really don't want to investigate dropping it from the installer for 
Bookworm. 1. https://lists.debian.org/debian-boot/2020/03/msg00182.html and 
replies. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- 
Release team member -- Freelance Consultant

Bug#1034361: haveged: autopkgtest fails on bookworm kernel: service fails to start

[Cyril Brulebois]

Paul Gevers  (2023-04-13):
> The release team has announced [1] that failing autopkgtest on amd64 and
> arm64 are considered RC in testing. [Release Team member hat on] Because
> we're currently in the hard freeze for bookworm, I have marked this bug as
> bookworm-ignore, however, I have a strong suspicion that it points out that
> the package is broken. Targeted fixes are still welcome.

The daemon starts just fine in d-i.

The daemon starts just fine from the service unit on baremetal.

I'd like extreme caution to be used before considering removing this
package. After the 5.4 announce, trying to drop it from the installer
didn't go quite well[1]. Maybe that's indeed better after 5.6, but I
really don't want to investigate dropping it from the installer for
Bookworm.

 1. https://lists.debian.org/debian-boot/2020/03/msg00182.html
and replies.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1034361: haveged: autopkgtest fails on bookworm kernel: service fails to start

[Paul Gevers]

Source: haveged
Version: 1.9.14-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails when the host 
is running a bookworm kernel. I have upgrade several of the 
ci.debian.net hosts (arm64, i386, ppc64el and s390x) to bookworm and 
that's where the failure happens. I confirm that running the test on 
amd64 with a bookworm kernel fails in the same way. Can you please 
investigate the situation and fix it? I copied some of the output at the 
bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore, however, I have a strong suspicion that it points 
out that the package is broken. Targeted fixes are still welcome.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/arm64/h/haveged/32696042/log.gz

autopkgtest [01:12:21]: test check-service: [---
failed
haveged service is not active
× haveged.service - Entropy Daemon based on the HAVEGE algorithm
 Loaded: loaded (/lib/systemd/system/haveged.service; enabled; 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2023-04-07 01:12:20 
CST; 1s ago

   Duration: 1ms
   Docs: man:haveged(8)
 http://www.issihosts.com/haveged/
Process: 1104 ExecStart=/usr/sbin/haveged --Foreground --verbose=1 
$DAEMON_ARGS (code=exited, status=225/NETWORK)

   Main PID: 1104 (code=exited, status=225/NETWORK)
CPU: 1ms
autopkgtest [01:12:21]: test check-service: ---]


OpenPGP_signature
Description: OpenPGP digital signature