Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1882690 +++
On foreman 1.24.3 it works as usual.
But if I load the same manifest on a foreman 2.1 I only get to see a few versions of repos, sometimes only some versions are missing, sometimes every version.
I also noticed that the time until the results appear is much longer. Before it was 5 seconds now it is 60 seconds until the contents are displayed.
No log information found.
One Pic is from Foreman 1.24 the other with less versions is from Foreman 2.1
!Screenshot_20200820_165449.png!
!Screenshot_20200820_165514.png!
--- Additional comment from on 2020-09-25T10:41:43Z
Created from redmine issue https://projects.theforeman.org/issues/30694
--- Additional comment from on 2020-09-25T10:41:45Z
Upstream bug assigned to jsherril
--- Additional comment from on 2020-09-25T10:49:38Z
Note that this is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1838917 but after applying that fix, things were still not working properly.
The behavior seen was slightly different, and only happened with an http proxy. It may not be 100% reproducible.
To reproduce:
1. Install satellite 6.8.
2. Add manifest file.
3- Configure a global content proxy
4- Expand a bunch of repos (rhel 6, rhel 7, etc...) the more resulting repos the better. Make sure all expected releases show up
--- Additional comment from on 2020-09-28T20:05:13Z
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30694 has been resolved.
--- Additional comment from on 2020-11-12T21:14:53Z
*** Bug 1894441 has been marked as a duplicate of this bug. ***
--- Additional comment from on 2020-11-16T23:15:40Z
Satellite 6.8.1 is due out soon and we are offering a hotfix that is applicable to Satellite 6.8.1.
*** Satellite 6.8.1 Hotfix Available ***
1) Download tfm-rubygem-katello-3.16.0.13-2.HOTFIXRHBZ1882690.el7sat.noarch.rpm from this bugzilla to your Satellite
2) stop services:
satellite-maintain service stop
3) Install:
rpm -Uvh tfm-rubygem-katello-3.16.0.13-2.HOTFIXRHBZ1882690.el7sat.noarch.rpm
4) restart:
satellite-maintain service start
5) resume operations
--- Additional comment from on 2020-11-16T23:16:28Z
Created attachment 1729917[details]
tfm-rubygem-katello-3.16.0.13-2.HOTFIXRHBZ1882690.el7sat.noarch.rpm
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 (Satellite 6.8.2 Async Bug Fix Update), 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/RHBA-2020:5467