OM Frontend cannot find an existing ticket for a WatchAssignmentsRequest

[Dijksta]

What happened:
I suddenly started having problems with Open Match WatchAssignmentsRequest I previously haven't experienced. My Frontend Client creates a ticket and sends a WatchAssignmentsRequest to the om-frontend. However, my Frontend Client throws an error that the ticket is not found

Error in request of type openmatch.Frontend$WatchAssignmentsRequest: NOT_FOUND: Ticket id: c5tv6lb13aih4ljkokmg not found

I see in the om-query-service that the ticket is indeed created and it also appears in my Matchmaking Function logs

Current tickets for profile quick-match_profile: [c5ttgrfm04au7hpgc13g, ..., c5tv6lb13aih4ljkokmg]

I can also confirm that the om-frontend cannot find the ticket:

time="2021-10-29T13:12:53Z" level=error msg="rpc error: code = NotFound desc = Ticket id: c5tv6lb13aih4ljkokmg not found" app=openmatch component=api.frontend

This is very bizarre, because the ticket is obviously created but cannot be fetched by the om-frontend. I am using OpenMatch v1.2.0. After I noticed the issue, I tried upgrading to v1.3.0, but that did not help.

What you expected to happen:
The ticket c5tv6lb13aih4ljkokmg to be found by the OpenMatch Frontend. It is obviously created and it appears in both the OM Query component and my Match Making Function.

How to reproduce it (as minimally and precisely as possible):
I just created a ticket and tried to watch its assignment.

Anything else we need to know?:
The redis pods from the default deployment (ReplicaSet) do not produce any logs.

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:38:50Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4-gke.2300", GitCommit:"b4e407e768299b79bc8ed8edf889f39bac1ea05f", GitTreeState:"clean", BuildDate:"2021-09-14T09:23:05Z", GoVersion:"go1.16.7b7", Compiler:"gc", Platform:"linux/amd64"

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
GKE

Open Match Release Version:
Tested on both 1.2.0 and 1.3.0

Install Method(yaml/helm)::
yaml

[Dijksta]

Ultimately, the problem disappeared when I deleted the second redis node. The issue seems to be a bad synchronization between the two redis nodes created by the default .yaml config.