-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[DPB]config load_minigraph initializes all ports admin status to up when using platform.json #8697
Comments
5 tasks
lguohan
pushed a commit
that referenced
this issue
Sep 13, 2021
…oading minigraph (#8711) To Fix #8697 . The config load_minigraph initializes 'admin_status' to up when platform.json has DPB configs. This doesn't happen when using port_config.ini The update minigraph has logic to initialize only the ports whose neighbors are defined or those belonging to portchannel However, a change was introduced to have default admin status to be 'up' in portconfig.py when the minigraph was using platform.json This will lead to sanity check failure in sonic-mgmt and thus no test cases could be run
judyjoseph
pushed a commit
that referenced
this issue
Sep 14, 2021
…oading minigraph (#8711) To Fix #8697 . The config load_minigraph initializes 'admin_status' to up when platform.json has DPB configs. This doesn't happen when using port_config.ini The update minigraph has logic to initialize only the ports whose neighbors are defined or those belonging to portchannel However, a change was introduced to have default admin status to be 'up' in portconfig.py when the minigraph was using platform.json This will lead to sanity check failure in sonic-mgmt and thus no test cases could be run
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
config load_minigraph initializes all ports admin status to up when using platform.json.
The update minigraph has logic to initialize only the ports whose neighbors are defined (https://github.com/Azure/sonic-buildimage/blob/202106/src/sonic-config-engine/minigraph.py#L1486)
or those belonging to portchannel (https://github.com/Azure/sonic-buildimage/blob/202106/src/sonic-config-engine/minigraph.py#L1481) to have admin status 'up' and rest left to default ('down')
However, the change introduced #3909 to have default admin status to be 'up' in portconfig.py.
This will lead to sanity check failure in sonic-mgmt and thus no test cases could be run
https://github.com/Azure/sonic-mgmt/blob/master/tests/common/plugins/sanity_check/checks.py#L140
Steps to reproduce the issue:
Describe the results you received:
All ports are shown admin up.
Describe the results you expected:
Only the ports that have neighbors and are part of portchannels should be admin up. Rest should be admin down.
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: