Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
3.0.0-alpha2
-
None
-
None
-
Docs Required, Release Notes Required
Description
The node start command has a timeout, after which it treats the startup process as failed, and exits, without including the node in the list shown by the node list command.
It is possible that the node actually manages to start after the timeout, in which case the CLI tool and the user are not aware of the running node.
We need to revisit the node management approach in the CLI, so that we can avoid issues like this.