Bug 2233753 - Recurring ansible jobs on Hostgroup do not run on client VMs which are added to the hostgroup after the creation of the recurring jobs
Summary: Recurring ansible jobs on Hostgroup do not run on client VMs which are added ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: 6.12.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-23 09:25 UTC by soham
Modified: 2023-09-02 13:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19700 0 None None None 2023-09-02 13:01:59 UTC

Description soham 2023-08-23 09:25:09 UTC
Description of problem:
Recurring ansible jobs on Hostgroup do not run on client VMs which are added to the hostgroup after the creation of the recurring jobs

Version-Release number of selected component (if applicable):

Satellite 6.11+

How reproducible:
Always


Steps to Reproduce:
1. Create a hostgroup with one client.

2. Click on Infrastructure -> Hostgroups -> Dropdown beside nest for the concerned hostgroup -> configure ansible job

3. Set up a recurring job to run every hour.

4. After atleast 1 hour, add another host to this hostgroup.

Actual results:

The recurring jobs get scheduled with only 1 host even after adding a 2nd host.

Expected results:

The recurring jobs should get scheduled on 2 hosts after 2nd host is added.

Additional info:

Comment 1 Adam Ruzicka 2023-08-24 08:54:46 UTC
The job stood up this way uses a static targeting. Static targeting is resolved once and then the result is reused so that changes to the hostgroup itself do not get reflected. It would probably make sense to kick the job off with dynamic targeting instead.

As a workaround, when setting up the ansible job, there's a line saying "For more advanced scheduling options view remote execution page" with a link. If you follow that link, you'll be able to flip the targeting type to dynamic yourself.


Note You need to log in before you can comment on or make changes to this bug.