ensure host_start runs after fsi-scan
An issue is being pursued where the synchronization target,
obmc-host-start-pre@.target is not being properly stopped in some
instances. This results in the services which depend on it for
synchronization purposes to execute out of order.
The only critical interaction between services which utilize this target
is the fsi-scan and start_host services. You do not want to be starting
the host until the fsi-scan has completed. For now just define the
dependency directly between the services.
Issue openbmc/openbmc#3755 has been opened to further investigate the
target issue.
Tested:
- Verified when a system was in the invalid state that it correctly
booted without issue with this change.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I53dd2cb9976066a7d5a495bf7f2b0b061a8226f6
diff --git a/meta-openpower/recipes-phosphor/fsi/op-fsi/fsi-scan@.service b/meta-openpower/recipes-phosphor/fsi/op-fsi/fsi-scan@.service
index c37863e..0067679 100644
--- a/meta-openpower/recipes-phosphor/fsi/op-fsi/fsi-scan@.service
+++ b/meta-openpower/recipes-phosphor/fsi/op-fsi/fsi-scan@.service
@@ -5,6 +5,7 @@
Wants=obmc-host-start-pre@%i.target
Before=obmc-host-start-pre@%i.target
After=op-cfam-reset.service
+Before=start_host@%i.service
Conflicts=obmc-chassis-poweroff@%i.target
Conflicts=obmc-host-stop@%i.target
ConditionPathExists=!/run/openbmc/mpreboot@%i