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.2] [ENHANCEMENT] Take advantage of the attach/detach mechanism in Longhorn v1.5+ #5853

Open
harvesterhci-io-github-bot opened this issue May 23, 2024 · 1 comment
Assignees
Labels
area/longhorn issues depends on the upstream longhorn kind/enhancement Issues that improve or augment existing functionality not-require/test-plan Skip to create a e2e automation test issue priority/0 Must be fixed in this release
Milestone

Comments

@harvesterhci-io-github-bot

backport the issue #4907

@harvesterhci-io-github-bot
Copy link
Author

harvesterhci-io-github-bot commented May 23, 2024

Pre Ready-For-Testing Checklist

  • If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at: refactor: remove mount logic in harvester #4910

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

  • Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
    The PR is at: refactor: remove mount logic in harvester (backport #4910) #5854

  • If labeled: area/ui Has the UI issue filed or ready to be merged?

  • If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?

  • If NOT labeled: not-require/test-plan Has the e2e 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?

    • The automation skeleton PR is at:
    • The automation test case PR 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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/longhorn issues depends on the upstream longhorn kind/enhancement Issues that improve or augment existing functionality not-require/test-plan Skip to create a e2e automation test issue priority/0 Must be fixed in this release
Projects
None yet
Development

No branches or pull requests

3 participants