Bug 1575017

Summary:	there is no option to change or disable out_of_sync interval
Product:	Red Hat Satellite	Reporter:	Jan Hutař <jhutar>
Component:	Ansible - Configuration Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	ehelms, mhulan
Target Milestone:	6.4.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman_ansible-2.1.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:26:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1449011

Description Jan Hutař 2018-05-04 14:30:39 UTC

Description of problem:
there is no option to change or disable out_of_sync interval in Administer -> Settings -> Ansible


Version-Release number of selected component (if applicable):
satellite-6.4.0-3.beta.el7sat.noarch
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.0.2-1.el7sat.noarch
tfm-rubygem-foreman_ansible-2.0.4-1.el7sat.noarch
ansible-2.4.2.0-2.el7.noarch


How reproducible:
always


Steps to Reproduce:
1. Check Administer -> Settings -> Ansible


Actual results:
There is no option to change or disable out-of-sync interval:

Administer > Settings > Ansible tab > Ansible out of sync disabled
Administer > Settings > Ansible tab > Ansible report timeout


Expected results:
Options are there and they works

Comment 4 jcallaha 2018-05-31 15:48:50 UTC

Verified in Satellite 6.4 Snap 5.

The 'Ansible report timeout' and 'Ansible out of sync disabled' setting are both present in the Setting->Ansible tab.

See attached screenshot

Comment 5 Bryan Kearney 2018-10-16 19:26:18 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