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.

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

[action] [PR:225] [active-standby] Fix show mux status inconsistency introduced by orchagent rollback (#225) #243

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

mssonicbld
Copy link
Collaborator

Approach
What is the motivation for this PR?
This is to fix the show mux status inconsistency introduced by orchagent roll back.

In mux port state machine design, linkmgrd honors hardware state for active-standby ports, and never intends to trigger a secondary toggle when everything is healthy. But after we introduce orchagent rollback, show mux status can return unmatched APP_DB and STATE_DB entries for this, which blocks upgrade.

Hence, submitting this PR as a workaround.

sign-off: Jing Zhang [email protected]

Work item tracking
Microsoft ADO (number only):
26136887

How did you do it?
How did you verify/test it?

…chagent rollback (sonic-net#225)

Approach
What is the motivation for this PR?
This is to fix the show mux status inconsistency introduced by orchagent roll back.

In mux port state machine design, linkmgrd honors hardware state for active-standby ports, and never intends to trigger a secondary toggle when everything is healthy. But after we introduce orchagent rollback, show mux status can return unmatched APP_DB and STATE_DB entries for this, which blocks upgrade.

Hence, submitting this PR as a workaround.

sign-off: Jing Zhang [email protected]

Work item tracking
Microsoft ADO (number only):
26136887

How did you do it?
How did you verify/test it?
@mssonicbld
Copy link
Collaborator Author

Original PR: #225

@mssonicbld mssonicbld merged commit 70b6d15 into sonic-net:202311 Feb 2, 2024
9 checks passed
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.

2 participants