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] Volume cannot attach because of the leftover non-empty volume.status.PendingNodeID after upgrading Longhorn #7996

Closed
github-actions bot opened this issue Feb 22, 2024 · 2 comments
Assignees
Labels
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
Milestone

Comments

@github-actions
Copy link

backport #7994

@github-actions github-actions bot added 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 Feb 22, 2024
@github-actions github-actions bot added this to the v1.5.5 milestone Feb 22, 2024
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Mar 6, 2024

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at: See base issue [BUG] Volume cannot attach because of the leftover non-empty volume.status.PendingNodeID after upgrading Longhorn #7994.

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

  • 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

  • Which areas/issues this PR might have potential impacts on?
    Area
    Issues

@james-munson james-munson self-assigned this Mar 19, 2024
@roger-ryao roger-ryao self-assigned this Mar 26, 2024
@roger-ryao
Copy link

Verified on v1.5.x-head 20240326

The test steps

#7994 (comment)

Result Passed

  1. After upgrading from v1.4.4 to v1.5.x-head, the volume can be attached successfully, and the data is consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Projects
None yet
Development

No branches or pull requests

3 participants