Description of problem: During either an upgrade, or during a lapse in subscriptions due to a renewal, the sync_plans for Red Hat Satellite stopped communicating with foreman. This case is a spin-off from BZ#1430836 which was determined to be a different issue relating mostly to invalid certificates. This affected all sync plans on the Satellite, and even newly created sync plans fail to execute. Version-Release number of selected component (if applicable): Currently Red Hat Satellite 6.2.10 How reproducible: Unknown Actual results: The sync status in the UI never gets updated after the sync plans are expected to run. There are no foreman tasks being created as a result of a sync plan execution. Expected results: Sync plans run on schedule, create the foreman tasks, and update the sync status page with results. Additional info: - Not using deferred (lazy) sync. - If a single repo is told to sync manually, it succeeds. - If the sync plan is executed manually (via bulk task) on sync plan page, it succeeds.
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
I tried to reproduce on 6.2.12 with pulp-server-2.8.7.15-1.el7sat.noarch but sync plan worked all the time. So I am moving this to VERIFIED.
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/RHBA-2017:2803