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][IMPROVEMENT] Do not terminate nfs-ganesha in share-manager pod after failing to access recovery backend #8347

Closed
github-actions bot opened this issue Apr 11, 2024 · 2 comments
Assignees
Labels
area/volume-rwx Volume RWX related kind/backport Backport request kind/improvement Request for improvement of existing function priority/0 Must be implement or fixed in this release (managed by PO) require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/manual-test-plan Require adding/updating manual test cases if they can't be automated
Milestone

Comments

@github-actions
Copy link

backport #8345

@github-actions github-actions bot added area/volume-rwx Volume RWX related kind/backport Backport request kind/improvement Request for improvement of existing function priority/0 Must be implement or fixed in this release (managed by PO) require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/manual-test-plan Require adding/updating manual test cases if they can't be automated labels Apr 11, 2024
@github-actions github-actions bot added this to the v1.5.5 milestone Apr 11, 2024
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Apr 12, 2024

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

#8345 (comment)

  • 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

rancher/nfs-ganesha#12
longhorn/longhorn-share-manager#176

  • Which areas/issues this PR might have potential impacts on?
    Area: RWX volume, nfs-ganesha
    Issues

@chriscchien chriscchien self-assigned this Apr 12, 2024
@chriscchien
Copy link
Contributor

Verified pass on longhorn v1.5.x (longhorn-share-manager e746ae)

Following test steps with custom image derekbit/longhorn-manager:v1.5.5-no-rb, the share-manager pod did not terminated.

12/04/2024 07:47:46 : epoch 6618e71c : share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9 : nfs-ganesha-35[svc_4] longhorn_add_clid :CLIENT ID :EVENT :Add client '29:Linux NFSv4.1 ip-172-31-38-39' to recovery backend share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9
12/04/2024 07:47:46 : epoch 6618e71c : share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9 : nfs-ganesha-35[svc_5] longhorn_add_clid :CLIENT ID :EVENT :Add client '29:Linux NFSv4.1 ip-172-31-45-99' to recovery backend share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9
12/04/2024 07:51:04 : epoch 6618e71c : share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9 : nfs-ganesha-35[svc_8] longhorn_add_clid :CLIENT ID :EVENT :Add client '30:Linux NFSv4.1 ip-172-31-43-214' to recovery backend share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9
12/04/2024 07:51:04 : epoch 6618e71c : share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9 : nfs-ganesha-35[svc_8] http_call :CLIENT ID :EVENT :Failed to perform CURL operation: Couldn't connect to server
12/04/2024 07:51:04 : epoch 6618e71c : share-manager-pvc-cd239dac-c766-48cb-88d5-598f6c3cc0a9 : nfs-ganesha-35[svc_8] longhorn_add_clid :CLIENT ID :EVENT :Failed to create client in recovery backend. HTTP call error: res=-1 ((null))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/volume-rwx Volume RWX related kind/backport Backport request kind/improvement Request for improvement of existing function priority/0 Must be implement or fixed in this release (managed by PO) require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/manual-test-plan Require adding/updating manual test cases if they can't be automated
Projects
Status: Closed
Development

No branches or pull requests

3 participants