openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.49k stars 4.7k forks source link

[release-4.17] OCPBUGS-44190: fix unexpected not ready #29226

Closed openshift-cherrypick-robot closed 3 days ago

openshift-cherrypick-robot commented 4 weeks ago

This is an automated cherry-pick of #29225

/assign kannon92

openshift-ci-robot commented 4 weeks ago

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OCPNODE-2668

In response to [this](https://github.com/openshift/origin/pull/29226): >This is an automated cherry-pick of #29225 > >/assign kannon92 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 4 weeks ago

/assign @deads2k

kannon92 commented 4 weeks ago

/retest

kannon92 commented 3 weeks ago

/retest-required

kannon92 commented 3 weeks ago

/test e2e-metal-ipi-ovn-ipv6

kannon92 commented 2 weeks ago

@deads2k could you take a look at this when you get a chance?

dgoodwin commented 2 weeks ago

/lgtm

openshift-ci[bot] commented 2 weeks ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, 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/origin/blob/release-4.17/OWNERS)~~ [dgoodwin] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
dgoodwin commented 2 weeks ago

/label backport-risk-assessed /label cherry-pick-approved

kannon92 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

@kannon92: This pull request references OCPNODE-2668 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.z" version, but no target version was set.

In response to [this](https://github.com/openshift/origin/pull/29226#issuecomment-2454685396): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/retitle [release-4.17] NO-JIRA: fix unexpected not ready

openshift-ci-robot commented 2 weeks ago

@openshift-cherrypick-robot: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/origin/pull/29226): >This is an automated cherry-pick of #29225 > >/assign kannon92 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

@kannon92: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/origin/pull/29226#issuecomment-2454991399): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/retitle [release-4.17] OCPBUGS-44190: fix unexpected not ready

openshift-ci-robot commented 2 weeks ago

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-44190, 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/origin/pull/29226): >This is an automated cherry-pick of #29225 > >/assign kannon92 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

@kannon92: This pull request references Jira Issue OCPBUGS-44190, 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/origin/pull/29226#issuecomment-2455028458): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

@kannon92: This pull request references Jira Issue OCPBUGS-44190, 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/origin/pull/29226#issuecomment-2455037089): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

@kannon92: This pull request references Jira Issue OCPBUGS-44190, 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/origin/pull/29226#issuecomment-2455040102): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

@kannon92: This pull request references Jira Issue OCPBUGS-44190, 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.17.z) matches configured target version for branch (4.17.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-44191](https://issues.redhat.com//browse/OCPBUGS-44191) is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-44191](https://issues.redhat.com//browse/OCPBUGS-44191) targets the "4.18.0" version, which is one of the valid target versions: 4.18.0 * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (schoudha@redhat.com), skipping review request.

In response to [this](https://github.com/openshift/origin/pull/29226#issuecomment-2455042882): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
kannon92 commented 2 weeks ago

/hold

There are some regressions with this PR in 4.18. Will investigate before carrying this into 4.17.

openshift-ci[bot] commented 2 weeks 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-agnostic-ovn-cmd 33294be811528729ef5c9d69994a85e43ea44fec link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-single-node-upgrade 33294be811528729ef5c9d69994a85e43ea44fec link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 33294be811528729ef5c9d69994a85e43ea44fec link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-single-node-serial 33294be811528729ef5c9d69994a85e43ea44fec link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-ipv6 33294be811528729ef5c9d69994a85e43ea44fec link unknown /test e2e-metal-ipi-ovn-ipv6

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).
kannon92 commented 3 days ago

/close

We don't need to backport this.

openshift-ci[bot] commented 3 days ago

@kannon92: Closed this PR.

In response to [this](https://github.com/openshift/origin/pull/29226#issuecomment-2485588704): >/close > >We don't need to backport this. 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.
openshift-ci-robot commented 3 days ago

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-44190. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to [this](https://github.com/openshift/origin/pull/29226): >This is an automated cherry-pick of #29225 > >/assign kannon92 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.