You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If task validation, we would only log it to the cass-operator logs and then requeue. This would happen forever and the only way user would know why the task is forever in the running state would be to check the cass-operator logs.
What did you expect to happen?
The task would have Failed condition set and it would have a message indicating what went wrong.
How can we reproduce it (as minimally and precisely as possible)?
Create a replace job without target podName.
cass-operator version
1.17.2
Kubernetes version
1.27
Method of installation
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered:
What happened?
If task validation, we would only log it to the cass-operator logs and then requeue. This would happen forever and the only way user would know why the task is forever in the running state would be to check the cass-operator logs.
What did you expect to happen?
The task would have Failed condition set and it would have a message indicating what went wrong.
How can we reproduce it (as minimally and precisely as possible)?
Create a replace job without target podName.
cass-operator version
1.17.2
Kubernetes version
1.27
Method of installation
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: