ContainerStarted signal should always be produced |
|||
Issue descriptionCurrently if you invoke StartContainer on concierge and the container is already running, the D-Bus signal for ContainerStarted will not be sent. This should be fixed so that it is always sent in response to that call. Related to this, if you invoke StartContainer on concierge in synchronous mode, that call should not return until the gRPC call from Garcon has come back indicating the container is fully started.
,
Apr 5 2018
The ContainerStarted signal fix was already done in: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/996772 so this will only be ensuring garcon is started up before StartContainer returns in synchronous mode.
,
Apr 6 2018
Obsolete...we decided to do this a different way with only doing async ContainerStarted calls and then using a tri-state return value to know when no signal will be received.
,
May 17 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jkardatzke@chromium.org
, Apr 4 2018