Skip to content

[201911][RFC1213]: Initialize lag oid map in reinit_data #234

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

Merged
merged 1 commit into from
Sep 17, 2021

Conversation

SuvarnaMeenakshi
Copy link
Contributor

updating in update_data. Updating lag oid map in update_data
can cause descrepancy as interface oid map is updated in
reinit_data.

Signed-off-by: Suvarna Meenakshi [email protected]

- What I did
Same change as: #232 for 201911 branch.
- How I did it

- How to verify it

- Description for the changelog

updating in update_data. Updating lag oid map in update_data
can cause descrepancy as interface oid map is updated in
reinit_data.

Signed-off-by: Suvarna Meenakshi <[email protected]>
@qiluo-msft qiluo-msft merged commit ad07720 into sonic-net:201911 Sep 17, 2021
qiluo-msft pushed a commit that referenced this pull request Sep 20, 2021
updating in update_data. Updating lag oid map in update_data
can cause descrepancy as interface oid map is updated in
reinit_data.
@judyjoseph
Copy link

Not able to cherry-pick cleanly in 202106, Please raise a separate PR in 202106.

judyjoseph pushed a commit that referenced this pull request Nov 14, 2021
updating in update_data. Updating lag oid map in update_data
can cause descrepancy as interface oid map is updated in
reinit_data.
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