Bug 811869

Summary: Package Updater crashes - requested datatype primary not available
Product: Red Hat Enterprise Linux 5 Reporter: Andras Gyalai <andras.gyalai>
Component: pirutAssignee: James Antill <james.antill>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.7CC: bkearney
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-15 19:55:48 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:
Attachments:
Description Flags
Crash dump of Package Updater none

Description Andras Gyalai 2012-04-12 07:43:42 UTC
Created attachment 576983 [details]
Crash dump of Package Updater

Description of problem:
Package Updater crashes when starts
Add/Remove Software crashes when starts

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


How reproducible:
Open System Tools -> Package Updater

Steps to Reproduce:
1. Open System Tools -> Package Updater
2.
3.
  
Actual results:

Summary: TBbb3d3620 repoMDObject.py:131:getData:RepoMDError: requested datatype primary not available

Expected results:


Additional info:

Comment 1 James Antill 2013-03-15 19:55:48 UTC
 The repo. you are pointing to seems broken, yum/pirut won't be able to do anything useful until you fix it.

 In theory we could catch this and give a better error experience. but...

This request was evaluated by Red Hat Engineering for inclusion in a Red 
Hat Enterprise Linux maintenance release.

Red Hat does not currently plan to provide this change in a Red Hat 
Enterprise Linux update release for currently deployed products.

With the goal of minimizing risk of change for deployed systems, and in 
response to customer and partner requirements, Red Hat takes a 
conservative approach when evaluating enhancements for inclusion in 
maintenance updates for currently deployed products. The primary 
objectives of update releases are to enable new hardware platform 
support and to resolve critical defects.