Bug 1981434

Summary:	After upgrade puppet content repository count still visible in products details page.
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Repositories	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	Danny Synk <dsynk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	ahumbe, dsynk, jsherril, pcreech, tbrisker
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:12:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Devendra Singh 2021-07-12 14:30:16 UTC

Description of problem: After upgrade puppet content repository count still visible in UI.


Version-Release number of selected component (if applicable):
6.10 Snap8

How reproducible:
always

Steps to Reproduce:
1. Prepare the 6.9.z setup using the upgrade template.
2. Checked the repository list and found all the puppet-related contents are available there.
3. Run the pre-migration steps before running the upgrade for 6.10 snap8.
4. Run the pulp migration and it completes successfully.
5. Run the upgrade from 6.9 to 6.10 and it completes successfully.
6. check the puppet related repository and find all the repository  removes after the upgrade
7. The count of puppet repository still showing their value.

Actual results:
Repository count of puppet product contents remains the same.

Expected results:

Repository count should be changed to zero

Additional info:

Comment 2 Justin Sherrill 2021-07-22 15:50:28 UTC

This likely has the same root cause as this: https://bugzilla.redhat.com/show_bug.cgi?id=1978571

Comment 3 Bryan Kearney 2021-07-22 15:56:38 UTC

Upstream bug assigned to jsherril

Comment 4 Bryan Kearney 2021-07-22 15:56:41 UTC

Upstream bug assigned to jsherril

Comment 5 Bryan Kearney 2021-07-31 00:01:14 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33058 has been resolved.

Comment 8 Danny Synk 2021-08-24 17:50:08 UTC

Verified on Satellite 6.10, snap 14.

Steps to Test:
1. Deploy Satellite 6.9.5, snap 2.
2. Create a new product.
3. Create a Puppet repository in the new product.
4. Upload a Puppet module to the repository.
5. Migrate from Pulp 2 to Pulp 3:

# satellite-maintain prep-6.10-upgrade
# satellite-maintain content prepare

6. Upgrade from Satellite 6.9 to 6.10.
7. Check the Content > Products page of the Satellite webUI and the output of `hammer repository list`.

Expected results:
The Puppet repository is not present in the hammer output. On the Content > Products page of the webUI, the "Repositories" column has a value of 0 for the new product. The Content > Products > [new product] > Details page has a value of 0 for the "Number of Repositories" field. The Puppet repository is no longer present on the Content > Products > [new product] > Repositories page.

Actual Results:
The Puppet repository is not present in the hammer output. On the Content > Products page of the webUI, the "Repositories" column has a value of 0 for the new product. The Content > Products > [new product] > Details page has a value of 0 for the "Number of Repositories" field. The Puppet repository is no longer present on the Content > Products > [new product] > Repositories page.

Comment 11 errata-xmlrpc 2021-11-16 14:12:34 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 (Moderate: Satellite 6.10 Release), 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-2021:4702