KC-1403: Fix NSF record update "This object no longer exists" after PAM tunnel/connection edit - #2298
Draft
sshrushanth-ks wants to merge 2 commits into
Draft
KC-1403: Fix NSF record update "This object no longer exists" after PAM tunnel/connection edit#2298sshrushanth-ks wants to merge 2 commits into
sshrushanth-ks wants to merge 2 commits into
Conversation
…edits Keep nested_share_records and record_cache revisions aligned after PAM and classic sync so NSF updates no longer send a stale revision. Route PAM connection/RBI/split updates through update_pam_record and retry once on RS_OUT_OF_SYNC.
Keep NSF permission caches after classic sync, mark classic PAM edits for resync, and safely retry stale-revision updates.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixed
nsf-record-updatefailing withRS_OUT_OF_SYNC/ "This object no longer exists" afterpam tunnel editand/orpam connection editon NSF PAM records. Stalenested_share_records.revisionwas preferred over a newer classicrecord_cacherevision, and post-PAM sync could roll the revision back from lagging NSF drive metadata.Changes
nested_share_folder/common.py/__init__.py: addedget_record_revision()andpatch_record_revision()helpersnested_share_folder/record_api.py:update_record_v3now uses the max known revision, patches both caches on success, and retries once after sync onRS_OUT_OF_SYNCnested_share_folder/sync.py: NSF sync no longer downgrades a newer local revision; reconstruct prefers a fresher classic vault payload over laggingkeeperDriveDatasync_down.py: classicresponse.recordsnow refreshesnested_share_records.revisionwhen the UID is NSFtunnel_and_connections.py: switchedpam connection edit,pam rbi edit, andpam-splitto NSF-awareupdate_pam_record(same pattern aspam tunnel edit)update_pam_recordtest_nested_share_folder.pyandtest_sync_down.py