PEL: Remove 'no_vpd_for_fru' maintenance procedure
This procedure was being used in a callout when the location code could
not be found on an inventory item. The code was changed to just not add
a callout in this case.
This was done for the following reasons:
1) There's no expected reason that the inventory would be missing a
location code for a valid inventory path.
2) There wasn't a way to give a hint to the end user about what the
callout should be in that case. Usually maintenance procedures should
have steps one can take to still do the appropriate replacement.
3) Because of 1), this case indicates a bad inventory path passed in by
the caller. Theoretically there is a way to have a 'bmc_code'
callout, but that wouldn't be appropriate to add in this log since
the intent of this one is for another problem.
3a) There is no way to create a new error log from inside a PEL section,
and I don't think this one case warrants coming up with a way to do
so.
4) The inventory path in question is still being added into a UserData
section so that development can debug it.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I0757080f04942807cc34029d8667387db6b959fe
diff --git a/extensions/openpower-pels/src.cpp b/extensions/openpower-pels/src.cpp
index b3e3e89..a6498af 100644
--- a/extensions/openpower-pels/src.cpp
+++ b/extensions/openpower-pels/src.cpp
@@ -878,12 +878,24 @@
": " + e.what();
addDebugData(msg);
- callout = std::make_unique<src::Callout>(CalloutPriority::high,
- "no_vpd_for_fru");
+ // Don't add a callout in this case, because:
+ // 1) With how the inventory is primed, there is no case where
+ // a location code is expected to be missing. This implies
+ // the caller is passing in something invalid.
+ // 2) The addDebugData call above will put the passed in path into
+ // a user data section that can be seen by development for debug.
+ // 3) Even if we wanted to do a 'no_vpd_for_fru' sort of maint.
+ // procedure, we don't have a good way to indicate to the user
+ // anything about the intended callout (they won't see user data).
+ // 4) Creating a new standalone event log for this problem isn't
+ // possible from inside a PEL section.
}
- createCalloutsObject();
- _callouts->addCallout(std::move(callout));
+ if (callout)
+ {
+ createCalloutsObject();
+ _callouts->addCallout(std::move(callout));
+ }
}
std::vector<message::RegistryCallout>