Host@.service: depend on templated chassis service
The Host@N services are depending on a Chassis@0 service which
may never exist on multi-host systems. For now assume a 1:1
mapping between Host:Chassis instances and update the dependency to
match so that multi-host systems do not block forever waiting for
a Chassis@0 service which will never start.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic280f2714a2876de2acd6a0bc4d4fde97b2941d5
diff --git a/service_files/xyz.openbmc_project.State.Host@.service b/service_files/xyz.openbmc_project.State.Host@.service
index fded2f0..922c39c 100644
--- a/service_files/xyz.openbmc_project.State.Host@.service
+++ b/service_files/xyz.openbmc_project.State.Host@.service
@@ -2,8 +2,8 @@
Description=Phosphor Host%i State Manager
Wants=mapper-wait@-xyz-openbmc_project-control-host%i-auto_reboot.service
After=mapper-wait@-xyz-openbmc_project-control-host%i-auto_reboot.service
-Wants=mapper-wait@-xyz-openbmc_project-state-chassis0.service
-After=mapper-wait@-xyz-openbmc_project-state-chassis0.service
+Wants=mapper-wait@-xyz-openbmc_project-state-chassis%i.service
+After=mapper-wait@-xyz-openbmc_project-state-chassis%i.service
Wants=obmc-mapper.target
After=obmc-mapper.target
After=phosphor-ipmi-host.service