Hide Forgot
Description of problem: Repository syncs will run even if pulp services are stopped Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. systemctl stop pulp_workers.service pulp_celerybeat.service pulp_resource_manager.service 2. Try to sync a repo 3. Repo will be stuck in "polling" stage Actual results: Repo will be stuck in "polling" stage Expected results: An error occurs in the task
Created redmine issue http://projects.theforeman.org/issues/16542 from this bug
Upstream bug assigned to jomitsch
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16542 has been resolved.
Still reproducible in Satellite 6.3 snap 6: satellite-6.3.0-6.1.beta.el7sat.noarch katello-3.2.0-3.rc3.el7.noarch With pulp_workers and pulp_celerybeat stopped, the sync task stays in pending state (see attached screenshot). No errors shown on the Errors tab. /var/log/foreman/production.log keeps rolling: 2016-11-28 04:49:56 c6e719e4 [app] [I] Started POST "/foreman_tasks/api/tasks/bulk_search" for 2620:52:0:2282:2ad2:44ff:fef2:d8d2 at 2016-11-28 04:49:56 -0500 2016-11-28 04:49:56 c6e719e4 [app] [I] Processing by ForemanTasks::Api::TasksController#bulk_search as JSON 2016-11-28 04:49:56 c6e719e4 [app] [I] Parameters: {"searches"=>[{"type"=>"task", "task_id"=>"667bab5d-dee0-4584-88c2-6374c1341a09", "search_id"=>"1"}], "task"=>{}} 2016-11-28 04:49:56 c6e719e4 [app] [I] Completed 200 OK in 80ms (Views: 2.4ms | ActiveRecord: 1.7ms)
Created attachment 1225218 [details] screenshot-pending_task.png
I'm changing the component since this is not an issue with pulp, but an issue with katello's use of pulp.
Upstream bug component is Pulp
I just discussed this with the pulp team, there is a bug in pulp that will show a faulty status report, which is the reason the check in katello isn't working. To summarize the issue: pulp_celerybeat does the cleanup of worker entries in our database when they stop. If you stop pulp_celerybeat first, and then stop the workers, there's nobody around to clean up. So the records stay in the DB, and the status API might continue reporting that those workers exist. When an upstream bug is filed in pulp, we can associate it with this BZ
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. 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 ASSIGNED. 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.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
providing info for a test
Requesting needsinfo from upstream developer dkliban because 'FailQA' flag is set.
Requesting needsinfo from upstream developer daviddavis because 'FailQA' flag is set.
Clearing NEEDSINFO since it failed qa before I worked on it.
Requesting needsinfo from upstream developer dkliban because the 'FailedQA' flag is set.
Requesting needsinfo from upstream developer daviddavis because the 'FailedQA' flag is set.
Removing the trackers for backport tasks - not the intended workflow and breaks some automation
Confirmed that the sync properly errors when trying to sync it while pulp is turned off in snap-11.0 My steps were: 1. systemctl stop pulp_workers.service pulp_celerybeat.service pulp_resource_manager.service 2. I tried to sync a repo in the UI and received an error warning.
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:0336