Project

General

Profile

Bug #19076

use single-consumer call when regenerating applicability

Added by Chris Duryee about 2 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

In http://projects.theforeman.org/issues/19055, a new API call is exposed to Pulp which allows applicability regen to not pin to a particular worker.

If only one consumer UUID is being updated, Katello should use this call instead of the multi-UUID call.

Associated revisions

Revision 59c58a8e (diff)
Added by Chris Duryee about 2 years ago

Fixes #19076 - use new runcible call for applicability

The previous consumer regen call would 'pin' to a single worker0.

Instead, use an API call to Pulp that can be spread across multiple
workers. Note that this requires
https://github.com/Katello/runcible/pull/189 to work.

I had to rename `name` to `consumer_name` to work around a tricky
issue. There was an interaction between minitest and VCR where it
would see a var named `name` in a test class, get confused, and pass
all the tests.

[0] https://pulp.plan.io/issues/1173#note-12

History

#1 Updated by The Foreman Bot about 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/6708 added

#2 Updated by Justin Sherrill about 2 years ago

  • Legacy Backlogs Release (now unused) set to 211

#3 Updated by Chris Duryee about 2 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by The Foreman Bot about 2 years ago

  • Pull request https://github.com/Katello/katello/pull/6730 added

Also available in: Atom PDF