Skip to content

SUSE 15: packaging enables non-existent rngd.service, so rng-tools is never started #14312

Description

@kiranchavala

problem

rng-tools is a hard dependency of both cloudstack-management and cloudstack-agent

The current packaging/suse15/cloud.spec still runs this in the post-install scripts for both management and agent (lines 469 and 533):

/usr/bin/systemctl enable --now rngd > /dev/null 2>&1 || true

/usr/bin/systemctl enable --now rngd > /dev/null 2>&1 || true

If rngd.service doesn't exist and rng-tools is inactive right after a fresh CloudStack install.

versions

ACS 4.22.x
ACS 4.23.0
Management and hypervisor os
SUSE Linux Enterprise Server 15 SP7 (kernel 6.4.0-150700.53.81-default),

The steps to reproduce the bug

On SLES 15 SP7 with the CloudStack SUSE repo configured

zypper install cloudstack-agent # or cloudstack-management

systemctl list-unit-files | grep -i rng
systemctl status rngd --no-pager
systemctl status rng-tools --no-pager

cskvm1-sles-sap:~ # systemctl status rng-tools --no-pager
○ rng-tools.service - Start the rngd daemon
Loaded: loaded (/usr/lib/systemd/system/rng-tools.service; disabled; preset: disabled)
Active: inactive (dead)
cskvm1-sles-sap:~ # systemctl status rng-tools --no-pager
○ rng-tools.service - Start the rngd daemon
Loaded: loaded (/usr/lib/systemd/system/rng-tools.service; disabled; preset: disabled)
Active: inactive (dead)

What to do about it?

rng-tools.service should be enabled and active (running) after the CloudStack package is installed.

workaround

systemctl enable --now rng-tools

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions