[minor] Add support to upgrade ocs/odf #428
Merged
Conversation
This file contains 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
caroazad
requested review from
durera,
andrercm,
sanjayprab,
terenceq and
whitfiea
as code owners
whitfiea
changed the title
whitfiea
approved these changes
Aug 22, 2023
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.
Added support for ocs/odf upgrade to update pipeline.
Update for ocs/odf is always going to run but if the storage operators are not present, it just displays a message to the user.
Added the ocs role in the dependencies tasks so that the pipeline can call the task to pass in the upgrade action.
Tested - nothing to upgrade (no storage operators in the cluster and up-to-date operator) - passed
Tested - odf 4.11 to odf 4.12
Since ansible devops included some intensive testing. I think this is enough verification.
FYI I also encountered a little struggle where my changes were not reflecting in the cluster. It was very devastating. I had to keep making changes thinking that the previous ones were wrong. It got to a time that I just couldn't believe that the piece of code would behave that way so I restarted the cluster and got passed the issue. This is just in case, anyone notices those odd repeating commits below.