[patch] Fix issue with latest grafana-operator#2148
Merged
Conversation
sanjayprab
approved these changes
Mar 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The latest grafana-operator can't be installed on OCP 4.18 or earlier due to grafana/grafana-operator#2552 and is breaking the MAS pipeline.
This change along with ibm-mas/python-devops#206 allows the ansible-devops role to apply a subscription with manual approval and to stick at one csv level. This mechanism should only be used in the cases were we can not fix the operator/subscription ourself. There is also a change to verify_subscription as the subscription will be in an UpgradePending state. The verify_subscription role will now accept this state if the approval plan is manual.
See ibm-mas/python-devops#206 for other details, and this must be merged in before this change.
Test Results
Tested locally by using the ansible-devops and also in the fvt-personal when combined with the other roles: