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

isisd: remove redundant northbound destroy callbacks #14541

Merged
merged 1 commit into from
Oct 8, 2023

Conversation

idryzhov
Copy link
Contributor

@idryzhov idryzhov commented Oct 6, 2023

Fixes startup warnings:

ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-segs-left'
ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-end-pop'
ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-h-encaps'
ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-end-d'

Fixes startup warnings:
```
ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-segs-left'
ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-end-pop'
ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-h-encaps'
ISIS: [ZKB8W-3S2Q4][EC 100663330] unneeded 'destroy' callback for '/frr-isisd:isis/instance/segment-routing-srv6/msd/node-msd/max-end-d'
```

Signed-off-by: Igor Ryzhov <[email protected]>
@mjstapp
Copy link
Contributor

mjstapp commented Oct 6, 2023

Can you say a bit about why these aren't needed? it does look as if those existing callbacks do ... something: is that work being done somewhere else?

@idryzhov
Copy link
Contributor Author

idryzhov commented Oct 6, 2023

Destroy callbacks are not needed for leafs that have default values. If such leaf is deleted from the configuration, the modify callback is called with a default value. As you can see, these destroy callbacks do exactly the same thing – they set values to default. But they are never called :)

@mjstapp
Copy link
Contributor

mjstapp commented Oct 6, 2023

Got it - thanks for the explanation.

Destroy callbacks are not needed for leafs that have default values. If such leaf is deleted from the configuration, the modify callback is called with a default value. As you can see, these destroy callbacks do exactly the same thing – they set values to default. But they are never called :)

@idryzhov
Copy link
Contributor Author

idryzhov commented Oct 6, 2023

ci:rerun

@rzalamena rzalamena merged commit 5c0a5aa into FRRouting:master Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants