Skip to content

Return NonRetryableApplicationError if Namespace is not found on remote cluster during verify #4786

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 21, 2023

Conversation

hehaifengcn
Copy link
Contributor

@hehaifengcn hehaifengcn commented Aug 21, 2023

What changed?
During force replication, namespace should exist on remote (target cluster). If namespace doesn't exist (due to operator error e.g.,), fail VerifyReplicationTasks activity fast. Otherwise, workflow will retry VerifyReplicationTasks activity infinitely.

Why?

How did you test it?

Potential risks

Is hotfix candidate?

@hehaifengcn hehaifengcn requested a review from a team as a code owner August 21, 2023 14:49
@hehaifengcn hehaifengcn merged commit f6755a5 into main Aug 21, 2023
@hehaifengcn hehaifengcn deleted the haifengh/not_found branch August 21, 2023 18:39
hehaifengcn added a commit that referenced this pull request Aug 22, 2023
…te cluster during verify (#4786)

<!-- Describe what has changed in this PR -->
**What changed?**
During force replication, namespace should exist on remote (target
cluster). If namespace doesn't exist (due to operator error e.g.,), fail
VerifyReplicationTasks activity fast. Otherwise, workflow will retry
VerifyReplicationTasks activity infinitely.


<!-- Tell your future self why have you made these changes -->
**Why?**


<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**


<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**


<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants