dbus: removed unnecessary is_method_error calls
The sdbusplus `call` methods throw an exception in all cases, so there
is no reason to also check the message reply for `is_method_error`
conditions.
https://github.com/openbmc/sdbusplus/blob/c67e1e8730a2d3dcb155b21ced735ee188e8ea7f/include/sdbusplus/bus.hpp#L283
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id5697e4186e3a6794292c736e0c3b248c8b57b82
diff --git a/dbusUtils.hpp b/dbusUtils.hpp
index 7f6f3f3..93898a3 100644
--- a/dbusUtils.hpp
+++ b/dbusUtils.hpp
@@ -30,13 +30,7 @@
try
{
auto msg = bus.call(mapper);
-
msg.read(resp);
- if (msg.is_method_error())
- {
- log<level::ERR>("Error in mapper call");
- elog<InternalFailure>();
- }
}
catch (const sdbusplus::exception::SdBusError& ex)
{
@@ -74,16 +68,6 @@
method.append(intf, property);
auto msg = bus.call(method);
-
- if (msg.is_method_error())
- {
- log<level::ERR>("Failed to get property",
- entry("PROPERTY=%s", property.c_str()),
- entry("PATH=%s", path.c_str()),
- entry("INTERFACE=%s", intf.c_str()));
- elog<InternalFailure>();
- }
-
msg.read(value);
return std::get<T>(value);