Project

General

Profile

Actions

Bug #19605

closed

errata applicability are not regenerated on re-registered client (with the same repos)

Added by Justin Sherrill almost 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Errata Management
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

1. Create a product
2. Create a repo with some errata that can be applicable
3. Register a system and assign the product with errata, run sub-man refresh, yum repolist
4. Notice errata are applicable
5. re-register the client using 'subscription-manger register --force'
6. Assign it to the same product
7. run sub-man refresh adn yum repolist
8. errata do not show up

Actions #1

Updated by The Foreman Bot almost 7 years ago

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

Updated by Justin Sherrill almost 7 years ago

  • Bugzilla link set to 1454352
Actions #3

Updated by Justin Sherrill almost 7 years ago

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

Updated by Justin Sherrill almost 7 years ago

  • translation missing: en.field_release set to 250
Actions #5

Updated by Justin Sherrill almost 7 years ago

  • translation missing: en.field_release changed from 250 to 258
Actions #6

Updated by Eric Helms almost 7 years ago

  • translation missing: en.field_release changed from 258 to 267
Actions #7

Updated by Eric Helms almost 7 years ago

  • translation missing: en.field_release changed from 267 to 258
Actions

Also available in: Atom PDF