Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1589768 - Ansible REX job shall not update host Configuration status
Summary: Ansible REX job shall not update host Configuration status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.4.0
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-11 11:10 UTC by Lukas Pramuk
Modified: 2019-11-05 23:23 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-foreman_ansible-2.2.1-1.el7sat and foreman_ansible_core-2.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:12:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23879 0 Normal Closed Ansible REX job shall not update host Configuration status 2020-08-26 10:05:24 UTC

Description Lukas Pramuk 2018-06-11 11:10:21 UTC 
Description of problem:
Ansible REX job (contrary to Ansible Play Roles) shall not update host Configuration status.

The only job that shall update Configuration status is Ansible Play roles job

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

Steps to Reproduce:
1. Run Ansible Command job that fails
2. Check configuration status is changed to "Error"
3. Run Ansible Command job that succeeds
4. Check configuration status is changed to "Active"


Actual results:
Configuration status is updated by Ansible REX jobs

Expected results:
only Remote execution status is updated
Comment 2 Marek Hulan 2018-06-11 11:17:59 UTC 
also non "play roles" runs should not produce new configuration report
Comment 3 Marek Hulan 2018-06-11 11:18:27 UTC 
Created redmine issue http://projects.theforeman.org/issues/23879 from this bug
Comment 4 Satellite Program 2018-07-02 12:09:07 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23879 has been resolved.
Comment 5 Lukas Pramuk 2018-07-17 07:41:28 UTC 
FailedQA.

@satellite-6.4.0-10.beta.el7sat.noarch
tfm-rubygem-foreman_ansible-2.2.3-1.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.1.0-1.el7sat.noarch
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
ansible-2.6.1-1.el7ae.noarch

by manual reproducer described in comment#0

>>> cfg status is still changed accordingly to last REX job result
Comment 6 Marek Hulan 2018-07-19 12:34:34 UTC 
We only shipped newer foreman_ansible but not foreman_ansible_core which is the problem. New version of foreman_ansible_core has been release today.
Comment 7 Lukas Pramuk 2018-07-30 11:49:02 UTC 
VERIFIED.

@satellite-6.4.0-10.beta.el7sat.noarch (Snap13)
tfm-rubygem-foreman_ansible-2.2.4-1.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.1.1-1.el7sat.noarch
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
ansible-2.6.1-1.el7ae.noarch

by using manual reproducer described in comment#0:

>>> Both failing and succeeding REX don't change Configuration Status of the host

>>> While "Run Ansible roles" still changes Configuration Status of the host
Comment 8 Bryan Kearney 2018-10-16 19:12:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927
Note You need to log in before you can comment on or make changes to this bug.