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 1498560 - deprecate/remove force_post_sync_actions
Summary: deprecate/remove force_post_sync_actions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.2.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.4.0
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-04 15:56 UTC by Chris Duryee
Modified: 2019-11-05 23:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:13:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23033 0 Normal Closed deprecate/remove force_post_sync_actions 2020-07-30 12:07:00 UTC

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
Note You need to log in before you can comment on or make changes to this bug.