Bug 1498560

Summary:	deprecate/remove force_post_sync_actions
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.11	CC:	bbuckingham, egolov, fcami, mvanderw
Target Milestone:	6.4.0	Keywords:	FieldEngineering, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:13:57 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:

Description Chris Duryee 2017-10-04 15:56:48 UTC

Description of problem:

Katello has a setting for 'force_post_sync_actions'. When this is set, all actions are performed even if there was no change in content.

This setting was originally added as a debugging aid, but has since been replaced by the 'skip-metadata-check' hammer flag. The hammer flag is preferred since it is not permenant. If 'force_post_sync_actions' is set, its easy to forget that it's set and then have mysterious performance issues.

We should be able to remove this setting entirely, so users have to set 'skip-metadata-check' to force post-sync actions.

Comment 3 Samir Jha 2018-03-27 15:45:53 UTC

Created redmine issue http://projects.theforeman.org/issues/23033 from this bug

Comment 4 Satellite Program 2018-04-10 14:13:44 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23033 has been resolved.

Comment 5 Peter Ondrejka 2018-06-11 12:38:52 UTC

Verified on Sat 6.3 snap 6

Comment 6 Peter Ondrejka 2018-07-09 12:58:21 UTC

Verified in sat 6.4 snap 11, the setting is no longer present

Comment 7 Bryan Kearney 2018-10-16 19:13:57 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