Fixed determine/process reboot-cause service dependency (#17406) (sonic-net#132)

Signed-off-by: anamehra <[email protected] sonic-net/sonic-buildimage#16990 for 202405 branch



determine-reboot-cause and process-reboot-cause service does not start If the database service fails to restart in the first attempt. Even if the Database service succeeds in the next attempt, these reboot-cause services do not start.

The process-reboot-cause service also does not restart if the docker or database service restarts, which leads to an empty reboot-cause history

deploy-mg from sonic-mgmt also triggers the docker service restart. The restart of the docker service caused the issue stated in 2 above. The docker restart also triggers determine-reboot-cause to restart which creates an additional reboot-cause file in history and modifies the last reboot-cause.

This PR fixes these issues by making both processes start again when dependency meets after dependency failure, making both processes restart when the database service restarts, and preventing duplicate processing of the last reboot reason.m>

Author: anamehra

Diff for: data/debian/sonic-host-services-data.determine-reboot-cause.service

@@ -2,6 +2,7 @@
 Description=Reboot cause determination service
 Requires=rc-local.service
 After=rc-local.service
+Wants=process-reboot-cause.service
 
 [Service]
 Type=oneshot

Diff for: data/debian/sonic-host-services-data.process-reboot-cause.service

@@ -1,8 +1,16 @@
 [Unit]
 Description=Retrieve the reboot cause from the history files and save them to StateDB
-Requires=database.service determine-reboot-cause.service
+PartOf=database.service
 After=database.service determine-reboot-cause.service
 
 [Service]
 Type=simple
+ExecStartPre=/usr/bin/systemctl is-active database
+ExecStartPre=/usr/bin/systemctl is-active determine-reboot-cause
+Restart=on-failure
+RestartSec=30
+RemainAfterExit=yes
 ExecStart=/usr/local/bin/process-reboot-cause
+
+[Install]
+WantedBy=multi-user.target