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.7.3][BUG] Test case test_node_eviction_multiple_volume failed to reschedule replicas after volume detached #9866

Open
github-actions bot opened this issue Nov 27, 2024 · 0 comments
Assignees
Labels
area/volume-replica-scheduling Volume replica scheduling related kind/backport Backport request kind/bug kind/regression Regression which has worked before priority/0 Must be implement or fixed in this release (managed by PO) reproduce/always 100% reproducible severity/1 Function broken (a critical incident with very high impact (ex: data corruption, failed upgrade)
Milestone

Comments

@github-actions
Copy link

backport #9857

@github-actions github-actions bot added area/volume-replica-scheduling Volume replica scheduling related kind/backport Backport request kind/bug kind/regression Regression which has worked before priority/0 Must be implement or fixed in this release (managed by PO) reproduce/always 100% reproducible severity/1 Function broken (a critical incident with very high impact (ex: data corruption, failed upgrade) labels Nov 27, 2024
@github-actions github-actions bot added this to the v1.7.3 milestone Nov 27, 2024
@github-project-automation github-project-automation bot moved this to New Issues in Longhorn Sprint Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/volume-replica-scheduling Volume replica scheduling related kind/backport Backport request kind/bug kind/regression Regression which has worked before priority/0 Must be implement or fixed in this release (managed by PO) reproduce/always 100% reproducible severity/1 Function broken (a critical incident with very high impact (ex: data corruption, failed upgrade)
Projects
Status: New Issues
Development

No branches or pull requests

1 participant