Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ec_deployment: Set snapshot restore strategy to partial on Update #309

Conversation

marclop
Copy link
Contributor

@marclop marclop commented May 6, 2021

Description

Fixes a bug where the strategy field wasn't set on either of the create
or update operations and it made restoring a snapshot on an existing
deployment impossible since when transient.snapshot_restore.strategy
isn't set, the API will make it default to "full", which isn't a valid
restoration strategy for snapshots when a deployment has already been
created and it's running, for the operation to succeed, "partial" must
be used.

Related Issues

Closes #249

How Has This Been Tested?

Manual, unit and acceptance tested.

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)

@marclop marclop added bug Something isn't working Team:Delivery labels May 6, 2021
@marclop marclop requested a review from a team as a code owner May 6, 2021 09:47
@marclop marclop self-assigned this May 6, 2021
@marclop marclop changed the title ec_deployment: Set partial strategy on Update ec_deployment: Set snapshot restore strategy to partial on Update May 6, 2021
Copy link

@Aran-K Aran-K left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was going to comment on the test failures and then I saw

11:01:46      testing_new.go:63: Error running post-test destroy, there may be dangling resources: exit status 1
11:01:46          
11:01:46          Error: found deployment plan errors: 1 error occurred:
11:01:46          	* deployment [723e46e3851ddc29d23660da8d03c4c2] - [elasticsearch][f2435f44614342f28023463f313df44e]: caught error: "Plan change failed: Timeout exceeded. Please adjust plan timeout and/or retry plan."

😅

Overall LGTM :shipit:

marclop added 3 commits May 12, 2021 16:35
Fixes a bug where the strategy field wasn't set on either of the create
or update operations and it made restoring a snapshot on an existing
deployment impossible since when `transient.snapshot_restore.strategy`
isn't set, the API will make it default to "full", which isn't a valid
restoration strategy for snapshots when a deployment has already been
created and it's running, for the operation to succeed, "partial" must
be used.

Signed-off-by: Marc Lopez <[email protected]>
Signed-off-by: Marc Lopez <[email protected]>
Signed-off-by: Marc Lopez <[email protected]>
@marclop marclop force-pushed the b/set-partial-snapshot-strategy-when-cluster-is-created branch from d30bd00 to 9f2da50 Compare May 12, 2021 11:35
@marclop marclop requested a review from Aran-K May 13, 2021 05:00
@marclop marclop merged commit 65e381c into elastic:master May 13, 2021
@marclop marclop deleted the b/set-partial-snapshot-strategy-when-cluster-is-created branch May 13, 2021 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Failed to restore a snapshot from different deployment
2 participants