-
Type:
Bug
-
Status: Done
-
Priority:
(None)
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.7.1, 3.0.0, 2.6.2, 3.0.0-report
-
Labels:
-
Days in progress:0
On any error while handling a D-Bus request from the client side, the request itself is never replied, and eventually just times out.
root@eecee596ebbe:/# dbus-send --system --print-reply --dest=io.mender.AuthenticationManager /io/mender/AuthenticationManager io.mender.Authentication1.GetJwtToken Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In the current released interfaces (only Authentication1) this is extremely unlikely to happen, but on the new interfaces we are developing (Update1) will happen simply when validating user parameters.