ledmanager: Disable persistent-led-asserted by default

Since not all systems start persistent-led-asserted by default,
persistent-led-asserted should be disabled by default in Yocto.

However, IBM’s p10 machine needs to be enabled by default.

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I9b5302f541bf814f96d5af7d20662b5bfcc4e6a8
diff --git a/meta-ibm/recipes-phosphor/leds/phosphor-led-manager_%.bbappend b/meta-ibm/recipes-phosphor/leds/phosphor-led-manager_%.bbappend
index b3bfaa4..b36adca 100644
--- a/meta-ibm/recipes-phosphor/leds/phosphor-led-manager_%.bbappend
+++ b/meta-ibm/recipes-phosphor/leds/phosphor-led-manager_%.bbappend
@@ -8,7 +8,7 @@
 # Use the JSON configuration file at runtime than the static led.yaml
 # Also, enable Lamp Test and OperationalStatus monitor feature for
 # p10bmc systems
-PACKAGECONFIG:append:p10bmc = " use-lamp-test monitor-operational-status"
+PACKAGECONFIG:append:p10bmc = " use-lamp-test monitor-operational-status persistent-led-asserted"
 
 # Install the lamp test override file for p10bmc
 SRC_URI:append:p10bmc = " file://lamp-test-led-overrides.json"