-
Bug
-
Resolution: Done
-
Major
-
6.11.4
Description of problem:
When restarting just foreman service, any new task invoked after the restart gets stuck in planned/pending forever.
Version-Release number of selected component (if applicable):
6.11.4
6.12
How reproducible:
100%
Steps to Reproduce:
1. Run a REX job (say execute "date command) just to see it works well.
2. satellite-maintain service restart --only=foreman.service
3. Repeat 1
4. satellite-maintain service restart --only=dynflow-sidekiq@orchestrator,dynflow-sidekiq@worker-1,dynflow-sidekiq@worker-2,dynflow-sidekiq@worker-hosts-queue-1
5. Repeat 1
Actual results:
3. gets stuck forever
5. jobs+tasks start to work again (including those invoked in 3)
Expected results:
3. tasks are completed as usual
Additional info:
Observation: Just restarting dynflow orchestrator service is not sufficient.
- is duplicated by
-
SAT-14727 Warning: Stopping foreman.service, but it can still be activated by: foreman.socket, when calling foreman-maintain service restart
-
- Closed
-
- external trackers