Bug #19055: runcible should support generate applicability call for single consumer - Runcible - Foreman

Actions

Copy link

Bug #19055

closed

runcible should support generate applicability call for single consumer

Added by Chris Duryee about 7 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Chris Duryee

Difficulty:

Triaged:

Bugzilla link:

1255901

Pull request:

https://github.com/Katello/runcible/pull/189

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Currently, runcible only supports making an applicability regen call where all of the UUIDs are passed in via POST. This works, but due to the way Pulp works, all of these calls get 'pinned' to the same worker. For example, if you make six calls with six different UUIDs (example: "[A]", "[B]", "[C]", ...), all six of these will get pinned to the same worker. This can make applicability regen very slow.

If you call the applicability regen differently, the call does not get pinned to a worker. See https://pulp.plan.io/issues/1173#note-12 for more detail.