Feature #2372
components in a higher level should not start if check on lower level fails
| Status: | Closed | Start date: | 08/28/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | R. Haschke | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
In the scenario when components are started in a group, with different levels.
If a component of a lower level (-L 0) does not start correctly, it could be nice to not started the dependent higher level components (-L 1 ).
Currently there is a bug that causes this to happen if the lower level component dies, but not if the check function fails.
A nicely running component with a failed check function should not be considered ok for next level components to start imho
History
#1 Updated by R. Haschke over 8 years ago
- Status changed from New to Resolved
Starting several components (by group, level, or all) should stop when a component fails.
That only worked accidentally, when the component's screen session closed,
and the component was explicitly stopped due to component monitoring.
However, when the screen didn't failed, but only the component's test,
starting further components simply continued.
Solved the issue by
- not stopping a component when its screen session closes
- setting WAIT_BREAK after a timeout in wait_ready()
#2 Updated by R. Haschke over 8 years ago
- Status changed from Resolved to Closed