Closed openshift-cherrypick-robot closed 1 year ago
@openshift-cherrypick-robot: Jira Issue OCPBUGS-11329 has been cloned as Jira Issue OCPBUGS-11348. Will retitle bug to link to clone.
Jira Issue OCPBUGS-11330 has been cloned as Jira Issue OCPBUGS-11349. Will retitle bug to link to clone.
Jira Issue OCPBUGS-11331 has been cloned as Jira Issue OCPBUGS-11350. Will retitle bug to link to clone. /retitle [release-4.12] OCPBUGS-11348,OCPBUGS-11349,OCPBUGS-11350: Various issues
@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh
.
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-11348, 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-11349, 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-11350, 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.
/approve /label backport-risk-assessed /label cherry-pick-approved /lgtm /cherry-pick release-4.11
@coreydaley: once the present PR merges, I will cherry-pick it on top of release-4.11 in a new PR and assign it to you.
/hold Until I fix the plugin updates for the previous versions.
@openshift-cherrypick-robot: all tests passed!
Full PR test history. Your PR dashboard.
/jira refresh
@coreydaley: This pull request references Jira Issue OCPBUGS-11348, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @coreydaley
This pull request references Jira Issue OCPBUGS-11349, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @coreydaley
This pull request references Jira Issue OCPBUGS-11350, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @coreydaley
/hold cancel /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: coreydaley, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/label qa-approved
@coreydaley: The label(s) /label qa-approved
cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved
. Is this label configured under labels -> additional_labels
or labels -> restricted_labels
in plugin.yaml
?
/label qe-approved
@openshift-cherrypick-robot: Jira Issue OCPBUGS-11348: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-11348 has been moved to the MODIFIED state.
Jira Issue OCPBUGS-11349: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-11349 has been moved to the MODIFIED state.
Jira Issue OCPBUGS-11350: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-11350 has been moved to the MODIFIED state.
@coreydaley: new pull request created: #1657
This is an automated cherry-pick of #1651
/assign coreydaley