Replace call_noreply() with call()
openbmc/phosphor-state-manager#4 tracks an intermittent issue that is
being hit in hardware CI. The root cause is not yet known but this
commit will help collect some more information on the cause of the
failure.
It has been noted that the only applications which hit this type of
failure are using the call_noreply() interface. Other applications
running at the same time as the chassis program are doing the exact same
call to systemd, but using the call() interface and not hitting this
timeout issue. This commit will provide some more information on whether
its related to the call()/call_noreply() interface.
Change-Id: Ifa9a2bd72ccb51050a6d7d553fdcd3d8d9f89b83
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed