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

Problem deleting non-last list element if ordered-by user #475

Closed
olofhagsand opened this issue Jan 5, 2024 · 0 comments
Closed

Problem deleting non-last list element if ordered-by user #475

olofhagsand opened this issue Jan 5, 2024 · 0 comments

Comments

@olofhagsand
Copy link
Member

A list element being removed with edit-config operation="delete" may result in a failed diff.
Which in turn may lead to other consequences (unclear)
A list X YANG "ordered by user" with elements X0, X1, X2, etc. An object Xi which is not last is removed. The error has a 50% chance of occurring.
Deletion is successful, but the sorting/equaity check is broken which may lead to unrecoverable errors.
One way to detect it is via the show compare command which shows wrong (ie too large) diff.

@olofhagsand olofhagsand added the bug label Jan 5, 2024
@olofhagsand olofhagsand self-assigned this Jan 6, 2024
olofhagsand added a commit that referenced this issue Jan 6, 2024
Remove sanity check for insert/search which does not hold for NETCONF attributes
olofhagsand added a commit to clicon/clixon-controller that referenced this issue Jan 6, 2024
Remove duplicate delete/adds
olofhagsand added a commit to clicon/clixon-controller that referenced this issue Jan 7, 2024
@olofhagsand olofhagsand assigned krihal and unassigned olofhagsand Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants