Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 875106

Summary: rhn_check writes "Fatal error in Python code occured" , when repository metadata doesn't exist
Product: [Community] Spacewalk Reporter: Pavel Studeník <pstudeni>
Component: ClientsAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.6   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-07 13:34:38 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: 1484117    

Description Pavel Studeník 2012-11-09 14:47:45 UTC
Description of problem:
I created new channel with packages. If I installed some package from this channel before event, when metadata was generated by taskomatic,  I got Error "local action status: ((6,), 'Fatal error in Python code occured', {})"

Version-Release number of selected component (if applicable):
yum-rhn-plugin-0.9.1-40.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. create channel with packages
2. install new package from this channel  (before  taskomatic create repository metadata)
3. rhn_check -vv
  
Actual results:
>> tail /var/log/up2date | grep -i "error"

    raise Errors.RepoError, msg
<class 'yum.Errors.RepoError'>: Cannot retrieve repository metadata (repomd.xml) for repository: test1352470635. Please verify its path and try again
up2date D: local action status: ((6,), 'Fatal error in Python code occured', {})


Expected results:
Better message than Fatal error

Comment 1 Milan Zázrivec 2012-12-07 13:34:38 UTC

*** This bug has been marked as a duplicate of bug 495792 ***

Comment 2 Eric Herget 2017-09-28 17:57:11 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.