Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.6.0
-
None
Description
This occurs when status command response is received after start of next stage which modifies sch state (quite often on starting services during install).
- status command is sent to agent (happens every 60 seconds)
- start commands are scheduled, generated event which move sch from INSTALLED to STARTING
- status command response received from agent. sch status directly set to INSTALLED bypassing state machine
- All subsequent task reports from agent trigger InvalidTransitionException, as OP_INPROGRESS event tries to do STARTING -> STARTING transition.
- However at task end we support INSTALLED -> STARTED transition for STARTED event. So tasks finish normally.
Attachments
Attachments
Issue Links
- links to