Bug #7559
closedMentat 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š over 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š over 2 years ago
- Related to Feature #6928: Reconsider Mentat process management added
Updated by Pavel Kácha over 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.
Updated by Rajmund Hruška 19 days ago
- Assignee set to Rajmund Hruška
- Target version changed from Backlog to 2.13.1
So the only thing needed here is to mention systemctl stop mentat.service in the documentation?
Updated by Radko Krkoš 18 days ago
Rajmund Hruška wrote in #note-5:
So the only thing needed here is to mention
systemctl stop mentat.servicein the documentation?
Short: That would solve the issue for this specific case. Replacing usage of mentat-controller.py with systemctl everywhere in the documentation (and in the heads of administrators ).
For discussion: I guess mentat-controller.py should be able to enable/disable or start/stop the mentat services and it should be integrated with general system management tools - ideally there should be no difference in using mentat-controller.py and systemctl. Then of course, those would be redundant interfaces. This leads us again to #6928.
Updated by Rajmund Hruška 16 days ago
- Related to Bug #7758: Stopping mentat.service results in failure even though modules are stopped added
Updated by Rajmund Hruška 16 days ago
- Related to deleted (Bug #7758: Stopping mentat.service results in failure even though modules are stopped)
Updated by Rajmund Hruška 16 days ago
- Blocked by Bug #7758: Stopping mentat.service results in failure even though modules are stopped added