Project

General

Profile

Bug #21493

Refreshing a manifest should no longer force regeneration of Entitlement Certificates

Added by Barnaby Court over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Subscriptions
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

The workaround for an upstream Candlepin bug originally applied with issue #17970 is no longer necessary. Specifically app/models/katello/glue/provider.rb:66[owner_regenerate_upstream_certificates] is no longer necessary as part of a manifest refresh as any entitlement certificates that need updating are automatically marked as dirty during the account refresh process and will be regenerated during the manifest export automatically. Leaving this code in place will result in much longer manifest export times for customers that have large numbers of pools as it forces a regeneration of all entitlements whether or not there are changes.

Associated revisions

Revision f79dc9dc (diff)
Added by Jonathon Turel over 4 years ago

Fixes #21493 - Don't blindly regen certs on manifest refresh

History

#1 Updated by Justin Sherrill over 4 years ago

  • Difficulty set to easy
  • Legacy Backlogs Release (now unused) set to 284
  • Target version set to 232
  • Assignee set to Jonathon Turel
  • Category set to Subscriptions

#2 Updated by The Foreman Bot over 4 years ago

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

#3 Updated by Anonymous over 4 years ago

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

Also available in: Atom PDF