RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
# rngd --quiet
Initalizing available sources
Enabling RDRAND rng support
Enabling JITTER rng support
(same for 'rngd -q')

Version-Release number of selected component (if applicable):
rng-tools-6.3.1-1.el7.x86_64
(was okay before, rng-tool-5-15.el7 I think)

How reproducible:
100%

Steps to Reproduce:
1. rngd --quiet 
2.
3.

Actual results:
Diagnostic messages in quiet mode

Expected results:
Minimal output only (or just $ERRORLEVEL)

Additional info:

Related to Bug 1558616 - mismatch of the rngd options in help and man pages

I think this is a regression against https://bugzilla.redhat.com/show_bug.cgi?id=1558616#c4 (I think that was rng-tool-5-15.el7 , but forgot to write down the exact version)

Ok, please confirm that this build allows acts as it should.  It works for me:
 https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17450207

Looks good to me:

# rpm -q rng-tools
rng-tools-6.3.1-2.el7.x86_64

# rngd
Initalizing available sources
Failed to init entropy source 0: Hardware RNG Device
Failed to init entropy source 1: TPM RNG Device
Enabling RDRAND rng support
Enabling JITTER rng support

# rngd --quiet

# rngd -q

# echo $?
0

Looks good in RHEL-7.6-20180801.n.0 Server x86_64 :

# rpm -q rng-tools
rng-tools-6.3.1-2.el7.x86_64

# rngd
Initalizing available sources
Failed to init entropy source 0: Hardware RNG Device
Failed to init entropy source 1: TPM RNG Device
Enabling RDRAND rng support
Enabling JITTER rng support

# killall rngd

# rngd -q

# killall rngd

# rngd --quiet

#

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3022