Bug 2033853
Summary: | Publish content view failed with "PulpRpmClient::ApiError Error message: the server returns an error" | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Hao Chang Yu <hyu> | |
Component: | Pulp | Assignee: | Justin Sherrill <jsherril> | |
Status: | CLOSED ERRATA | QA Contact: | Lai <ltran> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.10.0 | CC: | ahumbe, alsouza, casl, dkliban, gsulliva, iballou, jbhatia, jsherril, jstormshak, kkinge, matthew.lesieur, mjia, mkalyat, patalber, pcreech, pmendezh, pmoravec, pratshar, risantam, saydas, sraut, tharring, wpinheir | |
Target Milestone: | 6.11.0 | Keywords: | Triaged | |
Target Release: | Unused | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | pulpcore-client-3.16.7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2080350 (view as bug list) | Environment: | ||
Last Closed: | 2022-07-05 14:31:10 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: |
Description
Hao Chang Yu
2021-12-18 06:00:46 UTC
Hao, There's a bulk_load_size under Administer > Settings > Content that can be adjusted down from 2000, to 1000 or 500. Does that help? Justin (In reply to Justin Sherrill from comment #2) > Hao, > > There's a bulk_load_size under Administer > Settings > Content that can be > adjusted down from 2000, to 1000 or 500. Does that help? > > Justin Yeah, that seems to help. Thanks. How could I missed that? (In reply to Hao Chang Yu from comment #3) > (In reply to Justin Sherrill from comment #2) > > Hao, > > > > There's a bulk_load_size under Administer > Settings > Content that can be > > adjusted down from 2000, to 1000 or 500. Does that help? > > > > Justin > > Yeah, that seems to help. Thanks. How could I missed that? It seems like you might need to restart the Satellite to take effect? I only test it in foreman-rake console (calling repo.index_content). It seems like after adjusting the value from GUI, the setting doesn't get updated in the console until I exit and re-enter the console Hao, Yes, settings aren't reloaded in the console automatically, but are reloaded on every api request. So you shouldn't need to restart the server, but would need to restart the console. Justin FYI, This is affecting Satellite 7.0 (Beta) as well. Even if I have different sync plans for different products scheduled to be executed 2 or 3 hours apart from each other, atleast two Big repos fail to sync and the error is at the IndexContent step only. Yes, we're gonna take a look at this. I believe the timeout is actually 60 seconds, which is lower than intended. Connecting redmine issue https://projects.theforeman.org/issues/34411 from this bug After some investigation, this is a bit more complicated than i had thought. After making the proper change in katello: https://github.com/Katello/katello/pull/9930 I discovered that there is a bug in the pulp bindings. This is fixed upstream: https://github.com/OpenAPITools/openapi-generator/commit/0eb7189faea45cd83384119cbfd7180909066ead But to fix it in our pulp bindings would require all the ruby bindings to be rebuilt as well. Moving to the pulp component to figure that out. Due to this, i'm suggesting we remove this from 6.9.z, since there is a workaround for migrations and the complexity to achieving this in those old version is probably fairly high. Upstream bug assigned to jsherril Upstream bug assigned to jsherril *** Bug 2052333 has been marked as a duplicate of this bug. *** Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34411 has been resolved. The timeout setting was exposed in pulp-rpm-client 3.14.14. Moving to post, but keep in mind this needs a katello cherry pick AND rubygem-pulp-rpm-client 3.14.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 (Moderate: Satellite 6.11 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-2022:5498 |