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

After hub recovery, cant initiate failover #932

Merged

Conversation

GowthamShanmugam
Copy link
Contributor

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 24, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GowthamShanmugam

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

The pull request process is described 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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 24, 2023

@GowthamShanmugam: This pull request references Bugzilla bug 2209288, which is valid.

No validations were run on this bug

Requesting review from QA contact:
/cc @parikshithb

In response to this:

Bug 2209288: After hub recovery, cant initiate failover

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 24, 2023

@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: parikshithb.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@GowthamShanmugam: This pull request references Bugzilla bug 2209288, which is valid.

No validations were run on this bug

Requesting review from QA contact:
/cc @parikshithb

In response to this:

Bug 2209288: After hub recovery, cant initiate failover

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@GowthamShanmugam GowthamShanmugam changed the title Bug 2209288: After hub recovery, cant initiate failover Bug 2209288: After hub recovery, cant initiate failover - WIP Jul 25, 2023
@GowthamShanmugam
Copy link
Contributor Author

/hold

@GowthamShanmugam GowthamShanmugam changed the title Bug 2209288: After hub recovery, cant initiate failover - WIP Bug 2209288: After hub recovery, cant initiate failover Aug 3, 2023
@GowthamShanmugam
Copy link
Contributor Author

/hold cancel

placementDecision: ACMPlacementDecisionKind,
drPlacementControl: DRPlacementControlKind
): string[] => {
if (placementDecision?.status.decisions.length > 0) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

do we need to do this or its guaranteed that if "status" is present then "decisions" will be present as well ??

Suggested change
if (placementDecision?.status.decisions.length > 0) {
if ((placementDecision ?? {}).status?.decisions?.length > 0) {

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ack

@SanjalKatiyar
Copy link
Collaborator

so, this annotation will never get removed ?? not even during hub recovery ??

@GowthamShanmugam
Copy link
Contributor Author

GowthamShanmugam commented Aug 8, 2023

so, this annotation will never get removed ?? not even during hub recovery ??

When ramen starts to reconcile, it will add the annotation immediately. In hub recovery, they will get this info from s3 object storage and display it as a last-remembered application cluster.

@SanjalKatiyar
Copy link
Collaborator

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Aug 8, 2023
@GowthamShanmugam GowthamShanmugam changed the title Bug 2209288: After hub recovery, cant initiate failover After hub recovery, cant initiate failover Aug 8, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 8, 2023

@GowthamShanmugam: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

After hub recovery, cant initiate failover

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@GowthamShanmugam
Copy link
Contributor Author

/cherry-pick release-4.14

@openshift-cherrypick-robot

@GowthamShanmugam: once the present PR merges, I will cherry-pick it on top of release-4.14 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@GowthamShanmugam
Copy link
Contributor Author

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 8, 2023

@GowthamShanmugam: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@GowthamShanmugam
Copy link
Contributor Author

/cherry-pick release-4.14-compatibility

@openshift-cherrypick-robot

@GowthamShanmugam: once the present PR merges, I will cherry-pick it on top of release-4.14-compatibility in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.14-compatibility

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@GowthamShanmugam
Copy link
Contributor Author

/test odf-console-e2e-aws

1 similar comment
@GowthamShanmugam
Copy link
Contributor Author

/test odf-console-e2e-aws

@openshift-merge-robot openshift-merge-robot merged commit 2ff703f into red-hat-storage:master Aug 8, 2023
6 checks passed
@openshift-cherrypick-robot

@GowthamShanmugam: new pull request created: #956

In response to this:

/cherry-pick release-4.14-compatibility

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@GowthamShanmugam: new pull request created: #957

In response to this:

/cherry-pick release-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants