-
Notifications
You must be signed in to change notification settings - Fork 538
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
Do not apply QoS mapping object until it is resolved #3163
Conversation
47f3fff
to
f0e7809
Compare
vs test failure is not relevant to my change.
|
Signed-off-by: Stephen Sun <[email protected]>
f0e7809
to
771ac7f
Compare
vs failed due to installing .net core
|
The change LGTM. Just wondering how the issue was triggered ( |
Theoretically, the order is not guaranteed between redos db and orchagnet. |
…ed (sonic-net#3163) What I did Do not apply the global DSCP to TC map to the switch object until the mapping object has been created. Why I did it Fix issue: if orchagent handles tables in the following order, it will fail in step 1 and the configure will never applied. PORT_QOS_MAP|global object and then DSCP_TO_TC object
Cherry-pick PR to 202311: #3184 |
…ed (#3163) What I did Do not apply the global DSCP to TC map to the switch object until the mapping object has been created. Why I did it Fix issue: if orchagent handles tables in the following order, it will fail in step 1 and the configure will never applied. PORT_QOS_MAP|global object and then DSCP_TO_TC object
What I did
Do not apply the global DSCP to TC map to the switch object until the mapping object has been created.
Why I did it
Fix issue: if orchagent handles tables in the following order, it will fail in step 1 and the configure will never applied.
How I verified it
Mock and manual test
Details if related