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 1446712 - Lock is used to dispatch applicability calculation for a consumer
Summary: Lock is used to dispatch applicability calculation for a consumer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-28 16:24 UTC by Satellite Program
Modified: 2021-04-06 17:52 UTC (History)
16 users (show)

Fixed In Version: pulp-2.13.2,tfm-rubygem-katello-3.4.5.49-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1255901
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19055 0 Normal Closed runcible should support generate applicability call for single consumer 2020-03-10 13:42:18 UTC
Foreman Issue Tracker 19076 0 Normal Closed use single-consumer call when regenerating applicability 2020-03-10 13:42:15 UTC
Foreman Issue Tracker 22034 0 Normal Resolved re-enable single consumer applicability regeneration 2020-03-10 13:42:19 UTC
Pulp Redmine 1173 0 Normal CLOSED - WONTFIX Content Applicability Regeneration for individual consumers is sent to a single worker 2017-04-28 17:07:29 UTC
Pulp Redmine 2793 0 High CLOSED - WORKSFORME applicable rpms only show up if at least one errata is applicable 2018-01-09 22:32:22 UTC
Pulp Redmine 2797 0 High CLOSED - CURRENTRELEASE Single consumer aplicability generation does not work unless profile already has applicability generated 2017-06-27 19:02:17 UTC

Comment 2 pulp-infra@redhat.com 2017-04-28 17:07:30 UTC 
The Pulp upstream bug status is at CLOSED - WONTFIX. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2017-04-28 17:07:35 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5 pulp-infra@redhat.com 2017-06-27 19:02:18 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 6 pulp-infra@redhat.com 2017-06-27 19:02:23 UTC 
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 7 Peter Ondrejka 2017-10-05 13:15:32 UTC 
verified in satellite-6.3.0-19.0.beta.el7sat.noarch using both steps from https://bugzilla.redhat.com/show_bug.cgi?id=1255901#c14 and from https://bugzilla.redhat.com/show_bug.cgi?id=1255901#c17
Comment 9 Roman Plevka 2017-12-19 15:49:55 UTC 
failing this due this is still a problem on 6.3.0-29

- regenerate_applicability tasks for multiple consumers are scheduled to a single worker, thus being processed serially.

see comment#8
Comment 10 pulp-infra@redhat.com 2017-12-19 16:03:28 UTC 
Requesting needsinfo from upstream developer ttereshc because the 'FailedQA' flag is set.
Comment 12 Tanya Tereshchenko 2017-12-20 15:09:09 UTC 
All Pulp issues are closed
Comment 14 pulp-infra@redhat.com 2017-12-20 19:02:55 UTC 
Requesting needsinfo from upstream developer ttereshc because the 'FailedQA' flag is set.
Comment 16 pulp-infra@redhat.com 2018-01-05 14:32:19 UTC 
Requesting needsinfo from upstream developer ttereshc because the 'FailedQA' flag is set.
Comment 17 pulp-infra@redhat.com 2018-01-09 22:02:29 UTC 
Requesting needsinfo from upstream developer ttereshc because the 'FailedQA' flag is set.
Comment 18 pulp-infra@redhat.com 2018-01-09 22:32:23 UTC 
The Pulp upstream bug status is at CLOSED - WORKSFORME. Updating the external tracker on this bug.
Comment 19 pulp-infra@redhat.com 2018-01-09 22:32:29 UTC 
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 21 Roman Plevka 2018-01-24 10:56:40 UTC 
VERIFIED
on sat6.3.0-33

katlelo now uses the correct endpoint, making pulp schedule the regenerate_applicability tasks to multiple workers:


pulp_tasks:
- exception: 
  task_type: pulp.server.managers.consumer.applicability.regenerate_applicability_for_consumers
  _href: "/pulp/api/v2/tasks/dbf3b9f6-eb9f-4fa2-af16-6104a57edc30/"
  task_id: dbf3b9f6-eb9f-4fa2-af16-6104a57edc30
  tags:
  - pulp:action:consumer_content_applicability_regeneration
  finish_time: 
  _ns: task_status
  start_time: '2018-01-24T10:52:21Z'
  traceback: 
  spawned_tasks: []
  progress_report: {}
  queue: reserved_resource_worker-2.eng.bos.redhat.com.dq
  state: running
  ...



pulp_tasks:
- exception: 
  task_type: pulp.server.managers.consumer.applicability.regenerate_applicability_for_consumers
  _href: "/pulp/api/v2/tasks/66674bc4-eac4-464a-9c55-965b5abc2b31/"
  task_id: 66674bc4-eac4-464a-9c55-965b5abc2b31
  tags:
  - pulp:action:consumer_content_applicability_regeneration
  finish_time: 
  _ns: task_status
  start_time: '2018-01-24T10:52:22Z'
  traceback: 
  spawned_tasks: []
  progress_report: {}
  queue: reserved_resource_worker-1.eng.bos.redhat.com.dq
  state: running
  ...
Comment 22 Satellite Program 2018-02-21 16:54:37 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:0336
Note You need to log in before you can comment on or make changes to this bug.