Fix regression in CrashDump
25b54db introduced a bug where CrashDump was not looking at the correct
option. Was using BMCWEB_REDFISH_DUMP_LOG instead of the correct
BMCWEB_REDFISH_CPU_LOG.
This was caught in CI by a system that doesn't have CrashDump enabled
but was hitting:
1 failGet errors in /redfish/v1/Systems/system/LogServices/Crashdump
Tested: None. Visually inspected and this matches
redfish-core/src/redfish.cpp.
Change-Id: Ia6e72e5bbeaaa246fbbc5bcb2a525062e63d7d29
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
diff --git a/redfish-core/lib/log_services.hpp b/redfish-core/lib/log_services.hpp
index 1453a4b..058852c 100644
--- a/redfish-core/lib/log_services.hpp
+++ b/redfish-core/lib/log_services.hpp
@@ -1313,7 +1313,7 @@
logServiceArray.emplace_back(std::move(dumpLog));
}
- if constexpr (BMCWEB_REDFISH_DUMP_LOG)
+ if constexpr (BMCWEB_REDFISH_CPU_LOG)
{
nlohmann::json::object_t crashdump;
crashdump["@odata.id"] =