openshift / cluster-etcd-operator

Operator to manage the lifecycle of the etcd members of an OpenShift cluster
Apache License 2.0
95 stars 127 forks source link

[release-4.12] OCPBUGS-35501: return errors in wait-for-ceo #1277

Closed openshift-cherrypick-robot closed 2 months ago

openshift-cherrypick-robot commented 3 months ago

This is an automated cherry-pick of #1273

/assign openshift-cherrypick-robot

openshift-ci-robot commented 3 months ago

@openshift-cherrypick-robot: Jira Issue OCPBUGS-35077 has been cloned as Jira Issue OCPBUGS-35501. Will retitle bug to link to clone. /retitle [release-4.12] OCPBUGS-35501: return errors in wait-for-ceo

In response to [this](https://github.com/openshift/cluster-etcd-operator/pull/1277): >This is an automated cherry-pick of #1273 > >/assign openshift-cherrypick-robot Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-etcd-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci-robot commented 3 months ago

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

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](https://github.com/openshift/cluster-etcd-operator/pull/1277): >This is an automated cherry-pick of #1273 > >/assign openshift-cherrypick-robot Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-etcd-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
Elbehery commented 3 months ago

/lgtm /approve

openshift-ci[bot] commented 3 months ago

@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-gcp-qe-no-capabilities 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-gcp-qe-no-capabilities
ci/prow/e2e-azure-ovn-etcd-scaling 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-serial-ipv4 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-metal-ipi-serial-ipv4
ci/prow/e2e-metal-single-node-live-iso 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-metal-single-node-live-iso
ci/prow/e2e-aws-disruptive-ovn 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-aws-disruptive-ovn
ci/prow/e2e-vsphere-ovn-etcd-scaling 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-gcp-disruptive-ovn 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-gcp-disruptive-ovn
ci/prow/e2e-metal-ipi 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-metal-ipi
ci/prow/e2e-aws-disruptive 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-aws-disruptive
ci/prow/e2e-gcp-disruptive 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-gcp-disruptive
ci/prow/e2e-aws-etcd-recovery 113b10e202c879546046ba7b9ef44b6775e8f078 link false /test e2e-aws-etcd-recovery

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
tjungblu commented 3 months ago

/jira refresh

openshift-ci-robot commented 3 months ago

@tjungblu: This pull request references Jira Issue OCPBUGS-35501, which is invalid:

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](https://github.com/openshift/cluster-etcd-operator/pull/1277#issuecomment-2173793829): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-etcd-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
tjungblu commented 3 months ago

/label backport-risk-assessed

tjungblu commented 2 months ago

/jira refresh

openshift-ci-robot commented 2 months ago

@tjungblu: This pull request references Jira Issue OCPBUGS-35501, 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.12.z) matches configured target version for branch (4.12.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-35077](https://issues.redhat.com//browse/OCPBUGS-35077) 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-35077](https://issues.redhat.com//browse/OCPBUGS-35077) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z * bug has dependents

Requesting review from QA contact: /cc @geliu2016

In response to [this](https://github.com/openshift/cluster-etcd-operator/pull/1277#issuecomment-2199444398): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-etcd-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci[bot] commented 2 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Elbehery, geliu2016, 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: - ~~[OWNERS](https://github.com/openshift/cluster-etcd-operator/blob/release-4.12/OWNERS)~~ [Elbehery] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci-robot commented 2 months ago

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

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

In response to [this](https://github.com/openshift/cluster-etcd-operator/pull/1277): >This is an automated cherry-pick of #1273 > >/assign openshift-cherrypick-robot Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-etcd-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-bot commented 2 months ago

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-etcd-operator-container-v4.12.0-202407010936.p0.g4bf4f66.assembly.stream.el8 for distgit cluster-etcd-operator. All builds following this will include this PR.

openshift-merge-robot commented 2 months ago

Fix included in accepted release 4.12.0-0.nightly-2024-07-02-151653