-
Notifications
You must be signed in to change notification settings - Fork 711
[GCU] Check if BGP_INTERNAL_NEIGHBOR, BGP_MONITORS, BGP_PEER_RANGE, BGP_VOQ_CHASSIS_NEIGHBOR fields are create-only #2029
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
Comments
@qiluo-msft I didn't find a YANG table for BGP_INTERNAL_NEIGHBOR nor BGP_VOQ_CHASSIS_NEIGHBOR. I need to know the fields under these tables so I can double check if they are create-only or not. |
@ganglyu These tables are missing yang models and also minigraph parsing/validation unit test. |
sonic-net/sonic-buildimage#10157 |
https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-config-engine/minigraph.py#L727 |
#2092) #### What I did Fixes #2029 #2062 Changes to fields under BGP_PEER_RANGE, BGP_MONITORS using GCU are not reflected unless each key is deleted and added back. This means the fields are create-only. #### How I did it Marked the fields under BGP_PEER_RANGE, BGP_MONITORS as create-only #### How to verify it unit-test
Description
Create-Only fields are only created with their parent, but cannot be modified later.
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
Additional information you deem important (e.g. issue happens only occasionally)
Output of
show version
The text was updated successfully, but these errors were encountered: