Red Hat Bugzilla – Bug 1321167
Kickstarts fails using lazy sync after 10 attempts to fetch a package
Last modified: 2016-07-27 05:07:50 EDT
Description of problem: It looks like we missed a setting in our squid.conf that allows anaconda to retrieve lazy synced packages: range_offset_limit none Version-Release number of selected component (if applicable): 6.2 snap 5 How reproducible: Not always. Packages can sometimes be fetched if they are saved to the filesystem before anaconda retries a 10th time. Steps to Reproduce: 1. Download a RHEL kickstart via lazy sync 2. Provision a system using this kickstart 3. Actual results: Anaconda fails after 10 attempts to download a package. Expected results: Provisioning succeeds Additional info: We should probably check our generated squid.conf against pulp's documentation and make sure we aren't missing any other settings. http://pulp.readthedocs.org/en/latest/user-guide/deferred-download.html
Related to https://bugzilla.redhat.com/show_bug.cgi?id=1317047
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