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

[TASK] Improve the doc for troubleshooting NFS backuptarget #3825

Closed
derekbit opened this issue Apr 7, 2022 · 3 comments
Closed

[TASK] Improve the doc for troubleshooting NFS backuptarget #3825

derekbit opened this issue Apr 7, 2022 · 3 comments
Assignees
@mantissahz
Labels
kind/doc Doc request kind/task General task request to fulfill another primary request priority/2 Nice to implement or fix in this release (managed by PO) require/doc Require updating the longhorn.io documentation require/knowledge-base Require adding knowledge base document
Milestone
v1.3.0

Comments

@derekbit
Copy link
Member

derekbit commented Apr 7, 2022

What's the task? Please describe

Some users encountered the backup failure while using the NFS backuptarget. We can summarize the troubleshooting tips and solutions for helping users configure the NFS server.

Additional context

#3576
#3805
@derekbit derekbit added the kind/task General task request to fulfill another primary request label Apr 7, 2022
@innobead innobead added this to the v1.3.0 milestone Apr 7, 2022
@innobead innobead added kind/doc Doc request require/doc Require updating the longhorn.io documentation priority/2 Nice to implement or fix in this release (managed by PO) labels Apr 7, 2022
@innobead innobead assigned mantissahz and unassigned derekbit May 13, 2022
@innobead
Copy link
Member

@mantissahz Please help this one. You can check with @derekbit to understand the context and some other reported issues.

@innobead innobead added the require/knowledge-base Require adding knowledge base document label May 24, 2022
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented May 24, 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:
  • 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
  • If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
    The LEP PR is at
  • If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
    The UI issue/PR is at
  • If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
    The documentation issue/PR is at
    Add KB: Troubleshooting: NFS server setting and mount a NFS storage website#503
  • 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 (https://github.com/longhorn/longhorn/issues/new?assignees=&labels=area%2Ftest&template=test.md&title=%5BTEST%5D))
  • If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
    The engine automation PR is at
  • If labeled: require/manual-test-plan Has the manual test plan been documented?
    The updated manual test plan 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

@innobead
Copy link
Member

The doc merged, Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mantissahz mantissahz

Labels
kind/doc Doc request kind/task General task request to fulfill another primary request priority/2 Nice to implement or fix in this release (managed by PO) require/doc Require updating the longhorn.io documentation require/knowledge-base Require adding knowledge base document
Projects
Longhorn Sprint
Status: Closed
Milestone
v1.3.0
Development

No branches or pull requests
4 participants
@innobead @derekbit @mantissahz @longhorn-io-github-bot