Open MaxYaremchuk opened 3 years ago
The issue is due to sflow service start failing not starting as part of the "config reload".
Sep 2 12:44:40.228634 sonic-step-04 INFO sonic-ztp[9524]: Executing restart of service sflow...
Sep 2 12:44:40.243347 sonic-step-04 WARNING systemd[1]: sflow.service: Start request repeated too quickly.
Sep 2 12:44:40.244186 sonic-step-04 ERR systemd[1]: Failed to start sFlow container.
Sep 2 12:44:40.244876 sonic-step-04 NOTICE systemd[1]: sflow.service: Unit entered failed state.
Sep 2 12:44:40.245806 sonic-step-04 WARNING systemd[1]: sflow.service: Failed with result 'start-limit-hit'.
Sep 2 12:44:40.247692 sonic-step-04 INFO sonic-ztp[9524]: Job for sflow.service failed.
Sep 2 12:44:40.248548 sonic-step-04 INFO sonic-ztp[9524]: See "systemctl status sflow.service" and "journalctl -xe" for details.
Sep 2 12:44:40.249335 sonic-step-04 ERR config: Failed to execute restart of service sflow with error 1
Sep 2 12:44:40.370798 sonic-step-04 ERR sonic-ztp[22682]: configdb-json: Command '/usr/bin/config reload -y /tmp/config_dl.json' failed with exit code(1).
I propose that we can provide an additional option to specify in the configdb-json plugin to ignore errors seen during "config reload". This option will be disabled by default to catch errors seen during "config reload".
Please raise another issue for the sflow service issue seen.
config reload failed again recently when the ZTP tries to apply configdb-json plugin. Not because of Sflow though.
sonic_dump_DUT-1_20210419_130556.tar.gz
Apr 19 12:53:54.947222 sonic INFO sonic-ztp[15343]: Stopping SONiC target ...
..........
..........
Apr 19 12:53:55.153250 sonic INFO sonic-ztp[15374]: Job for sonic.target canceled.
Apr 19 12:53:55.729680 sonic ERR sonic-ztp[13308]: configdb-json: Command 'config reload -y /tmp/config_dl.json' failed with exit code(1).
Description From time to time execution of built-in configdb-json plugin fails with exit code(1). It doesn't depends on whether ZTP process is running just after cold rebooting or not. The following run of ZTP process may finish successfully (no changes on config_db.json or ztp_config.json have applied) This issue is reproduced intermittently (approximately one time out of ten)
Steps to reproduce the issue 1.Boot sonic with ZTP enabled feature 2.Announce DHCP option 67 pointing to ztp_config.json (see at the bottom) 3.Put all necessary plugins and configuration files using in ZTP process on WEB server.
5.Wait till ZTP process has finished. 6.Verify the status of ZTP execution: 7.sudo show ztp status --verbose 8.Check /var/log/ztp.log
Describe the results you received Example of unsuccessful execution of configdb-json plugin:
Next attempt of execution (no changes on config_db.json or ztp_config.json have applied between executions ) was successful:
Describe the results you expected
Output of
show version
sonic_dump_DUT-1_20200902_133602.tar.gz
files.zip