Project

General

Profile

Bug #16559

checksum changes not propagated to new content view publishes

Added by Justin Sherrill over 2 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

1. Create a repo, set its checksum to sha256
2. create a content view with the repo added
3 Create a filter to filter out 1 package from the repo
4. Publish the content view
5. Change the repo to sha1
6. Republish the content view

check the content view to ensure that the repo in the content view was published with sha1

Associated revisions

Revision 46b580cf (diff)
Added by Justin Sherrill over 2 years ago

Fixes #16559 - propagate repo info to cv copies (#6322)

History

#1 Updated by Justin Sherrill over 2 years ago

  • Bugzilla link set to 1288656

#2 Updated by Justin Sherrill over 2 years ago

Actually the above workflow will not suffice. The only way to see the affect is with a capsule sync, or by examining the pulp repo distributors manually.

#3 Updated by The Foreman Bot over 2 years ago

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

#4 Updated by Justin Sherrill over 2 years ago

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

#5 Updated by Justin Sherrill over 2 years ago

  • Legacy Backlogs Release (now unused) set to 162

Also available in: Atom PDF