We are running into an issue where tctl pull up the namespace but temporal says it cannot find the namespace and the workflow workers are reporting the same thing. We restarted the container twice and the issue continues to happen.
would run
tctl adm cl d
to describe your cluster and look at your ring members. seen this happen when you might have multiple not-network-isolated clusters join together due to some config issues (typically membership ports)
I checked the rings and everything looked good see below:
“rings”: [
{
“role”: “frontend”,
“memberCount”: 1,
“members”: [
{
“identity”: “172.17.0.6:7233”
}
]
},
{
“role”: “history”,
“memberCount”: 1,
“members”: [
{
“identity”: “172.17.0.6:7234”
}
]
},
{
“role”: “matching”,
“memberCount”: 1,
“members”: [
{
“identity”: “172.17.0.6:7235”
}
]
},
{
“role”: “worker”,
“memberCount”: 1,
“members”: [
{
“identity”: “172.17.0.6:7239”
}
]
}
]
},
