8000 [BACKPORT][v1.7.3][BUG] Failed to inspect the backup backing image information if NFS backup target URL with options · Issue #9703 · longhorn/longhorn · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BACKPORT][v1.7.3][BUG] Failed to inspect the backup backing image information if NFS backup target URL with options #9703

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

Closed
github-actions bot opened this issue Oct 24, 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 #9702

@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 Oct 24, 2024
@github-actions github-actions bot added this to the v1.7.3 milestone Oct 24, 2024
@github-project-automation github-project-automation bot moved this to New Issues in Longhorn Sprint Oct 24, 2024
@mantissahz mantissahz moved this from New Issues to Review in Longhorn Sprint Oct 28, 2024
@longhorn-io-github-bot
Copy link
Collaborator
longhorn-io-github-bot commented Oct 28, 2024
8000

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:
  1. Set up a NFS server
  2. Set up the backup target URL with NFS options as nfs://longhorn-test-nfs-svc.default:/opt/backupstore?nfsOptions=soft,timeo=330,retrans=3
  3. Back up a backing image.
  4. Check if the backup backing image information is synchronized from the remote backup target.
  • Is there a workaround for the issue? If so, where is it documented?
    The workaround is at:

Temporarily change the backup target URL to the one without the NFS options as
nfs://longhorn-test-nfs-svc.default:/opt/backupstore?nfsOptions=soft,timeo=330,retrans=3
to
nfs://longhorn-test-nfs-svc.default:/opt/backupstore

  • 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
    fix(deps): update patch digest dependencies (v1.7.x) longhorn-manager#3239

  • 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

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

  • 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

@mantissahz mantissahz moved this from Review to Ready For Testing in Longhorn Sprint Oct 28, 2024
@yangchiu
Copy link
Member
yangchiu commented Nov 4, 2024

Verification passed on v1.7.x-head (longhorn-manager bdf5da8) following the test plan.

$ kubectl get backupbackingimages.longhorn.io -n longhorn-system
NAME     BACKINGIMAGE   SIZE      BACKUPCREATEDAT        STATE       LASTSYNCEDAT
test-1   test-1         1161728   2024-11-04T02:53:56Z   Completed   2024-11-04T03:19:04Z
test-2   test-2         1161728   2024-11-04T03:07:12Z   Completed   2024-11-04T03:19:05Z
test     test           1161728   2024-11-04T02:46:05Z   Completed   2024-11-04T03:19:05Z
test-3   test-3         1161728   2024-11-04T03:20:25Z   Completed   2024-11-04T03:20:27Z

$ kubectl logs -l app=longhorn-manager -c longhorn-manager -n longhorn-system | grep "Error inspecting backup config"
# Empty

@yangchiu yangchiu closed this as completed Nov 4, 2024
@github-project-automation github-project-automation bot moved this from Ready For Testing to Closed in Longhorn Sprint Nov 4, 2024
@yangchiu yangchiu self-assigned this Nov 4, 2024
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
Status: Closed
Development

No branches or pull requests

3 participants
0