Bug 2227028 - re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages that are available.
Summary: re-synchronizing the repository whose sync had failed earlier, the Content Vi...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: 6.14.0
Assignee: Samir Jha
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-27 13:21 UTC by Aniket
Modified: 2023-08-17 18:29 UTC (History)
6 users (show)

Fixed In Version: rubygem-katello-4.9.0.10-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36622 0 Normal Closed Re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages... 2023-08-03 06:19:48 UTC
Red Hat Issue Tracker SAT-19213 0 None None None 2023-07-27 13:35:07 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.