Bug 2227028

Summary:	re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages that are available.
Product:	Red Hat Satellite	Reporter:	Aniket <amahindr>
Component:	Content Views	Assignee:	Samir Jha <sajha>
Status:	VERIFIED ---	QA Contact:	Cole Higgins <chiggins>
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.14.0	CC:	ahumbe, chiggins, iballou, pcreech, rlavi, sajha
Target Milestone:	6.14.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-katello-4.9.0.10-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Aniket 2023-07-27 13:21:10 UTC

Description of problem:

After re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages that are available.

Version-Release number of selected component (if applicable):
Satellite 6.14.0

How reproducible:

Steps to Reproduce:

1. Enabled the following repositories on Satellite 6.14.0 and added them to the Content View:

Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8
Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8
Red Hat Satellite Client 6 for RHEL 8 x86_64 RPMs

2. Published the Content View without synchronizing the repositories.

3. Performed a repository sync, and as a result, new packages were visible in the Content View. (new feature)

~~~
Updates available: Repositories and/or filters have changed.
~~~

4. Published a new version of the Content View.

5. However, upon verifying the sync status, I discovered that the AppStream sync had failed.

6. Re-synced the failed repository "Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8".

7. After verifying in the Content View, based on our new feature, it was expected to show new packages available. But I found that there were no new updates available.

8. But when I published another new version of the Content View, I found that there were new packages and erratas available.

Actual results:
After re-synchronizing the failed repository, in the Content View no new packages were available.

Expected results:
Re-synchronizing the failed repository should show new packages available in the Content View.

Comment 2 Samir Jha 2023-07-28 20:12:21 UTC

Created redmine issue https://projects.theforeman.org/issues/36622 from this bug

Comment 3 Bryan Kearney 2023-08-02 20:03:37 UTC

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