Run ceph update if part of the deployment #2349
Draft
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.
In case we perform a minor update job where
Ceph
is deployed, as part of the minor update procedure we might want to updateCeph
(according to a givencontainer image tag
) to verify the combination between the target Ceph version and the target OpenStack version is still healthy. This patch introduces the tasks that are supposed to call theCeph
update before OpenStack:Ceph
clusterceph_update
variable is passed or it is set to false--skip-tags ceph_update
to the playbookBy doing this we have the ability to trigger a Ceph update and make sure we continue to test the combination between the two projects, but at the same time we are not introducing an hard dependency as it can easily be skipped.
Jira: https://issues.redhat.com/browse/OSPRH-9697