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

[BACKPORT][v1.5.5][BUG] Replica rebuild failed #8257

Closed
github-actions bot opened this issue Mar 27, 2024 · 2 comments
Closed

[BACKPORT][v1.5.5][BUG] Replica rebuild failed #8257

github-actions bot opened this issue Mar 27, 2024 · 2 comments
Assignees
Labels
area/resilience System or volume resilience kind/backport Backport request kind/bug require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage
Milestone

Comments

@github-actions
Copy link

backport #8091

@github-actions github-actions bot added area/resilience System or volume resilience kind/backport Backport request kind/bug require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage labels Mar 27, 2024
@github-actions github-actions bot added this to the v1.5.5 milestone Mar 27, 2024
@chriscchien
Copy link
Contributor

Verified pass on longhorn v1.5.x (longhorn-instance-manager e63d8e)

  1. Following the manual test plan, volume can be reattached.
    1. Create and attach a v1 volume
    2. Enter into the instance manager pod the volume engine resides on
    3. Detach the volume and suspend the instance manager process kill -STOP <instance manager process PID> simultaneously.
    4. Wait for at least 30s. The volume should get stuck in detaching state.
    5. Resume the process kill -CONT <instance manager process PID>
    6. Check if the volume will be detached.
    7. Check if the volume can be reattached.
  2. Did not observe outstanging error on v1.5.x daily regression result.

@khushboo-rancher
Copy link
Contributor

@chriscchien Do we have this test case automated? If not, could you help adding this test case?

@chriscchien chriscchien added the require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/resilience System or volume resilience kind/backport Backport request kind/bug require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage
Projects
None yet
Development

No branches or pull requests

3 participants