Bug 1389816 - [RFE] Add repository name to yum-cron error message
Summary: [RFE] Add repository name to yum-cron error message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum
Version: 7.2
Hardware: Unspecified
OS: Linux
high
low
Target Milestone: rc
: ---
Assignee: Michal Domonkos
QA Contact: Jan Blazek
Lenka Kimlickova
URL:
Whiteboard:
Depends On:
Blocks: 1393866 1420802
TreeView+ depends on / blocked
 
Reported: 2016-10-28 18:29 UTC by Ashlee Burch
Modified: 2020-09-10 09:54 UTC (History)
5 users (show)

Fixed In Version: yum-3.4.3-151.el7
Doc Type: Release Note
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Clone Of:
: 1420802 (view as bug list)
Environment:
Last Closed: 2017-08-01 09:07:52 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2295 0 normal SHIPPED_LIVE yum bug fix and enhancement update 2017-08-01 12:40:03 UTC

Comment 2 Pat Riehecky 2016-10-31 15:15:50 UTC
/usr/lib/python2.7/site-packages/yum/yumRepo.py
    def _groupCheckDataMDNewer(self):
        """ We check the timestamps, if any of the timestamps for the
            "new" data is older than what we have ... we revert. """

        if 'old_repo_XML' not in self._oldRepoMDData:
            return True
        old_repo_XML = self._oldRepoMDData['old_repo_XML']

        if (self.timestamp_check and
            old_repo_XML.timestamp > self.repoXML.timestamp):
            logger.warning("Not using downloaded repomd.xml because it is "
                           "older than what we have:\n"
                           "  Current   : %s\n  Downloaded: %s" %
                           (time.ctime(old_repo_XML.timestamp),
                            time.ctime(self.repoXML.timestamp)))
            return False
        return True

Comment 11 errata-xmlrpc 2017-08-01 09:07:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2295


Note You need to log in before you can comment on or make changes to this bug.