-
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
port_config.ini is not a part of saved config during upgrade #2047
Comments
that should solve this s2s upgrade issue. |
does it mean to process port_config.ini on first boot and move all info to config_db (including aliases, etc) as we do with the minigraph? |
@lguohan Do you mean portsyncd or portorch in your comment?
|
@andriymoroz-mlnx Is this issue address already? Please feel free to reopen if the issue still exists. |
…NG container (sonic-net#2047) #### What I did Did a debug session with Ping Mao and found this case is failing in her PR: sonic-net#9545 I think it is an interesting case and I added it explicitly to GCU. Adding unit-test where path and ref paths are under the same YANG container [sonic-loopback-interface.yang](https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/yang-models/sonic-loopback-interface.yang) has: ```yang container sonic-loopback-interface { container LOOPBACK_INTERFACE { list LOOPBACK_INTERFACE_LIST { ... leaf name{ type string; } ... list LOOPBACK_INTERFACE_IPPREFIX_LIST { leaf name{ ... type leafref { path "../../LOOPBACK_INTERFACE_LIST/name"; } } ... ``` #### How I did it Unit-test added #### How to verify it unit-test #### 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)
Description
After sonic2sonic upgrade changed port_config.ini is replaced by default version from the image.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Upgraded SONiC.HEAD.6-6cf2d10 --> SONiC.HEAD.5-90257f5
The text was updated successfully, but these errors were encountered: