led-manager: start led-manager after object mapper

The new commit in led-manager may make a call to object mapper
in some case as part of its start and hence putting the dependency

(From meta-phosphor rev: c5c8d92ac6b9ff85ce4dee9b908a3c04a0c29bda)

Change-Id: I7d897d88ac658088333824cb56b979745f23a1f5
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/meta-phosphor/recipes-phosphor/leds/phosphor-led-manager/xyz.openbmc_project.LED.GroupManager.service b/meta-phosphor/recipes-phosphor/leds/phosphor-led-manager/xyz.openbmc_project.LED.GroupManager.service
index 8e852a4..5e361a3 100644
--- a/meta-phosphor/recipes-phosphor/leds/phosphor-led-manager/xyz.openbmc_project.LED.GroupManager.service
+++ b/meta-phosphor/recipes-phosphor/leds/phosphor-led-manager/xyz.openbmc_project.LED.GroupManager.service
@@ -1,6 +1,8 @@
 [Unit]
 Description=Phosphor LED Group Management Daemon
 Before=mapper-wait@-xyz-openbmc_project-led-groups.service
+Wants=obmc-mapper.target
+After=obmc-mapper.target
 
 [Service]
 Restart=always