Project

General

Profile

Actions

Bug #22991

closed

recurring job having wild card filter start running against newly added hosts

Added by Lukas Pramuk over 6 years ago. Updated about 6 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

When recurring job has wild card filter "." it starts running against newly added hosts that are visible to the user who set up the job.
Filter in next job iterations is possibly evaluated again and again therefore it can pick up new hosts that appeared within the scope of the user who scheduled the job.

foreman-1.18.0-0.develop.201803202124git6ed2083.el7.noarch
tfm-rubygem-foreman_remote_execution-1.4.6-1.fm1_18.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.1-1.fm1_18.el7.noarch
rubygem-smart_proxy_remote_execution_ssh-0.1.5-1.el7.noarch
katello-3.7.0-1.nightly.el7.noarch

1) setup recurring job with filter '.'
2) add hosts
3) check next instances of the job running against more hosts than was in 1st instance of the job


Related issues 1 (0 open1 closed)

Is duplicate of Foreman Remote Execution - Bug #20285: Each run of recurring job invocation resolves static targeting againClosedAdam RuzickaActions
Actions #1

Updated by Adam Ruzicka about 6 years ago

  • Is duplicate of Bug #20285: Each run of recurring job invocation resolves static targeting again added
Actions #2

Updated by Adam Ruzicka about 6 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF