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

[muxorch] Adding case for maintaining current state #2280

Merged
merged 3 commits into from
Dec 6, 2022

Conversation

Ndancejic
Copy link
Contributor

What I did:
Added a case where if current and previous Mux states
are the same, post a log entry that acknowleges this
change and returns without doing anything.

Why I did it:
Valid state changes such as active-active and
standby-standby were causing error logs

How I tested it:
added a case to check active-active state change
and standby-standby state change.

Signed-off-by: Nikola Dancejic ndancejic@microsoft.com

prsunny
prsunny previously approved these changes May 18, 2022
@prsunny
Copy link
Collaborator

prsunny commented May 18, 2022

@Ndancejic , seems like there are some VS failures due to the change:

test_mux.py::TestMuxTunnel::test_Tunnel PASSED                           [ 50%]
test_mux.py::TestMuxTunnel::test_Peer PASSED                             [ 50%]
test_mux.py::TestMuxTunnel::test_Neighbor FAILED                         [ 51%]
test_mux.py::TestMuxTunnel::test_Fdb FAILED                              [ 51%]
test_mux.py::TestMuxTunnel::test_Route FAILED                            [ 51%]
test_mux.py::TestMuxTunnel::test_acl FAILED                              [ 51%]

@Ndancejic
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Commenter does not have sufficient privileges for PR 2280 in repo sonic-net/sonic-swss

@Ndancejic
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Ndancejic
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Ndancejic
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

What I did:
Added a case where if current and previous Mux states
are the same, post a log entry that acknowleges this
change and returns without doing anything.

Why I did it:
Valid state changes such as active-active and
standby-standby were causing error logs

How I tested it:
added a case to check active-active state change
and standby-standby state change.

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
@Ndancejic
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@prsunny prsunny merged commit bd652a0 into sonic-net:master Dec 6, 2022
yxieca pushed a commit that referenced this pull request Dec 7, 2022
* [muxorch] Adding case for maintaining current state

What I did:
Added a case where if current and previous Mux states are the same, post a log entry that acknowleges this change and returns without doing anything.
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.

4 participants