8000 [BACKPORT][v1.7.3][BUG] DR volume fails to reattach and faulted after node stop and start during incremental restore · Issue #9803 · longhorn/longhorn · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BACKPORT][v1.7.3][BUG] DR volume fails to reattach and faulted after node stop and start during incremental restore #9803

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

Closed
github-actions bot opened this issue Nov 14, 2024 · 2 comments
Assignees
Labels
area/cli Longhorn CLI area/negative-testing Negative e2e testing in robot area/resilience System or volume resilience area/volume-disaster-recovery Volume DR kind/backport Backport request kind/bug reproduce/rare < 50% reproducible require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/qa-review-coverage Require QA to review coverage
Milestone

Comments

@github-actions
Copy link

backport #9752

@github-actions github-actions bot added area/cli Longhorn CLI area/negative-testing Negative e2e testing in robot area/resilience System or volume resilience area/volume-disaster-recovery Volume DR kind/backport Backport request kind/bug reproduce/rare < 50% reproducible require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/qa-review-coverage Require QA to review coverage labels Nov 14, 2024
@github-actions github-actions bot added this to the v1.7.3 milestone Nov 14, 2024
@github-project-automation github-project-automation bot 8000 moved this to New Issues in Longhorn Sprint Nov 14, 2024
@c3y1huang c3y1huang moved this from New Issues to Implement in Longhorn Sprint Nov 14, 2024
@c3y1huang c3y1huang moved this from Implement to New Issues in Longhorn Sprint Nov 14, 2024
@c3y1huang c3y1huang moved this from New Issues to Review in Longhorn Sprint Nov 28, 2024
@longhorn-io-github-bot
Copy link
Collaborator
longhorn-io-github-bot commented Nov 28, 2024

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

  • Is there a workaround for the issue? If so, where is it documented?
    The workaround is:

    • Scale up the CoreDNS replica count.
  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

  • Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
    The PR is at: feat: check CoreDNS (backport #120) cli#130

  • Which areas/issues this PR might have potential impacts on?
    Area DR volumes, CLI
    Issues

  • If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
    The LEP PR is at

  • If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
    The UI issue/PR is at

  • If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
    The documentation issue/PR is at doc(1.8.0, 1.7.4, 1.6.3): add CoreDNS setup to best practices website#1011

  • If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
    The automation skeleton PR is at
    The automation test case PR is at
    The issue of automation test case implementation is at (please create by the template)

  • If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
    The engine automation PR is at

  • If labeled: require/manual-test-plan Has the manual test plan been documented?
    The updated manual test plan is at

  • If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
    The compatibility issue is filed at

@c3y1huang c3y1huang moved this from Review to Ready For Testing in Longhorn Sprint Nov 28, 2024
@roger-ryao roger-ryao moved this from Ready For Testing to Testing in Longhorn Sprint Dec 5, 2024
@roger-ryao
Copy link

Verified on v1.7.3-dev-20241201 20241205

  • longhorn v1.7.3-dev-20241201 bd3b199

Result Passed

@github-project-automation github-project-automation bot moved this from Testing to Closed in Longhorn Sprint Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli Longhorn CLI area/negative-testing Negative e2e testing in robot area/resilience System or volume resilience area/volume-disaster-recovery Volume DR kind/backport Backport request kind/bug reproduce/rare < 50% reproducible require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/qa-review-coverage Require QA to review coverage
Projects
Status: Closed
Development

No branches or pull requests

3 participants
0