Closed amirreza8002 closed 1 day ago
Thanks for taking the time to report this issue. It seems the issue is related to the latest changes introduced in 7.2.7-debian-12-r1. We are going to take a look at it and update this thread as soon as possible.
In the meantime, you can use 7.2.7-debian-12-r0 or any 8.0.x tag.
We are working on building an updated version of the container and adding new test to our container. Please stay tuned
7.2.7-debian-12-r3 was released with the changes to fix this issue. Did you have the chance to take a look at it?
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/valkey-sentinel:7.2.7
What architecture are you using?
None
What steps will reproduce the bug?
running valkey:7.2.7 fails:
Unrecognized sentinel configuration statement.
What is the expected behavior?
No response
What do you see instead?
seems like the sentinel conf is not supported by valkey:7.2.7 worth noting that this is a new error(3 days ago), the same tests had no problems some time ago
Additional information
7.2.7 fails latest passes