kiranchavala opened a new issue, #14312:
URL: https://github.com/apache/cloudstack/issues/14312

   ### 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):
   
   
https://github.com/apache/cloudstack/blob/1a48a87587c03472feefb081cfac71b2ebd0f407/packaging/suse15/cloud.spec#L469
   
   
   /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
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to