Bug 949992

Summary: Anaconda fails if groups.xml is compressed.
Product: Red Hat Enterprise Linux 6 Reporter: James Findley <james.findley>
Component: anaconda-yum-pluginsAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: dgregor
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: 2013-10-07 01:43:09 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:
Bug Depends On:    
Bug Blocks: 1002711    
Attachments:
Description Flags
Patch to fix whiteout.py and blacklist.py none

Description James Findley 2013-04-09 12:38:59 UTC
Created attachment 733201 [details]
Patch to fix whiteout.py and blacklist.py

Description of problem:

If you use a repo during installation (even if you dont install any packages from this repo) where groups.xml is gzipped, the whiteout.py and blacklist.py yum plugins cause anaconda to crash, as they do not handle compressed metadata.

Yum in general handles this fine - it's just these two plugins that fail.

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

anaconda-13.21.195-1.el6

How reproducible:

Always


Steps to Reproduce:
1. Create a valid repo using compressed metadata that contains package groups.
2. Verify that groups.xml is gzipped
3. Use this repo within anaconda
  
Actual results:

Anaconda produces an error with a stack trace.


Expected results:

Anaconda works fine.


Additional info:

I've attached a patch for whiteout.py - blacklist.py needs the same changes applied.

Comment 3 Andrius Benokraitis 2013-10-07 01:43:09 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6, and will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.