Bug 1317864

Summary:	Anaconda tries to install partly downloaded rpm-package
Product:	Red Hat Enterprise Linux 5	Reporter:	Gennadii Altukhov <galtukho>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	5.11	CC:	hartsjc
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-18 21:55:00 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 Gennadii Altukhov 2016-03-15 11:49:57 UTC

Description of problem:
Original bug 1302072. When our customers kickstarting RHEL 5 via Satellite Proxy 5, a kickstarted system doesn't boot. The problem is Proxy returns only part of rpm-packages and Anaconda tries to install this package. After installation finished, I can see an error in install.log:

Installing kernel-2.6.18-398.el5.x86_64
error: unpacking of archive failed on file /boot/vmlinuz-2.6.18-398.el5;56495c6d: cpio: read

the same maybe for different packages.
if I download package with curl I can see an error:

curl: (18) transfer closed with 20755079 bytes remaining to read

Actually the same error for Anaconda on RHEL 6, but in case of RHEL 6 it tries to download a package again. in anaconda.log I can see:
15:28:04,440 WARNING : Try 1/10 for http://dhcp131-19.brq.redhat.com/ty/6BGjRC8Z/Packages/man-pages-3.22-20.el6.noarch.rpm failed: [Errno 14] PYCURL ERROR 18 - "transfer closed with 3023108 bytes remaining to read"
15:28:04,695 WARNING : Failed to get http://dhcp131-19.brq.redhat.com/ty/6BGjRC8Z/Packages/man-pages-3.22-20.el6.noarch.rpm from mirror 1/1, or downloaded file is corrupt
15:28:04,697 WARNING : package download failure, retrying automatically


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

How reproducible:
100%

Steps to Reproduce:
I reproduce this bug the way described in bug 1302072.
The squid version of 3.1.23-9.el6 on RHEL 6 does not let us download package completely if we made Range request for the same package before.
(In case of Anaconda, it downloads rpm header first with Range request).

Actual results:
Installed system doesn't boot

Expected results:
Anaconda checks package and tries to download it again.

Comment 1 Brian Lane 2016-03-18 00:26:14 UTC

Sure sounds like a squid problem and not something that Anaconda can fix.

Comment 2 Gennadii Altukhov 2016-03-18 12:31:15 UTC

(In reply to Brian Lane from comment #1)
> Sure sounds like a squid problem and not something that Anaconda can fix.

Hello, Brian.

Anaconda tries to install cut package. There is a problem. I believe Anaconda version of 11.1.2.263 should do verification of a package the same way as Anaconda version of 13.21.239 does.

There is no difference who cut a package proxy/web-server/or-something-else.

Comment 3 Chris Williams 2017-04-18 21:55:00 UTC

Red Hat Enterprise Linux 5 shipped it's last minor release, 5.11, on September 14th, 2014. On March 31st, 2017 RHEL 5 exited Production Phase 3 and entered Extended Life Phase. For RHEL releases in the Extended Life Phase, Red Hat  will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only.  If the customer purchases the Extended Life-cycle Support (ELS), certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release will be provided.  For more details please consult the Red Hat Enterprise Linux Life Cycle Page:
https://access.redhat.com/support/policy/updates/errata

This BZ does not appear to meet ELS criteria so is being closed WONTFIX. If this BZ is critical for your environment and you have an Extended Life-cycle Support Add-on entitlement, please open a case in the Red Hat Customer Portal, https://access.redhat.com ,provide a thorough business justification and ask that the BZ be re-opened for consideration of an errata. Please note, only certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release can be considered.