Bug 1838917
| Summary: | Repositories are not showing their available Release versions due to a low default db pool size | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> | ||||||
| Component: | Dynflow | Assignee: | satellite6-bugs <satellite6-bugs> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.8.0 | CC: | aruzicka, ehelms, jsherril, lpramuk, mawerner, mmccune, pcreech, swadeley, zhunting | ||||||
| Target Milestone: | 6.8.0 | Keywords: | Triaged | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| 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
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-10-27 13:02:42 UTC | 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1690935 [details]
repository listed version without http-proxy
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. Moving to the installer as there are a lot of considerations there. 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. *** Bug 1867934 has been marked as a duplicate of this bug. *** 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? Upstream fix was merged, moving to POST Upstream release 1.4.7 containing fix for this BZ is out, moving to modified. 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. 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 |
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.