Closed kevinrizza closed 8 months ago
@kevinrizza: This pull request references Jira Issue OCPBUGS-28597, which is valid.
Requesting review from QA contact: /cc @jianzhangbjz
The bug has been updated to refer to the pull request using the external bug tracker.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: grokspawn, kevinrizza
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest-required
Remaining retests: 0 against base HEAD 4929daf2587e2e22159d7971cd3bde993b60c036 and 2 for PR HEAD 7fcd70bd9735663b22b3f5c6c3ac4801c1d8c301 in total
/label qe-approved
@kevinrizza: This pull request references Jira Issue OCPBUGS-28597, which is valid.
Requesting review from QA contact: /cc @kuiwang02
/label qe-approved cancel
/remove-label qe-approved
wait @jianzhangbjz to add qe-approved
/retest
/retest
this looks like cluster init problems. trying again.
/retest
@kevinrizza: all tests passed!
Full PR test history. Your PR dashboard.
@kevinrizza: Jira Issue OCPBUGS-28597: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-28597 has been moved to the MODIFIED state.
[ART PR BUILD NOTIFIER]
This PR has been included in build ose-cluster-olm-operator-container-v4.16.0-202402010042.p0.g8b0539d.assembly.stream for distgit ose-cluster-olm-operator. All builds following this will include this PR.
Temporarily disable this component while upgrading rukpak with a breaking change