[release-4.19] OCPBUGS-56662: Fix failed etcd test on arbiter ci run

[openshift-cherrypick-robot]

This is an automated cherry-pick of #29694

/assign eggfoobar

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OCPEDGE-1678

In response to this:

This is an automated cherry-pick of #29694

/assign eggfoobar

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.

[eggfoobar]

/retitle [release-4.19] OCPEDGE-1894: Fix failed etcd test on arbiter ci run

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references OCPEDGE-1894 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #29694

/assign eggfoobar

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.

[eggfoobar]

/lgtm

[eggfoobar]

/test e2e-metal-ovn-two-node-arbiter

[eggfoobar]

/assign @dusk125

Hey Allen, when you get a chance can you approve this backport. This is the last test to going green on our ci lanes :) https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/65116/rehearse-65116-periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ovn-two-node-arbiter-techpreview/1924666446495879168

[dusk125]

/approve
/label backport-risk-assessed

[openshift-ci]

@dusk125: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/approve
/label backport-risk-assessed

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, eggfoobar, openshift-cherrypick-robot

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:

• test/extended/etcd/OWNERS [dusk125]

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-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-single-node-upgrade	a58e47b	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial	a58e47b	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-rt-upgrade	a58e47b	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-metal-ovn-two-node-arbiter	a58e47b	link	false	/test e2e-metal-ovn-two-node-arbiter
ci/prow/e2e-gcp-csi	a58e47b	link	false	/test e2e-gcp-csi

Full PR test history. Your PR dashboard.

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.

[dhensel-rh]

/label qe-approved

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references OCPEDGE-1894 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #29694

/assign eggfoobar

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.

[hasbro17]

/label backport-risk-assessed

[openshift-ci]

@hasbro17: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label backport-risk-assessed

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.

[hasbro17]

/assign @sjenning

[sjenning]

/label backport-risk-assessed

[sjenning]

/label cherry-pick-approved

[eggfoobar]

/retitle [release-4.19] OCPBUGS-56662: Fix failed etcd test on arbiter ci run

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-56662, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• dependent bug OCPEDGE-1678 is not in the required OCPBUGS project

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

This is an automated cherry-pick of #29694

/assign eggfoobar

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.

[eggfoobar]

/jira refresh

Making the bot happy :)

[openshift-ci-robot]

@eggfoobar: This pull request references Jira Issue OCPBUGS-56662, which is invalid:

• expected dependent Jira Issue OCPBUGS-56663 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Making the bot happy :)

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.

[eggfoobar]

/jira refresh

[openshift-ci-robot]

@eggfoobar: This pull request references Jira Issue OCPBUGS-56662, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-56663 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-56663 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

In response to this:

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

[openshift-ci-robot]

@eggfoobar: This pull request references Jira Issue OCPBUGS-56662, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-56663 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-56663 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

In response to this:

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b807b51 and 2 for PR HEAD a58e47b in total

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56662: All pull requests linked via external trackers have merged:

• openshift/origin#29826

Jira Issue OCPBUGS-56662 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #29694

/assign eggfoobar

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202505261342.p0.g828598b.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.19.0-0.nightly-2025-05-27-102921