Skip to content

OCPBUGS-20254: [release-4.14] Revert Kuryr MTU fixes#2046

Merged
openshift-ci[bot] merged 1 commit intoopenshift:release-4.14from
openshift-cherrypick-robot:cherry-pick-2038-to-release-4.14
Oct 9, 2023
Merged

OCPBUGS-20254: [release-4.14] Revert Kuryr MTU fixes#2046
openshift-ci[bot] merged 1 commit intoopenshift:release-4.14from
openshift-cherrypick-robot:cherry-pick-2038-to-release-4.14

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #2038

/assign dulek

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 4, 2023

/test e2e-openstack-kuryr

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 4, 2023

/retest-required

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 4, 2023

/retitle OCPBUGS-20088: [release-4.14] Revert Kuryr MTU fixes

@openshift-ci openshift-ci Bot changed the title [release-4.14] Revert Kuryr MTU fixes OCPBUGS-20088: [release-4.14] Revert Kuryr MTU fixes Oct 4, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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 Oct 4, 2023
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-20087 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-20087 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

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

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 #2038

/assign dulek

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-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-20088, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-20087 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-20087 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

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

Details

In response to this:

This is an automated cherry-pick of #2038

/assign dulek

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.

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 4, 2023

/lgtm

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 4, 2023

/label backport-risk-assessed

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 4, 2023

@dulek: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

Details

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

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 4, 2023
@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 4, 2023

/retest-required

@MaysaMacedo
Copy link
Copy Markdown
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 4, 2023
@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 6, 2023
@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 6, 2023

/assign @dcbw

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 6, 2023

@dulek: GitHub didn't allow me to assign the following users: dcbw.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @dcbw

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.

@dulek dulek removed their assignment Oct 6, 2023
@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 6, 2023

/assign @danwinship

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 9, 2023

/retest-required
/retitle OCPBUGS-19377: [release-4.14] Revert Kuryr MTU fixes

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 9, 2023

/retitle OCPBUGS-20254: [release-4.14] Revert Kuryr MTU fixes

@openshift-ci openshift-ci Bot changed the title OCPBUGS-20088: [release-4.14] Revert Kuryr MTU fixes OCPBUGS-19377: [release-4.14] Revert Kuryr MTU fixes Oct 9, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 9, 2023
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

  • expected the bug to target the "4.14.0" version, but it targets "4.15.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
  • expected Jira Issue OCPBUGS-19377 to depend on a bug targeting a version in 4.15.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

Details

In response to this:

This is an automated cherry-pick of #2038

/assign dulek

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-ci openshift-ci Bot changed the title OCPBUGS-19377: [release-4.14] Revert Kuryr MTU fixes OCPBUGS-20254: [release-4.14] Revert Kuryr MTU fixes Oct 9, 2023
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

  • expected Jira Issue OCPBUGS-20254 to depend on a bug targeting a version in 4.15.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

Details

In response to this:

This is an automated cherry-pick of #2038

/assign dulek

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.

@dulek
Copy link
Copy Markdown
Contributor

dulek commented Oct 9, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 9, 2023
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-19377 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-19377 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

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

Details

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

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 9, 2023
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-20254, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-19377 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-19377 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

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

Details

In response to this:

This is an automated cherry-pick of #2038

/assign dulek

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.

@dcbw
Copy link
Copy Markdown
Contributor

dcbw commented Oct 9, 2023

/override ci/prow/e2e-metal-ipi-ovn-ipv6
/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 9, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dcbw, dulek, openshift-cherrypick-robot

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 9, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 9, 2023

@dcbw: Overrode contexts on behalf of dcbw: ci/prow/e2e-metal-ipi-ovn-ipv6

Details

In response to this:

/override ci/prow/e2e-metal-ipi-ovn-ipv6
/approve

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-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD a936ce4 and 2 for PR HEAD 4d4c51a in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 9, 2023

@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-metal-ipi-ovn-ipv6-ipsec 4d4c51a link false /test e2e-metal-ipi-ovn-ipv6-ipsec
ci/prow/e2e-aws-ovn-serial 4d4c51a link false /test e2e-aws-ovn-serial
ci/prow/e2e-aws-hypershift-ovn-kubevirt 4d4c51a link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration-periodic 4d4c51a link false /test e2e-aws-ovn-shared-to-local-gateway-mode-migration-periodic
ci/prow/e2e-ovn-step-registry 4d4c51a link false /test e2e-ovn-step-registry
ci/prow/e2e-azure-ovn 4d4c51a link false /test e2e-azure-ovn
ci/prow/e2e-ovn-hybrid-step-registry 4d4c51a link false /test e2e-ovn-hybrid-step-registry
ci/prow/e2e-vsphere-ovn 4d4c51a link false /test e2e-vsphere-ovn
ci/prow/e2e-network-mtu-migration-ovn-ipv6 4d4c51a link false /test e2e-network-mtu-migration-ovn-ipv6
ci/prow/e2e-openstack-ovn 4d4c51a link false /test e2e-openstack-ovn
ci/prow/e2e-openstack-sdn 4d4c51a link false /test e2e-openstack-sdn
ci/prow/e2e-network-mtu-migration-sdn-ipv4 4d4c51a link false /test e2e-network-mtu-migration-sdn-ipv4
ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration 4d4c51a link false /test e2e-aws-ovn-local-to-shared-gateway-mode-migration
ci/prow/e2e-vsphere-ovn-dualstack 4d4c51a link false /test e2e-vsphere-ovn-dualstack
ci/prow/e2e-openstack-kuryr 4d4c51a link false /test e2e-openstack-kuryr
ci/prow/e2e-metal-ipi-ovn-ipv6 4d4c51a link true /test e2e-metal-ipi-ovn-ipv6

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

@openshift-ci openshift-ci Bot merged commit ed997d2 into openshift:release-4.14 Oct 9, 2023
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

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

Details

In response to this:

This is an automated cherry-pick of #2038

/assign dulek

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
Copy Markdown
Contributor

Fix included in accepted release 4.14.0-0.nightly-2023-10-10-084534

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

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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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

Development

Successfully merging this pull request may close these issues.