Skip to content

[5.0] nova: Don't retry creating existing flavors#2143

Merged
JanZerebecki merged 1 commit into
crowbar:stable/5.0-pikefrom
skazi0:nova-flavor-existing-8
Jun 3, 2019
Merged

[5.0] nova: Don't retry creating existing flavors#2143
JanZerebecki merged 1 commit into
crowbar:stable/5.0-pikefrom
skazi0:nova-flavor-existing-8

Conversation

@skazi0

@skazi0 skazi0 commented May 30, 2019

Copy link
Copy Markdown
Member

In some cases the flavor create call succeeds but client still returns
non-zero status. Retries of the create call fail with "Flavor already
exists" and the retry loop never succeeds. Added check is executed in
every loop turn and will stop reytring if the flavor already exists.

Example scenario where flavor might be correctly created but client
doesn't return zero is when one of HA nodes executes flavor create
commands while others perform delayed restart of nova API after config
files are modified. If the "create" request hits the API just before
restart it could be accepted but the client might not get the correct
response back.

port of #2142

In some cases the flavor create call succeeds but client still returns
non-zero status. Retries of the create call fail with "Flavor already
exists" and the retry loop never succeeds. Added check is executed in
every loop turn and will stop reytring if the flavor already exists.

Example scenario where flavor might be correctly created but client
doesn't return zero is when one of HA nodes executes flavor create
commands while others perform delayed restart of nova API after config
files are modified. If the "create" request hits the API just before
restart it could be accepted but the client might not get the correct
response back.

(cherry picked from commit 8085fb9)
@nicolasbock

Copy link
Copy Markdown
Contributor

Could you look into the CI failure? Seems a bit strange that it's failing on what looks like an SSL problem?

@skazi0

skazi0 commented May 30, 2019

Copy link
Copy Markdown
Member Author

@nicolasbock this looks like the log quoted by @toabctl here: #2134 (comment)
@toabctl is there some fix for this?

@toabctl

toabctl commented May 31, 2019

Copy link
Copy Markdown
Contributor

@toabctl is there some fix for this?

Nope. #2134 just made the real failure visible.

@nicolasbock

Copy link
Copy Markdown
Contributor

At this point I can't see how the CI failure is related to your change here @skazi0 , but the failure is in Nova and I would feel better if we addressed it before merging your change.

@JanZerebecki JanZerebecki merged commit a9cc7f3 into crowbar:stable/5.0-pike Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

4 participants