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

DFBUGS-1258: [release-4.18] controllers: allow failover to complete when peer site is down #2961

Merged

Conversation

rewantsoni
Copy link
Member

For the failover to be completed, we need to reconcile the rbdMirror CR.
ocs-client creation was blocking the reconciliation of rbdMirror, hence
move the creation of ocs-client to where it is required

Manual Cherry pick of #2957

For failover to complete, we need to reconcile the rbdMirror CR.
ocs-client creation was blocking reconcile of rbdMirror, hence
continue reconcile for local resources even if the peer site is
down

Signed-off-by: Rewant Soni <[email protected]>
(cherry picked from commit e7121c8)
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Jan 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 9, 2025

@rewantsoni: This pull request references [Jira Issue DFBUGS-1258](https://issues.redhat.com//browse/DFBUGS-1258), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jilju

In response to this:

For the failover to be completed, we need to reconcile the rbdMirror CR.
ocs-client creation was blocking the reconciliation of rbdMirror, hence
move the creation of ocs-client to where it is required

Manual Cherry pick of #2957

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

openshift-ci bot commented Jan 9, 2025

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: jilju.

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:

@rewantsoni: This pull request references [Jira Issue DFBUGS-1258](https://issues.redhat.com//browse/DFBUGS-1258), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jilju

In response to this:

For the failover to be completed, we need to reconcile the rbdMirror CR.
ocs-client creation was blocking the reconciliation of rbdMirror, hence
move the creation of ocs-client to where it is required

Manual Cherry pick of #2957

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 openshift-eng/jira-lifecycle-plugin 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-sigs/prow repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 10, 2025
Copy link
Contributor

openshift-ci bot commented Jan 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, rewantsoni

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 10, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 08092c9 into red-hat-storage:release-4.18 Jan 10, 2025
11 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 10, 2025

@rewantsoni: [Jira Issue DFBUGS-1258](https://issues.redhat.com//browse/DFBUGS-1258): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-1258](https://issues.redhat.com//browse/DFBUGS-1258) has been moved to the MODIFIED state.

In response to this:

For the failover to be completed, we need to reconcile the rbdMirror CR.
ocs-client creation was blocking the reconciliation of rbdMirror, hence
move the creation of ocs-client to where it is required

Manual Cherry pick of #2957

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 openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants