-
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
[swss/syncd] remove dependency on interfaces-config.service #13084
[swss/syncd] remove dependency on interfaces-config.service #13084
Conversation
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
in interfaces-config.sh file, there are some ZTP support which enable dhclient on front panel port as well. from current look, it seems it only try to generate correct /etc/network/interfaces file and restart networking service. i tend to agree that swss and syncd should not have dependency on interfaces-config.service. |
…t#13084) - Why I did it Remove dependency on interfaces-config.service to speed up boot, because interfaces-config.service takes a lot of time on boot. - How I did it Changed service files for swss, syncd. - How to verify it Boot and check swss/syncd start time comparing to interfaces-config Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Cherry-pick PR to 202205: #14252 |
- Why I did it Remove dependency on interfaces-config.service to speed up boot, because interfaces-config.service takes a lot of time on boot. - How I did it Changed service files for swss, syncd. - How to verify it Boot and check swss/syncd start time comparing to interfaces-config Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
…t#13084) - Why I did it Remove dependency on interfaces-config.service to speed up boot, because interfaces-config.service takes a lot of time on boot. - How I did it Changed service files for swss, syncd. - How to verify it Boot and check swss/syncd start time comparing to interfaces-config Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Cherry-pick PR to 202211: #14341 |
All these 3 services started after swss service, which used to start after interface-config service. But sonic-net#13084 remove the time constraints for swss. After that, these 3 services has the chance of start earlier when the inteface-config service is restarting the networking service, which could cause db connect request to fail. Signed-off-by: Ying Xie <ying.xie@microsoft.com>
Why I did it All these 3 services started after swss service, which used to start after interface-config service. But #13084 remove the time constraints for swss. After that, these 3 services has the chance of start earlier when the inteface-config service is restarting the networking service, which could cause db connect request to fail. How I did it Delay mux/sflow/snmp timer after the interface-config service. How to verify it PR test. Config reload can repro the issue in 1-3 retries. With this change. config reload run 30+ iterations without hitting the issue. Signed-off-by: Ying Xie <ying.xie@microsoft.com>
…14506) Why I did it All these 3 services started after swss service, which used to start after interface-config service. But sonic-net#13084 remove the time constraints for swss. After that, these 3 services has the chance of start earlier when the inteface-config service is restarting the networking service, which could cause db connect request to fail. How I did it Delay mux/sflow/snmp timer after the interface-config service. How to verify it PR test. Config reload can repro the issue in 1-3 retries. With this change. config reload run 30+ iterations without hitting the issue. Signed-off-by: Ying Xie <ying.xie@microsoft.com>
…14506) Why I did it All these 3 services started after swss service, which used to start after interface-config service. But sonic-net#13084 remove the time constraints for swss. After that, these 3 services has the chance of start earlier when the inteface-config service is restarting the networking service, which could cause db connect request to fail. How I did it Delay mux/sflow/snmp timer after the interface-config service. How to verify it PR test. Config reload can repro the issue in 1-3 retries. With this change. config reload run 30+ iterations without hitting the issue. Signed-off-by: Ying Xie <ying.xie@microsoft.com>
…onic-net#13084) (sonic-net#14341)" This reverts commit 499f57a.
…onic-net#13084)" This reverts commit 661669c.
…onic-net#13084) (sonic-net#14341)" (sonic-net#15094) (sonic-net#17367) This reverts commit 499f57a. Co-authored-by: Nazarii Hnydyn <nazariig@nvidia.com>
…onic-net#13084) (sonic-net#14341)" (sonic-net#15094) (sonic-net#17367) This reverts commit 499f57a. Co-authored-by: Nazarii Hnydyn <nazariig@nvidia.com>
Signed-off-by: Stepan Blyschak stepanb@nvidia.com
Why I did it
Remove dependency on interfaces-config.service to speed up boot, because interfaces-config.service takes a lot of time on boot.
How I did it
Changed service files for swss, syncd.
How to verify it
Boot and check swss/syncd start time comparing to interfaces-config
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)