Bug #27302
closed
Filter is only evaluate when planning not running recurring job
Added by Dirk Götz almost 6 years ago.
Updated almost 6 years ago.
Description
I want to run Ansible every 30 minutes using recurring job logic from REX, but the filter is evaluated when the job is planned and not when it is executed, so future systems will not be included. This makes the feature more or less useless to me.
As a simple reproducer:
1. Create a job like SSH command id with hosts in active state when no host is active and a scheduling like */5 * * * *.
2. Mark a host as active with something like puppet apply -e "notify{'foo':}".
3. Next run still runs on 0 systems.
Found in Foreman Remote Execution 1.8.0 with Katello 3.12.0
Was this with dynamic query?
Thanks, Adam, for giving me the right key word. Now I found the dynamic query option.
But this makes me wonder from a usability perspective if we have the right default or if hidding this in advanced options when sticking with the static query as default makes sense or should it be more prominent for future and recurring execution?
Maybe taking this to discourse and gathering more user feedback would be a good course of action?
I don't mind static being the default, to me it makes sense as it behaves in a wysiwyg way.
Anyway, can I mark it as resolved?
- Status changed from New to Resolved
I marked it as resolved and will open an RFC for it on community.
- Assignee set to Dirk Götz
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/419 added
- Fixed in Releases foreman_remote_execution 1.8.3 added
Also available in: Atom
PDF