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
bgpd : Prevent deletion of BGP peer groups associated to listen range #15670
bgpd : Prevent deletion of BGP peer groups associated to listen range #15670
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix styling/formatting also.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good ... waiting on other's comments
Still... styling issues + signed-off is missing. |
19f7b3a
to
474fee0
Compare
Still, styling issues, see:
|
474fee0
to
33eb965
Compare
33eb965
to
9e6699c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still have one question. If we do no neighbor PG
should it also be prevented from deleting it or only for no neighbor PG peer-group
?
Yeah true Thanks for bringing it up! I'll add the fix for the same. |
9e6699c
to
e792cd2
Compare
Description: ----- Deleting a peer group also deletes its associated BGP listen range. This behaviour is undesired as it could cause unintended configuration changes. Fix : ----- -Do not allow peer group deletion until they are no longer associated with any listen range. -Check the count of listen ranges attached to the group. If any listen ranges are found, returns a configuration warning, preventing the deletion. Signed-off-by: Pooja Rathore <rathorepo@vmware.com>
e792cd2
to
48faeaf
Compare
Description:
Deleting a peer group also deletes its associated BGP listen range. This behaviour is undesired as it could cause unintended configuration changes.
Fix :
-Do not allow peer group deletion until they are no longer associated with any listen range.
-Check the count of listen ranges attached to the group. If any listen ranges are found, returns a configuration warning, preventing the deletion.