OPRUN-3267: blocked-edges/4.15.10-OLMOperatorsInFailedState: Fixed in 4.15.11#5170
Conversation
[1] includes [2]. In cb0259d (blocked-edges/4.15.10-OLMOperatorsInFailedState: Not fixed yet, 2024-04-18, openshift#5132), I'd also thought [3] might be relevant, but it turns out it isn't [4]. [1]: https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4.15.11 [2]: https://issues.redhat.com/browse/OCPBUGS-32311 [3]: https://issues.redhat.com/browse/OCPBUGS-32439 [4]: https://issues.redhat.com/browse/OCPBUGS-32439?focusedId=24599986&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-24599986
openshift-ci-robot
added
the
jira/valid-reference
|
@wking: This pull request references OPRUN-3267 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
Self-LGTM; everyone else is already weekending |
2 participants
4.15.11 includes OCPBUGS-32311. In cb0259d (#5132), I'd also thought OCPBUGS-32439 might be relevant, but it turns out it isn't.