Skip to content

[release-4.17] USHIFT-4878: Add support for low-latency feature#4170

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.17from
openshift-cherrypick-robot:cherry-pick-3769-to-release-4.17
Nov 12, 2024
Merged

[release-4.17] USHIFT-4878: Add support for low-latency feature#4170
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.17from
openshift-cherrypick-robot:cherry-pick-3769-to-release-4.17

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #3769

/assign agullon

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 12, 2024

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-2987

Details

In response to this:

This is an automated cherry-pick of #3769

/assign agullon

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 openshift-ci bot requested review from copejon and ggiguash November 12, 2024 09:02
@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 12, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, 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 Nov 12, 2024
@agullon
Copy link
Contributor

agullon commented Nov 12, 2024

/test microshift-metal-tests-arm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2024

@openshift-cherrypick-robot: all tests passed!

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

@pacevedom
Copy link
Contributor

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

@openshift-ci openshift-ci bot added 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. labels Nov 12, 2024
@agullon
Copy link
Contributor

agullon commented Nov 12, 2024

/retitle

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2024

@agullon: Titles may not be empty.

Details

In response to this:

/retitle

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.

@agullon
Copy link
Contributor

agullon commented Nov 12, 2024

/retitle [release-4.17] USHIFT-4878: Add support for low-latency feature

@openshift-ci openshift-ci bot changed the title [release-4.17] USHIFT-2987: Add support for low-latency feature [release-4.17] USHIFT-4878: Add support for low-latency feature Nov 12, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 12, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 12, 2024

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

Details

In response to this:

This is an automated cherry-pick of #3769

/assign agullon

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.

@agullon
Copy link
Contributor

agullon commented Nov 12, 2024

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 12, 2024

@agullon: This pull request references USHIFT-4878 which is a valid jira issue.

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

@pacevedom
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 12, 2024

@pacevedom: This pull request references USHIFT-4878 which is a valid jira issue.

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

@pacevedom
Copy link
Contributor

/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 12, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit f85833b into openshift:release-4.17 Nov 12, 2024
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/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.

5 participants