Describe the bug

All sentinels show "status=sdown" after taking down the master - but no failover appears.

To reproduce 3 sentinel 1 master/2 replica

  1. set for every single sentinel a different sentinel auth-pass and sentinel auth-user
  2. enable aclfile /etc/redis/sentinel-users.acl
  3. provide a single acl with all users and hashed passwords:
user default on nopass allkeys -@all +SENTINEL|get-master-addr-by-name
user admin on #... allchannels +@all
user sentinel-01 on #... allkeys -@all +auth +client|getname +client|id +client|setname +command +hello +ping +role +sentinel|get-master-addr-by-name +sentinel|master +sentinel|myid +sentinel|replicas +sentinel|sentinels
user sentinel-02 on #... allkeys -@all +auth +client|getname +client|id +client|setname +command +hello +ping +role +sentinel|get-master-addr-by-name +sentinel|master +sentinel|myid +sentinel|replicas +sentinel|sentinels
user sentinel-03 on #... allkeys -@all +auth +client|getname +client|id +client|setname +command +hello +ping +role +sentinel|get-master-addr-by-name +sentinel|master +sentinel|myid +sentinel|replicas +sentinel|sentinels
  1. deploy this file for every single sentinel and take the master redis-server down

A description of what you expected to happen.

After some downtime the sentinels should do the failover.

Any additional information that is relevant to the problem.

# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0 
sentinel_scripts_queue_length:0 
sentinel_simulate_failure_flags:0 
master0:name=master,status=sdown,address=redis-01:6379,slaves=2,sentinels=3

SENTINEL ckquorum master
OK 3 usable Sentinels. Quorum and failover authorization can be reached

As soon as I disable the aclfile (default has then no password protection with all permissions), the failover works flawless. fyi - I also use an aclfile for the redis-server, no issues there, so the sha256 hashes are correctly made. The passwords are long but no special characters because of earlier issues.

Package: redis-server
Version: 6:6.2.6-1rl1~focal1
Package: redis-sentinel
Version: 6:6.2.6-1rl1~focal1

Comment From: HidingCherry

Looks like there is some wrong acl - it was taken from here: https://redis.io/topics/sentinel#configuring-sentinel-instances-with-authentication It works without issues if I change -@all to +@all.

Comment From: HidingCherry

missing acl permission: +sentinel|is-master-down-by-addr