Bug 1321167
Summary: | Kickstarts fails using lazy sync after 10 attempts to fetch a package | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | David Davis <daviddavis> |
Component: | WebUI | Assignee: | David Davis <daviddavis> |
Status: | CLOSED ERRATA | QA Contact: | Lukas Pramuk <lpramuk> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | bbuckingham, cwelton, ehelms, lpramuk, mmccune |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/14361 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-27 09:07:50 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
David Davis
2016-03-24 20:17:44 UTC
It looks like in addition to range_offset_limit, we're also not setting the following option: minimum_object_size 0 kB I wonder if we need to be? Created redmine issue http://projects.theforeman.org/issues/14361 from this bug Upstream bug component is WebUI Regarding minimum_object_size, the default in squid is 0 kB already but since pulp sets it explicitly (it needs to be 0 kB), I'm going to add it to our squid configuration. Upstream PR: https://github.com/Katello/puppet-pulp/pull/137 VERIFIED. @Sat6.2.0-Beta-Snap6 0. new settings are applied: # grep -e range_offset_limit -e minimum_object_size /etc/squid/squid.conf minimum_object_size 0 kB range_offset_limit none 1. synced Red Hat Enterprise Linux 7 Server Kickstart x86_64 7.2 using Download Policy "On Demand" (default) 2. provisioned new host using local libvirt compute resource 3. host OS install finished successfully 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, 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-2016:1500 |