Avoid running drivegroup based osd deployment post-upgrade #1625
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
|
@susebot run teuthology |
|
Commit df09bcb is NOT OK for suite deepsea:tier2. |
jan--f
approved these changes
Apr 24, 2019
In a post-upgrade scenario the user still has old-style profiles defined in the pillar. Since we don't force the user to move to the new drive-group implementation right after the upgrade, we have to detect that they are running in 'legacy' mode and stop.
jschmid1
force-pushed
the
wip-post-upgrade-deploy
branch
from
df09bcb to
21cdcef
Compare
I added a placeholder for future references.. Only telling users to remove the profile line from the policy will probably result in a mess. We have to have a proper document ready that describes the profiles -> drive-group migration process |
|
@susebot run teuthology |
|
Commit 21cdcef is OK for suite deepsea:tier2. |
|
From here: #1629 |
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.
In a post-upgrade scenario the user still has old-style profiles defined in the
pillar.
Since we don't force the user to move to the new drive-group implementation
right after the upgrade, we have to detect that they are running in 'legacy'
mode and stop.
Fixes #
Description:
Checklist: