run openpower-debug-collector after stop instructions

openpower-debug-collector may end up requesting a SBE or hostboot dump.
Ensure that if stop-instruction is also scheduled in the same systemd
target, that we first stop instruction to get the hardware in a known
state and then start the dump collection.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I1156a20b16545ff42e20d4a8e3fc1089786ba605
diff --git a/meta-openpower/recipes-phosphor/debug/openpower-debug-collector/openpower-debug-collector-watchdog@.service b/meta-openpower/recipes-phosphor/debug/openpower-debug-collector/openpower-debug-collector-watchdog@.service
index 6fc3fec..6826764 100644
--- a/meta-openpower/recipes-phosphor/debug/openpower-debug-collector/openpower-debug-collector-watchdog@.service
+++ b/meta-openpower/recipes-phosphor/debug/openpower-debug-collector/openpower-debug-collector-watchdog@.service
@@ -1,6 +1,7 @@
 [Unit]
 Description=OpenPOWER debug data collector for host watchdog timeout
 Before=obmc-host-quiesce@%i.target
+After=op-stop-instructions@%i.service
 
 [Service]
 ExecStart=/usr/bin/env watchdog_timeout