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(system-backup): wait for last backup of volume updated #2221

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mantissahz
Copy link
Contributor

@mantissahz mantissahz commented Dec 23, 2024

Which issue(s) this PR fixes:

Issue #

What this PR does / why we need it:

Modify the test case:

  • test_system_backup_with_volume_backup_policy_if_not_present

to wait for the last backup of the volume to be updated when creating the first backup.

Special notes for your reviewer:

Additional documentation or context

https://ci.longhorn.io/job/private/job/longhorn-tests-regression/7935/
re-run: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/7945/

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Enhanced backup verification process to ensure immediate validation of the last backup after creation.
  • Bug Fixes

    • Improved logic for system backup creation and volume backup checking.

@mantissahz mantissahz self-assigned this Dec 23, 2024
@mantissahz mantissahz requested a review from a team as a code owner December 23, 2024 03:53
Copy link

coderabbitai bot commented Dec 23, 2024

Walkthrough

The pull request introduces modifications to the system backup restoration test within the integration test suite. It adds an import statement for check_volume_last_backup from the common module and updates the test_system_backup_with_volume_backup_policy_if_not_present function. The changes ensure that the backup volume is captured after the first system backup is created and that the last backup name is immediately verified, enhancing the validation of the backup state.

Changes

File Change Summary
manager/integration/tests/test_system_backup_restore.py Added import for check_volume_last_backup and modified the test function to capture the backup volume and verify the last backup name.

Possibly related PRs

Suggested reviewers

  • yangchiu
  • c3y1huang

Poem

🐰 A Backup Bunny's Ballad 🔍

In tests of system's backup might,
A rabbit checks with keen delight,
Volumes saved with careful care,
Ensuring data's journey rare,
With checks that sparkle, clean and bright!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c69f835 and f857ed8.

📒 Files selected for processing (1)
  • manager/integration/tests/test_system_backup_restore.py (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • manager/integration/tests/test_system_backup_restore.py

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

return backup_volume

bv = create_system_backup_and_assert_volume_backup_count(1)
check_volume_last_backup(client, volume_name, bv.lastBackupName)
Copy link
Member

Choose a reason for hiding this comment

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

Do you think it would make sense to move check_volume_last_backup into create_system_backup_and_assert_volume_backup_count?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it could be moved into the create_system_backup_and_assert_volume_backup_count, and I will have an update soon. Thanks.

Modify the test case:
- `test_system_backup_with_volume_backup_policy_if_not_present`

to wait for the last backup of the volume updated when creating
the first backup.

Signed-off-by: James Lu <jamesluhz@gmail.com>
@derekbit derekbit force-pushed the fix-test-sb-vol-backup-if-not-present branch from c69f835 to f857ed8 Compare December 27, 2024 12:11
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