[4.0] magnum: retry magnum image creation (SOC-10015)#2181
Merged
Conversation
Creating the magnum image is done as a delayed action, alongside all other delayed actions, such as restarting services. If one of those restarted services is apache (e.g. because it was triggered by another barclamp configuration change), then keystone and other API services might not be available right away, in which case the magnum image creation will fail. Re-attempting magnum image creation fixes this issue.
stefannica
changed the title
rsalevsky
approved these changes
Jul 30, 2019
gosipyan
approved these changes
Jul 30, 2019
sayalilunkad
approved these changes
Jul 31, 2019
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
4 participants
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.
Creating the magnum image is done as a delayed action, alongside
all other delayed actions, such as restarting services.
If one of those restarted services is apache (e.g. because it
was triggered by another barclamp configuration change), then
keystone and other API services might not be available right
away, in which case the magnum image creation will fail.
Re-attempting magnum image creation fixes this issue.
NOTE: this is a follow-up to #2179