Sentinels set up with wrong master password not throwing when authentication fails

Problem

So not sure how to explain this quickly and cleanly but basically this is roughly the case scenario that happened due to some configuration not being (automatically) deployed correctly: 3 redis servers UP ips: 1, 2, 3 port 6379 server 1 is master (protected with password: password) server 2,3 slaves (correctly configured to be slave of server 1) 3 sentinels UP ips: 1,2,3 port 26379 Sentinels are badly configured /etc/sentinel.conf sentinel 1 monitor master 1 (correctly configured to monitor the master with the right password) sentinel 2 monitor master 2 (2 is not a master) <- bad configuration (master ip is that of the slave ip ) sentinel 3 monitor master 3 (3 is not a master) <- bad configuration (master ip is that of the slave ip ) with quorum set to 2 With this set up [code block] The connect event is being raised (Right we can connect to the sentinels) The Ready event is never being raised (Right the sentinels cannot communicate / agree / authenticate to the master ) However no error event being raised.... Hence we don't know from a client side perspective what it is wrong even though the connection to sentinels is established Sending set redis commands also results in no errors being raised and (nothing actually gets set in the cache) Does this mean that we always have to wait for the ready event before actually trying to send a command when connected to sentinels? sorry if its configuration is not properly detailed I will try to do so soo