Modifying ZTP to adapt to force config reload#29
Modifying ZTP to adapt to force config reload#29rajendra-dendukuri merged 1 commit intosonic-net:masterfrom
Conversation
|
@rajendra-dendukuri Can you please review this? |
rajendra-dendukuri
left a comment
There was a problem hiding this comment.
Don't we want to validate if the "config reload" command did what it was supposed to do and all the services are operational, before we declare success in the ZTP step. Adding -f in ztp defeats the purpose of adding these checks. Isn't it?
The purpose of the check is to perform system checks before the 'config reload' command is executed and not after. In the scenarios where user explicitly gives config reload, when services are starting up (immediately after config reload or reboot of the device) there are some issues as some services have problems being partially initialized during processing of configurations. Hence to restrict the user from giving 'config reload' command when the system has had one recently, these checks were introduced. However, from ZTP point of view since we are internally issuing the 'config reload' on receiving a config file, and before receiving the configuration file there isn't not much configuration to be processed (except the interface configs which I believe would have been processed and the links are up), I would prefer we do a force. The reason I want force here is if there are some failed services (like say reboot determination service) or the delayed services have not started up(like snmp), It shouldn't stop ZTP from happening. So I wanted to retain the current behavior of ZTP. If there are any issues faced during config reload execution part of ZTP prior, it would be good to consider this but without any issues I don't want to change ZTP behavior. |
DO NOT MERGE THIS until sonic-net/sonic-utilities#1664 is merged
Added force config reload in ZTP to avoid newly introduced system checks when in ztp mode.