|Summary:||[RFE] ::Actions::Insights::EmailPoller to be automatically started on foreman-tasks startup, like e.g. LOCE is|
|Product:||Red Hat Satellite 6||Reporter:||Pavel Moravec <pmoravec>|
|Component:||Tasks Plugin||Assignee:||satellite6-bugs <satellite6-bugs>|
|Status:||NEW ---||QA Contact:||Jan Hutař <jhutar>|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Pavel Moravec 2017-10-23 08:20:28 UTC
Description of problem: In case ::Actions::Insights::EmailPoller task is stopped (due to whatever error or user (wrong) intervention), (re)starting foreman-tasks service should ensure re-spawning the task. This feature is already present for ListenOnCandlepinEevents (LOCE) task, as well as for MonitoQueue::Listener one. It should be available also for the last forever-running/pending task in Satellite. Version-Release number of selected component (if applicable): Sat 6.2.12 How reproducible: 100% Steps to Reproduce: 1. Somehow stop that task, e.g. manually Cancel it 2. service foreman-tasks restart 3. Check if that task is running Actual results: An instance of that task type is running or scheduled, most probably it is in stopped/error state. Expected results: An instance of that task type should be in scheduled/pending state. Additional info:
Comment 1 Adam Ruzicka 2017-10-23 08:22:27 UTC
Created redmine issue http://projects.theforeman.org/issues/21421 from this bug
Comment 2 Pavel Moravec 2017-10-23 08:28:10 UTC
Linking KCS with workaround.
Comment 5 Ivan Necas 2017-10-25 09:14:06 UTC
In that case, the tasks issue should describe the changes needed to be done one tasks side. Wouldn't the solution be insights using the same approach as LOCE?
Comment 6 Adam Ruzicka 2017-11-16 13:15:56 UTC
(In reply to Ivan Necas from comment #5) > In that case, the tasks issue should describe the changes needed to be done on tasks side. Makes sense, I'll file a new BZ which will block this one and turn this one over to Insights. > Wouldn't the solution be insights using the same approach as LOCE? Not really, LOCE and EQM should be running all the time. IEP is different, it should be triggered once a week and do some kind of one-shot action. We could convert it to an always-running action which would be suspended most of the time but I think it would cause more trouble than its worth.
Comment 7 Adam Ruzicka 2017-11-29 08:50:40 UTC
Created another BZ to handle things on tasks side, leaving this BZ for changes which would need to go into insights.