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.
Bug 1838917 - Repositories are not showing their available Release versions due to a low default db pool size
Summary: Repositories are not showing their available Release versions due to a low de...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dynflow
Version: 6.8.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
: 1867934 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-22 04:16 UTC by Devendra Singh
Modified: 2021-01-08 13:11 UTC (History)
9 users (show)

Fixed In Version: tfm-rubygem-dynflow-1.4.7
Doc Type: Known Issue
Doc Text:
Repositories are not showing their available release versions due to a low default db pool size
Clone Of:
Environment:
Last Closed: 2020-10-27 13:02:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
repository listed version with-proxy (32.04 KB, image/png)
2020-05-22 04:16 UTC, Devendra Singh 		no flags Details
repository listed version without http-proxy (20.77 KB, image/png)
2020-05-22 04:17 UTC, Devendra Singh 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:02:55 UTC

Description Devendra Singh 2020-05-22 04:16:13 UTC 
Created attachment 1690934 [details]
repository listed version with-proxy

Description of problem: Repositories are not showing their supportable hardware version properly with http-proxy.


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

How reproducible:
always

Steps to Reproduce:
1. Install satellite 6.8.
2. Add manifest file.
3. Check the recommended repository, the recommended repository show the correct supportable hardware version.   
4- After that configure the HTTP proxy
5- Refresh the manifest file
6- Check the repository again, this time recommended repository show only few supportable hardware versions.

Actual results:
Repositories are not showing their supportable hardware version properly with http-proxy.


Expected results:
The repository should show the proper supportable hardware version with http-proxy.

Additional info:
The problem exists on both IPv4 and IPv6 machines.
Comment 1 Devendra Singh 2020-05-22 04:17:22 UTC 
Created attachment 1690935 [details]
repository listed version without http-proxy
Comment 8 Justin Sherrill 2020-05-26 17:27:58 UTC 
Thanks Devendra!

I did some investigation and from what i can tell this has nothing to do with the http-proxy.  The default db pool size is '5' and i think as part of the changes in dynflow this is now a problem under certain situations.  If you run:

satellite-installer --foreman-db-pool=20

That should increase the pool size.  When i manually adjusted it (now adjusted back), it worked fine.  I've also opened https://projects.theforeman.org/issues/29933  to help make this issue easier to debug, but that is no the fix for this issue.  I think we should increase the default db pool size to something higher.
Comment 10 Justin Sherrill 2020-06-09 15:52:16 UTC 
Moving to the installer as there are a lot of considerations there.
Comment 12 Mike McCune 2020-07-27 20:08:31 UTC 
The error:

"Could not evaluate: Proxy qesatipv668.infra-ipv6-proxy.ipv6.infra.sat.rdu2.redhat.com cannot be retrieved: unknown error (response 502)"

is from:

https://bugzilla.redhat.com/show_bug.cgi?id=1850934

likely, unrelated to this bug.
Comment 14 Justin Sherrill 2020-08-20 18:10:27 UTC 
*** Bug 1867934 has been marked as a duplicate of this bug. ***
Comment 15 Adam Ruzicka 2020-08-27 07:28:11 UTC 
If this is just about the pool running out of connections, then this is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1869812 . Should we keep this open to have it verified separately, just in case there's something else going on in here?
Comment 16 Adam Ruzicka 2020-08-28 11:52:56 UTC 
Upstream fix was merged, moving to POST
Comment 17 Adam Ruzicka 2020-08-29 09:01:08 UTC 
Upstream release 1.4.7 containing fix for this BZ is out, moving to modified.
Comment 18 Lukáš Hellebrandt 2020-09-15 09:35:43 UTC 
Although bug 1869812 (which is a superset of this bug) may not have been fixed, I can't reproduce this issue. With default foreman-db-pool, I always get all the versions of RHEL 7 Server RPMS repository - whether I use proxy or not.

=> Verified with Sat 6.8 snap 14.
Comment 21 errata-xmlrpc 2020-10-27 13:02:42 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 (Important: Satellite 6.8 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.