RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Also happens for yum-3.2.29-73.el6.noarch

+++ This bug was initially created as a clone of Bug #1281593 +++

Description of problem:
Can upstream commit, 22271bf34e71bbfc75d0a59354fc0108e004f36c, which re-reads yum-fs vars be backported to yum

Version-Release number of selected component (if applicable):yum-3.4.3-125.el7


How reproducible:100%


Steps to Reproduce:
1.
2.
3.

Actual results:
yum fs vars are not read as expected

Expected results:
yum fs vars are read as expected

Additional info:
http://yum.baseurl.org/gitweb?p=yum.git;a=commit;h=22271bf34e71bbfc75d0a59354fc0108e004f36c

...

--- Additional comment from Michal Domonkos on 2016-04-15 11:35:20 CEST ---

Hi Karel,

Previously, yum wouldn't expand fsvars used in include= lines in /etc/yum.conf or repo files.  That's what this commit is fixing.  Here's a reproducer:

# echo debuglevel=10 > /root/foo.conf
# echo foo > /etc/yum/vars/myvar
# echo 'include=/root/$myvar.conf' >> /etc/yum.conf
# yum repolist  # or whichever yum subcommand

Before the patch, yum would terminate with this error message:

CRITICAL:yum.cli:Config error: Error accessing file for config file:///root/$myvar.conf

After the patch, the command (yum repolist in this case) should succeed and the configuration from /root/foo.conf should be applied (being more verbose in this case).

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/