Closed dmage closed 1 year ago
@dmage: 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
.
/assign @flavianmissi
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dmage, flavianmissi
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/jira refresh
@flavianmissi: This pull request references Jira Issue OCPBUGS-4678, 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
@flavianmissi: This pull request references Jira Issue OCPBUGS-4678, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @xiuwang
/retest
@dmage: all tests passed!
Full PR test history. Your PR dashboard.
/label backport-risk-assessed
@flavianmissi: Can not set label backport-risk-assessed: Must be member in one of these teams: []
/label backport-risk-assessed
/label qe-approved /label cherry-pick-approved
/label backport-risk-assessed
/hold let's aim for 4.12.1
/hold cancel
@dmage: Some pull requests linked via external trackers have merged:
The following pull requests linked via external trackers have not merged:
These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh
.
Jira Issue OCPBUGS-4678 has not been moved to the MODIFIED state.
@dmage: This pull request references Jira Issue OCPBUGS-4678, 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.