Bug 1695687

Summary:	Force yum metadata generate during CV publish
Product:	Red Hat Satellite	Reporter:	Samir Jha <sajha>
Component:	Content Views	Assignee:	Samir Jha <sajha>
Status:	CLOSED ERRATA	QA Contact:	Lai <ltran>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	bkearney
Target Milestone:	Released	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.10.0.42-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-14 19:57:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1664288, 1732066

Description Samir Jha 2019-04-03 15:26:59 UTC

As part of https://projects.theforeman.org/issues/25400, we removed the flag force_yum_metadata_regeneration. We need to modify the behavior of the same in CV publish to force metadata generate every time.

Comment 1 Samir Jha 2019-04-03 15:27:01 UTC

Created from redmine issue http://projects.theforeman.org/issues/26517

Comment 2 Samir Jha 2019-04-03 15:27:02 UTC

Upstream bug assigned to None

Comment 6 Brad Buckingham 2019-04-04 11:38:50 UTC

Moving to MODIFIED based upon the creation of the downstream MR.  The MR has also been reviewed/tested/ACKed.

Comment 8 Brad Buckingham 2019-04-05 12:54:09 UTC

*** Bug 1695686 has been marked as a duplicate of this bug. ***

Comment 10 Lai 2019-04-16 19:38:47 UTC

Steps to retest:

1. Add a repository and sync
2. Verify the checksum type on the repo.
3. Check the environment on capsule you intend to test with.
4. Add the repository to content view and publish, promote to an env tied to a capsule.
5. Sync the capsule.
6. Verify the checksum type is correct on synced cv repo on capsule.
7. Update the checksum type on the repo and sync the repo.
8. Re-publish/ re-promote to cv tied to capsule's environment.
8. Sync capsule
9. Verify that the checksum type is correctly updated  for the cv repo on the capsule.

Started off with sha256 and verified that it's both on satellite and capsule.  After updating the checksum to sha1, I verified that the satellite and capsule has sha1 on it.

Marking issue as verified.  Tested on 6.5.0_24

Comment 11 Bryan Kearney 2019-05-14 19:57:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:1222