Project

General

Profile

Actions

Bug #36622

closed

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

Added by Samir Jha 12 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2227028

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.

Actions #1

Updated by The Foreman Bot 12 months ago

  • Status changed from New to Ready For Testing
  • Assignee set to Samir Jha
  • Pull request https://github.com/Katello/katello/pull/10668 added
Actions #2

Updated by Quinn James 12 months ago

  • Subject changed from Re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages that are available. to Re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages that are available.
  • Target version set to Katello 4.9.2
  • Triaged changed from No to Yes
Actions #3

Updated by The Foreman Bot 12 months ago

  • Fixed in Releases Katello 4.10.0 added
Actions #4

Updated by Samir Jha 12 months ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by William Clark 10 months ago

  • Fixed in Releases Katello 4.9.2 added
Actions #6

Updated by The Foreman Bot 10 months ago

  • Pull request https://github.com/Katello/katello/pull/10754 added
Actions #7

Updated by The Foreman Bot 10 months ago

  • Pull request deleted (https://github.com/Katello/katello/pull/10668, https://github.com/Katello/katello/pull/10754)
Actions #8

Updated by David Moore 10 months ago

  • Subject changed from Re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages that are available. to Re-synchronizing the repository whose sync had failed earlier, the Content View does not display new upgradable packages that are available
Actions

Also available in: Atom PDF