You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently config reload command doesn't check if the system is up before executing. If config reload is given immediately after reboot when services are booting up, it leads to issues with some services.
Example when config reload is given between snmp.timer trigger but before snmp spawns, snmp will never start as the timer will not trigger after 'config reload' as it had triggered once and snmp in order to start after 'config reload' should have already executed once which didn't happen.
Steps to reproduce the issue:
reboot the device
Perform config reload
Describe the results you received:
config reload proceeds even with the system completely up.
Describe the results you expected:
config reload should fail and only succeed when the system is up.
This doesn't help as the above command returns running even before tasks like snmp are spawned(which have delayed start)
sudo systemctl is-system-running
running
root@sonic:~#
Description
Currently config reload command doesn't check if the system is up before executing. If config reload is given immediately after reboot when services are booting up, it leads to issues with some services.
Example when config reload is given between snmp.timer trigger but before snmp spawns, snmp will never start as the timer will not trigger after 'config reload' as it had triggered once and snmp in order to start after 'config reload' should have already executed once which didn't happen.
Steps to reproduce the issue:
Describe the results you received:
config reload proceeds even with the system completely up.
Describe the results you expected:
config reload should fail and only succeed when the system is up.
Output of
show version
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: