Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We could confirm in more than one test PR that these changes are causing issues in downstream.
The jobs do not pass even after fixing the dependency issue (see: openshift/operator-framework-olm#1125) until we revert those commits.
The errors observed are similar to:
Example: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_oper[…]perator-framework-olm-main-e2e-gcp-ovn/1980948158116532224
In order to isolate the issues and unblock the downstream sync, I propose reverting the commits that we’ve confirmed are breaking downstream. Once the sync is fixed and stable, we can reintroduce those commits with the necessary adjustments.
Example of places that we could prove it: