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

fix(backup): set backup error if backup target invalid (backport #2086) #2091

Merged
merged 1 commit into from
Jul 27, 2023

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 27, 2023

This is an automatic backport of pull request #2086 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

When starting a backup monitor, it will start to take a snapshot
backup procedure and it will be failed if the s3 backup target is
invalid (nfs backup target will be not be failed because of timeout
and test the backup when it is in progress.)
Set the backup state as `Error` if starting the backup procedure
returns an error.

Ref: 1249

Signed-off-by: James Lu <james.lu@suse.com>
(cherry picked from commit e278ba0)
@innobead innobead merged commit 57839ae into v1.4.x Jul 27, 2023
4 checks passed
@innobead innobead deleted the mergify/bp/v1.4.x/pr-2086 branch July 27, 2023 15:51
@mantissahz
Copy link
Contributor

ref: longhorn/longhorn#6402

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants