Skip to content
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

Updated the clean up application resource message #1375

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

TimothyAsirJeyasing
Copy link
Contributor

Copy link
Contributor

openshift-ci bot commented May 10, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: TimothyAsirJeyasing
Once this PR has been reviewed and has the lgtm label, please assign bipuladh for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@TimothyAsirJeyasing
Copy link
Contributor Author

image

@SanjalKatiyar , @GowthamShanmugam Please review

@@ -150,7 +150,7 @@
"Relocated to cluster {{ preferredCluster }}": "Relocated to cluster {{ preferredCluster }}",
"Completed": "Completed",
"FailingOver to cluster {{ failoverCluster }}": "FailingOver to cluster {{ failoverCluster }}",
"Cleanup of resources requires user attention. Finish cleanup to restart replication.": "Cleanup of resources requires user attention. Finish cleanup to restart replication.",
"Clean up application resources/application workload on current primary cluster {{ failoverCluster }} to start the relocation.": "Clean up application resources/application workload on current primary cluster {{ failoverCluster }} to start the relocation.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The error message is different for Failover and relocates actions.

Also, the failover & relocate error message will differ for regional and metro.

Comment on lines -66 to -68
description: t('Relocating to cluster {{ preferredCluster }}', {
preferredCluster,
}),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why does the relocating status have to be removed?

Comment on lines +68 to +73
description: t(
'Clean up application resources on current primary cluster {{failoverCluster}} to start the relocation.',
{
failoverCluster,
}
),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont see any check for cleanup in progress

preferredCluster,
}),
description: t(
'Clean up application resources on current primary cluster {{failoverCluster}} to start the relocation.',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, the message says current primary but the placeholder is referring to {{failoverCluster}}, it is confusing.

Comment on lines +98 to +112
'Clean up application resources on failed cluster {{failoverCluster}} to start the replication.',
{
failoverCluster,
}
),
status: t('Pending'),
icon: <PendingIcon />,
};
} else {
return {
description: t(
'Clean up application resources on failed cluster {{failoverCluster}}.',
{
failoverCluster,
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to repeat everything, just message is differs for Async and sync

Comment on lines +119 to +124
return {
description: t('FailedOver to cluster {{failoverCluster}}', {
failoverCluster,
}),
status: t('Completed'),
icon: <GreenCheckCircleIcon />,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optimize this failover/relocate/cleanup checks

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.

None yet

2 participants