Closed jrvaldes closed 9 months ago
@jrvaldes: This pull request references Jira Issue OCPBUGS-24523, 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.
/jira refresh
@jrvaldes: This pull request references Jira Issue OCPBUGS-24523, 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
@jrvaldes: This pull request references Jira Issue OCPBUGS-24523, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @rrasouli
@jrvaldes: all tests passed!
Full PR test history. Your PR dashboard.
/lgtm
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jrvaldes, rrasouli, sferich888
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/label backport-risk-assessed
@jrvaldes: Can not set label backport-risk-assessed: Must be member in one of these teams: []
@sferich888 could you help with /label backport-risk-assessed
?
@sferich888 could you help with /label backport-risk-assessed
?
cc @RickJWagner
/label backport-risk-assessed
/label cherry-pick-approved
@jrvaldes: Can not set label cherry-pick-approved: Must be member in one of these teams: []
/label cherry-pick-approved
@rrasouli: Can not set label cherry-pick-approved: Must be member in one of these teams: []
@sferich888 I think this PR falls under the Backports Approvals in Repositories Where QE Does Not Verify Changes category.
Could you also help with /label cherry-pick-approved
?
cc @RickJWagner
@sferich888 @RickJWagner Following up on the request for /label cherry-pick-approved
. We'd like to get this bug closed out this sprint and only have a few days left.
/label cherry-pick-approved
@sferich888: Can not set label cherry-pick-approved: Must be member in one of these teams: []
Based on this list the following users should be able to add the required cherry-pick-approved label. @kasturinarra @lihongan @zhouying7780 @xingxingxia
Also, it appears the repo is configured to add the cherry-pick-approved label when the backport-risk-assessed label is applied, however that didn't happen.
Any help in untangling this situation is greatly appreciated.
Based on this list the following users should be able to add the required cherry-pick-approved label. @kasturinarra @lihongan @zhouying7780 @xingxingxia
Also, it appears the repo is configured to add the cherry-pick-approved label when the backport-risk-assessed label is applied, however that didn't happen.
Any help in untangling this situation is greatly appreciated.
sorry about that, adding it now.
/label cherry-pick-approved
/label cherry-pick-approved
@rrasouli since this is a backport and if you are unable to set the cherry-pick-approved label please help check the file here https://github.com/openshift/release/blob/master/core-services/prow/02_config/openshift/must-gather/_pluginconfig.yaml#L11-L18 (similar file is present for all openshift components, thanks !!) and do a @ on us so that we can add the same.
@jrvaldes: Jira Issue OCPBUGS-24523: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-24523 has been moved to the MODIFIED state.
[ART PR BUILD NOTIFIER]
This PR has been included in build ose-must-gather-container-v4.12.0-202401311148.p0.gdc23fd8.assembly.stream for distgit ose-must-gather. All builds following this will include this PR.
Fix included in accepted release 4.12.0-0.nightly-2024-01-31-124257
This is a manual cherry-pick of https://github.com/openshift/must-gather/pull/374