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.

Sign up for GitHub

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

Jump to bottom

[BACKPORT][v1.3.3][BUG] Volume metafile getting deleted or empty results in a detach-attach loop #4847

Closed
github-actions bot opened this issue Nov 8, 2022 · 2 comments
Closed

[BACKPORT][v1.3.3][BUG] Volume metafile getting deleted or empty results in a detach-attach loop #4847

github-actions bot opened this issue Nov 8, 2022 · 2 comments
Assignees
@mantissahz @roger-ryao
Labels
area/replica Volume replica where data is placed area/v1-data-engine v1 data engine (iSCSI tgt) kind/backport Backport request kind/bug severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact)
Milestone
v1.3.3

Comments

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

backport #4846
@github-actions github-actions bot added area/v1-data-engine v1 data engine (iSCSI tgt) area/replica Volume replica where data is placed kind/backport Backport request kind/bug severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact) labels Nov 8, 2022
@github-actions github-actions bot added this to the v1.3.3 milestone Nov 8, 2022
@mantissahz mantissahz mentioned this issue Dec 2, 2022
Merged
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Dec 2, 2022 •
edited by mantissahz
Loading

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:
  1. Create a pod using Longhorn volume
  2. Write some data to the volume then get the md5sum
  3. Delete the pod and wait for the volume detached
  4. Randomly pick up replicas and manually delete or empty the volume meta file in this replica data path
  5. Recreate the pod and wait for the volume attached
  6. Check if the volume is Healthy after the volume attached
  7. Check if data is not corrupted
  8. Check if r/w to volume is ok in pod

  • Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
    The PR is at
    [BACKPORT][v1.3.3] fix(replica): volume metafile deleted or empty longhorn-engine#778

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

  • 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)

@roger-ryao
Copy link

Verified on v1.3.x-head 20221209

  • longhorn v1.3.x-head (b2c607d)
  • longhorn-engine v1.3.x-head (0cf6268)

The test steps

Ref #4847 (To Reproduce)

Result Passed

@derekbit derekbit moved this to Closed in Longhorn Sprint Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mantissahz mantissahz

@roger-ryao roger-ryao

Labels
area/replica Volume replica where data is placed area/v1-data-engine v1 data engine (iSCSI tgt) kind/backport Backport request kind/bug severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact)
Projects
Longhorn Sprint
Status: Closed
Milestone
v1.3.3
Development

No branches or pull requests
3 participants
@mantissahz @longhorn-io-github-bot @roger-ryao