PEL: Fix to support early msg registry callouts
The existing code would make a D-Bus call to read the Compatible
interface provided by entity-manager in order to have it when creating a
PEL from the PEL message registry. However, early in the boot there are
attempts to create PELs before entity-manager has put its interfaces on
D-Bus, causing the message registry parsing to fail.
The fix is to continue on even if that interface isn't present. The
caller will need to beware that if they want to create PELs early in the
boot that they can't refer to any system names in the PEL message
registry entry for that error.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ie488786675c33107402b1e19cccfbebc0e73f9f7
diff --git a/extensions/openpower-pels/src.cpp b/extensions/openpower-pels/src.cpp
index 5f6f121..9257036 100644
--- a/extensions/openpower-pels/src.cpp
+++ b/extensions/openpower-pels/src.cpp
@@ -855,10 +855,19 @@
if (regEntry.callouts)
{
+ std::vector<std::string> systemNames;
+
try
{
- auto systemNames = dataIface.getSystemNames();
+ systemNames = dataIface.getSystemNames();
+ }
+ catch (const std::exception& e)
+ {
+ // Compatible interface not available yet
+ }
+ try
+ {
registryCallouts = message::Registry::getCallouts(
regEntry.callouts.value(), systemNames, additionalData);
}