repoDirector.py, initRepoDirector() contains the following block: # bz #158256 (allow up2date to continue if yum repomd support isnt found) try: from repoBackends import repomdRepo repomdRepo.register(rd) except ImportError: log = up2dateLog.initLog() log.log_me("Unable to import repomd support so repomd support will not be available") Since users generally don't have yum installed on RHEL3, there is no yum python module and users are seeing this message every time up2date is started.
Blocking rhnupr4u4 and rhnupr3u8 to track the progress of the release
Moving bugs to the CanFix List
This bug has been fixed in this release
The two files changed to fix this bug were in /usr/share/rhn/up2date_client: sourcesConfig.py: Added a configHasRepomd() method. when supplied with a list of sources it will return 1 or 0 depending on if at least one of the sources is a repomd source. repoDirector.py: Load the list of sources and only try to import the repomd backend if at least one of the sources is a repomd source.
How to reproduce the problem: Install an old version of up2date on an x86_64 box, and run up2date --showall and tail -f /var/log/up2date: [Mon May 15 16:56:43 2006] up2date updating login info [Mon May 15 16:56:43 2006] up2date logging into up2date server [Mon May 15 16:56:44 2006] up2date successfully retrieved authentication token from up2date server [Mon May 15 16:56:44 2006] up2date availablePackageList from network [Mon May 15 16:56:44 2006] up2date Unable to import repomd support so repomd support will not be available Verified the fix on i386 and ia64 using up2date-4.4.69-8 (requires rhnlib-1.8.7-1): [Mon May 15 16:48:18 2006] up2date updating login info [Mon May 15 16:48:18 2006] up2date logging into up2date server [Mon May 15 16:48:19 2006] up2date successfully retrieved authentication token from up2date server [Mon May 15 16:48:19 2006] up2date availablePackageList from network [Mon May 15 16:57:03 2006] up2date updating login info [Mon May 15 16:57:03 2006] up2date logging into up2date server [Mon May 15 16:57:03 2006] up2date successfully retrieved authentication token from up2date server [Mon May 15 16:57:03 2006] up2date availablePackageList from network Seems it doesn't really matter if there is yum repo stuff in /etc/sysconfig/rhn/sources or not, the repomd error message no longer appears in /var/log/up2date. Regression tested the sources file: up2date VMware-console says "package not found" when no yum repos are listed in sources. up2date VMware-console gives a different error message (404) when yum repos are listed in sources. This at least proves the yum stuff is being read from the sources file and no repomd errors are showing up in /var/log/up2date.
And I tried up2date VMware-console via yum again and it worked. No 404.
I'm seeing the same error about repomd support in up2date logs on RHEL 3 Update 7 systems; there is an open bug for this as 173492. Would it be possible to update the RHEL 3 up2date with this fix?
*** Bug 173492 has been marked as a duplicate of this bug. ***
(In reply to comment #15) > I'm seeing the same error about repomd support in up2date logs on RHEL 3 Update > 7 systems; there is an open bug for this as 173492. Would it be possible to > update the RHEL 3 up2date with this fix? This fix should be in the next updates for RHEL 3 and RHEL 4.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0465.html