Bug #7559
openMentat import pipeline running after reboot while disabled
0%
Description
The DB upgrade procedure, as described in #7555, allows for reboot in step 9, if the circumstances require it. During execution on mentat-hub
, after the reboot, the Mentat's import pipeline (the daemons) were running. No data was actually imported as the warden-filer
was disabled at systemctl
level (and the issue described in #7121 also surfaced).
In step 1, Mentat is stopped and disabled using mentat-controller.py
, so there seems to be some inconsistency. Should those two steps actually be enough to prevent the pipeline from running?
Setting low priority as this is actually a very rare scenario.
Related issues
Updated by Radko Krkoš about 2 years ago
- Assignee set to Jan Mach
- To be discussed changed from Yes to No
Mek, see the last question. Any ideas?
Updated by Radko Krkoš about 2 years ago
- Related to Feature #6928: Reconsider Mentat process management added
Updated by Pavel Kácha about 2 years ago
Seems this is wanted behavior - stop stops Mentat daemons, disable stops cronjobs.
For disabling starting up after reboot, systemctl disable is needed. Would be fine to update docs.