Bug 1097570

Summary: repoquery tracebacks when fails to open the config file
Product: Red Hat Enterprise Linux 6 Reporter: Karel Srot <ksrot>
Component: yum-utilsAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: low    
Version: 6.5CC: vmukhame
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: 2014-05-14 08:24:42 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 Karel Srot 2014-05-14 06:06:41 UTC 
Description of problem:

$ repoquery -c /tmp/nosuchfile --installed -a
Traceback (most recent call last):
  File "/usr/bin/repoquery", line 1242, in <module>
    main(sys.argv)
  File "/usr/bin/repoquery", line 1150, in main
    repoq.conf
  File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 908, in <lambda>
    conf = property(fget=lambda self: self._getConfig(),
  File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 299, in _getConfig
    startupconf = config.readStartupConfig(fn, root)
  File "/usr/lib/python2.6/site-packages/yum/config.py", line 871, in readStartupConfig
    confpp_obj = ConfigPreProcessor(configfile)
  File "/usr/lib/python2.6/site-packages/yum/parser.py", line 87, in __init__
    fo = self._pushfile( url )
  File "/usr/lib/python2.6/site-packages/yum/parser.py", line 196, in _pushfile
    'Error accessing file for config %s' % (absurl)
yum.Errors.ConfigError: Error accessing file for config file:///tmp/nosuchfile


on RHEL7:
Error accessing file for config file:///tmp/nosuchfile

Version-Release number of selected component (if applicable):
yum-utils-1.1.30-17.el6_5

How reproducible:
always
Comment 1 Valentina Mukhamedzhanova 2014-05-14 08:24:42 UTC 
The patch proposed for bug 1097560 fixes this traceback for me.

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