Closed zeeke closed 4 months ago
/jira cherrypick OCPBUGS-36734
@zeeke: Jira Issue OCPBUGS-36734 has been cloned as Jira Issue OCPBUGS-36753. Will retitle bug to link to clone. /retitle OCPBUGS-36753: [release-4.14] Critical Bugs
/jira cherrypick OCPBUGS-36733
@zeeke: Jira Issue OCPBUGS-36733 has been cloned as Jira Issue OCPBUGS-36754. Will retitle bug to link to clone. /retitle OCPBUGS-36754: [release-4.14] Critical Bugs
/jira cherrypick OCPBUGS-36731
@zeeke: This pull request references Jira Issue OCPBUGS-36753, 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.
@zeeke: Jira Issue OCPBUGS-36731 has been cloned as Jira Issue OCPBUGS-36755. Will retitle bug to link to clone. /retitle OCPBUGS-36755: OCPBUGS-36753: [release-4.14] Critical Bugs
/jira cherrypick OCPBUGS-36730
@zeeke: This pull request references Jira Issue OCPBUGS-36754, 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.
@zeeke: This pull request references Jira Issue OCPBUGS-36755, 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.
@zeeke: Jira Issue OCPBUGS-36730 has been cloned as Jira Issue OCPBUGS-36756. Will retitle bug to link to clone. /retitle OCPBUGS-36756: OCPBUGS-36754: [release-4.14] Critical Bugs
@zeeke: This pull request references Jira Issue OCPBUGS-36756, 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.
/retitle OCPBUGS-36753,OCPBUGS-36754,OCPBUGS-36755OCPBUGS-36756: [release-4.14] Critical Bugs
@zeeke: This pull request references Jira Issue OCPBUGS-36753, 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.
This pull request references Jira Issue OCPBUGS-36754, 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.
This pull request references Jira Issue OCPBUGS-36755, 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.
This pull request references Jira Issue OCPBUGS-36756, 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.
@zeeke: all tests passed!
Full PR test history. Your PR dashboard.
@zeeke: This pull request references Jira Issue OCPBUGS-36753, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @zhaozhanqi
This pull request references Jira Issue OCPBUGS-36754, 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.
This pull request references Jira Issue OCPBUGS-36755, 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.
This pull request references Jira Issue OCPBUGS-36756, 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.
/jira refresh
@zeeke: This pull request references Jira Issue OCPBUGS-36753, which is valid.
Requesting review from QA contact: /cc @zhaozhanqi
This pull request references Jira Issue OCPBUGS-36754, 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.
This pull request references Jira Issue OCPBUGS-36755, 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.
This pull request references Jira Issue OCPBUGS-36756, 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.
/jira refresh
@zeeke: This pull request references Jira Issue OCPBUGS-36753, which is valid.
Requesting review from QA contact: /cc @zhaozhanqi
This pull request references Jira Issue OCPBUGS-36754, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @zhaozhanqi
This pull request references Jira Issue OCPBUGS-36755, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @zhaozhanqi
This pull request references Jira Issue OCPBUGS-36756, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @zhaozhanqi
@SchSeba , @evgenLevin, @wizhaoredhat , @ajaggapa
Please take a look and put labels if it looks good
/lgtm /approve /label backport-risk-assessed
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: SchSeba, wizhaoredhat, zeeke
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/label cherry-pick-approved
@zeeke: Jira Issue OCPBUGS-36753: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-36753 has been moved to the MODIFIED state.
Jira Issue OCPBUGS-36754: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-36754 has been moved to the MODIFIED state.
Jira Issue OCPBUGS-36755: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-36755 has been moved to the MODIFIED state.
Jira Issue OCPBUGS-36756: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-36756 has been moved to the MODIFIED state.
[ART PR BUILD NOTIFIER]
This PR has been included in build sriov-network-webhook-container-v4.14.0-202407100810.p0.g9e7bc3a.assembly.stream.el8 for distgit sriov-network-webhook. All builds following this will include this PR.
4.14 backport of:
cc @SchSeba, @mlguerrero12
ref: