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.

Sign up for GitHub

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

Jump to bottom

[GCU] BGP_PEER_RANGE should be create only #2062

Closed
wen587 opened this issue Feb 11, 2022 · 0 comments
Closed

[GCU] BGP_PEER_RANGE should be create only #2062

wen587 opened this issue Feb 11, 2022 · 0 comments
Assignees
@ghooo
Labels
generic-config-updater p0

Comments

@wen587
Copy link
Contributor

wen587 commented Feb 11, 2022

Description

Refering #2029 and verified that fields under BGP_PEER_RANGE such as BGPSLBPassive are create-only.

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

(paste your output here)
@qiluo-msft qiluo-msft added the p0 label Mar 4, 2022
@ghooo ghooo mentioned this issue Mar 4, 2022
Merged
qiluo-msft pushed a commit that referenced this issue Mar 9, 2022
@ghooo
[GCU] Marking fields under BGP_PEER_RANGE, BGP_MONITORS as create-only (
2c56e92 
#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
@ghooo ghooo closed this as completed Mar 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ghooo ghooo

Labels
generic-config-updater p0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ghooo @wen587 @qiluo-msft