dae5c4c930
Fixes #5663 - Why I did it It's currently possible for the SNMP timer to conflict with config reload (specifically if the timer triggers while config reload is stopping the SWSS service). config reload triggers SWSS to shutdown, which causes SNMP to shutdown, which conflicts with the SNMP timer causing SNMP to startup. See the linked issue for more details. - How I did it Including the After ordering dependency forces the SNMP timer to wait until SWSS finishes stopping, preventing the conflict. If there is an ordering dependency between two units (e.g. one unit is ordered After another), if one unit is shutting down while the other is starting up, the shutdown will always be ordered before the startup. In this case, that means that the SNMP timer is forced to wait for the SWSS shutdown to complete. Only then can the SNMP timer proceed. See here for more details. It's important to note that the After dependency will not cause SWSS to be started when the SNMP timer fires (assuming that SWSS has not yet been started). The existing Requisite dependency in the SNMP service will also not cause SWSS to be started, instead it will cause the SNMP service to fail if SWSS is not active. Signed-off-by: Lawrence Lee <lawlee@microsoft.com> |
||
|---|---|---|
| .. | ||
| per_namespace | ||
| buffers_config.j2 | ||
| config-setup.service.j2 | ||
| database.service.j2 | ||
| dhcp_relay.service.j2 | ||
| docker_image_ctl.j2 | ||
| init_cfg.json.j2 | ||
| lldp.service.j2 | ||
| mgmt-framework.service.j2 | ||
| mgmt-framework.timer | ||
| nat.service.j2 | ||
| organization_extensions.sh | ||
| pmon.service.j2 | ||
| process-reboot-cause.timer | ||
| qos_config.j2 | ||
| radv.service.j2 | ||
| restapi.service.j2 | ||
| sflow.service.j2 | ||
| snmp.service.j2 | ||
| snmp.timer | ||
| sonic_debian_extension.j2 | ||
| telemetry.service.j2 | ||
| telemetry.timer | ||
| updategraph.service.j2 | ||