Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
In some versions of redis (starting with 4.0.10) we have commits [1] and
[2] which add a warning on stderr which will be printed out every single
time a monitor operation takes place:

foo pacemaker-remoted[57563]: notice: redis_monitor_20000:1930:stderr
[ Warning: Using a password with '-a' option on the command line interface may not be safe. ]

Later on commit [3] (merged with 5.0rc4) was merged which added the option
'--no-auth-warning' to disable said warning since it broke a bunch of
scripts [4]. I tried to forcibly either try the command twice (first
with --no-auth-warning and then without in case of errors) but it is
impossible to distinguish between error due to missing param and other
errors.

All this horror and pain is due to the fact that redis does not support
any other means to pass a password (we could in theory first connect to
the server and then issue an AUTH command, but that seems even more
complex and error prone). See [5] for more info (or [6] for extra fun)

[1] [antirez/redis@c082221](https://github.com/antirez/redis/commit/c082221aefbb2a472c7193dbdbb90900256ce1a2)
[2] [antirez/redis@ef931ef](https://github.com/antirez/redis/commit/ef931ef93e909b4f504e8c6fbed350ed70c1c67c)
[3] [antirez/redis@a4ef94d](https://github.com/antirez/redis/commit/a4ef94d2f71a32f73ce4ebf154580307a144b48f)
[4] [antirez/redis#5073](https://github.com/antirez/redis/issues/5073)
[5] [antirez/redis#3483](https://github.com/antirez/redis/issues/3483)
[6] [antirez/redis#2413](https://github.com/antirez/redis/pull/2413)

Verified , 

[stack@undercloud-0 ~]$ ansible controller -b -mshell -a'rpm -q resource-agents;podman exec `podman ps -f name=redis-bundle-podman -q` sh -c "rpm -q resource-agents"'

controller-1 | CHANGED | rc=0 >>
resource-agents-4.1.1-23.el8.x86_64
resource-agents-4.1.1-23.el8.x86_64

controller-0 | CHANGED | rc=0 >>
resource-agents-4.1.1-23.el8.x86_64
resource-agents-4.1.1-23.el8.x86_64

controller-2 | CHANGED | rc=0 >>
resource-agents-4.1.1-23.el8.x86_64
resource-agents-4.1.1-23.el8.x86_64

[stack@undercloud-0 ~]$ ansible controller -b -mshell -a"grep -ir 'Using a password' /var/log/containers/redis"
 [WARNING]: Found both group and host with same name: undercloud

controller-1 | FAILED | rc=1 >>
non-zero return code

controller-0 | FAILED | rc=1 >>
non-zero return code

controller-2 | FAILED | rc=1 >>
non-zero return code

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-2019:3307