Describe the bug

On upgrading to redis version: 7.2.5-debian-12-r0 from version: 6.2.6-debian-10-r140 redis gets upgraded successfully. But when it is restarted, we get the following error for the pods: Unrecoverable error: corrupted cluster config file "5270a2453e7db28eee53f976faca81306e649b19 10.151.6.27:6379@16379,,tls-port=0,shard-id=2a12a835ae20c88b96627ed19a42f1ac18b5086c slave 54395be964fa95e84bf83da107c8231aeb4c7904 0 1719394776000 51 connected and all of the redis nodes fall into CrashLoopBackOff state and never recover from there.

To reproduce

  1. Try upgrading to version: 7.2.5-debian-12-r0 , it may get upgraded successfully. After it's upgraded, restart all the redis pods, you should see the above error and it is unrecoverable.

Steps to reproduce the behavior and/or a minimal code sample.

Expected behavior

The aforementioned error should not occur and after upgrading, after restart, all the redis nodes should come up successfully.

Additional information

There are already a few issues reported for this bug, link to all the reported issues: 1. https://github.com/redis/redis/issues/12761 2. https://github.com/redis/redis/pull/13428

Please help resolve this issue, or let us know if we should put the upgrade to 7.2.5 on hold for now if any fix for it is coming in the near future.

Comment From: sundb

Please help resolve this issue, or let us know if we should put the upgrade to 7.2.5 on hold for now if any fix for it is coming in the near future.

yes, #13428 will backport to 7.2 if it works. can your try #13428 to see if it works? thanks.

Comment From: ihussainbadshah

@sundb thanks for your prompt response. Could you please elaborate a little as to how to implement the solution explained in #13428 ? I mean does anything need to be changed in the configuration file and which configuration file would that be?

Comment From: sundb

@ihussainbadshah can you apply the patch, build and run it in your develoopment environment? don't need to change any config.

Comment From: ihussainbadshah

@sundb so the fix is not released yet officially? Please confirm.

Comment From: sundb

@ihussainbadshah yes, it's still in review, need more tests.

Comment From: ihussainbadshah

@sundb ok thanks for the confirmation.

Comment From: ihussainbadshah

@sundb 7.4.0 version of redis server also does not guarantee the fix for this issue, right?

Comment From: sundb

@ihussainbadshah yes, it hasn't been merged yet.

Comment From: ihussainbadshah

@sundb could you please tell when the fix for this issue will be officially released?

Comment From: sundb

@ihussainbadshah it will probably be released in next 7.4.

Comment From: ihussainbadshah

@sundb any timeline you could specify?

Comment From: sundb

@ihussainbadshah sorry, i'm not sure the timeline, but sure that it won't be recently.

Comment From: sundb

Close via #13468