OPRUN-3267: blocked-edges/4.15.10-OLMOperatorsInFailedState: Not fixed yet #5132
Conversation
I'm a bit confused by the current state of [1]. I see: * olm#736 [2], although that seems to have just-missed 4.15.10 [3]. * olm#738 [4], which is still in flight. I'm not sure if we're waiting for both or not, but either way, 4.15.10 doesn't have what we need, so I'm extending that risk here. [1]: https://issues.redhat.com/browse/OPRUN-3267 [2]: https://issues.redhat.com/browse/OCPBUGS-32311 [3]: https://amd64.ocp.releases.ci.openshift.org/releasestream/4.15.0-0.nightly/release/4.15.0-0.nightly-2024-04-19-015656?from=4.15.10 [4]: https://issues.redhat.com/browse/OCPBUGS-32439
|
@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. In 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. |
openshift-ci-robot
added
the
jira/valid-reference
|
[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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
openshift-merge-bot
bot
merged commit 8a78c5b
into
openshift:master
[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
I'm a bit confused by the current state of OPRUN-3267. I see:
I'm not sure if we're waiting for both or not, but either way, 4.15.10 doesn't have what we need, so I'm extending that risk here.