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.

Sign up for GitHub

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

Jump to bottom

OCPBUGS-18527: Ignore timeout and connection refused errors during upgrade tests for 4.12 #28270

Merged
merged 1 commit into from Oct 2, 2023
Merged

OCPBUGS-18527: Ignore timeout and connection refused errors during upgrade tests for 4.12 #28270

merged 1 commit into from Oct 2, 2023

Conversation

harche
Copy link
Contributor

@harche harche commented Sep 21, 2023

Ignore timeout and connection refused errors during upgrade tests for 4.12

@harche
ignore timeout and connection refused error during upgrade tests
4f390cb 
Signed-off-by: Harshal Patil <harpatil@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 21, 2023
@openshift-ci-robot
Copy link

@harche: This pull request references Jira Issue OCPBUGS-18527, which is invalid:

  • expected Jira Issue OCPBUGS-18527 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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:

Ignore timeout and connection refused errors during upgrade tests for 4.12

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/test-infra repository.

@harche harche changed the title OCPBUGS-18527: Ignore timeout and connection refused errors during upgrade tests for 4.11 OCPBUGS-18527: Ignore timeout and connection refused errors during upgrade tests for 4.12 Sep 21, 2023
@rphillips
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 21, 2023
@harche
Copy link
Contributor Author

harche commented Sep 28, 2023

/retest-required

1 similar comment
@harche
Copy link
Contributor Author

harche commented Sep 29, 2023

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2023 •
edited

@harche: 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-serial 4f390cb link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-csi 4f390cb link false /test e2e-aws-csi
ci/prow/e2e-gcp-ovn-rt-upgrade 4f390cb link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-openstack-ovn 4f390cb link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-upgrade 4f390cb link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-single-node 4f390cb link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-cgroupsv2 4f390cb link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-single-node-upgrade 4f390cb link false /test e2e-aws-ovn-single-node-upgrade

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

@mrunalp mrunalp removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 29, 2023
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 29, 2023
@openshift-ci-robot
Copy link

@harche: This pull request references Jira Issue OCPBUGS-18527, which is invalid:

  • expected Jira Issue OCPBUGS-18527 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Ignore timeout and connection refused errors during upgrade tests for 4.12

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/test-infra repository.

@mrunalp mrunalp added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 29, 2023
@openshift-ci-robot
Copy link

@harche: This pull request references Jira Issue OCPBUGS-18527, which is invalid:

  • expected Jira Issue OCPBUGS-18527 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Retaining the jira/valid-bug label as it was manually added.

In response to this:

Ignore timeout and connection refused errors during upgrade tests for 4.12

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/test-infra repository.

1 similar comment
@openshift-ci-robot
Copy link

@harche: This pull request references Jira Issue OCPBUGS-18527, which is invalid:

  • expected Jira Issue OCPBUGS-18527 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Retaining the jira/valid-bug label as it was manually added.

In response to this:

Ignore timeout and connection refused errors during upgrade tests for 4.12

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/test-infra repository.

@mrunalp mrunalp added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 29, 2023
@mrunalp mrunalp added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 29, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2023

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: harche, mrunalp, rphillips

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

@harche
Copy link
Contributor Author

harche commented Sep 29, 2023

/test e2e-aws-ovn-fips

@mrunalp mrunalp added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 2, 2023
@openshift-ci openshift-ci bot merged commit b771de0 into openshift:release-4.12 Oct 2, 2023
14 of 22 checks passed
@openshift-ci-robot
Copy link

@harche: Jira Issue OCPBUGS-18527: All pull requests linked via external trackers have merged:

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

In response to this:

Ignore timeout and connection refused errors during upgrade tests for 4.12

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/test-infra repository.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.12.0-0.nightly-2023-10-03-100605

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mrunalp mrunalp mrunalp approved these changes

@mfojtik mfojtik Awaiting requested review from mfojtik

@spadgett spadgett Awaiting requested review from spadgett

Assignees

@rphillips rphillips

@dgoodwin dgoodwin

@stbenjam stbenjam

@kasturinarra kasturinarra

@jadhaj jadhaj

@sunilcio sunilcio

@pamoedom pamoedom

@jitendar-singh jitendar-singh

@prietyc123 prietyc123

@gangwgr gangwgr

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet