824d7adc2d
**- Why I did it** On the Mellanox platform, reboot cause is fetched from some certain sysfs which is created by the hw-management service. So determine-reboot-cause service shall start after hw-management, otherwise it could fail due to the related sysfs is not available yet. **- How I did it** Add a patch to the hw-management service to make sure determine-reboot-cause service should start after it. Signed-off-by: Kebo Liu <kebol@nvidia.com>
27 lines
800 B
Diff
27 lines
800 B
Diff
From 1a1011b6da491d35001df5a7204d4eecb2769767 Mon Sep 17 00:00:00 2001
|
|
From: keboliu <kebol@mellanox.com>
|
|
Date: Fri, 15 Jan 2021 14:41:16 +0800
|
|
Subject: [PATCH] Make SONiC determine-reboot-cause service start after hw-mgmt
|
|
service
|
|
|
|
Signed-off-by: Kebo Liu <kebol@nvidia.com>
|
|
---
|
|
debian/hw-management.hw-management.service | 1 +
|
|
1 file changed, 1 insertion(+)
|
|
|
|
diff --git a/debian/hw-management.hw-management.service b/debian/hw-management.hw-management.service
|
|
index 39a2a54..2104b87 100755
|
|
--- a/debian/hw-management.hw-management.service
|
|
+++ b/debian/hw-management.hw-management.service
|
|
@@ -1,6 +1,7 @@
|
|
[Unit]
|
|
Description=Chassis HW management service of Mellanox systems
|
|
Documentation=man:hw-management.service(8)
|
|
+Before=determine-reboot-cause.service
|
|
|
|
[Service]
|
|
Type=oneshot
|
|
--
|
|
1.9.1
|
|
|