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

[config][muxcable] fix minor config DB logic issue #2210

Merged
merged 1 commit into from
Jun 15, 2022

Conversation

vdahiya12
Copy link
Contributor

@vdahiya12 vdahiya12 commented Jun 11, 2022

Signed-off-by: vaibhav-dahiya vdahiya@microsoft.com
For active-standby type cable there will not be any soc_ipv4 entry in the "MUX_CABLE" table, hence when updating the config DB entry with update
for
sudo config mux mode <state> <port>
we should just check the cable_type and update the table entry
if no soc_ipv4 the value written in none in that case

What I did

How I did it

How to verify it

Unit-tests cover the change

Previous command output (if the output of a command-line utility has changed)

New command output (if the output of a command-line utility has changed)

Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com>
@vdahiya12 vdahiya12 merged commit c0dffba into sonic-net:master Jun 15, 2022
yxieca pushed a commit that referenced this pull request Jun 15, 2022
Signed-off-by: vaibhav-dahiya vdahiya@microsoft.com
For active-standby type cable there will not be any soc_ipv4 entry in the "MUX_CABLE" table, hence when updating the config DB entry with update
for
sudo config mux mode <state> <port>
we should just check the cable_type and update the table entry
if no soc_ipv4 the value written in none in that case

What I did
How I did it
How to verify it
Unit-tests cover the change

Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com>
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