Skip to content

OCPBUGS-78776: [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index#1573

Open
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-1565-to-release-4.18
Open

OCPBUGS-78776: [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index#1573
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-1565-to-release-4.18

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #1565

/assign JoelSpeed

@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug OCPBUGS-78353 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":[],"errors":{"rankBeforeIssue":"expected Object","rankAfterIssue":"expected Object"}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.
/retitle [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index

Details

In response to this:

This is an automated cherry-pick of #1565

/assign JoelSpeed

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.

@openshift-ci openshift-ci bot changed the title [release-4.18] OCPBUGS-78353: Prefer to remove members where they have another healthy machine in the same failure domain index [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index Mar 16, 2026
@openshift-ci openshift-ci bot requested review from Elbehery and hasbro17 March 16, 2026 15:04
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details 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

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 16, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8593d4f0-c446-430c-9cca-4d0dd043640a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 17, 2026

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/jira cherry-pick OCPBUGS-78353

@openshift-ci-robot
Copy link
Copy Markdown

@JoelSpeed: An error was encountered cloning bug for cherrypick for bug OCPBUGS-78353 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":[],"errors":{"rankBeforeIssue":"expected Object","rankAfterIssue":"expected Object"}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.
/retitle : [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index

Details

In response to this:

/jira cherry-pick OCPBUGS-78353

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.

@openshift-ci openshift-ci bot changed the title [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index : [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index Mar 17, 2026
@JoelSpeed
Copy link
Copy Markdown
Contributor

/jira cherry-pick OCPBUGS-78353

Does this work again yet? 🤔

@openshift-ci-robot
Copy link
Copy Markdown

@JoelSpeed: An error was encountered cloning bug for cherrypick for bug OCPBUGS-78353 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":["[CHART] Date of First Response: Invalid date format. Please enter the date in the format \"d/MMM/yy\"."],"errors":{"customfield_10024":"Invalid date format. Please enter the date in the format \"d/MMM/yy\"."}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.
/retitle : : [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index

Details

In response to this:

/jira cherry-pick OCPBUGS-78353

Does this work again yet? 🤔

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.

@openshift-ci openshift-ci bot changed the title : [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index : : [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index Mar 18, 2026
@JoelSpeed JoelSpeed changed the title : : [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index OCPBUGS-78776: [release-4.18] : Prefer to remove members where they have another healthy machine in the same failure domain index Mar 18, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 18, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-78776, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-78353 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-78353 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @geliu2016

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1565

/assign JoelSpeed

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.

@openshift-ci openshift-ci bot requested a review from geliu2016 March 18, 2026 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-bug Indicates that a 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants