Enhance log traces related to PCIe association errors
When Redfish PCIeDevice GET fails due to the association error,
sometimes it may be difficult to debug the root cause as bmcweb log
entries do not show the related dbus object paths.
This commit is to enhance ffdc log traces to show dbus object paths if
the association is in error.
The areas of the changes are:
- the association error between pcie device to pcieSlot
Tested:
- Redfish Service Validator runs and passes
Change-Id: I507260c38d7b7ba735832b470122b86967c22343
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
diff --git a/redfish-core/lib/pcie.hpp b/redfish-core/lib/pcie.hpp
index db3b945..090fb95 100644
--- a/redfish-core/lib/pcie.hpp
+++ b/redfish-core/lib/pcie.hpp
@@ -255,6 +255,10 @@
BMCWEB_LOG_ERROR(
"PCIeDevice {} is associated with more than one PCIeSlot: {}",
pcieDevicePath, endpoints.size());
+ for (const std::string& slotPath : endpoints)
+ {
+ BMCWEB_LOG_ERROR("Invalid PCIeSlotPath: {}", slotPath);
+ }
messages::internalError(asyncResp->res);
return;
}