Cluster Slave Error about redis HOT 2 OPEN

I am seeing this error as well after upgrading a cluster from 5.0.10 to 5.0.14.1.
Masters OK, Slaves have the problem.
Built a new cluster (since for upgrade I did the binary file replacement). Same issue on the new cluster.

Turning off appendonly in the slave allows it to work...and it can become a master. but basically any node that has appendonly yes can not startup or become a slave.

This looks to be related to the changes in 5.0.14.1.
Changed to 5.0.14 and it works fine with the slaves and appendonly yes.

I am not currently using additonal redis modules so I feel that 5.0.14 is good for me at the moment.

??? loadServerConfig(configfile,options,NULL);.

from redis.

[28356] 10 Apr 19:49:44.131 * Connecting to MASTER 109.242.233.245:22
[28356] 10 Apr 19:49:44.132 * MASTER <-> REPLICA sync started
[28356] 10 Apr 19:50:05.134 * Non blocking connect for SYNC fired the event.
[28356] 10 Apr 19:50:05.135 # Sending command to master in replication handshake: -Writing to master: 找不到指定的模块。
[28356] 10 Apr 19:50:05.204 * Connecting to MASTER 109.242.233.245:22
[28356] 10 Apr 19:50:05.205 * MASTER <-> REPLICA sync started
[28356] 10 Apr 19:50:26.208 * Non blocking connect for SYNC fired the event.
[28356] 10 Apr 19:50:26.209 # Sending command to master in replication handshake: -Writing to master: 找不到指定的模块。
[28356] 10 Apr 19:50:26.283 * Connecting to MASTER 109.242.233.245:22
[28356] 10 Apr 19:50:26.284 * MASTER <-> REPLICA sync started
[28356] 10 Apr 19:50:47.288 * Non blocking connect for SYNC fired the event.
[28356] 10 Apr 19:50:47.289 # Sending command to master in replication handshake: -Writing to master: 找不到指定的模块。

I had this problem too, but I didn't set up the master-slave relationship！

from redis.